Weird issue starting network at boot [Solved]

psilo357 · 2009-12-19 19:46:19

So, whenever i bootup, when it comes to starting the network, it hangs for a few seconds, then says 'fail', however, whenever i get gnome up and working, the connection is working just fine, so far, i have tried to increase the timeout though it doesn't really seem to make it wait any longer during boot...here is my rc.conf if it helps anyone, also, i am trying to connect to some NFS shares from my freeNAS box on boot, but since that fails, the network shares normally do to, but after booted, i can just do mount -a and they all connect just fine...its weird

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="localtime"
TIMEZONE="America/Chicago"
KEYMAP="us"
CONSOLEFONT=
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=(sky2 slhc snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore !usblp)

# 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="myhost"

# 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
#eth0="dhcp"
eth0="dhcp"
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 192.168.2.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 dbus hal fam network rpcbind nfs-common netfs crond)

also, i do have 'myhost' added to my hosts file as well, did so during setup...

anyone got any ideas?

Thanks

Last edited by psilo357 (2009-12-21 00:02:46)

jasonwryan · 2009-12-19 19:53:08

You could always background network in your DAEMONS array...

psilo357 · 2009-12-19 20:13:33

ok, should i background everything else that relies on the network being ready too? like nfs-common and netfs? also, with the order i have listed above, it seems rpcbind still starts up before network does...any idea on that?

I will give this stuff a go and see what happens...

thanks

psilo357 · 2009-12-19 20:27:43

alright, if just backgrounded 'network' it woudl cause rpcbind to start after it, but fail, so i backgrounded them all, and while network no longer says FAIL while booting, the network drives still don't mount, i still have to issue a mount -a after boot to get everything mounted...

thanks for the tip though. I don't mind it not running in background and waiting an extra few seconds to get everything setup as i want it to be as soon as i am logged in, just want it to all start correctly.

EDIT: alright, all network drives ARE mounting correctly on boot if nothing is in background, but i still don't like that network says FAIL when it is starting up, though it is apparently working...

all help is appreciated.

Last edited by psilo357 (2009-12-19 20:31:27)

jasonwryan · 2009-12-19 20:47:59

You could try

DAEMONS=(syslog-ng hal fam network netfs nfs-common crond  @rpcbind)

otherwise, you might want to look at using networkmanager.

psilo357 · 2009-12-20 19:23:01

yeah, that wouldn't work, i need rpcbind running before netfs/nfs-common start up and mount all my network drives...at least i think.

Anyways, i will give it a go...im just being picky anyways, even though it says FAIL on the boot screen, everything is mounting just fine and internet and all available, just weird that it shows like that.

peace

psilo357 · 2009-12-21 00:02:28

alright, after watching bootup a little closer, i noticed that rpcbind was starting up twice, even though it is only in my daemons array once...

DAEMONS=(syslog-ng dbus hal fam network rpcbind nfs-common netfs crond)

it appears it is starting up right after hal, so i guess fam has a dependency on it, anyways, by removing rpcbind all together, it still starts up, and network now doesn't say 'FAIL' when it starts up, it could have been rpcbind part 2 saying it the whole time as well,b ut i have a large monitor, so its hard to tell for sure.

jasonwryan · 2009-12-21 00:06:11

Good stuff. You also don't need dbus in there - hal will start it.

Arch Linux

#1 2009-12-19 19:46:19

Weird issue starting network at boot [Solved]

#2 2009-12-19 19:53:08

Re: Weird issue starting network at boot [Solved]

#3 2009-12-19 20:13:33

Re: Weird issue starting network at boot [Solved]

#4 2009-12-19 20:27:43

Re: Weird issue starting network at boot [Solved]

#5 2009-12-19 20:47:59

Re: Weird issue starting network at boot [Solved]

#6 2009-12-20 19:23:01

Re: Weird issue starting network at boot [Solved]

#7 2009-12-21 00:02:28

Re: Weird issue starting network at boot [Solved]

#8 2009-12-21 00:06:11

Re: Weird issue starting network at boot [Solved]

Board footer