After update to 1.7.0 - v-update-letsencrypt-ssl - nginx restart failed

Community Support Web
1

greetings,

i had a bunch of hestia servers successfully update from 1.6.14 to 1.7.0 today, but they have all sent me error emails afterwards.

first e-mail is the successful upgrade from 1.6.14 to 1.7.0

second e-mail is from Cron with subject: sudo /usr/local/hestia/bin/v-update-letsencrypt-ssl
content of e-mail is:
Error: nginx restart failed

third e-mail is from Hestia Control Panel with subject: (name of server): nginx restart failed
content of e-mail is:
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

the servers appear alive and the websites appear to be running.
i assume the issue is related to letsencrypt renew checks after the server has updated.

what is the problem and what remediation do we need to take?

cheers, wizdude.

2

Same emails in the same order Update 1.7 at 2:07 AM Two error emails at 7:14 AM

3
4

nano /usr/local/hestia/conf/hestia.conf
Set DEBUG_MODE=“true”
And try to trigger the error again…

And hopefully it will log what went wrong…

5

same here. the next day after hesticp updates to 1.7.0.

I looked at /var/log/syslog and it shows the nginx stopping failing. But then log entries show a successful stop and restart. If it happens again tomorrow, I’ll dig deeper.

6

Same error here, but everything works fine.

Best regards
Tom

/var/log/syslog:

Mar 24 03:22:04 mx10 systemd[1]: Reloading nginx - high performance web server.
Mar 24 03:22:04 mx10 sh[31361]: Usage:
Mar 24 03:22:04 mx10 sh[31361]: kill [options] […]
Mar 24 03:22:04 mx10 sh[31361]: Options:
Mar 24 03:22:04 mx10 sh[31361]: […] send signal to every listed
Mar 24 03:22:04 mx10 sh[31361]: -, -s, --signal
Mar 24 03:22:04 mx10 sh[31361]: specify the to be sent
Mar 24 03:22:04 mx10 sh[31361]: -l, --list=[] list all signal names, or convert one to a name
Mar 24 03:22:04 mx10 sh[31361]: -L, --table list all signal names in a nice table
Mar 24 03:22:04 mx10 sh[31361]: -h, --help display this help and exit
Mar 24 03:22:04 mx10 sh[31361]: -V, --version output version information and exit
Mar 24 03:22:04 mx10 sh[31361]: For more details see kill(1).
Mar 24 03:22:04 mx10 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 24 03:22:04 mx10 systemd[1]: Reload failed for nginx - high performance web server.
Mar 24 03:22:04 mx10 systemd[1]: Stopping nginx - high performance web server…
Mar 24 03:22:04 mx10 sh[31378]: Usage:
Mar 24 03:22:04 mx10 sh[31378]: kill [options] […]
Mar 24 03:22:04 mx10 sh[31378]: Options:
Mar 24 03:22:04 mx10 sh[31378]: […] send signal to every listed
Mar 24 03:22:04 mx10 sh[31378]: -, -s, --signal
Mar 24 03:22:04 mx10 sh[31378]: specify the to be sent
Mar 24 03:22:04 mx10 sh[31378]: -l, --list=[] list all signal names, or convert one to a name
Mar 24 03:22:04 mx10 sh[31378]: -L, --table list all signal names in a nice table
Mar 24 03:22:04 mx10 sh[31378]: -h, --help display this help and exit
Mar 24 03:22:04 mx10 sh[31378]: -V, --version output version information and exit
Mar 24 03:22:04 mx10 sh[31378]: For more details see kill(1).
Mar 24 03:22:04 mx10 systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 24 03:22:04 mx10 systemd[1]: nginx.service: Failed with result ‘exit-code’.
Mar 24 03:22:04 mx10 systemd[1]: Stopped nginx - high performance web server.
Mar 24 03:22:04 mx10 systemd[1]: Starting nginx - high performance web server…
Mar 24 03:22:04 mx10 systemd[1]: Started nginx - high performance web server.

7

we cant reproduce the error until now, maybe save to ignore - we still try to reproduce.