Dear Maintainer,

After upgrading from buster to bullseye,
radicale keeps on restarting (every 90 seconds);
it seems it never leaves the 'start' status,
so i guess the systemd behaviour in such a case is to restart after 90 seconds?

this applies to version in bullseye and bullseye-backports

in practice this means its very hard to sync calendars that take longer than 90 seconds to synchronize,
so not completely unusable, but not trustable what is going to get synced and what not;
in my practice it is unusable (having around 6 entries/day)

# apt policy radicale
radicale:
  Installed: 3.1.5-1~bpo11+1
  Candidate: 3.1.5-1~bpo11+1
  Version table:
 *** 3.1.5-1~bpo11+1 100
        100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
        100 /var/lib/dpkg/status
     3.0.6-3 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages

# journalctl --unit radicale.service --follow
..
Apr 08 08:35:25 vps-2bff47e9 env[19464]: [2022-04-08 08:35:25 +0000] [19464] [INFO] Listening on '[0.0.0.0]:5232' with SSL
Apr 08 08:35:25 vps-2bff47e9 env[19464]: [2022-04-08 08:35:25 +0000] [19464] [INFO] Radicale server ready
Apr 08 08:36:55 vps-2bff47e9 systemd[1]: radicale.service: start operation timed out. Terminating.
Apr 08 08:36:55 vps-2bff47e9 env[19464]: [2022-04-08 08:36:55 +0000] [19464] [INFO] Stopping Radicale
Apr 08 08:36:55 vps-2bff47e9 systemd[1]: radicale.service: Failed with result 'timeout'.
Apr 08 08:36:55 vps-2bff47e9 systemd[1]: Failed to start A simple CalDAV (calendar) and CardDAV (contact) server.
Apr 08 08:36:55 vps-2bff47e9 systemd[1]: radicale.service: Scheduled restart job, restart counter is at 642.
Apr 08 08:36:55 vps-2bff47e9 systemd[1]: Stopped A simple CalDAV (calendar) and CardDAV (contact) server.
Apr 08 08:36:55 vps-2bff47e9 systemd[1]: Starting A simple CalDAV (calendar) and CardDAV (contact) server...
Apr 08 08:36:55 vps-2bff47e9 env[19477]: [2022-04-08 08:36:55 +0000] [19477] [INFO] Loaded default config
Apr 08 08:36:55 vps-2bff47e9 env[19477]: [2022-04-08 08:36:55 +0000] [19477] [INFO] Loaded config file '/etc/radicale/config'
..

# systemctl status radicale.service
● radicale.service - A simple CalDAV (calendar) and CardDAV (contact) server
     Loaded: loaded (/etc/systemd/system/radicale.service; enabled; vendor preset: enabled)
     Active: activating (start) since Fri 2022-04-08 08:36:55 UTC; 1min 6s ago
Cntrl PID: 19477 (python3)
      Tasks: 1 (limit: 2303)
     Memory: 19.4M
        CPU: 772ms
     CGroup: /system.slice/radicale.service
             └─19477 python3 -m radicale

Apr 08 08:36:55 vps-2bff47e9 env[19477]: [2022-04-08 08:36:55 +0000] [19477] [INFO] Loaded default config
Apr 08 08:36:55 vps-2bff47e9 env[19477]: [2022-04-08 08:36:55 +0000] [19477] [INFO] Loaded config file '/etc/radicale/config'
Apr 08 08:36:55 vps-2bff47e9 env[19477]: [2022-04-08 08:36:55 +0000] [19477] [INFO] Skipped missing config file '/var/lib/radicale/.config/radicale/config'
Apr 08 08:36:55 vps-2bff47e9 env[19477]: [2022-04-08 08:36:55 +0000] [19477] [INFO] Starting Radicale
Apr 08 08:36:55 vps-2bff47e9 env[19477]: [2022-04-08 08:36:55 +0000] [19477] [INFO] auth type is 'radicale.auth.htpasswd'
Apr 08 08:36:56 vps-2bff47e9 env[19477]: [2022-04-08 08:36:56 +0000] [19477] [INFO] storage type is 'radicale.storage.multifilesystem'
Apr 08 08:36:56 vps-2bff47e9 env[19477]: [2022-04-08 08:36:56 +0000] [19477] [INFO] rights type is 'radicale.rights.authenticated'
Apr 08 08:36:56 vps-2bff47e9 env[19477]: [2022-04-08 08:36:56 +0000] [19477] [INFO] web type is 'radicale.web.internal'
Apr 08 08:36:56 vps-2bff47e9 env[19477]: [2022-04-08 08:36:56 +0000] [19477] [INFO] Listening on '[0.0.0.0]:5232' with SSL
Apr 08 08:36:56 vps-2bff47e9 env[19477]: [2022-04-08 08:36:56 +0000] [19477] [INFO] Radicale server ready

S.

Hello,

i had the same problem,
changing the service type to simple in
/etc/systemd/system/radicale.service
solved this issue

hth,
Wim

Quoting wim (2022-04-08 12:15:49)

Are you sure you used the default systemd service unit before that edit?


 - Jonas

Hi Steven,

Quoting steven (2022-04-08 10:43:17)

Sorry, I cannot reproduce that - I normally use uwsgi, but have now
tried enable the systemd service unit and it stays running.

Maybe something was carried over from your older system, so that either
system unit or Radicale configuration is unusual?


 - Jonas

[ resent to maybe cheat crap Microsoft blockage at ucll.be ]

Quoting wim (2022-04-08 12:15:49)

Are you sure you used the default systemd service unit before that edit?


 - Jonas

Jonas Smedegaard schreef op vr 08-04-2022 om 13:45 [+0200]:

i don't recall changing it, (but also not 100%sure)
but this is on a debian 9>10>11 machine,
so maybe this is remnant from the dist-upgrade process?

Quoting Wim Bertels (2022-04-08 14:14:29)

I use Midnight Commander where I can simply hit ENTER on the .deb file
downloaded from
https://packages.debian.org/bullseye-backports/all/radicale/download

If you don't use Midnight Commander, then try something like this:

  dpkg-deb -x *.deb newdir

Alternatively, for the systemd service unit file you can try this:

  systemd-delta

...or compare manually with the file here:
https://salsa.debian.org/debian/radicale/-/blob/debian/3.1.5-1_bpo11+1/debian/radicale.service


 - Jonas

[ resent to maybe cheat crap Microsoft blockage at ucll.be ]

Quoting Wim Bertels (2022-04-08 14:14:29)

I use Midnight Commander where I can simply hit ENTER on the .deb file
downloaded from
https://packages.debian.org/bullseye-backports/all/radicale/download

If you don't use Midnight Commander, then try something like this:

  dpkg-deb -x *.deb newdir

Alternatively, for the systemd service unit file you can try this:

  systemd-delta

...or compare manually with the file here:
https://salsa.debian.org/debian/radicale/-/blob/debian/3.1.5-1_bpo11+1/debian/radicale.service


 - Jonas

Jonas Smedegaard schreef op vr 08-04-2022 om 14:38 [+0200]:

interesting:
my service file is different,
so i probably made it myself quite a while ago,
as there does not seem to be a service file in
https://packages.debian.org/buster/all/radicale/download

conclusion:
a upgrade of radicale does not upgrade the service file (or asks to),
(as it was probably expecting none)

hth,
Wim

Quoting Wim Bertels (2022-04-08 15:27:37)
configuration files are "conffiles" and systemd in particular uses
"shadowed configuration" not involving conffiles.

More about conffiles at https://wiki.debian.org/DpkgConffileHandling

Thanks for investigating,

 - Jonas