[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#59515: nginx: Fails to start on boot while upstream service is not y
From: |
Jonathan Brielmaier |
Subject: |
bug#59515: nginx: Fails to start on boot while upstream service is not yet running |
Date: |
Mon, 2 Jan 2023 18:09:26 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 |
On 27.11.22 22:14, Ludovic Courtès wrote:> That looks like a bug in the
radicale service: there’s no
synchronization upon startup:
I think its rather an issue with nscd, networking or some other base
service.
Changing the nginx configuration from
(servers (list "localhost:5232"))
to
(servers (list "127.0.0.1:5232"))
resolves the issue for me :)
It should wait for a PID file or be started as a systemd or inetd
service. That way, we’d be sure that shepherd considers it started once
it’s really listening for input. A quick grep in the source suggests it
creates a PID file somewhere.
I couldn't find any PID file on my server of radicale. But there seems
to by a .lock file: /var/lib/radicale/collections/.Radicale.lock
No idea if that would be helpful...
~Jonathan
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#59515: nginx: Fails to start on boot while upstream service is not yet running,
Jonathan Brielmaier <=