Closing.
Workaround with using "127.0.0.1" instead of "localhost" provided.
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 (
Jonathan Brielmaier skribis:
> I added `(shepherd-requirement '(radicale))` to my nginx-configuration.
> Sadly the issue is not fixed, the situation is the same as before.
>
> I assume that radicale takes a fracture of a second to start. And nginx
> starts faster up. See this small experiment:
T
Ah thanks.
I added `(shepherd-requirement '(radicale))` to my nginx-configuration.
Sadly the issue is not fixed, the situation is the same as before.
I assume that radicale takes a fracture of a second to start. And nginx
starts faster up. See this small experiment:
$ sudo herd stop radicale
$
nginx-configuration has a 'shepherd-requirement' parameter that can be used here
When I start my personal server with a radicale service behind a nginx
reverse proxy, nginx fails to start.
The relevant part in the log:
Nov 23 16:02:56 localhost shepherd[1]: Service networking has been started.
Nov 23 16:02:56 localhost shepherd[1]: Service radicale has been started.
Nov 23 16
