PDA

View Full Version : [ubuntu] "Starting NFS kernel Daemon" Hanging

GriFF3n
October 9th, 2009, 01:12 PM
I have 9.04 Ubuntu server running. I just did an update/upgrade on the system and performed a reboot. Now when i start the system it loads to the "Starting NFS kernel Daemon" and just hangs there. I'm unable to get the system up and I can not ssh into it. Any suggestions?
karlson
October 9th, 2009, 01:26 PM
I have 9.04 Ubuntu server running. I just did an update/upgrade on the system and performed a reboot. Now when i start the system it loads to the "Starting NFS kernel Daemon" and just hangs there. I'm unable to get the system up and I can not ssh into it. Any suggestions?

Boot into single user mode.
disable nfsd from running.

Then once booted. Try Starting it manually to see what happens.
GriFF3n
October 9th, 2009, 01:31 PM
Boot into single user mode.
disable nfsd from running.

Then once booted. Try Starting it manually to see what happens.

How do I boot into "single user mode"?
karlson
October 9th, 2009, 01:52 PM
How do I boot into "single user mode"?

When you get the grub tickdown you can press ESC then a on the selected line and type in single at the end of the boot string.

Then press Enter.
GriFF3n
October 11th, 2009, 11:04 AM
When you get the grub tickdown you can press ESC then a on the selected line and type in single at the end of the boot string.

Then press Enter.

Disabled nfs-kernel-server, but now it hangs at "Starting Samba daemons". Going to disable that and see what happens.
GriFF3n
October 11th, 2009, 11:10 AM
Ok, she boots up, but for some reason it can not obtain an ip address. ifconfig shows no ip address. Samba and NFS were disabled from startup. When I boot the recover kernel, I can startup as "netroot" and will receive a default IP of 192.168.1.101. Any time I try to reload into my normal kernel, it is unalbe to obtain the static ip I have assigned it. Any other suggestions?
GriFF3n
October 11th, 2009, 03:01 PM
Ok, so trying to restart my network through:



sudo /etc/init.d/networking restart

causes this error:



ifdown: failed to open statefile /var/run/network/ifstate: no such file or directory

ifup: failed to open statefile /var/run/network/ifstate: no such file or directory

still there, but i get an error of:


ifdown: failed to open statefile /var/run/network/ifstate: Is a directory

ifup: failed to open statefile /var/run/network/ifstate: Is a directory

Any ideas?
karlson
October 12th, 2009, 08:02 AM
Ok, so trying to restart my network through:


Any ideas?

Does /var/run/network exist?
GriFF3n
October 12th, 2009, 11:31 AM
Does /var/run/network exist?

I have to create it everytime i restart the server. Once I make the directory and restart the network, everything works. It's listed as a bug on launchpad, but the solution is to delete the file "/etc/udev/rules.d/85-ifupdown.rules", which I do not have. Here's the launchpad LINK (https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/377432/).
GriFF3n
October 13th, 2009, 02:08 PM
Bump, still having the same problem. Any suggestions?
karlson
October 13th, 2009, 03:16 PM
Bump, still having the same problem. Any suggestions?

You can try a few things:

1. Try manually stopping and Starting NetworkManager to see if that removes the directory.
2. Check the rc Scripts if any of them refer to /var/run/network
3. based on what I see in /etc/network/if-up.d/mountfs it creates that directory, so you may have to debug the script to see why it doesn't in your case.