[clug] Fedora 15 boot issue (5 minutes pause)

[Eyal Lebedinsky]

I do have nfs mounts, and they, naturally, do not happen (fail) due
to networking not coming up. These mounts are not even looked at before
the 5 minutes expire.

One sees:


Started LSB: Port reservation utility.
Starting LSB: Bring up/down networking...
Started LSB: Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Bringing up loopback interface:
<5 minutes pause>
Starting LSB: Bring up/down networking failed, see 'systemctl status network.service' for details.

then later:

Starting Network Manager...
Starting Command Scheduler...
Started Command Scheduler.
Starting Machine Check Exception Logging Daemon...
Starting irqbalance daemon...
Starting Self Monitoring and Reporting Technology (SMART) Daemon...
Started Self Monitoring and Reporting Technology (SMART) Daemon.
Starting D-Bus System Message Bus...
Started SYSV: The rpcbind utility is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls on a server on that machine..
Started SYSV: This starts the SELinux Context Translation System Daemon.
Started ACPI Event Daemon.
Started Console Mouse manager.
Starting Network Manager failed, see 'systemctl status NetworkManager.service' for details.
Started Machine Check Exception Logging Daemon.
Started irqbalance daemon.
Starting /data1-nfs...

Eyal

On 09/12/11 21:30, David C wrote:
> Don't suppose you have any Nfs mounts in fstab? Combine foreground nfs mounts with gigabyte network negotiations and you could hit five minutes easily.
> That little gem screws us at work on a regular basis in AIX.
>
> On Sep 12, 2011 9:23 PM, "Eyal Lebedinsky" <eyal at eyal.emu.id.au <mailto:eyal at eyal.emu.id.au>> wrote:
>  > I did not try the live CD. Installation was a standard live upgrade
>  > (preupgrade etc.).
>  >
>  > I have only one NIC (wired Ethernet) so this is pretty trivial, nothing
>  > out of the ordinary.
>  >
>  > As F15 was out for a while now, I am surprised to have this trouble.
>  > But I still think that something else is wrong here. I *did* remove
>  > and then install NetworkManager just to be sure that this is not due
>  > to some upgrade fluff.
>  >
>  > Oh well, I will just not reboot anymore :-)
>  >
>  > cheers
>  >
>  > On 09/12/11 21:01, Owen wrote:
>  >>
>  >>> I do have it up and running, and no updates are available.
>  >>> It is just that booting is difficult (not that I do it too
>  >>> often though).
>  >>>
>  >>> I can see that the NetworkManager packages have an issue:
>  >>>
>  >>> yum says:
>  >>>
>  >>> Installed Packages
>  >>> NetworkManager.x86_64
>  >>> 1:0.9.0-1.fc15 @updates
>  >>> NetworkManager-glib.x86_64
>  >>> 1:0.9.0-1.fc15 installed
>  >>> NetworkManager-gnome.x86_64
>  >>> 1:0.9.0-1.fc15 @updates
>  >>> Available Packages
>  >>> NetworkManager-devel.i686
>  >>> 1:0.9.0-1.fc15 updates
>  >>> NetworkManager-devel.x86_64
>  >>> 1:0.9.0-1.fc15 updates
>  >>> NetworkManager-glib.i686
>  >>> 1:0.9.0-1.fc15 updates
>  >>> NetworkManager-glib-devel.i686
>  >>> 1:0.9.0-1.fc15 updates
>  >>> NetworkManager-glib-devel.x86_64
>  >>> 1:0.9.0-1.fc15 updates
>  >>> NetworkManager-openconnect.x86_64
>  >>> 0.8.999-1.fc15 fedora
>  >>> NetworkManager-openswan.x86_64
>  >>> 0.8.999-2.git20110721.fc15 updates
>  >>> NetworkManager-openvpn.x86_64
>  >>> 1:0.8.9997-2.git20110721.fc15 updates
>  >>> NetworkManager-pptp.x86_64
>  >>> 1:0.8.999-2.git20110721.fc15 updates
>  >>> NetworkManager-vpnc.x86_64
>  >>> 1:0.8.999-3.git20110721.fc15 updates
>  >>>
>  >>> but at the same time:
>  >>>
>  >>> # yum provides '*/init.d/NetworkManager'
>  >>> [trim]
>  >>> 1:NetworkManager-0.8.999-2.git20110509.fc15.x86_64 : Network
>  >>> connection manager and user applications
>  >>> Repo : fedora
>  >>> Matched from:
>  >>> Filename : /etc/rc.d/init.d/NetworkManager
>  >>>
>  >>> Now, I do not have init.d/NetworkManager (should I have one?)
>  >>> and it is not available in the latest packages.
>  >>>
>  >>> Eyal
>  >>>
>  >>> On 09/12/11 20:03, Owen wrote:
>  >>>>
>  >>>>> Having upgraded to F15, I found that the boot process pauses for 5
>  >>>>> minutes
>  >>>>> part way through.
>  >>>>>
>  >>>>> I traced this to
>  >>>>> nmcli -t --fields running nm status
>  >>>>> which is used during the part that brings up loopback. It should
>  >>>>> return
>  >>>>> "running" or "not running".
>  >>>>>
>  >>>>> NetworkManager is *not* up at that time, and it seems that when it
>  >>>>> comes
>  >>>>> up it takes a *very* long time to become responsive, so the 'nmcli'
>  >>>>> hangs.
>  >>>>>
>  >>>>> When the boot completes I need to switch to a text console and do
>  >>>>> service network start
>  >>>>> mount ...nfs shares and such...
>  >>>>> which succeeds without a hitch.
>  >>>>>
>  >>>>> I searched for a solution (or even a cause) and did not yet find
>  >>>>> it.
>  >>>>>
>  >>>>> Anyone encountered this? It seems to have been seen in F13 and F14
>  >>>>> too.
>  >>>>> Any clue will be appreciated.
>  >>>>>
>  >>>>> BTW, The gnome 3 desktop is very different from earlier fedora
>  >>>>> releases
>  >>>>> and it took me a while to "adjust" some of it to my comfort level.
>  >>>>> I
>  >>>>> am getting there slowly.
>  >>>>
>  >>>> I am pretty sure that this is a recognized nm problem with the F15
>  >>>> initial distro.
>  >>>>
>  >>>> Get it up and running and do an upgrade.
>  >>
>  >> I think I will bow out, you have the latest version. NetworkManager
>  >> selects the "best" network. Do you have a lan cable connection (to a
>  >> router), it will pick that first.
>  >>
>  >> Did it work ok as a live cd?
>  >>
>  >> Just what are you installing it from, F16 is about to hit the streets
>  >> (november).
>  >>
>  >> --
>  >> Owen
>  >
>  > --
>  > Eyal Lebedinsky (eyal at eyal.emu.id.au <mailto:eyal at eyal.emu.id.au>)
>  > --
>  > linux mailing list
>  > linux at lists.samba.org <mailto:linux at lists.samba.org>
>  > https://lists.samba.org/mailman/listinfo/linux

-- 
Eyal Lebedinsky	(eyal at eyal.emu.id.au)