Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#35831 - [netctl] .service restore failing due to uninitialized interface

Attached to Project: Arch Linux
Opened by Daniel Albers (al) - Monday, 17 June 2013, 10:56 GMT
Last edited by Jelle van der Waa (jelly) - Friday, 11 August 2023, 15:17 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

In my freshly set up KVM installation netctl.service fails to restore a working profile on boot, due to
1) interface driver not being fully loaded
2) predictable interface name ("ens3" in this case) not yet established by udev.

Running `netctl start ethernet-dhcp` once the boot sequence finishes succeeds without error.

[root@localhost ~]# journalctl -b | egrep 'netctl|eth|ens3'
Jun 17 10:43:38 localhost kernel: 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
Jun 17 10:43:38 localhost network[155]: Starting network profile 'ethernet-dhcp'...
Jun 17 10:43:38 localhost network[155]: Interface 'ens3' does not exist
Jun 17 10:43:38 localhost network[155]: Failed to bring the network up for profile 'ethernet-dhcp'
Jun 17 10:43:38 localhost systemd[1]: netctl@ethernet\x2ddhcp.service: main process exited, code=exited, status=1/FAILURE
Jun 17 10:43:38 localhost systemd[1]: Failed to start Networking for netctl profile ethernet-dhcp.
Jun 17 10:43:38 localhost systemd[1]: Unit netctl@ethernet\x2ddhcp.service entered failed state.
Jun 17 10:43:38 localhost netctl[140]: Job for netctl@ethernet\x2ddhcp.service failed. See 'systemctl status netctl@ethernet\x2ddhcp.service' and 'journalctl -xn' for details.
Jun 17 10:43:38 localhost systemd[1]: Started (Re)store the netctl profile state.
Jun 17 10:43:38 localhost kernel: 8139cp 0000:00:03.0 eth0: RTL-8139C+ at 0xffffc90000658000, 52:54:00:aa:bd:68, IRQ 11
Jun 17 10:43:38 localhost kernel: 8139too: 8139too Fast Ethernet driver 0.9.28
Jun 17 10:43:38 localhost kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jun 17 10:43:39 localhost systemd-udevd[135]: renamed network interface eth0 to ens3

[root@localhost ~]# netctl list
* ethernet-dhcp
[root@localhost ~]# cat /etc/netctl/ethernet-dhcp
Description='A basic dhcp ethernet connection'
Interface=ens3
Connection=ethernet
IP=dhcp
This task depends upon

Closed by  Jelle van der Waa (jelly)
Friday, 11 August 2023, 15:17 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/n etctl/issues/2
Comment by Jouke Witteveen (jouke) - Monday, 17 June 2013, 14:14 GMT
Please follow the `netctl enable <profile>`, `systemctl disable netctl@<profile>` steps outlined in netctl.special(7). I believe this will fix your problem.
Comment by Daniel Albers (al) - Wednesday, 19 June 2013, 16:50 GMT
That does work, but isn't that just a workaround? Could `netctl store` be changed to do these things?
Comment by Lara Maia (mrk3004) - Monday, 11 November 2013, 12:10 GMT
I have the same problem
Comment by Doug Newgard (Scimmia) - Wednesday, 13 May 2015, 03:53 GMT
Jouke, so is this a bug or expected behavior? Nearing 2 years later, is this still relevant?
Comment by Jouke Witteveen (jouke) - Wednesday, 13 May 2015, 11:56 GMT
This is expected behavior, although very unwelcome. What this bug needs is a good proposal for a 'fix'. Adding the steps to `netctl store` introduces too much side effects to the store command, which should remain as simple as its name: it just stores the currently running profiles.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...