You are not logged in.

#1 2013-07-01 15:50:22

doru001
Member
Registered: 2013-01-25
Posts: 138

"netctl start" fails when the system at the other end is down [SOLVED]

My ethernet-static profile is not started by netctl when the next system to connect to is stopped at boot time. Is there any simple fix?

Last edited by doru001 (2013-07-12 09:33:32)

Offline

#2 2013-07-01 18:22:19

danft2
Member
Registered: 2013-07-01
Posts: 4

Re: "netctl start" fails when the system at the other end is down [SOLVED]

Run:
#systemctl status netctl@<YOUR NETWORK>.service
#journalctl -xn
They're gonna tell what happend when netctl tried to connect to your network.

Offline

#3 2013-07-04 10:45:06

doru001
Member
Registered: 2013-01-25
Posts: 138

Re: "netctl start" fails when the system at the other end is down [SOLVED]

I have got a message saying that I should run these commands when I did "sudo netctl start ethernet-static" so here they are:

# systemctl status netctl@ethernet\x2dstatic.service
netctl@ethernetx2dstatic.service - Networking for netctl profile ethernetx2dstatic
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: inactive (dead)
     Docs: man:netctl.profile(5)

# journalctl -xn
-- Logs begin at Tue 2013-03-12 16:19:28 EET, end at Thu 2013-07-04 13:22:06 EEST. --
Jul 04 13:21:19 dan sudo[408]: pam_unix(sudo:session): session opened for user root by john(uid=0)
Jul 04 13:21:19 dan sudo[408]: pam_unix(sudo:session): session closed for user root
Jul 04 13:21:26 dan sudo[410]: user : TTY=tty1 ; PWD=/home/john ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Jul 04 13:21:26 dan sudo[410]: pam_unix(sudo:session): session opened for user root by john(uid=0)
Jul 04 13:21:31 dan sudo[410]: pam_unix(sudo:session): session closed for user root
Jul 04 13:21:52 dan sudo[415]: user : TTY=tty1 ; PWD=/home/john/shared ; USER=root ; COMMAND=/usr/bin/systemctl status netctl@ethernetx2dstatic.service
Jul 04 13:21:52 dan sudo[415]: pam_unix(sudo:session): session opened for user root by john(uid=0)
Jul 04 13:21:52 dan sudo[415]: pam_unix(sudo:session): session closed for user root
Jul 04 13:22:06 dan sudo[418]: user : TTY=tty1 ; PWD=/home/john/shared ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Jul 04 13:22:06 dan sudo[418]: pam_unix(sudo:session): session opened for user root by john(uid=0)

They don't look helpful to me.

Offline

#4 2013-07-10 10:56:01

doru001
Member
Registered: 2013-01-25
Posts: 138

Re: "netctl start" fails when the system at the other end is down [SOLVED]

I tried it again. When there is no working device at the other end of the ethernet line I get this:

$ sudo netctl start ethernet-static
... fails with message to run the following two commands ... 
$ sudo systemctl status netctl@ethernet\x2dstatic.service
netctl@ethernetx2dstatic.service - Networking for netctl profile ethernetx2dstatic
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: inactive (dead)
     Docs: man:netctl.profile(5)

$ sudo journalctl -xn
-- Logs begin at Tue 2013-01-29 16:08:38 EET, end at Wed 2013-07-10 13:19:14 EEST. --
Jul 10 13:18:48 george network[1159]: Failed to bring the network up for profile 'ethernet-static'
Jul 10 13:18:48 george systemd[1]: netctl@ethernet\x2dstatic.service: main process exited, code=exit
Jul 10 13:18:48 george systemd[1]: Failed to start lan.
-- Subject: Unit netctl@ethernet\x2dstatic.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d
--
-- Unit netctl@ethernet\x2dstatic.service has failed.
--
-- The result is failed.
[I removed some pam sudo related lines]
...skipping...
-- Logs begin at Tue 2013-01-29 16:08:38 EET, end at Wed 2013-07-10 13:19:14 EEST. --
Jul 10 13:18:48 george network[1159]: Failed to bring the network up for profile 'ethernet-static'
Jul 10 13:18:48 george systemd[1]: netctl@ethernet\x2dstatic.service: main process exited, code=exit
Jul 10 13:18:48 george systemd[1]: Failed to start lan.
-- Subject: Unit netctl@ethernet\x2dstatic.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d
--
-- Unit netctl@ethernet\x2dstatic.service has failed.
--
-- The result is failed.
Jul 10 13:18:48 george systemd[1]: Unit netctl@ethernet\x2dstatic.service entered failed state.
[I removed some pam sudo related lines]

They don't help. I only followed instructions to set up a static ethernet connection, I am sure that some people have had the same problem before.

Last edited by doru001 (2013-07-10 10:57:15)

Offline

#5 2013-07-10 12:49:30

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,835

Re: "netctl start" fails when the system at the other end is down [SOLVED]

Stating the obvious here (I hope) but if there's nothing "at the other end of the line", as you put it, there is no network to bring up - wouldn't you agree?

Anyway, what is at the other end of the line?

Offline

#6 2013-07-11 07:35:23

doru001
Member
Registered: 2013-01-25
Posts: 138

Re: "netctl start" fails when the system at the other end is down [SOLVED]

tomk wrote:

Stating the obvious here (I hope) but if there's nothing "at the other end of the line", as you put it, there is no network to bring up - wouldn't you agree?

Anyway, what is at the other end of the line?

The other end of the line is a switch. I want to bring up my NIC, not a network. A network is made up of two or more computers, which have to be started one after another. It is normal to bring up a NIC when there is nothing at the other end of the line. What would happen when two systems are connected and each of them refuses to bring its NIC up before the other one does the same? My NIC stays up after the physical connection is cut. So maybe someone will help me solve this problem.

Offline

#7 2013-07-11 10:18:32

doru001
Member
Registered: 2013-01-25
Posts: 138

Re: "netctl start" fails when the system at the other end is down [SOLVED]

In order to have the NIC started when the other end system is up you need to follow the Multiple Profiles Netctl wiki even though this is counterintuitive for a single NIC:
- disable netctl:
  # netctl disable ethernet-static
- install wpa_actiond for wireless connections and ifplugd for wired connections
- configure /etc/ifplugd/ifplugd.conf. I used:
  INTERFACES="enp2s0"
  ARGS="-fwI -u0 -d0"
- enable the services:
  # systemctl enable netctl-auto@enp2s0.service
  # systemctl enable netctl-ifplugd@enp2s0.service
  # systemctl is-enabled netctl-ifplugd@.service      # to verify
wait 10 seconds after the cable is plugged or unplugged to see the result with ip addr show

Last edited by doru001 (2013-07-12 09:35:38)

Offline

#8 2013-07-13 08:46:16

doru001
Member
Registered: 2013-01-25
Posts: 138

Re: "netctl start" fails when the system at the other end is down [SOLVED]

Disregard my last post (which still works, anyway, but it is only required if you want to dynamically manage your NIC's depending of whether they are connected or not), in order to have your NIC up even when not connected it is enough to add:

SkipNoCarrier=yes

at the end of your /etc/netctl/ethernet-static profile file (see man netctl.profile).

Last edited by doru001 (2013-07-13 09:12:03)

Offline

Board footer

Powered by FluxBB