local loopback interface isn't brought up on boot

[Erik]

Apple PowerBook G4 (5,4)
Ubuntu 7.04 (PPC) up to date as of 07/02/07

The lo interface is not automatically brought up on boot.

It should be defined in /etc/network/interfaces otherwise all sorts of things don't work like mail delivery etc.

[Brian Murray (brian-murray)]

Thanks for your bug report. Could you add your /etc/network/interfaces config file, as installed, to it? Thanks in advance.

[Erik (echakr)]

My /etc/network/interfaces has one line only

'auto eth1'

I suspect this file may have been modified by network-manager as I'm
sure there was more stuff in it before...

It should obviously have 'auto lo' in it somewhere.

On Wed, 2007-02-07 at 18:34 +0000, Brian Murray wrote:
> Thanks for your bug report. Could you add your /etc/network/interfaces
> config file, as installed, to it? Thanks in advance.
>
> ** Changed in: Ubuntu
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>

[Erik (echakr)]

Apologies I misread the interfaces file - there is are a lot of carriage
returns in the file so when I ran cat /etc/network/interfaces it looked
like it only had one line in it. I don't know the reason why the file is
formatted like this...

Please find complete file attached.

iface lo inet loopback

iface eth1 inet
address 192.168.1.11
netmask 255.255.255.0
gateway 192.168.1.1
wireless-essid BTVOYAGER2091-79
ap 00:12:A9:03:F8:9D

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto eth1

[EricDHH (ericdhh)]

Confirmed on Feisty-Beta.

root@ingerimm:/home/eric# more /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

root@ingerimm:/home/eric# ifconfig
eth1 Protokoll:Ethernet Hardware Adresse 00:1A:92:22:31:C5
          inet Adresse:192.168.1.101 Bcast:192.168.1.255 Maske:255.255.255.0
          inet6 Adresse: fe80::21a:92ff:fe22:31c5/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:129 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:12248 (11.9 KiB) TX bytes:18622 (18.1 KiB)
          Interrupt:23

The loopback is not up at boot, that mess up the gnome-session start here. This will take several minutes with error dialog "gnome-session problem" at the end.

Bye
Eric

[Stephen Irons (stephen-irons)]

This happens on Fiesty release too. At home, I have no wired network connected; I use GnomePPP to dial in to the ISP.
Updated to repositories on 2007-05-14. Kernel 2.6.20-15-generic.

Immediately after startup::

xxxx$ ping localhost
connect: Network is unreachable

xxxx$ ifconfig
eth1 Link encap:Ethernet HWaddr 00:15:C5:00:01:5A
          UP 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:18

There is no 'lo' interface.

This causes all sorts of problems (startup delays, slow application launch, slow response to power button and panel Quit applet, Evince and EOG not printing, etc...)

xxxx$ sudo ifup lo
ifup: interface lo already configured

This is strange, ifconfig did not see 'lo'

xxxx$ sudo ifdown lo
xxxx$ sudo ifup lo
xxxx$ ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.033 ms

After this, power button works properly, Evince and EOG print properly, etc.

/etc/hosts, /etc/network/interfaces seem to be correct:

xxxx$ cat /etc/hosts
127.0.0.1 localhost xxxx
127.0.1.1 xxxx

# The following lines are desirable for IPv6 capable hosts
#::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

xxxx$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

#iface eth0 inet static
#address 172.25.143.31
#netmask 255.255.0.0
#gateway 172.25.161.1

#auto eth0

#iface eth1 inet dhcp

#auto eth1

So everything seems to be set up properly, but it appears that nothing calls /etc/init.d/loopback

Any ideas?

[Henrik Nilsen Omma (henrik)]

Hi, did either of you get a chance to test this on Gutsy?

It would be interesting to see a copy of /etc/network/interfaces right after install before NM does it's first connect to a wireless network. Also, what hardware are you using? The output from 'lspci -v' would be good. Thanks.

[Alexander Sack (asac)]

network-manager doesn't touch lo interfaces from what i know ... rassigning to ifupdown package in the hope that its a better place to track this.

[Nick Jenkins (nickpj)]

Running 8.04 RC Hardy Heron, experiencing a similar problem. Upgraded a few days ago from 7.10, and in 7.10 I could not print reliably in evince (ended up assuming it was a buggy app and installing acroread instead), and I would get a ~3 minute delay on login. The same annoying ~3 minute delay persisted in 8.04 RC, and furthermore I would often get a gnome session error on login. By good luck I came across this bug (after many unsuccessful attempts to google for similar problem reports). From the comments here, I then tried pinging localhost, and got no answer, and "ifconfig" showed no loopback interface. The solution was very simple - just add these 3 lines to /etc/network/interfaces :
# The loopback network interface
auto lo
iface lo inet loopback

... and I rebooted and now logging in is fast and quick. Yay! I have no idea where the loopback interface lines went to from the interfaces file. Maybe some bit of software deleted it? Maybe I deleted it? Seems a bit unlikely to me though, as I have no recollection of doing that.

[Jayson Rowe (jayson.rowe)]

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!