[Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot

[Cesar Mora]

root at spce:~# journalctl -u nginx
Jan 22 10:57:53 spce systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server...
Jan 22 10:57:53 spce nginx[688]: 2025/01/22 10:57:53 [emerg] 688#688: a duplicate listen 127.0.0.1:8081 in /etc/nginx/sites-enabled/nginx>
Jan 22 10:57:53 spce nginx[688]: nginx: configuration file /etc/nginx/nginx.conf test failed
Jan 22 10:57:53 spce systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Jan 22 10:57:53 spce systemd[1]: nginx.service: Failed with result 'exit-code'.
Jan 22 10:57:53 spce systemd[1]: Failed to start nginx.service - A high performance web server and a reverse proxy server.
lines 1-6/6 (END)

> On Jan 22, 2025, at 10:47 AM, Michael Prokop via Spce-user <spce-user at lists.sipwise.com> wrote:
> 
> Hi,
> 
> * Cesar Mora [Wed Jan 22, 2025 at 10:43:00AM -0400]:
> 
>> Syslog shows that nginx will be commanded for start, but later will fail with:
>> 
>> Jan 22 10:12:00 spce systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
>> Jan 22 10:12:00 spce systemd[1]: nginx.service: Failed with result 'exit-code’.
> [...]
>> But nginx does not try to restart...
> 
> The relevant messages should be there *before* those lines.
> But as I wrote in my previous mail, if you don't see why it's
> failing from syslog, enable journald and see what you get there.
> 
> regards
> -mika-
> 
> -- 
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com