cPanel Monitoring failures without reason
I often get a "cPanel Monitoring" alert of two custom services I've installed has failed.
But I do not see any error in the message.
And it is unlikely that two distinct services (varnish and nginx) will not function properly at the same time. **(apache too sometimes)**
45731 45735
Five minutes later I get the alert that the service has been restored successfully.
These failures happen on average every week.
Before setting up the nginx and varnish services under "cPanel Monitoring" I've never had these problems. Varnish and Nginx have always been very stable, with long periods of uptime.
Custom chkserv.d files:
All logs I found about Varnish and Nginx:
I did not find any errors in the logs, It seems that chkserv just restarted the services. What could be happening? I explored all the possibilities I know to debug this error, but I did not get much information.
/etc/chkserv.d/varnish
service[varnish]=x,x,x,service varnish restart,varnishd,varnish/etc/chkserv.d/varnish_ssl
service[varnish_ssl]=x,x,x,service nginx restart,nginx,rootAll logs I found about Varnish and Nginx:
Mar 15 01:35:49 server systemd: Starting The nginx HTTP and reverse proxy server...
Mar 15 01:35:49 server systemd: Starting Varnish Cache, a high-performance HTTP accelerator...
Mar 15 01:35:49 server nginx: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
Mar 15 01:35:49 server nginx: nginx: configuration file /etc/nginx/nginx.conf test is successful
Mar 15 01:35:49 server systemd: Started The nginx HTTP and reverse proxy server.
Mar 15 01:35:50 server systemd: Started Varnish Cache, a high-performance HTTP accelerator.I did not find any errors in the logs, It seems that chkserv just restarted the services. What could be happening? I explored all the possibilities I know to debug this error, but I did not get much information.
-
Hello, This looks related to a similar report on the following thread: SOLVED - upcp killing alternate web server Thank you. 0 -
That's right!! I am relieved to know that the problem has now been resolved. Thank you! 0
Please sign in to leave a comment.
Comments
2 comments