[solved]stopping Networkmanager: FAIL on shutdown or on restart

jithin1987 · 2009-09-12 14:33:10

Hi has anyone faced this issue. Its not actually troublesome but seeing it everytime I shutdown or reboot makes me thinking if anything is wrong with my setup.

Last edited by jithin1987 (2009-09-16 16:11:13)

Zack89 · 2009-09-12 16:27:17

Hello! In order for one of us to properly trouble shoot the issue, please report back more information so we can better understand whats going on. If you can report back what the error is (you can prolly simulate it by typing:

# /etc/rc.d/network restart

) and also the internet info in your /etc/rc.conf file including daemons.

jithin1987 · 2009-09-12 17:06:00

/etc/rc.d/networkmanager restart
:: Stopping NetworkManager                                                                                                                            [DONE]
:: Starting NetworkManager                                                                                                                             [DONE]

rc.conf

# 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="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
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.0.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 !network netfs crond hal networkmanager)

Last edited by jithin1987 (2009-09-12 17:06:41)

Zack89 · 2009-09-12 17:12:13

Hmm.. why do you have your network daemon disabled and using network manager instead?

jithin1987 · 2009-09-12 17:35:13

No specific reason. I have been using that for a long time. I haven been using that in kubuntu before, migrated yesterday. And I was able to make wireless work with knetworkmanager - kde front end to networkmanager.

Is there a better way to handle wireless, wired connections vpn and all. Functional wise I have no issues. Its just that its giving this error message during shutdown

combuster · 2009-09-12 18:14:37

I stumbled upon a post regarding this issue (but I can't find it now) when I was Ubuntu user while back... The trick was to give network manager enough time to shutdown properly, I can't remember how I did this...

jithin1987 · 2009-09-12 18:16:51

But is this safe enough to ignore? How is generally wired and wireless managed in arch. wicd ?

combuster · 2009-09-12 18:27:30

Yes, it's safe to ignore, network manager can not kill itself in time so hence the failed message, everything is perfectly normal as you can see when you restart networkmanager daemon in rc.d

Zack89 · 2009-09-13 02:23:18

Theres prolly a time delay you can add in with a specific flag. Same as if you do a shutdown for the entire system you can delay it.

jithin1987 · 2009-09-13 02:31:42

Zack89 wrote:

Theres prolly a time delay you can add in with a specific flag. Same as if you do a shutdown for the entire system you can delay it.

Can you give me any pointers as in how to do that?

piezoelectric · 2009-09-13 02:40:37

Zack89 wrote:

Hmm.. why do you have your network daemon disabled and using network manager instead?

I'm also a former (long time) ubuntu user who switch to arch within the past week. I did the same thing: disabled network and enabled networkmanager. (It's just a lot easier when you're often in new places with new wireless networks of various auth types, as well as VPNs and cell phone dongling.

Zack89 · 2009-09-13 03:20:51

Meh iono Ive always used network considering this on a desktop... Jithin, since networkmanager is a daemon vs a command.. I imagine you can open up a daemons settings correct? If so maybe you can specify a certain time delay either that or edit its source code since its prolly predetermined in it

jithin1987 · 2009-09-13 15:35:30

This is the code in /etc/rc.d/networkmanager which handles shutdown

stop)                                       
                stat_busy "Stopping NetworkManager" 
                        [ ! -z "$PID" ] && kill $PID &> /dev/null
                if [ $? -gt 0 ]; then                            
                        stat_fail                                
                else                                             
                        rm_daemon networkmanager                 
                        stat_done                                
                fi                                               
                ;;

This "[ ! -z "$PID" ] && kill $PID &> /dev/null" seems to be the issue.
In my case its returning 1 . When I ran manually. Can any one else running networkmanager please confirm?

Zack89 · 2009-09-14 00:18:05

Theres prolly something you can remove or whatever.. I did something a while ago when DHCPCD would timeout on me.. I removed the timeout portion of the code so it could NEVER time out and it fixed it.

and btw.. thats NOT the problem, thats just the command thats issued. The problem comes in WHEN it does that.. does networkmanager have a log it outputs to?

Last edited by Zack89 (2009-09-14 00:19:53)

nTia89 · 2009-09-14 09:22:57

i've resolved it .....
by appending DBUS before HAL in rc.conf ....

try ...

jithin1987 · 2009-09-14 11:49:32

nTia89 wrote:

i've resolved it .....
by appending DBUS before HAL in rc.conf ....
try ...

That fixed the issue completely

BlueSkyNis · 2009-10-31 23:10:42

Hey, thanks! It helped me too.

Cheers

nTia89 · 2009-11-01 08:35:28

i think it resolved the problem, because DBUS and HAL are not completely compatible in so things, ......

trusktr · 2010-02-24 11:59:33

Hey, me too! woo!

leeyee · 2010-04-11 13:03:53

nTia89 wrote:

i've resolved it .....
by appending DBUS before HAL in rc.conf ....
try ...

Sorry to bump this old thread.

First, I confirm this way fixes the problem. However, this issue reminds me another _quite-old/odd_ problem in my box, so I think it might be a good point to start here.(If not, I will start a new thread)

You know, when I didn't have dbus appended before HAL, NetworkMananger fails to stop on shutdown/restart. In the "restart" case, however, it seems that in the following, BIOS would fail to reload(just showing loading screen and freeze). I have to hard shutdown the computer and re-open it to boot correctly.

This kind thing happens even since my installation of Archlinux back to Jan. 2009. I mean, when some processes didn't stop correctly during restart, the following BIOS loading would always fail, at least on my thinkpad T400. It seems that system are not reset and RAMs are not cleaned up completely, so I am wondering this might be a bug of the shutdown script? Although I didn't look much into it, I still would like to know if anybody else have similar problems?

Thanks sincerely.

Arch Linux

#1 2009-09-12 14:33:10

[solved]stopping Networkmanager: FAIL on shutdown or on restart

#2 2009-09-12 16:27:17

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#3 2009-09-12 17:06:00

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#4 2009-09-12 17:12:13

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#5 2009-09-12 17:35:13

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#6 2009-09-12 18:14:37

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#7 2009-09-12 18:16:51

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#8 2009-09-12 18:27:30

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#9 2009-09-13 02:23:18

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#10 2009-09-13 02:31:42

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#11 2009-09-13 02:40:37

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#12 2009-09-13 03:20:51

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#13 2009-09-13 15:35:30

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#14 2009-09-14 00:18:05

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#15 2009-09-14 09:22:57

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#16 2009-09-14 11:49:32

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#17 2009-10-31 23:10:42

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#18 2009-11-01 08:35:28

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#19 2010-02-24 11:59:33

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

#20 2010-04-11 13:03:53

Re: [solved]stopping Networkmanager: FAIL on shutdown or on restart

Board footer