[SOLVED] Network bridge fails to start after systemd update

aya · 2014-03-05 15:26:47

Hello,
After rebooting with the upgraded systemd (208-11 -> 210-2) by bridge could not start.

journal

Mar 06 00:08:45 myhost systemd[1]: Job sys-subsystem-net-devices-enp2s0.device/start timed out.
Mar 06 00:08:45 myhost systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp2s0.device.
Mar 06 00:08:45 myhost systemd[1]: Dependency failed for My network bridge with DHCP.
Mar 06 00:08:45 myhost systemd[1]: Starting Network.
Mar 06 00:08:45 myhost systemd[1]: Reached target Network.

# cat /etc/systemd/system/netctl@br0.service 
.include /usr/lib/systemd/system/netctl@.service
[Unit]
Description=My network bridge with DHCP
BindsTo=sys-subsystem-net-devices-enp2s0.device
After=sys-subsystem-net-devices-enp2s0.device

# cat /etc/netctl/br0 
Description="My network bridge with DHCP"
Interface=br0
Connection=bridge
BindsToInterfaces=(enp2s0)
IP=dhcp

Commenting out BindsTo and After in the unit file allows to start the service, but it would still throw an error

Mar 06 00:14:05 myhost systemd[1]: Starting My network bridge with DHCP...
Mar 06 00:14:05 myhost network[732]: Starting network profile 'br0'...
Mar 06 00:14:05 myhost kernel: Bridge firewalling registered
Mar 06 00:14:05 myhost systemd-udevd[739]: Could not apply link config to br0

I never renamed interfaces, it was always the system-assigned enp2s0.

What could have become wrong?

Last edited by aya (2014-03-11 14:31:31)

aya · 2014-03-06 13:25:59

still cannot get it working
if somebody has working service file for bridge, pls. share

starting the service manually after boot also does not work

Mar 06 22:09:10 myhost systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp2s0.device.

though this exists: /sys/class/net/enp2s0/ and the device is up.

Last edited by aya (2014-03-07 01:16:30)

WonderWoofy · 2014-03-06 17:42:00

I don't use netctl for briding, but I do recall seeing the maintainer of netctl appear on these forums to say that this is a known issue with the most recent release of netctl. I think it should be fixed upstream, but I am not sure if it has made it to the repos as of yet.

You should just write out a simple oneshot service file that sets up the bridge for you. It shouldn't be hard to just use bridgectl directly.

Also, please use code tags for things like... code. Otherwise HalosGhost will come slap you with the dead puppies.

HalosGhost · 2014-03-07 00:46:24

WonderWoofy wrote:

Otherwise HalosGhost will come slap you with the dead puppies.

This is less of a joke than you think.

% printf '%s' "every time you post terminal output or code snippets without code tags, someone kicks a kitten"

Live and learn.

All the best,

-HG

Last edited by HalosGhost (2014-03-07 00:46:36)

aya · 2014-03-07 01:16:06

Hi
Thanks for replies.
I don't see any open bugs or recent issues for netctl, but if you mean this one
https://bbs.archlinux.org/viewtopic.php?id=178000
it is a different issue (which I faced as well when I tried to upgrade to netctl 1.5 in hope that it would work)

Surely, a separate service file will work, I just thought that netctl exists to be used and pretty much like it.
Looks like the new systemd just cannot find sys-subsystem-net-devices-enp2s0.device even when the interface is obviously there. I am still to figure this out.
thanks

Last edited by aya (2014-03-07 01:17:38)

mattage · 2014-03-11 13:33:35

Do you happen to run a custom kernel?

I had a similar issue - the latest systemd not generating device units for my hardware. I am on a chromebook and using a chrome kernel. After lots of searching around I found someone with a similar issue (https://bugs.freedesktop.org/show_bug.cgi?id=75512). The solution in that report works, enabling CONFIG_FHANDLE in the Linux kernel. It is now a requirement for the latest systemd.

aya · 2014-03-11 14:31:13

mattage,
Thanks for your comment. It happens that you are right on the money.
I do use a custom kernel and I did not have CONFIG_FHANDLE enabled. I wish it was posted as an announcement or something.
I have now rebuilt the kernel with CONFIG_FHANDLE and the netctl bridge worked as usual.
Thanks
solved

WonderWoofy · 2014-03-11 19:16:30

aya wrote:

I do use a custom kernel and I did not have CONFIG_FHANDLE enabled. I wish it was posted as an announcement or something.

From the 210 release announcement:

systemd 210 announcement wrote:

Heya,
And here's the next release 210:
http://www.freedesktop.org/software/sys … 210.tar.xz
<snip>
Oh, and one reminder that kinda got lost when we announced 209: you have
to enable CONFIG_FHANDLE in your kernel to use systemd >= 209
successfully, otherwise udev won't find any devices.
<snip>

aya · 2014-03-12 01:36:04

I meant on archlinux website or a notification during package installation. Thanks

WonderWoofy · 2014-03-12 02:20:41

IMO, such a message is not necessarily appropriate. To me, if you are rolling a custom kernel, you are kind of on your own. The expectation with the Arch systemd package is that it will be compatible with the Arch kernel. As with anything, customized packages are your responsibility to ensure the compatibility.

Arch Linux

#1 2014-03-05 15:26:47

[SOLVED] Network bridge fails to start after systemd update

#2 2014-03-06 13:25:59

Re: [SOLVED] Network bridge fails to start after systemd update

#3 2014-03-06 17:42:00

Re: [SOLVED] Network bridge fails to start after systemd update

#4 2014-03-07 00:46:24

Re: [SOLVED] Network bridge fails to start after systemd update

#5 2014-03-07 01:16:06

Re: [SOLVED] Network bridge fails to start after systemd update

#6 2014-03-11 13:33:35

Re: [SOLVED] Network bridge fails to start after systemd update

#7 2014-03-11 14:31:13

Re: [SOLVED] Network bridge fails to start after systemd update

#8 2014-03-11 19:16:30

Re: [SOLVED] Network bridge fails to start after systemd update

#9 2014-03-12 01:36:04

Re: [SOLVED] Network bridge fails to start after systemd update

#10 2014-03-12 02:20:41

Re: [SOLVED] Network bridge fails to start after systemd update

Board footer