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#35992 - [netctl] silent crash when interface is already up

Attached to Project: Arch Linux
Opened by Nathan Typanski (ndat) - Tuesday, 02 July 2013, 01:06 GMT
Last edited by Jouke Witteveen (jouke) - Thursday, 18 July 2013, 07:08 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Normally, when an interface eth0 (for example) is up and netctl start is
called on a profile which uses the interface, netctl will fail on its
first test as to whether eth0 is an interface, with the message "main
process exited". This is undesireable and skips the remainder of tests
on the interface without leaving ANY trailing log messages:

Starting Networking for netctl profile eth...
Starting network profile 'eth'...
netctl@eth.service: main process exited, code=exited
Failed to start Networking for netctl profile eth

I've attached a patch which makes it behave properly. With the patch,
it will display "The interface of network profile 'eth' is already up"
before the "main process exited" error.

Steps to reproduce:

ip link set eth0 up
netcfg start <profile name>
This task depends upon

Closed by  Jouke Witteveen (jouke)
Thursday, 18 July 2013, 07:08 GMT
Reason for closing:  Upstream
Additional comments about closing:  Probably systemctl's fault
Comment by Jouke Witteveen (jouke) - Sunday, 14 July 2013, 19:03 GMT
with and without the patch, the error message appears in my journal. I see no reason why this patch should do anything.
Comment by Nathan Typanski (ndat) - Monday, 15 July 2013, 23:34 GMT
I will admit that my patch doesn't make any sense. I tested it more today and my results were intermittent. It had nothing to do with that line, but by pure dumb luck changing solved the problem in my ~six times testing it before posting here. Forgive me. I honestly could not articulate why it "worked" either.

But I am still getting silent crashes, and not only when an interface is already up. Here is an example.

root # cat /etc/netctl/eth
Description='A more versatile static ethernet connection'
Interface=eth0
Connection=ethernet
IP=dhcp
root # dhcpcd eth0
dhcpcd[7284]: version 5.6.8 starting
dhcpcd[7284]: eth0: sending IPv6 Router Solicitation
dhcpcd[7284]: eth0: sendmsg: Network is unreachable
dhcpcd[7284]: eth0: broadcasting for a lease
dhcpcd[7284]: eth0: offered 137.155.197.12 from 137.155.12.15
dhcpcd[7284]: eth0: acknowledged 137.155.197.12 from 137.155.12.15
dhcpcd[7284]: eth0: checking for 137.155.197.12
dhcpcd[7284]: eth0: sending IPv6 Router Solicitation
dhcpcd[7284]: eth0: sendmsg: Network is unreachable
dhcpcd[7284]: eth0: leased 137.155.197.12 for 691200 seconds
dhcpcd[7284]: forked to background, child pid 7316
root # wget archlinux.org
2013-07-15 19:23:49 (66.9 MB/s) - ‘index.html’ saved [27352/27352]
root # dhcpcd -k eth0
dhcpcd[7800]: sending signal 1 to pid 7316
dhcpcd[7800]: waiting for pid 7316 to exit
root # netctl start eth
Job for netctl@eth.service failed. See 'systemctl status netctl@eth.service' and 'journalctl -xn' for details.
root # systemctl status netctl@eth.service
netctl@eth.service - Networking for netctl profile eth
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
Active: failed (Result: exit-code) since Mon 2013-07-15 19:24:33 EDT; 4s ago
Docs: man:netctl.profile(5)
Process: 7856 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)

Jul 15 19:24:33 network[7856]: Starting network profile 'eth'...
Jul 15 19:24:33 systemd[1]: netctl@eth.service: main process exited, code=exited, statu...LURE
Jul 15 19:24:33 systemd[1]: Failed to start Networking for netctl profile eth.
Jul 15 19:24:33 systemd[1]: Unit netctl@eth.service entered failed state.

I can provide any further details you ask.
Comment by Nathan Typanski (ndat) - Tuesday, 16 July 2013, 00:49 GMT
[[ double post, please ignore ]]
Comment by Jouke Witteveen (jouke) - Tuesday, 16 July 2013, 08:28 GMT
This might be a bug in systemctl. I bet the journal (journalctl) does show the error lines. I don't know why they (sometimes?) don't show up in `netctl status <profile>`...
Comment by Nathan Typanski (ndat) - Wednesday, 17 July 2013, 20:26 GMT
Ok, journalctl shows the proper report (at least in this instance).

Probably this is not netctl's fault here and the bug report may be closed.

Loading...