Arch Linux

whoop

Member

Registered: 2009-05-28

Posts: 101

[SOLVED] netctl stopped working (how to get eth0 up?)

It was working, then it stopped... Overlooking something? Can't find it...
Info:

cat /etc/netctl/my-ethernet-static

Description='A basic static ethernet connection'
Interface=eth0
Connection=ethernet
IP=static
Address=('11.1.6.128/24')
#Routes=('192.168.0.0/24 via 192.168.1.2')
Gateway='11.1.6.1'
DNS=('11.1.6.1')

## For IPv6 autoconfiguration
#IP6=stateless

## For IPv6 static address configuration
#IP6=static
#Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#Routes6=('abcd::1234')
#Gateway6='1234:0:123::abcd'

netctl start my-ethernet-static

Job for netctl@my\x2dethernet\x2dstatic.service failed. See 'systemctl status netctl@my\x2dethernet\x2dstatic.service' and 'journalctl -xn' for details.
[root@VIRTUE whoop]# 

systemctl status netctl@my\x2dethernet\x2dstatic.service

netctl@myx2dethernetx2dstatic.service - Networking for netctl profile myx2dethernetx2dstatic
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: inactive (dead)
     Docs: man:netctl.profile(5)

journalctl -xn

-- Logs begin at Sat 2013-03-16 16:06:48 CET, end at Mon 2013-06-10 18:35:22 CEST. --
Jun 10 18:34:47 VIRTUE sudo[872]: pam_unix(sudo:session): session closed for user root
Jun 10 18:34:48 VIRTUE /etc/gdm/Xsession[456]: ** (nautilus:620): WARNING **: Could not establish a connection to Tracker: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The na
Jun 10 18:34:49 VIRTUE /etc/gdm/Xsession[456]: ** (nautilus:620): WARNING **: Could not establish a connection to Tracker: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The na
Jun 10 18:34:53 VIRTUE sudo[889]: whoop : TTY=pts/0 ; PWD=/home/whoop ; USER=root ; COMMAND=/usr/bin/bash
Jun 10 18:34:53 VIRTUE sudo[889]: pam_unix(sudo:session): session opened for user root by whoop(uid=0)
Jun 10 18:35:14 VIRTUE sudo[889]: pam_unix(sudo:session): session closed for user root
Jun 10 18:35:16 VIRTUE /etc/gdm/Xsession[456]: ** (nautilus:620): WARNING **: Could not establish a connection to Tracker: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The na
Jun 10 18:35:16 VIRTUE /etc/gdm/Xsession[456]: ** (nautilus:620): WARNING **: Could not establish a connection to Tracker: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The na
Jun 10 18:35:22 VIRTUE sudo[911]: whoop : TTY=pts/0 ; PWD=/home/whoop ; USER=root ; COMMAND=/usr/bin/bash
Jun 10 18:35:22 VIRTUE sudo[911]: pam_unix(sudo:session): session opened for user root by whoop(uid=0)

Please help...
Cheers.

Last edited by whoop (2013-09-03 21:24:23)

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

I have heard of netctl having issues with systemd's handling of the escaped dashes (-).  Try renaming the profile to something like my_network_static and see if that helps.

whoop

Member

Registered: 2009-05-28

Posts: 101

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

Thanks for your response. I tried your suggestion but it did not work. For some strange reason the output is different though:

netctl start my_ethernet_static

Job for netctl@my_ethernet_static.service failed. See 'systemctl status netctl@my_ethernet_static.service' and 'journalctl -xn' for details.

systemctl status netctl@my_ethernet_static.service

netctl@my_ethernet_static.service - Networking for netctl profile my_ethernet_static
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Tue 2013-06-11 12:48:57 CEST; 27s ago
     Docs: man:netctl.profile(5)
  Process: 825 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)

Jun 11 12:48:52 VIRTUE network[825]: Starting network profile 'my_ethernet_static'...
Jun 11 12:48:57 VIRTUE network[825]: No connection on interface 'eth0'
Jun 11 12:48:57 VIRTUE network[825]: Failed to bring the network up for profile 'my_ethernet_static'
Jun 11 12:48:57 VIRTUE systemd[1]: netctl@my_ethernet_static.service: main process exited, code=exited, status=1/FAILURE
Jun 11 12:48:57 VIRTUE systemd[1]: Failed to start Networking for netctl profile my_ethernet_static.
Jun 11 12:48:57 VIRTUE systemd[1]: Unit netctl@my_ethernet_static.service entered failed state.

journalctl -xn

-- Logs begin at Sat 2013-03-16 16:06:48 CET, end at Tue 2013-06-11 12:48:57 CEST. --
Jun 11 12:48:52 VIRTUE kernel: r8169 0000:03:00.0 eth0: link down
Jun 11 12:48:52 VIRTUE kernel: r8169 0000:03:00.0 eth0: link down
Jun 11 12:48:52 VIRTUE kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 11 12:48:57 VIRTUE network[825]: No connection on interface 'eth0'
Jun 11 12:48:57 VIRTUE network[825]: Failed to bring the network up for profile 'my_ethernet_static'
Jun 11 12:48:57 VIRTUE systemd[1]: netctl@my_ethernet_static.service: main process exited, code=exited, status=1/FAILURE
Jun 11 12:48:57 VIRTUE systemd[1]: Failed to start Networking for netctl profile my_ethernet_static.
-- Subject: Unit netctl@my_ethernet_static.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- 
-- Unit netctl@my_ethernet_static.service has failed.
-- 
-- The result is failed.
Jun 11 12:48:57 VIRTUE systemd[1]: Unit netctl@my_ethernet_static.service entered failed state.
Jun 11 12:48:57 VIRTUE systemd[1]: Starting Network.
-- Subject: Unit network.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit network.target has begun starting up.
Jun 11 12:48:57 VIRTUE systemd[1]: Reached target Network.
-- Subject: Unit network.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit network.target has finished starting up.
-- 
-- The start-up result is done.

rix

Member

Registered: 2012-07-25

Posts: 238

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

Have you tried connecting manually as wiki suggested?

Last edited by rix (2013-06-11 14:24:14)

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

From your logs: "No connection on interface 'eth0'".  Are you absolutely certain that your device is both named eth0 and up?  If this is a new install, systemd uses a new naming interface that is not what you are used to.  Use "ip link" to see what your interfaces might be named now.  If the interface is the right name, it might not actually be up.  You might need to do "ip link set eth0 up" and/or check the status with rfkill.

If your interfaces are named with the new naming scheme, you can make it go back to the old way by masking 80-net-name-slot.rules.  So you either touch a blank file or your make it a symlink to /dev/null at /etc/udev/rules.d/80-net-name-slot.rules.  This will effective take precedence over the file of the same name in /usr/lib/udev/rules.d.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,354

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

Use "ip link" to see what your interfaces might be named now.  If the interface is the right name, it might not actually be up.

You might also look at that output to see if it warns you that there is no carrier.  Which, as a hardware guy, leads me to the question:  You did check the cables, right?  It is unbelievable how often it is a bad or disconnected cable.  Ensure that the (if present) the link lights are on at both your computer's NIC, and at the router/switch/hub/modem. </soapbox mode>

Last edited by ewaller (2013-06-11 15:13:15)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

whoop

Member

Registered: 2009-05-28

Posts: 101

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

Thanks for the responses... It's getting a bit weird here. eth0 indeed seems down, but I can't get it "up"...

[root@VIRTUE whoop]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:1b:fc:18:a2:90 brd ff:ff:ff:ff:ff:ff
[root@VIRTUE whoop]# ip link set eth0 up
[root@VIRTUE whoop]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 00:1b:fc:18:a2:90 brd ff:ff:ff:ff:ff:ff
[root@VIRTUE whoop]# ifconfig eth0 up
[root@VIRTUE whoop]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 00:1b:fc:18:a2:90 brd ff:ff:ff:ff:ff:ff

Cable is connected because I can get a normal connection when using NetworkManager...

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,354

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

Cable is connected because I can get a normal connection when using NetworkManager...

With No-CARRIER in ip link??  That is weird.  When last did you try that?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

whoop

Member

Registered: 2009-05-28

Posts: 101

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

Cable is connected because I can get a normal connection when using NetworkManager...

With No-CARRIER in ip link??  That is weird.  When last did you try that?

right now...
After I tried all the suggestions in this post I ran:

systemctl start NetworkManager.service

Now  ip link gives me:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 00:1b:fc:18:a2:90 brd ff:ff:ff:ff:ff:ff

whoop

Member

Registered: 2009-05-28

Posts: 101

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

I am starting to think this has nothing to do with netctl but more something to do with not getting out of NO-CARRIER without the use of NetworkManager...

should this thread be closed and that I start a new thread as the topic and posts are not related anymore?

Last edited by whoop (2013-06-11 21:28:04)

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

No I would think it sitll applies as netctl stops working... seems silly to make pointless abandoned threads.

whoop

Member

Registered: 2009-05-28

Posts: 101

Re: [SOLVED] netctl stopped working (how to get eth0 up?)

It looks like I solved this problem by removing all comments (lines starting with '#') from the netctl config file... I haven't confirmed/tested this but it really looks like it....

Last edited by whoop (2014-09-25 15:20:36)