New initscripts, static IP not working anymore

.:B:. · 2008-03-25 05:04:05

Okay so here goes. I am running an Arch slice (Slicehost) and ran a pacman upgrade today. Initscripts got upgraded, I installed netcfg just to be sure. I reboot, I can still reach the server. So far so good.

Then I edit rc.conf to use netcfg instead of the static line in rc.conf (I initially thought the network config got moved out completely of rc.conf, seems it's only for more complicated setups and the loopback interface). I reboot. Server unreachable...

I am able to run the server in rescue mode to restore stuff but up till now I've been unsuccessful in doing so. I disabled & threw out netcfg alltogether (shouldn't be needed right?) and my rc.conf looks like this now:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Canada/Pacific"
USEDIRECTISA="yes"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
MOD_AUTOLOAD="yes"
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="nauseamedialis"
#
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
eth0="eth0 67.207.141.131 netmask 255.255.255.0 broadcast 67.207.141.255"
INTERFACES=(eth0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 67.207.141.1"
ROUTES=(gateway)
#
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng crond iptables sshd mysqld lighttpd)

What I've tried already: let netcfg handle the interface setup, let rc.conf do it, added/removed net-profiles and network (alternating) to DAEMONS=(). Still stuck. To me my rc.conf looks ok... No Arch users were present on #slicehost at this time, so that's why I try here.

If someone can shed any light on this I'd be utterly grateful .

Last edited by B (2008-03-25 05:06:36)

jarryson · 2008-03-25 06:45:40

it seems i have the same problem.

:: Stopping Network            [Done]
:: Starting Network              [BUSY]  
SIOCADDRT: No such process

it only showed when i restart the network , but when i reboot , it was fine again

so i have to use /etc/rc.d/net-profile instead

i only have the static ethernet , so im not realy want to use netcfg

luca · 2008-03-25 06:51:50

Hi B,
add "net-profile" in DAEMONS array and create in /etc/network.d a profile for you connection.
Add

NETWORKS=(<profile name>)

in /etc/rc.conf

tomk · 2008-03-25 07:32:13

B -your config is almost correct, except for the absence of 'network' in the DAEMONS array.

Use of netcfg is optional - if you weren't using the previous integrated version, then you don't need the new standalone version.

.:B:. · 2008-03-25 09:13:07

Thanks guys, but even with network _in_ the DAEMONS array, it does not work... I already tried this (both suggestions, with the net-profiles & network entry).

[stijn@lysithea ~]$ ping 67.207.141.1
PING 67.207.141.1 (67.207.141.1) 56(84) bytes of data.
64 bytes from 67.207.141.1: icmp_seq=1 ttl=48 time=123 ms
64 bytes from 67.207.141.1: icmp_seq=2 ttl=48 time=117 ms
64 bytes from 67.207.141.1: icmp_seq=3 ttl=48 time=118 ms

--- 67.207.141.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 117.681/119.772/123.501/2.658 ms
[stijn@lysithea ~]$ ping 67.207.141.131
PING 67.207.141.131 (67.207.141.131) 56(84) bytes of data.
From 38.104.162.22 icmp_seq=2 Destination Host Unreachable
From 38.104.162.22 icmp_seq=3 Destination Host Unreachable
From 38.104.162.22 icmp_seq=4 Destination Host Unreachable

--- 67.207.141.131 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4002ms
, pipe 3
[stijn@lysithea ~]$ ssh root@67.207.141.131
ssh: connect to host 67.207.141.131 port 22: No route to host

Last edited by B (2008-03-25 09:13:59)

luca · 2008-03-25 09:26:15

Hi B,
post the output of

netstat -rn

Ramses de Norre · 2008-03-25 11:47:37

I'm also having the situation jarryson described, restarting network results in that error and only rebooting gets network up again...
I've configured a static ip in rc.conf and never had problems before... Relevant piece of rc.conf:

HOSTNAME="icarus"
eth0="eth0 192.168.###.### netmask 255.255.###.### broadcast 192.168.###.###"
INTERFACES=(eth0)
gateway="default gw 192.168.###.###"
ROUTES=(gateway)
DAEMONS=(@syslog-ng iptables @network @dbus @crond !ifplugd @alsa @denyhosts @sshd @mpd @powernowd @ddclient portmap nfslock nfsd !sensors @transmissiond)

.:B:. · 2008-03-25 20:42:37

jarryson wrote:

it seems i have the same problem.
:: Stopping Network            [Done]
:: Starting Network              [BUSY]  
SIOCADDRT: No such process
it only showed when i restart the network , but when i reboot , it was fine again
so i have to use /etc/rc.d/net-profile instead
i only have the static ethernet , so im not realy want to use netcfg

Well, after I found out on #slicehost that opera doesn't like their web console (or the other way around), I tried firefox and got in. And I got an identical error.

In the end i just salvaged my configs and data and rebuilt the slice. All up happy now.

fwojciec · 2008-03-25 22:15:59

I started getting similar errors recently when trying to *restart* network daemon. The network would come up fine during regular boot routine. A workaround, in my case, was to stop the network daemon, rmmod the wifi card module, modprobe it again, and start network daemon again. All this, in the end, prompted me to switch to netcfg2 which works without any problems.

jarryson · 2008-03-26 02:34:13

i reported a Bug , i hope my description is correct , and u can understand what i said.

http://bugs.archlinux.org/task/9960

broch · 2008-03-26 17:44:14

ping 67.207.141.131
PING 67.207.141.131 (67.207.141.131) 56(84) bytes of data.
From 38.104.162.22 icmp_seq=2 Destination Host Unreachable
From 38.104.162.22 icmp_seq=3 Destination Host Unreachable
From 38.104.162.22 icmp_seq=4 Destination Host Unreachable

this seems to be a problem, looks like messed up config: pinging your adders 67.207.141.131 generates response from 38.104.162.22

pinging gateway works though:

ping 67.207.141.1
PING 67.207.141.1 (67.207.141.1) 56(84) bytes of data.
64 bytes from 67.207.141.1: icmp_seq=1 ttl=48 time=123 ms
64 bytes from 67.207.141.1: icmp_seq=2 ttl=48 time=117 ms
64 bytes from 67.207.141.1: icmp_seq=3 ttl=48 time=118 ms

.:B:. · 2008-03-26 19:29:53

jarryson wrote:

i reported a Bug , i hope my description is correct , and u can understand what i said.
http://bugs.archlinux.org/task/9960

Yes, other people also pointed to this part of the code being the culprit, possibly.

@ Broch: it is peculiar indeed, the SIOCADDRT error seems to point to a bad routing configuration. I have done everything manually (assigning IP, netmask, broadcast, adding default route) and I cannot ping the slice either. After spending hours on using the rescue mode (and a web console that doesn't like Opera - which I found out only at the end...) I decided to rebuild the slice, not like there was much on it already . Basic stuff like this is not supposed to break though .

broch · 2008-03-27 00:22:26

actually this:

ping 67.207.141.131
PING 67.207.141.131 (67.207.141.131) 56(84) bytes of data.
From 38.104.162.22 icmp_seq=2 Destination Host Unreachable

suggests your error during network configuration.

With such configuration network will never work properly.

this has nothing to do with inability to restart network with static ip. this is simply wrong configuration.

.:B:. · 2008-03-27 00:32:46

Well what did I do wrong then, according to you? Very nice that it 'suggests' my error, cause I don't see it. I had other people take a look at my configuration, they weren't finding any errors either. If you do see it, I'd be most happy to hear it.

My rc.conf is on top, if you want to check .

Last edited by B (2008-03-27 00:34:51)

broch · 2008-03-27 12:51:54

for example
/etc/hosts

rc.conf is not the only network configuration file

this error would happen if pinging your own ip address.

.:B:. · 2008-03-27 15:25:28

/etc/hosts was supplied by Slicehost, as was rc.conf. I didn't touch it .

That of course doesn't rule out an error from Slicehost's side, but they said they investigated and couldn't find anything either. Ah well, all over now anyway...

Last edited by B (2008-03-27 15:26:29)

fff · 2008-04-01 19:30:46

I have the same problem , everything works fine after a reboot tho. Have anyone found a good solution for this problem?
Its not a huge issue but i would like to have the possibility to restart my network interface without rebooting.

1st post here for me , and I'm pretty fresh to Archlinux but not to Linux in general.

-thomas

Arch Linux

#1 2008-03-25 05:04:05

New initscripts, static IP not working anymore

#2 2008-03-25 06:45:40

Re: New initscripts, static IP not working anymore

#3 2008-03-25 06:51:50

Re: New initscripts, static IP not working anymore

#4 2008-03-25 07:32:13

Re: New initscripts, static IP not working anymore

#5 2008-03-25 09:13:07

Re: New initscripts, static IP not working anymore

#6 2008-03-25 09:26:15

Re: New initscripts, static IP not working anymore

#7 2008-03-25 11:47:37

Re: New initscripts, static IP not working anymore

#8 2008-03-25 20:42:37

Re: New initscripts, static IP not working anymore

#9 2008-03-25 22:15:59

Re: New initscripts, static IP not working anymore

#10 2008-03-26 02:34:13

Re: New initscripts, static IP not working anymore

#11 2008-03-26 17:44:14

Re: New initscripts, static IP not working anymore

#12 2008-03-26 19:29:53

Re: New initscripts, static IP not working anymore

#13 2008-03-27 00:22:26

Re: New initscripts, static IP not working anymore

#14 2008-03-27 00:32:46

Re: New initscripts, static IP not working anymore

#15 2008-03-27 12:51:54

Re: New initscripts, static IP not working anymore

#16 2008-03-27 15:25:28

Re: New initscripts, static IP not working anymore

#17 2008-04-01 19:30:46

Re: New initscripts, static IP not working anymore

Board footer