Hi Brant, Scalr Server service logs are available in /opt/scalr-server/var/log/service. Typically when these types of errors occur and persist after a reconfigure or service restart, there may be a stuck process preventing the new process from being started correctly. In such a case you should be able to manually kill any stuck Scalr services and then reconfigure or restart these services as expected.
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Saturday, March 11, 2017 at 11:17:36 AM UTC-7, Brant Fortest wrote: > > Hi, Team, > Where can I find service process logs? > I met this problem, want to know more info. Thanks! > > # scalr-server-manage status > crond RUNNING pid 1164, uptime 3 days, > 10:29:09 > httpd RUNNING pid 1143, uptime 3 days, > 10:29:09 > memcached RUNNING pid 1163, uptime 3 days, > 10:29:09 > rrd RUNNING pid 1147, uptime 3 days, > 10:29:09 > service-analytics_poller FATAL Exited too quickly (process > log may have details) > service-analytics_processor FATAL Exited too quickly (process log > may have details) > service-dbqueue FATAL Exited too quickly (process log > may have details) > service-msgsender FATAL Exited too quickly (process log > may have details) > service-plotter RUNNING pid 1159, uptime 3 days, > 10:29:09 > service-poller RUNNING pid 1158, uptime 3 days, > 10:29:09 > service-szrupdater FATAL Exited too quickly (process log > may have details) > zmq_service RUNNING pid 1166, uptime 3 days, > 10:29:09 > > not here, /var/log/scalr/msgsender.log and > /var/log/scalr/SzrMessaging*.log > > Best wishes > Brant > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
