[Freedombox-discuss] uwsgi service masked, radicale not working, bepasty seems ok.
Sunil Mohan Adapa
sunil at medhas.org
Thu Apr 2 21:41:01 BST 2026
Hello,
A future version of systemd (already in testing/unstable) does not
support init.d scripts anymore. So, we migrated away from
'uwsgi.service', which is backed by /etc/init.d/uwsgi script, to
uwsgi-app at .socket systemd unit. Accordingly, FreedomBox disables and
masks the old init.d script 'uwsgi.service'. It configures and starts
'uwsgi-app at radicale.socket' and 'uwsgi-app at bepasty-freedombox.socket'.
These two socket files inturn start 'uwsgi-app at radicale.service' and
'uwsgi-app at bepasty-freedombox.service' whenever they are needed. So,
please do not start 'radicale.service' or 'uwsgi.service'. I have
tested the automatic migration from older setup to newer setup. Sorry
to hear that you ran into a problem with radicale.
To debug your problem, please run the following commands:
systemctl status uwsgi-app at bepasty-freedombox.socket
systemctl status uwsgi-app at radicale.socket
Also, you can view the logs with
journalctl -u uwsgi-app at bepasty-freedombox.socket -u
uwsgi-app at bepasty-freedombox.service
journalctl -u uwsgi-app at radicale.socket -u uwsgi-app at radicale.service
--
Sunil
On 4/2/26 12:21, A. F. Cano via Freedombox-discuss wrote:
>
> The 2 new errrors are:
>
> bepasty:
>
> Service uwsgi-app at bepasty-freedombox.socket is running failed
>
> Radicale:
>
> Service uwsgi-app at radicale.socket is running failed
>
> Attempt to repair takes a while but doesn't fix it. After the repair is
> done it says "Service Radicale is not running." and "Service bepasty is
> not running."
>
> Bepasty seems to run ok even though it has this diagnostic error.
> Radicale is not working. Syncing the phone fails with soft errors.
>
> $ sudo systemctl status radicale
> ● radicale.service - A simple CalDAV (calendar) and CardDAV (contact) server
> Loaded: loaded (/usr/lib/systemd/system/radicale.service; disabled; preset: enabled)
> Active: active (running) since Sun 2026-03-29 15:28:12 EDT; 3 days ago
> Invocation: 56cc0f74b3424429b3231e827da828f1
> Docs: man:radicale(1)
> Main PID: 1166660 (radicale)
> Tasks: 1 (limit: 4618)
> Memory: 320K (peak: 24.3M, swap: 18.4M, swap peak: 18.4M)
> CPU: 1.401s
> CGroup: /system.slice/radicale.service
> └─1166660 /usr/bin/python3 /usr/bin/radicale
>
> Notice: journal has been rotated since unit was started, output may be incomplete.
>
> $ sudo systemctl start radicale
>
> Completes without error and subsequent status returns the above.
>
> Is it normal that uwsgi is masked? Should it be running?
>
> Details:
>
> $ sudo systemctl status uwsgi
> × uwsgi.service
> Loaded: masked (Reason: Unit uwsgi.service is masked.)
> Active: failed (Result: exit-code) since Tue 2026-03-31 06:43:25 EDT; 2 days ago
> Duration: 4h 22min 53.718s
> Invocation: dded8ef1b1994fdfac030d45b8ab76da
> Tasks: 21 (limit: 4618)
> Memory: 10.9M (peak: 527.6M, swap: 299.4M, swap peak: 399.2M)
> CPU: 4h 11.178s
> CGroup: /system.slice/uwsgi.service
> ├─ 104924 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searx.ini --daemonize /var/log/uwsgi/app/searx.log
> ├─ 105126 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searx.ini --daemonize /var/log/uwsgi/app/searx.log
> ├─ 105128 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searx.ini --daemonize /var/log/uwsgi/app/searx.log
> ├─ 105129 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searx.ini --daemonize /var/log/uwsgi/app/searx.log
> ├─ 105134 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searx.ini --daemonize /var/log/uwsgi/app/searx.log
> ├─1284637 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/bepasty-freedombox.ini --daemonize /var/log/uwsgi/app/bepasty-freedombox.log
> ├─1284663 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/bepasty-freedombox.ini --daemonize /var/log/uwsgi/app/bepasty-freedombox.log
> ├─1284664 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/bepasty-freedombox.ini --daemonize /var/log/uwsgi/app/bepasty-freedombox.log
> ├─1284722 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/radicale.ini --daemonize /var/log/uwsgi/app/radicale.log
> ├─1284900 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/radicale.ini --daemonize /var/log/uwsgi/app/radicale.log
> ├─1284901 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/radicale.ini --daemonize /var/log/uwsgi/app/radicale.log
> └─1284902 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/radicale.ini --daemonize /var/log/uwsgi/app/radicale.log
>
> Notice: journal has been rotated since unit was started, output may be incomplete.
> $ sudo systemctl start uwsgi
> Failed to start uwsgi.service: Unit uwsgi.service is masked
>
> _______________________________________________
> Freedombox-discuss mailing list
> Freedombox-discuss at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x36C361440C9BC971.asc
Type: application/pgp-keys
Size: 59827 bytes
Desc: OpenPGP public key
URL: <http://alioth-lists.debian.net/pipermail/freedombox-discuss/attachments/20260402/786a3e80/attachment-0001.asc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/freedombox-discuss/attachments/20260402/786a3e80/attachment-0001.sig>
More information about the Freedombox-discuss
mailing list