error with starting radicale #1464
Replies: 42 comments
-
|
I was getting that too, can't remember how i fixed it :( |
Beta Was this translation helpful? Give feedback.
-
|
for me, after what seemed like a mostly painless upgrade from ubuntu 16.04 lts to 18, radicale was also not working, with similar errors. |
Beta Was this translation helpful? Give feedback.
-
|
@peter33826 the logs you've provided are just from systemd telling radicale stops and systemd tries to restart it. Can you please enable the radicale logging and paste the radicale logs here (https://radicale.org/logging/). |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for comments. I also actived logging. But my logging folder is still empty. |
Beta Was this translation helpful? Give feedback.
-
|
@peter33826 Please take a look at the systemd logs with |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
and
|
Beta Was this translation helpful? Give feedback.
-
|
I had a similar problem and was wondering: Is anyone running Radicale 2.1.10 on Ubuntu 18.04? It was too working fine with executing the After uncommenting After setting |
Beta Was this translation helpful? Give feedback.
-
|
@peter33826 I'm sorry for the late response. I think I can see your problem now. Please remove the You can find an example systemd unit file here: https://radicale.org/setup/ |
Beta Was this translation helpful? Give feedback.
-
|
@mookie- I removed '--daemon' from the 'ExecStart' file, but it did not change anything. Any Ideas what could help? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
This is the output of
● radicale.service - A simple CalDAV (calendar) and CardDAV (contact) server Jan 04 22:36:20 radicale systemd[1]: radicale.service: Service hold-off time over, scheduling restart. |
Beta Was this translation helpful? Give feedback.
-
|
after a few seconds Radicale crashs: at 964ms it works But after 4s it is down |
Beta Was this translation helpful? Give feedback.
-
|
And how does your |
Beta Was this translation helpful? Give feedback.
-
|
This is my |
Beta Was this translation helpful? Give feedback.
-
|
This is what I have: Some days ago I alredy wrote, what I had to change here to get meaningful error messages. |
Beta Was this translation helpful? Give feedback.
-
|
To the person who asked:
I'm just as confused as everyone else, but I will note that "/var/lib/radicale" is the home directory of the user radicale. I noticed this, because in attempting the test someone else did above changing User=root, the permission denied error I get suddenly changes to: How is it possible that root is getting a permission denied error? |
Beta Was this translation helpful? Give feedback.
-
|
@cianci You error message shows "Read-only file system". Even root can't write to a Read-only file system. |
Beta Was this translation helpful? Give feedback.
-
|
@FBachofner please try this If you configured 0.0.0.0:5253 and radicale isn't listening on this port, then probably your configuration isn't used. |
Beta Was this translation helpful? Give feedback.
-
Perhaps I should have been more specific: In neither case (/root and /var/lib/radicale) is the filesystem mounted read only. The root user can (obviously) write to both of them (when invoked manually by me at cmdline), and the radicale user can create whatever it wants in /var/lib/radicale, also verified by direct testing. In the end, I gave up and added This seems to make it work for now [Shrug]. |
Beta Was this translation helpful? Give feedback.
-
|
@cianci if it works if you manually start it from command line, then it's properly a problem with the systemd unit file configuration. Unfortunately I don't use systemd and can't help you there. But you could try to remove the "optional security settings" and check if it works then. |
Beta Was this translation helpful? Give feedback.
-
|
I had the authors problem on ubuntu 18.10 as well. What solved the problem was adding |
Beta Was this translation helpful? Give feedback.
-
|
I also had the same problem as the author and nothing really worked. I got |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue. The |
Beta Was this translation helpful? Give feedback.
-
|
I am using a different directory to store the collections directory in. My fix is to alter the radicale.service file |
Beta Was this translation helpful? Give feedback.
-
|
For those who would face a similar issue on Ubuntu 23 : the service seems to be failing when it's started for the first time with all optional security settings. In my radicale.service file I commented all the settings below , and the service started fine: Optional security settingsPrivateTmp=trueProtectSystem=strictProtectHome=truePrivateDevices=trueProtectKernelTunables=trueProtectKernelModules=trueProtectControlGroups=trueNoNewPrivileges=trueReadWritePaths=/var/lib/radicale/collections Then I uncommented them one by one to check which one would cause me trouble, everything worked fine even with all of them enabled. That solved it for me ! |
Beta Was this translation helpful? Give feedback.
-
|
@GosuJunk GitHub uses markdown to format your post, please wrap your example in back ticks https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#code-and-syntax-highlighting |
Beta Was this translation helpful? Give feedback.
-
No wonder as you disabled now all "Optional security settings", question would be which particular one is causing issues. |
Beta Was this translation helpful? Give feedback.
-
|
looks like systemd example file should be documented somewhere... |
Beta Was this translation helpful? Give feedback.
-
|
I am on debian, just after upgrading from buster to bookworm and I am now getting this error. |
Beta Was this translation helpful? Give feedback.
-
looks like this update had implicit a major upgrade of "radicale" from 2 to 3, where both options were dropped. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I have problems starting radicale 2.1 automatically on Lubuntu 18.04.
Directly after reboot
systemctl status radicalesays this:But after a few seconds
systemctl status radicalesays this:Does anyone know what could be the reason?
When I run
python3 -m radicale --config "" --storage-filesystem-folder=/var/lib/radicale/collectionsmanually, radicale works fine.Thanks.
Beta Was this translation helpful? Give feedback.
All reactions