Yesterday, I noticed that radicale was inactive on my rockpro64 with freedombox installed on top of Debian 13, so I disabled and re-enabled it.
Today, radicale was inactive again. After I disabled and re-enabled it, it works again. I ran diagnostics, all are successfull.
Did other people have the same situation?
I did not take the time to look at the journal (rather busy now), but I will do it at some point.
Yes, I’m having same issue. Haven’t tried debugging yet. Rebooting only temporarily solves the issue.
The new setup with radicale is such that there is a ‘socket’ unit that always keeps listening for new connections and a ‘service’ unit that may (not verified yet) automatically shutdown when not being used. As soon a new connection arrives on /radicale/ URL, systemd should automatically start the radicale service and pass on the incoming connection. All this work transparently to reduce resource usage when services are not being used. Users should not notice it and for them it appears as if service is always running.
But it looks like things are not working as expected. Since you are able to consistently reproduce the issue after a day, I will try to do the same and find out what’s going wrong.
Yesterday, what made me notice that radicale was not running was a failed diagnostic. Today, it was that I had evolution fail to access radicale. Both times, on the plinth page for radicale, there was a notification that the service was inactive.
We are tracking a bug on why diagnostic test is failing. But evolution failing to access should not happen.
This morning, none of my clients complain so radicale probably works but on the plinth page for radicale, there is the warning message that radicale is not working.