All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
VestaCP-nginx.service failed Email Alert
on one of my freshly installed AWS-T2 Debian 8 VestaCP instance, I'm getting Email alerts from VestaCP saying:
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful Job for nginx.service failed. See 'systemctl status nginx.service' and 'journalctl -xn' for details.
Funny thing is... Nginx seems to running fine... serving all my sites fine! It hasn't restarted at all.
Any pointers what may be causing this alert to be sent ? I did post on Vesta Forums... yet to receive a reply.
As suggested in the alert, I ran the
systemctl status nginx.service ● nginx.service - LSB: Stop/start nginx Loaded: loaded (/etc/init.d/nginx) Active: active (running) since Mon 2016-07-25 17:24:22 EDT; 3 days ago CGroup: /system.slice/nginx.service ├─6768 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf ├─6769 nginx: worker process ├─6770 nginx: worker process └─6771 nginx: cache manager process
Then
srv$:# journalctl -xn -- Logs begin at Wed 2016-07-20 15:53:32 EDT, end at Fri 2016-07-29 03:25:01 EDT. -- Jul 29 03:25:01 srv$ CRON[26447]: pam_unix(cron:session): session opened for user admin by (uid=0) Jul 29 03:25:01 srv$ CRON[26448]: pam_unix(cron:session): session opened for user admin by (uid=0) Jul 29 03:25:01 srv$ CRON[26449]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-rrd) Jul 29 03:25:01 srv$ CRON[26451]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue backup) Jul 29 03:25:01 srv$ sudo[26450]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 29 03:25:01 srv$ sudo[26452]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 29 03:25:01 srv$ sudo[26452]: pam_unix(sudo:session): session closed for user root Jul 29 03:25:01 srv$ CRON[26448]: pam_unix(cron:session): session closed for user admin Jul 29 03:25:01 srv$ sudo[26450]: pam_unix(sudo:session): session closed for user root Jul 29 03:25:01 srv$ CRON[26447]: pam_unix(cron:session): session closed for user admin
and then I goto check exactly when the alert was sent.
srv$:# journalctl --since "8.5 hour ago" -- Logs begin at Wed 2016-07-20 15:53:32 EDT, end at Fri 2016-07-29 03:30:02 EDT. -- Jul 28 19:05:01 srv$ CRON[19341]: pam_unix(cron:session): session opened for user admin by (uid=0) Jul 28 19:05:01 srv$ CRON[19342]: pam_unix(cron:session): session opened for user admin by (uid=0) Jul 28 19:05:01 srv$ CRON[19343]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-rrd) Jul 28 19:05:01 srv$ CRON[19344]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue backup) Jul 28 19:05:01 srv$ sudo[19346]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 28 19:05:01 srv$ sudo[19345]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 28 19:05:01 srv$ sudo[19345]: pam_unix(sudo:session): session closed for user root Jul 28 19:05:01 srv$ CRON[19342]: pam_unix(cron:session): session closed for user admin Jul 28 19:05:01 srv$ sudo[19346]: pam_unix(sudo:session): session closed for user root Jul 28 19:05:01 srv$ CRON[19341]: pam_unix(cron:session): session closed for user admin Jul 28 19:09:01 srv$ CRON[19818]: pam_unix(cron:session): session opened for user root by (uid=0) Jul 28 19:09:01 srv$ CRON[19819]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean) Jul 28 19:09:01 srv$ CRON[19818]: pam_unix(cron:session): session closed for user root Jul 28 19:10:01 srv$ CRON[19945]: pam_unix(cron:session): session opened for user admin by (uid=0) Jul 28 19:10:01 srv$ CRON[19944]: pam_unix(cron:session): session opened for user admin by (uid=0) Jul 28 19:10:01 srv$ CRON[19946]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue backup) Jul 28 19:10:01 srv$ CRON[19947]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-rrd) Jul 28 19:10:01 srv$ sudo[19948]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 28 19:10:01 srv$ sudo[19949]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 28 19:10:01 srv$ sudo[19948]: pam_unix(sudo:session): session closed for user root Jul 28 19:10:01 srv$ CRON[19945]: pam_unix(cron:session): session closed for user admin Jul 28 19:10:01 srv$ sudo[19949]: pam_unix(sudo:session): session closed for user root Jul 28 19:10:01 srv$ CRON[19944]: pam_unix(cron:session): session closed for user admin Jul 28 19:15:01 srv$ CRON[20656]: pam_unix(cron:session): session opened for user admin by (uid=0) Jul 28 19:15:01 srv$ CRON[20657]: pam_unix(cron:session): session opened for user admin by (uid=0) Jul 28 19:15:01 srv$ CRON[20658]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue backup) Jul 28 19:15:01 srv$ CRON[20659]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-rrd) Jul 28 19:15:01 srv$ sudo[20660]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 28 19:15:01 srv$ sudo[20661]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 28 19:15:01 srv$ sudo[20661]: pam_unix(sudo:session): session closed for user root Jul 28 19:15:01 srv$ CRON[20657]: pam_unix(cron:session): session closed for user admin Jul 28 19:15:02 srv$ sudo[20660]: pam_unix(sudo:session): session closed for user root Jul 28 19:15:02 srv$ CRON[20656]: pam_unix(cron:session): session closed for user admin Jul 28 19:17:01 srv$ CRON[20974]: pam_unix(cron:session): session opened for user root by (uid=0) Jul 28 19:17:01 srv$ CRON[20975]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jul 28 19:17:01 srv$ CRON[20974]: pam_unix(cron:session): session closed for user root Jul 28 19:20:01 srv$ CRON[21284]: pam_unix(cron:session): session opened for user admin by (uid=0) Jul 28 19:20:01 srv$ CRON[21283]: pam_unix(cron:session): session opened for user admin by (uid=0) Jul 28 19:20:01 srv$ CRON[21285]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-rrd)
Comments
Please run nginx -t and post the outut
Edit...ignore this
if you get those alerts by mail, it is probably one of the cron-tasks running/causing this, so I'd also try matching the timestamp of that mail with the log-entries like your last quote suggests. yet your nginx was running since monday, so probably that cronjob tried to restart but wasn't even able to stop it in first place.
may be try to issue a nginx restart by hand and make sure there are no old/stuck ningx-child left over.
on a sidenote: I did run into troubles after upgrading some VMs running vesta to their newest version. seems like they did some bigger changes on their shell-scripts which may break things at least if you are upgrading... in detail I experienced problems with rewriting apache/fcgi-wrapper config as they switched from absolute to relative paths at some places so it seems.
Vesta's current release was rushed out to fix a security vulnerability and is super duper buggy. New installs are a total crapshoot. I'd highly suggest staying away until the next release.