We are tracking a related issue with diagnostic test what is not effecting the service.

https://salsa.debian.org/freedombox-team/freedombox/-/issues/2571

On 4/2/26 13:41, Sunil Mohan Adapa wrote:
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- [email protected] systemd unit.  Accordingly, FreedomBox disables and masks the old init.d script 'uwsgi.service'.  It configures and starts 'uwsgi- [email protected]' and '[email protected]'. These two socket files inturn start '[email protected]' and 'uwsgi- [email protected]' 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 [email protected]
systemctl status [email protected]

Also, you can view the logs with

journalctl -u [email protected] -u uwsgi-app@bepasty- freedombox.service
journalctl -u [email protected] -u [email protected]


_______________________________________________
Freedombox-discuss mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss

Attachment: OpenPGP_0x36C361440C9BC971.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
Freedombox-discuss mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss

Reply via email to