![]() It may be that nginx cant start after reboot, because of the start order? Tried to add a resolver: resolver IP valid=30s rvice: Failed with result 'exit-code'.įailed to start A high performance web server and a reverse proxy server. rvice: Control process exited, code=exited, status=1/FAILURE Nginx: configuration file /etc/nginx/nf test failed The syslogs show some errors for nginx after reboot: nginx: host not found in upstream "in /etc/nginx/sites-enabled/default:100 I still have no clue why nginx does not start.Īfter every shutdown -r (I use this to test reboot) I check with sudo service -status-all and nginx is not running. You can also use systemctl edit nginx to create the file. Which you place as the file /etc/systemd/system//nf (creating the directory if it doesn't exist). Server_name ssl_certificate /var/wwwssl/example.pem ĭo that with a systemd drop-in: ![]() I also tried: /etc/init.d/nginx sudo service nginx reload It works for forever, but nginx never starts. ![]() Here is my current crontab: root /etc/init.d/nginx /usr/local/bin/forever start /var/www/rtc/index.js I am using crontab to start some services after a reboot.
0 Comments
Leave a Reply. |