Re: [systemd-devel] failed to change interface name (systemd-networkd)

[Martin Pitt]

Lennart Poettering [2015-10-14 18:15 +0200]:
> My educated guess is that DEbian's ifupdown scripts are responsible for
> this... IIRC they install a unit file that is pulled in on hotplug,
> and might keep the device busy...

Yes, /lib/udev/net.agent. It calls ifup or ifdown if the interface is
configured in /etc/network/interfaces, i. e. with ifupdown. But if it
does not appear in "ifquery -l" the script doesn't touch the
interface.

To be 100% sure you can temporarily move away /lib/udev/net.agent and
see if it still happens?

Thanks,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] failed to change interface name (systemd-networkd)

[Lennart Poettering]

On Wed, 23.09.15 22:17, James (jamesze...@gmail.com) wrote:

> Hello,
> 
> Hoping someone can point me in the right direction. I'm attempting to
> change the interface name (eth0 -> wired) on one of my servers.
> 
> Here's the output from the journal:
> 
> ~# journalctl --no-pager | grep -i wired
> Sep 23 17:11:15 vivid systemd-udevd[399]: error changing net interface
> name 'eth0' to 'wired0': Device or resource busy
> Sep 23 17:11:15 vivid systemd-udevd[399]: could not rename interface
> '2' from 'eth0' to 'wired0': Device or resource busy
> Sep 23 17:11:17 vivid sh[566]: Unknown interface wired0
> Sep 23 17:11:17 vivid systemd[1]: Started ifup for wired0.
> Sep 23 17:11:17 vivid systemd[1]: Starting ifup for wired0...
> 
> Here's what the .link contains:
> 
> # cat 10-ethernet.link
> [Match]
> MACAddress=fa:16:3e:31:7a:4b
> [Link]
> Name=wired0
> MACAddress=fa:15:33:55:33:44
> 
> And the .network:
> 
> # cat 20-ethernet.network
> [Match]
> Name=wired*
> [Network]
> DNS=8.8.8.8
> DNS=8.8.4.4
> [Address]
> Address=10.1.1.190/24
> [Route]
> Destination=0.0.0.0/0
> Gateway=10.1.1.1
> 
> The MAC address of the interface changes properly, so I know that the
> unit is at least being read and parsed.
> 
> As an aside, this is happening on Ubuntu 15.04. I've disabled
> NetworkManager and am relying, obviously, on systemd-networkd and
> systemd-resolved. I've also temporarily disabled dhcpd thinking that
> may have had something to do with the interface being busy, to no
> avail.
> 
> Any thoughts on why the interface is busy resulting in the name change 
> failing?

My educated guess is that DEbian's ifupdown scripts are responsible for
this... IIRC they install a unit file that is pulled in on hotplug,
and might keep the device busy...


Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] failed to change interface name (systemd-networkd)

[Lennart Poettering]

On Thu, 01.10.15 15:09, James (jamesze...@gmail.com) wrote:

> Thanks Kay - that jives with what I was thinking, as well. Is there a
> good way to tell?
> 
> I've used systemd-analyze critical-chain to see if there is something
> being kicked off by systemd before the network scripts can run, but
> alas it appears that none of the systemd units are the culprit here.
> 
> I'm running into this issue on Ubuntu 15.04 (Vivid). If there are any
> pointers on how to best determine the script / root cause I'd be very
> much appreciative.

Consider checking if you hve NM installed, or debian's ifupdown
scripts take possession of it first.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] failed to change interface name (systemd-networkd)

[James]

Hello, just following up to see if there were any ideas on what may be
causing this.

Any thoughts appreciated.

On Wed, Sep 23, 2015 at 10:17 PM, James  wrote:
> Hello,
>
> Hoping someone can point me in the right direction. I'm attempting to
> change the interface name (eth0 -> wired) on one of my servers.
>
> Here's the output from the journal:
>
> ~# journalctl --no-pager | grep -i wired
> Sep 23 17:11:15 vivid systemd-udevd[399]: error changing net interface
> name 'eth0' to 'wired0': Device or resource busy
> Sep 23 17:11:15 vivid systemd-udevd[399]: could not rename interface
> '2' from 'eth0' to 'wired0': Device or resource busy
> Sep 23 17:11:17 vivid sh[566]: Unknown interface wired0
> Sep 23 17:11:17 vivid systemd[1]: Started ifup for wired0.
> Sep 23 17:11:17 vivid systemd[1]: Starting ifup for wired0...
>
> Here's what the .link contains:
>
> # cat 10-ethernet.link
> [Match]
> MACAddress=fa:16:3e:31:7a:4b
> [Link]
> Name=wired0
> MACAddress=fa:15:33:55:33:44
>
> And the .network:
>
> # cat 20-ethernet.network
> [Match]
> Name=wired*
> [Network]
> DNS=8.8.8.8
> DNS=8.8.4.4
> [Address]
> Address=10.1.1.190/24
> [Route]
> Destination=0.0.0.0/0
> Gateway=10.1.1.1
>
> The MAC address of the interface changes properly, so I know that the
> unit is at least being read and parsed.
>
> As an aside, this is happening on Ubuntu 15.04. I've disabled
> NetworkManager and am relying, obviously, on systemd-networkd and
> systemd-resolved. I've also temporarily disabled dhcpd thinking that
> may have had something to do with the interface being busy, to no
> avail.
>
> Any thoughts on why the interface is busy resulting in the name change 
> failing?
>
> Thanks!
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] failed to change interface name (systemd-networkd)

[James]

Thanks Kay - that jives with what I was thinking, as well. Is there a
good way to tell?

I've used systemd-analyze critical-chain to see if there is something
being kicked off by systemd before the network scripts can run, but
alas it appears that none of the systemd units are the culprit here.

I'm running into this issue on Ubuntu 15.04 (Vivid). If there are any
pointers on how to best determine the script / root cause I'd be very
much appreciative.

Thank you.

On Thu, Oct 1, 2015 at 2:31 PM, Kay Sievers  wrote:
> On Thu, Oct 1, 2015 at 7:21 PM, James  wrote:
>> Hello, just following up to see if there were any ideas on what may be
>> causing this.
>>
>> Any thoughts appreciated.
>>
>> On Wed, Sep 23, 2015 at 10:17 PM, James  wrote:
>>> Hello,
>>>
>>> Hoping someone can point me in the right direction. I'm attempting to
>>> change the interface name (eth0 -> wired) on one of my servers.
>>>
>>> Here's the output from the journal:
>>>
>>> ~# journalctl --no-pager | grep -i wired
>>> Sep 23 17:11:15 vivid systemd-udevd[399]: error changing net interface
>>> name 'eth0' to 'wired0': Device or resource busy
>>> Sep 23 17:11:15 vivid systemd-udevd[399]: could not rename interface
>>> '2' from 'eth0' to 'wired0': Device or resource busy
>>> Sep 23 17:11:17 vivid sh[566]: Unknown interface wired0
>>> Sep 23 17:11:17 vivid systemd[1]: Started ifup for wired0.
>>> Sep 23 17:11:17 vivid systemd[1]: Starting ifup for wired0...
>>>
>>> Here's what the .link contains:
>>>
>>> # cat 10-ethernet.link
>>> [Match]
>>> MACAddress=fa:16:3e:31:7a:4b
>>> [Link]
>>> Name=wired0
>>> MACAddress=fa:15:33:55:33:44
>>>
>>> And the .network:
>>>
>>> # cat 20-ethernet.network
>>> [Match]
>>> Name=wired*
>>> [Network]
>>> DNS=8.8.8.8
>>> DNS=8.8.4.4
>>> [Address]
>>> Address=10.1.1.190/24
>>> [Route]
>>> Destination=0.0.0.0/0
>>> Gateway=10.1.1.1
>>>
>>> The MAC address of the interface changes properly, so I know that the
>>> unit is at least being read and parsed.
>>>
>>> As an aside, this is happening on Ubuntu 15.04. I've disabled
>>> NetworkManager and am relying, obviously, on systemd-networkd and
>>> systemd-resolved. I've also temporarily disabled dhcpd thinking that
>>> may have had something to do with the interface being busy, to no
>>> avail.
>>>
>>> Any thoughts on why the interface is busy resulting in the name change 
>>> failing?
>
> Most likely you have some other daemon running, or a script executed
> by udev, or the interface is found by some init script, something that
> brings the interface up before the attempt to rename it by
> udev/networkd.
>
> Kay
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] failed to change interface name (systemd-networkd)

[Kay Sievers]

On Thu, Oct 1, 2015 at 7:21 PM, James  wrote:
> Hello, just following up to see if there were any ideas on what may be
> causing this.
>
> Any thoughts appreciated.
>
> On Wed, Sep 23, 2015 at 10:17 PM, James  wrote:
>> Hello,
>>
>> Hoping someone can point me in the right direction. I'm attempting to
>> change the interface name (eth0 -> wired) on one of my servers.
>>
>> Here's the output from the journal:
>>
>> ~# journalctl --no-pager | grep -i wired
>> Sep 23 17:11:15 vivid systemd-udevd[399]: error changing net interface
>> name 'eth0' to 'wired0': Device or resource busy
>> Sep 23 17:11:15 vivid systemd-udevd[399]: could not rename interface
>> '2' from 'eth0' to 'wired0': Device or resource busy
>> Sep 23 17:11:17 vivid sh[566]: Unknown interface wired0
>> Sep 23 17:11:17 vivid systemd[1]: Started ifup for wired0.
>> Sep 23 17:11:17 vivid systemd[1]: Starting ifup for wired0...
>>
>> Here's what the .link contains:
>>
>> # cat 10-ethernet.link
>> [Match]
>> MACAddress=fa:16:3e:31:7a:4b
>> [Link]
>> Name=wired0
>> MACAddress=fa:15:33:55:33:44
>>
>> And the .network:
>>
>> # cat 20-ethernet.network
>> [Match]
>> Name=wired*
>> [Network]
>> DNS=8.8.8.8
>> DNS=8.8.4.4
>> [Address]
>> Address=10.1.1.190/24
>> [Route]
>> Destination=0.0.0.0/0
>> Gateway=10.1.1.1
>>
>> The MAC address of the interface changes properly, so I know that the
>> unit is at least being read and parsed.
>>
>> As an aside, this is happening on Ubuntu 15.04. I've disabled
>> NetworkManager and am relying, obviously, on systemd-networkd and
>> systemd-resolved. I've also temporarily disabled dhcpd thinking that
>> may have had something to do with the interface being busy, to no
>> avail.
>>
>> Any thoughts on why the interface is busy resulting in the name change 
>> failing?

Most likely you have some other daemon running, or a script executed
by udev, or the interface is found by some init script, something that
brings the interface up before the attempt to rename it by
udev/networkd.

Kay
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] failed to change interface name (systemd-networkd)

[James]

Hello,

Hoping someone can point me in the right direction. I'm attempting to
change the interface name (eth0 -> wired) on one of my servers.

Here's the output from the journal:

~# journalctl --no-pager | grep -i wired
Sep 23 17:11:15 vivid systemd-udevd[399]: error changing net interface
name 'eth0' to 'wired0': Device or resource busy
Sep 23 17:11:15 vivid systemd-udevd[399]: could not rename interface
'2' from 'eth0' to 'wired0': Device or resource busy
Sep 23 17:11:17 vivid sh[566]: Unknown interface wired0
Sep 23 17:11:17 vivid systemd[1]: Started ifup for wired0.
Sep 23 17:11:17 vivid systemd[1]: Starting ifup for wired0...

Here's what the .link contains:

# cat 10-ethernet.link
[Match]
MACAddress=fa:16:3e:31:7a:4b
[Link]
Name=wired0
MACAddress=fa:15:33:55:33:44

And the .network:

# cat 20-ethernet.network
[Match]
Name=wired*
[Network]
DNS=8.8.8.8
DNS=8.8.4.4
[Address]
Address=10.1.1.190/24
[Route]
Destination=0.0.0.0/0
Gateway=10.1.1.1

The MAC address of the interface changes properly, so I know that the
unit is at least being read and parsed.

As an aside, this is happening on Ubuntu 15.04. I've disabled
NetworkManager and am relying, obviously, on systemd-networkd and
systemd-resolved. I've also temporarily disabled dhcpd thinking that
may have had something to do with the interface being busy, to no
avail.

Any thoughts on why the interface is busy resulting in the name change failing?

Thanks!
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel