Description of problem: radicale starts before network initialization is complete
Version-Release number of selected component (if applicable):
How reproducible: Configure radicale to listen on explicit static interface address.
Steps to Reproduce:
1. reboot system
Actual results: radicale silently fails to start.
Expected results: radicale starts
Additional info: This is a generic problem with all services binding to explicit interface addresses and depending on network.target only. network.target does not make sure that all statically configured interfaces are up. Onle network-online.target does that. Therefore the solution for all configurable services not supporting IP_FREEBIND is to change the dependency
from network.target to a depedency on network-online.target:
Other network services are affected as well so this bug report is only one in a row.
I'm not sure if it's a good idea to add those dependencies. Many systems will be configured binding to 0.0.0.0, and if an administrator wants to bind to an explicit IP, he should also add those dependencies to /etc/systemd/system/radicale.service
Maybe it will be better to add a readme explaining this problem.
The problem is that the service settings are not safe.
You have the choice between fast and safe. The default settings should opt
for being safe. The behaviour that the service is started before the network is up and then fails is surprising, to say the least.
Alternatively the server should use the IP_FREEBIND setsockopt option, in which
case defaulting to network.target is safe again.
(In reply to Juan Orti Alcaine from comment #1)
> I'm not sure if it's a good idea to add those dependencies. Many systems
> will be configured binding to 0.0.0.0, and if an administrator wants to bind
> to an explicit IP, he should also add those dependencies to
IP_FREEBIND is a much better solution than forcing the user to reconfigure systemd whenever he wants the service to listen on a specific IP.
radicale-0.8-10.fc20 has been submitted as an update for Fedora 20.
* 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.8-10.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
radicale-0.8-10.fc20 works for me.
radicale-0.8-10.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.