[SOLVED] no network after arch 2014.10.01 install

nixIT · 2014-10-13 15:38:09

Hello all,

My desktop at work failed to boot on Friday so I proceeded to download the latest arch 2014.10.01 file, burned to USB and booted. All seemed fine. I then proceeded to follow the beginners guide to get arch up and running, which I was able to install the base system by the time I left work.

I came into work this AM to finish up the install (adding users, graphical environment etc.), however, I don't have a network connection.

I followed the wiki, checked and enabled the proper netctl file (even changed my device from eth0 to enp8s0), rebooted, no go.

The install has evolved since the last time I installed, and I have to say, I've spent 3 hours switching my KVM from running mac mini to my arch install trying to get it up and running, but no dice.

ip link shows that device enp8s0 is up, though I can't ping anything via ip address.

ping 8.8.8.8 returns "network unreachable"

I know it's something stupid, most likely a id10t error.

All help is appreciated.

[EDIT]
more info
When I issue

netctl status my_profile

I get an error:

Dependency failed for A basic static ethernet connection

journalctl -xn

systemd-udevd[536]: Error calling EVIOCSKEYCODE on device node '/dev/input/event2' (scan code 0xc022d, key code 418): invalid argument
systemd-udevd[536]: Error calling EVIOCSKEYCODE on device node '/dev/input/event2' (scan code 0xc022e, key code 419): invalid argument

not sure what they mean.

--nixIT

Last edited by nixIT (2014-10-15 18:19:59)

nomorewindows · 2014-10-13 16:52:25

Keyboard error shouldn't be related to network connection problems.
Do a ip link to find your adapter. Then do a dhcpcd/dhclient <whatever it's called>, assuming you have a DHCP server somewhere.

nixIT · 2014-10-13 18:11:20

@nomorewindows,

Thanx, my ethernet card is enp8s0, so I did dhcpcd enp8s0, and I was given an IP address. Is there a way I can set a static IP address and not dhcp?

--nixIT

nomorewindows · 2014-10-13 18:29:03

You can set it up with ip addr, but a more permanent solution is to replace all required information into the netctl script or use a network manager such as wicd, wifi-menu, or connman/cmst.

nixIT · 2014-10-13 19:06:56

@nomorewindows, I do have the information in my netctl script, I copied the one from examples and modified it to my liking. I then attempted to start and enable it, but didn't have any luck.

This system only has a wired connection, and I've don't remember using a network manager the last time I installed arch, which shows how long it's been running without issues.

What info can I provide that would help troubleshoot my static IP issues? As this will help me going forward since I'm about to (also) upgrade my home system soon.

--nixIT

nomorewindows · 2014-10-13 19:23:18

What does your netctl script look like? Mostly, you set the address method to static instead of dhcp, and set a manual IP address.
What does the journalctl or systemctl status <netctl script> show?

nixIT · 2014-10-14 15:33:20

@nomorewindows,
So, after I finished installed Arch and XFCE last night, I rebooted and wouldn't you know it, no network connection. I had to issue dhcpcd enp8s0 in order to get a dhcp lease, though I would prefer a static IP address. I'm sure there is something I missed somewhere...

Here is the contents of my netctl script, which is called work_network:

Description='A basic static ethernet connection'
Interface=enp8s0
Connection=ethernet
IP=static
Address=('10.241.0.77/24')
#Routes=('192.168.0.0/24 via 192.168.1.2')
Gateway='10.241.0.1'
DNS=('10.241.0.7')

## 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'

during install, for a static IP address, I followed the wiki:

https://wiki.archlinux.org/index.php/Be … he_network

when I reenter the command

netctl enable work_network

I get a message saying "A unit file for profile 'work_network' already exists.

I'm kinda lost at why it's not working.

Thanx again for your help.

--nixIT.

nomorewindows · 2014-10-14 15:47:37

It starts automatically now, so it doesn't need to be reenabled. Try netctl status work_network or journalctl to see if it will tell us what the problem is.

nixIT · 2014-10-14 15:58:33

Unfortunately it still doesn't start automatically, the only way I can get network connection is with dhcpd.

netctl status work_network

$ netctl status work_network
● netctl@work_network.service - A basic static ethernet connection
Loaded: loaded (/etc/systemd/system/netctl@work_network.service; enabled)
Active: inactive (dead)
Docs: man:netctl.profile(5)
Oct 14 09:23:28 doit systemd[1]: Dependency failed for A basic static etherne...n.
Hint: Some lines were ellipsized, use -l to show in full.

Where do I put the -l to show in full?

--nixIT

nomorewindows · 2014-10-14 16:19:29

Just on the end of the command for netctl.

nixIT · 2014-10-14 16:23:11

Here is what I get:

$ netctl status work_network -l
Usage: netctl {COMMAND} [PROFILE]
              [--help|--version]

Commands:
  list                  List available profiles
  store                 Save which profiles are active
  restore               Load saved profiles
  stop-all              Stops all profiles
  start [PROFILE]       Start a profile
  stop [PROFILE]        Stop a profile
  restart [PROFILE]     Restart a profile
  switch-to [PROFILE]   Switch to a profile
  status [PROFILE]      Show runtime status of a profile
  enable [PROFILE]      Enable the systemd unit for a profile
  disable [PROFILE]     Disable the systemd unit for a profile
  is-enabled [PROFILE]  Check whether a profile is enabled
  reenable [PROFILE]    Reenable the systemd unit for a profile

this can't be correct.

nomorewindows · 2014-10-14 16:26:00

Try it with systemctl status netctl@<profile> -l. Anyways if you maximize your terminal window, it'll do the same thing.

nixIT · 2014-10-14 17:45:26

@nomorewindows,

thanx for your continued help. Here is the output

$ systemctl status netctl@work_network -l
● netctl@work_network.service - A basic static ethernet connection
Loaded: loaded (/etc/systemd/system/netctl@work_network.service; enabled)
Active: inactive (dead)
Docs: man:netctl.profile(5)
Oct 14 12:15:22 doit systemd[1]: Dependency failed for A basic static ethernet connection.

nomorewindows · 2014-10-14 19:19:04

Looks like you need the journalctl -xb output.

nixIT · 2014-10-14 19:26:46

I'm not sure what to be looking for.

Last edited by nixIT (2014-10-14 19:28:59)

nixIT · 2014-10-14 19:40:21

@nomorewindows,

I did a fresh reboot on the box and didn't have an internet connection after logging, so I did the following:

$ journalctl -xb | grep enp8s0
Oct 14 15:31:45 doit systemd-udevd[216]: renamed network interface eth0 to enp8s0

$ journalctl -xb | grep eth0
Oct 14 15:31:45 doit kernel: tg3 0000:08:00.0 eth0: Tigon3 [partno(BCM95754) rev b002] (PCI Express) MAC address 00:1e:4f:b1:87:7f
Oct 14 15:31:45 doit kernel: tg3 0000:08:00.0 eth0: attached PHY is 5787 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
Oct 14 15:31:45 doit kernel: tg3 0000:08:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Oct 14 15:31:45 doit kernel: tg3 0000:08:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Oct 14 15:31:45 doit systemd-udevd[216]: renamed network interface eth0 to enp8s0

not sure if this helps.

nomorewindows · 2014-10-14 19:44:03

Looking for the reason why the dependency failed.

nixIT · 2014-10-14 19:47:27

not sure which dependency. I posted the results of journalctl -xb | grep enp8s0 above, and nothing has failed.

nomorewindows · 2014-10-14 19:53:24

Probably what you need is journalctl -xb | grep netctl

nixIT · 2014-10-14 19:58:20

hmmm.

$ journalctl -xb | grep netctl
-- Subject: Unit netctl@work_network.service has failed
-- Unit netctl@work_network.service has failed.

I'm about ready to perform another re-install to see if it was something during the install.

nomorewindows · 2014-10-14 20:00:05

Below that line it should show what the error is. If you just journalctl -xb by itself and just scroll through or use /netctl to take you there, you might find the reason.

nixIT · 2014-10-14 20:10:51

the good news is, I'm learning something from you... thank you again for helping me.

The bad news:

-- Subject: Unit netctl@work_network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@work_network.service has failed.
-- 
-- The result is dependency.

I knew it was a dependency issue yesterday, but what dependency? garrrgggghhhh.

nomorewindows · 2014-10-14 20:14:05

Are you running it as root or as a normal user? There are some other options such as journalctl -xb (boot).

nixIT · 2014-10-14 20:40:38

If I remember, I set everything up as root when installing, then created a user.

Ok, so I just su - to root and stopped and disabled the profile, then attempted to restart it:

# netctl start work_network
Job for netctl@work_network.service failed. See 'systemctl status netctl@work_network.service' and 'journalctl -xn' for details.
[root@doit ~]# systemctl status netctl@work_network -l
● netctl@work_network.service - Networking for netctl profile work_network
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Tue 2014-10-14 16:20:08 EDT; 3s ago
     Docs: man:netctl.profile(5)
  Process: 716 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 716 (code=exited, status=1/FAILURE)

Oct 14 16:20:08 doit network[716]: Starting network profile 'work_network'...
Oct 14 16:20:08 doit network[716]: The interface of network profile 'work_network' is already up
Oct 14 16:20:08 doit systemd[1]: netctl@work_network.service: main process exited, code=exited, status=1/FAILURE
Oct 14 16:20:08 doit systemd[1]: Failed to start Networking for netctl profile work_network.
Oct 14 16:20:08 doit systemd[1]: Unit netctl@work_network.service entered failed state.

I am so confused now.

nixIT · 2014-10-14 20:51:25

ok, rebooted that troubled box and issues all commands when non network was running, hopefully giving some clue as to what's going on.

# netctl start work_network
Job for netctl@work_network.service failed. See 'systemctl status netctl@work_network.service' and 'journalctl -xn' for details.
[root@doit ~]# systemctl status netctl@work_network.service -l
● netctl@work_network.service - Networking for netctl profile work_network
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Tue 2014-10-14 16:47:07 EDT; 8s ago
     Docs: man:netctl.profile(5)
  Process: 617 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 617 (code=exited, status=1/FAILURE)

Oct 14 16:47:06 doit network[617]: Starting network profile 'work_network'...
Oct 14 16:47:07 doit network[617]: RTNETLINK answers: File exists
Oct 14 16:47:07 doit network[617]: Could not add address '10.241.0.77' to interface 'enp8s0'
Oct 14 16:47:07 doit network[617]: Failed to bring the network up for profile 'work_network'
Oct 14 16:47:07 doit systemd[1]: netctl@work_network.service: main process exited, code=exited, status=1/FAILURE
Oct 14 16:47:07 doit systemd[1]: Failed to start Networking for netctl profile work_network.
Oct 14 16:47:07 doit systemd[1]: Unit netctl@work_network.service entered failed state.
[root@doit ~]# journalctl -xn
-- Logs begin at Fri 2014-10-10 16:31:07 EDT, end at Tue 2014-10-14 16:47:09 EDT. --
Oct 14 16:47:07 doit kernel: tg3 0000:08:00.0 enp8s0: Flow control is on for TX and on for RX
Oct 14 16:47:07 doit kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp8s0: link becomes ready
Oct 14 16:47:07 doit network[617]: RTNETLINK answers: File exists
Oct 14 16:47:07 doit network[617]: Could not add address '10.241.0.77' to interface 'enp8s0'
Oct 14 16:47:07 doit systemd-networkd[304]: enp8s0          : removing non-existent address: fe80::21e:4fff:feb1:877f/64 (valid for ever)
Oct 14 16:47:07 doit network[617]: Failed to bring the network up for profile 'work_network'
Oct 14 16:47:07 doit systemd[1]: netctl@work_network.service: main process exited, code=exited, status=1/FAILURE
Oct 14 16:47:07 doit systemd[1]: Failed to start Networking for netctl profile work_network.
-- Subject: Unit netctl@work_network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@work_network.service has failed.
--
-- The result is failed.
Oct 14 16:47:07 doit systemd[1]: Unit netctl@work_network.service entered failed state.
Oct 14 16:47:09 doit ntpd[311]: Deleting interface #5 enp8s0, 10.241.0.77#123, interface stats: received=0, sent=0, dropped=0, active_time=2 secs

Is there something here that helps narrow down what's going on?

--nixIT

Arch Linux

#1 2014-10-13 15:38:09

[SOLVED] no network after arch 2014.10.01 install

#2 2014-10-13 16:52:25

Re: [SOLVED] no network after arch 2014.10.01 install

#3 2014-10-13 18:11:20

Re: [SOLVED] no network after arch 2014.10.01 install

#4 2014-10-13 18:29:03

Re: [SOLVED] no network after arch 2014.10.01 install

#5 2014-10-13 19:06:56

Re: [SOLVED] no network after arch 2014.10.01 install

#6 2014-10-13 19:23:18

Re: [SOLVED] no network after arch 2014.10.01 install

#7 2014-10-14 15:33:20

Re: [SOLVED] no network after arch 2014.10.01 install

#8 2014-10-14 15:47:37

Re: [SOLVED] no network after arch 2014.10.01 install

#9 2014-10-14 15:58:33

Re: [SOLVED] no network after arch 2014.10.01 install

#10 2014-10-14 16:19:29

Re: [SOLVED] no network after arch 2014.10.01 install

#11 2014-10-14 16:23:11

Re: [SOLVED] no network after arch 2014.10.01 install

#12 2014-10-14 16:26:00

Re: [SOLVED] no network after arch 2014.10.01 install

#13 2014-10-14 17:45:26

Re: [SOLVED] no network after arch 2014.10.01 install

#14 2014-10-14 19:19:04

Re: [SOLVED] no network after arch 2014.10.01 install

#15 2014-10-14 19:26:46

Re: [SOLVED] no network after arch 2014.10.01 install

#16 2014-10-14 19:40:21

Re: [SOLVED] no network after arch 2014.10.01 install

#17 2014-10-14 19:44:03

Re: [SOLVED] no network after arch 2014.10.01 install

#18 2014-10-14 19:47:27

Re: [SOLVED] no network after arch 2014.10.01 install

#19 2014-10-14 19:53:24

Re: [SOLVED] no network after arch 2014.10.01 install

#20 2014-10-14 19:58:20

Re: [SOLVED] no network after arch 2014.10.01 install

#21 2014-10-14 20:00:05

Re: [SOLVED] no network after arch 2014.10.01 install

#22 2014-10-14 20:10:51

Re: [SOLVED] no network after arch 2014.10.01 install

#23 2014-10-14 20:14:05

Re: [SOLVED] no network after arch 2014.10.01 install

#24 2014-10-14 20:40:38

Re: [SOLVED] no network after arch 2014.10.01 install

#25 2014-10-14 20:51:25

Re: [SOLVED] no network after arch 2014.10.01 install

Board footer