Description of problem: If radicale crashes, it must be manually restarted. It should restart itself after failure. Version-Release number of selected component (if applicable): radicale-0.8-10.fc20.noarch How reproducible: every time (it crashes) Steps to Reproduce: 1. start radicale systemctl enable radicale.service systemctl start radicale.service 2. kill it (killall ridcale) to simulate a crash 3. watch as all the contacts in your phone disappear when it times out trying to verify they still exist Actual results: radicale, when it's dead, is truely dead and not just pining for the fjords. Expected results: it should spring back to life, a phoenix anew. Additional info: Suggested patch is to add these two lines to the [Service] part of /lib/systemd/system/radicale.service: Restart=always RestartSec=42s I'm not sure why it crashes. An alternative is to fix all the bugs in it. In the meantime, I suggest Restart is a plausible work-around. Thanks.
Why RestartSec=42s? Have you tested if the default 100ms works?
Nothing special about RestartSec=42s, I just copied it from sshd.service. If you know better, please change it.
radicale-0.9-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/radicale-0.9-1.fc20
thanks, looks fixed to me with radicale-0.9-1.fc20
Package radicale-0.9-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing radicale-0.9-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-9470/radicale-0.9-1.fc20 then log in and leave karma (feedback).
radicale-0.9-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.