Red Hat Bugzilla – Bug 1001834
mediatomb could not find Ethernet interface at system startup
Last modified: 2013-09-06 21:28:44 EDT
Description of problem:
If mediatomb is enabled via systemctl and started automatically at system boot, there might be a race condition between the NetworkManager and mediatomb. Sometimes when the system is started, mediatomb fails with the messages:
ERROR: Could not determine interface address: Cannot assign requested address
ERROR: Could not find interface: em1
When doing a "systemctl restart mediatomb.service", mediatomb starts normally.
Version-Release number of selected component (if applicable):
On my machine, mediatomb does not start in 9 of 10 times. It depends on how fast the NetworkManager is able to activate the Ethernet interface.
I managed to fix the problem by changing the file
/usr/lib/systemd/system/mediatomb.service. Here, the "After" statement has to be modified:
In addition, the NetworkManager-wait-online.service has to be enabled:
systemctl enable NetworkManager-wait-online.service
If mediatomb is enabled in the original configuration on my machine, the Ethernet interface is generally not enabled at system startup by the Network Manager. In /var/log/messages the following messages appear:
NetworkManager: <warn> (em1): device not up after timeout!
NetworkManager: <info> (em1): deactivating device (reason 'managed')
The Ethernet interface comes up normally at system startup, if mediatomb is not enabled or mediatomb.service is modified as described above.
Instead of NetworkManager-wait-online.service, does network-online.target work, which seems to be enabled by default?
(In reply to Jon Ciesla from comment #1)
> Instead of NetworkManager-wait-online.service, does network-online.target
> work, which seems to be enabled by default?
No, it does not work.
Changing the line from
"After=NetworkManager-wait-online.service" to "After=network-online.target" results in the error messages "ERROR: Could not determine interface address: Cannot assign requested address, ERROR: Could not find interface: em1"
However, I am not sure if network-online.target is really used on my system. I'm using a fresh fc19 installation. The command "systemctl | grep network" only delivers "network.target loaded active active Network"
Hmm. What if you have both After= lines in place? That way it could work whether people are using NetworkManager or the older network service.
(In reply to Jon Ciesla from comment #3)
> Hmm. What if you have both After= lines in place? That way it could work
> whether people are using NetworkManager or the older network service.
If I change the line to "After=NetworkManager-wait-online.service network-online.target" mediatomb is activated. (The NetworkManager-wait-online.service is still enabled)
Ok, cool, I'll get an update out. Thanks!
mediatomb-0.12.1-31.fc19.20120403gitb66dc1 has been submitted as an update for Fedora 19.
mediatomb-0.12.1-31.fc18.20120403gitb66dc1 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mediatomb-0.12.1-31.fc19.20120403gitb66dc1'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
mediatomb-0.12.1-31.fc19.20120403gitb66dc1 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mediatomb-0.12.1-31.fc18.20120403gitb66dc1 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.