Originally Posted by cipher7836
The other day the power went down, and the TimeTrex server had to reboot. For some odd reason it didn't start the TimeTrex service. Found out why the service did not start up.
When a service is shut down it'll try to do this as safe as possible making sure any clients are disconnected properly, data is flushed out to disk and the application is stopped like it should. Using an UPS may help allowing for just enough time to shut down properly. Some services may revolt or refuse to start when previously interrupted. If no verbose or debug output (ore related errors) are available from /var/log/messages (see /etc/syslog.conf) you best look for application-specific logging configuration
(also see timetrex.ini.php ?). Reading the log or egrepping it for '-ie "(error|warning|fail|fatal)"' might reveal what went on, else 'tail -F /var/log/postgresql' might show more when you try to restart the app (with or without setting "log_error_verbosity" to verbose ?).
* Since you're new here a short remark about thread titles. Members will often check if they can or want to chip in a reply or answer from looking at a thread title. Your thread title "services" seems to be lacking detail. Basically nobody knows what it's about until they read it. Now your thread is for a specific distribution, a specific service, a specific situation (startup prob) with a specific cause (pwr fail). I hope you see that a thread title like "TimeTrex on Centos: service startup problem due to power failure" or the more terse "TimeTrex startup after power failure" would be way better.