Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1009176: radicale.service: start operation timed out. Terminating.

81 views
Skip to first unread message

steven

unread,
Apr 8, 2022, 4:50:03 AM4/8/22
to
Package: radicale
Version: 3.1.5-1~bpo11+1
Severity: normal
X-Debbugs-Cc: steven....@disroot.org

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.

-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-13-cloud-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages radicale depends on:
ii adduser 3.118
ii init-system-helpers 1.60
ii lsb-base 11.1.0
ii python3 3.9.2-3
ii python3-radicale 3.1.5-1~bpo11+1

Versions of packages radicale recommends:
ii ssl-cert 1.1.0+nmu1

Versions of packages radicale suggests:
ii apache2 2.4.53-1~deb11u1
ii apache2-utils 2.4.53-1~deb11u1
ii libapache2-mod-proxy-uwsgi 2.4.53-1~deb11u1
ii python3-bcrypt 3.1.7-4
ii python3-passlib 1.7.4-1
ii uwsgi 2.0.19.1-7.1
ii uwsgi-plugin-python3 2.0.19.1-7.1

-- Configuration Files:
/etc/radicale/config changed:
[server]
hosts = 0.0.0.0:5232
timeout = 120
ssl = True
certificate = /etc/letsencrypt/live/joe/fullchain.pem
key = /etc/letsencrypt/live/joe/privkey.pem
[encoding]
[auth]
type = htpasswd
htpasswd_filename = /etc/radicale/users
htpasswd_encryption = bcrypt
delay = 3
[rights]
type = authenticated
file = /etc/radicale/rights
[storage]
[web]
[logging]
level = info
mask_passwords = True
[headers]

/etc/radicale/logging changed:
[loggers]
keys = root
[handlers]
keys = console,file
[formatters]
keys = simple
[logger_root]
level = WARNING
handlers = console,file
[handler_console]
class = StreamHandler
args = (sys.stderr,)
formatter = simple
[handler_file]
class = FileHandler
args = ('/var/log/radicale/radicale.log',)
level = INFO
formatter = simple
[formatter_simple]
format = [%(thread)x] %(levelname)s: %(message)s


-- no debconf information

wim

unread,
Apr 8, 2022, 6:20:04 AM4/8/22
to
Package: radicale
Followup-For: Bug #1009176
X-Debbugs-Cc: wim.b...@ucll.be

Hello,

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

hth,
Wim

Jonas Smedegaard

unread,
Apr 8, 2022, 7:30:04 AM4/8/22
to
Quoting wim (2022-04-08 12:15:49)
> i had the same problem,
> changing the service type to simple in
> /etc/systemd/system/radicale.service
> solved this issue

That sounds odd: Default type is documented to be "simple".

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


- Jonas

--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/

[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc

Jonas Smedegaard

unread,
Apr 8, 2022, 7:50:04 AM4/8/22
to
X-Debbugs-Cc: wim.b...@ucll.be

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

Quoting wim (2022-04-08 12:15:49)
> i had the same problem,
> changing the service type to simple in
> /etc/systemd/system/radicale.service
> solved this issue

signature.asc

Jonas Smedegaard

unread,
Apr 8, 2022, 8:40:04 AM4/8/22
to
Quoting Wim Bertels (2022-04-08 14:14:29)
> Jonas Smedegaard schreef op vr 08-04-2022 om 13:45 [+0200]:
> > Quoting wim (2022-04-08 12:15:49)
> > > i had the same problem,
> > > changing the service type to simple in
> > > /etc/systemd/system/radicale.service
> > > solved this issue
> >
> > That sounds odd: Default type is documented to be "simple".
> >
> > Are you sure you used the default systemd service unit before that
> > edit?
>
> 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?

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
signature.asc

Jonas Smedegaard

unread,
Apr 8, 2022, 8:40:04 AM4/8/22
to
X-Debbugs-Cc: wim.b...@ucll.be

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

Quoting Wim Bertels (2022-04-08 14:14:29)
> Jonas Smedegaard schreef op vr 08-04-2022 om 13:45 [+0200]:
> > Quoting wim (2022-04-08 12:15:49)
> > > i had the same problem,
> > > changing the service type to simple in
> > > /etc/systemd/system/radicale.service
> > > solved this issue
> >
> > That sounds odd: Default type is documented to be "simple".
> >
> > Are you sure you used the default systemd service unit before that
> > edit?
>
> 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?

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


signature.asc

Jonas Smedegaard

unread,
Apr 8, 2022, 10:30:03 AM4/8/22
to
X-Debbugs-Cc: wim.b...@ucll.be

Quoting Wim Bertels (2022-04-08 15:27:37)
> Jonas Smedegaard schreef op vr 08-04-2022 om 14:38 [+0200]:
> > 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
>
> 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)

Right: Debian packages warn when "conffiles" change, but not all
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,
signature.asc
0 new messages