loopback error message at boot time

Athunye · 2010-06-01 22:04:15

I get this message at boot time:

lo up error fetching up interface information: Device not found.
(some other stuff I can't remember)
SIOCADDRT No such process

HOSTNAME="vaio" in /etc/rc.conf.

And heres my /etc/hosts file:

#<ip-address>    <hostname.domain.org>    <hostname>
127.0.0.1       localhost.localdomain    localhost   vaio
192.168.1.10    vaio.domain.org   localhost  vaio
192.168.1.2    cati
# End of file

I have no idea where to go from here. Any help would be appreciated.

EDIT: I run /etc/rc.d/network restart and got the same message I see when booting the system.
Here it goes the entire message:

vaio@root, Tue Jun 01 20:43:31 
/home/nando #  
bash >>> /etc/rc.d/network restart
:: Stopping Network                                                                                                   [DONE] 
:: Starting Network                                                                                                   [BUSY] up: error fetching interface information: Device not found
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1056 (1.0 Kb)  TX bytes:1056 (1.0 Kb)

SIOCADDRT: No such process
                                                                                                                      [FAIL] 
vaio@root, Tue Jun 01 20:46:07 
/home/nando #  
bash >>>

Last edited by Athunye (2010-06-01 23:51:04)

Surgat_ · 2010-06-02 12:05:47

I don't know about that error, but your /etc/hosts seems weird to me. I assume that 192.168.1.10 is your IP, so why are you putting it into the hosts file? If you need to access your own computer via network, just use 127.0.0.1, which will be faster. I don't think it's a good idea to attach the same host name for two different IPs.

Athunye · 2010-06-02 13:25:37

Thanks for the replay. I was starting to think that nobody would answer...

I use that second line on /etc/hosts because of this:
From http://wiki.archlinux.org/index.php/Beg … tc.2Fhosts

If you use a static IP, add another line using the syntax: <static-IP> <hostname.domainname.org> <hostname> e.g.:
192.168.1.100 yourhostname.domain.org  yourhostname

Bolts · 2010-06-02 19:15:24

Could you post your whole rc.conf and what interfaces are shown with `ifconfig -a`?

Athunye · 2010-06-02 19:42:45

/etc/rc.conf

#
# /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", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# 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.UTF-8"
HARDWARECLOCK=""
TIMEZONE="America/Sao_Paulo"
KEYMAP="br-abnt2"
CONSOLEFONT="lat9w-16"
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="vaio"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# 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
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#wlan0="wlan0 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255"
#eth0="dhcp"
#lo="lo 127.0.0.1"
INTERFACES=(lo wlan0)

# 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 192.168.1.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=(static_wireless)

# -----------------------------------------------------------------------
# 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 dbus hal @iptables network @net-profiles !netfs crond alsa)

ifconfig -a

vaio@nando, Wed Jun 02 16:35:35 
~ $  
bash >>> ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:24:BE:42:63:DF  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:16 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

vboxnet0  Link encap:Ethernet  HWaddr 0A:00:27:00:00:00  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:26:5E:F6:4A:85  
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::226:5eff:fef6:4a85/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:752011 errors:0 dropped:0 overruns:0 frame:0
          TX packets:664681 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:662203200 (631.5 Mb)  TX bytes:291397492 (277.8 Mb)

vaio@nando, Wed Jun 02 16:35:39 
~ $  
bash >>>

I don't actually use eth0.
I set wlan0 through netcfg.

Bolts · 2010-06-03 20:15:17

Try removing `network' from your daemons array. Since you're using netcfg, you don't need it because rc.sysinit brings up lo and netcfg will bring up wlan0.

Athunye · 2010-06-04 00:39:48

I removed 'network' from DAEMONS in /etc/rc.conf but the 'error' message was still shown.

Thankfully, that lo 'problem' was not actually a problem. The system was working just fine.

I reinstalled the system (I had some spare time) and did the same network configuration. I noticed that on the first boot after the install the damn message did not show up. Did some tests, configuring /etc/hosts differently and still no 'error' message. I don't know what the problem was. The error message in the previous install showed up just on the first reboot when the installation finished, and continued no matter what configurations I tried afterwards.

I installed Arch in at least 9 different hardware (I know loopback has nothing to do with hardware) since kernel 2.6.14 and tried lots of window managers from the *box family to xmonad. Never saw something like that. I'm glad it is okay now.
That message embarrassed me because other people saw it.

Anyway, Arch as the distro of my dreams.

Arch Linux

#1 2010-06-01 22:04:15

loopback error message at boot time

#2 2010-06-02 12:05:47

Re: loopback error message at boot time

#3 2010-06-02 13:25:37

Re: loopback error message at boot time

#4 2010-06-02 19:15:24

Re: loopback error message at boot time

#5 2010-06-02 19:42:45

Re: loopback error message at boot time

#6 2010-06-03 20:15:17

Re: loopback error message at boot time

#7 2010-06-04 00:39:48

Re: loopback error message at boot time

Board footer