NFS not starting on Fedora 14

**SimonWEC** · 31st May 2011, 09:07 PM

Hello,

I've just updated to Fedora 14 from Fc10 via preupgrade ( going Fc10 - Fc11 - Fc12 -Fc14 ). The process has been pretty good except that now in Fc14 I have problems with NFS and have lost networking. A portion of the bootlog shows this:

Code:

Starting cups: Starting LSB: Mount and unmount network filesystems....
                                                           [  OK  ]
Starting LSB: Moves the generated persistent udev rules to /etc/udev/rules.d...
Retrigger failed udev events                               [  OK  ]
Starting LSB: start and stop NetworkManager...
Setting network parameters...                              [  OK  ]
Starting NetworkManager daemon:                            [  OK  ]
Starting LSB: Daemon to access a smart card using PC/SC...
Starting PC/SC smart card daemon (pcscd): Starting HAL Hardware Manager...
                                                           [  OK  ]
Starting LSB: Starts the Name Switch Cache Daemon...
Starting LSB: Start up the NFS server sevice...
Starting nscd:                                             [  OK  ]
Starting rpcsvcgssd (via systemctl):  Reloading nscd: 
Starting LSB: Start up the NFS server sevice failed.
Starting LSB: Starts the RPCSEC GSS server daemon...
Starting Bluetooth Manager...
Starting systemd Logging Daemon...
Starting LSB: Start up the OpenSSH server daemon...
Starting sshd:                                             [  OK  ]

It seems to show that the NFS service starts but then shows it failed. Typing chkconfig shows NFS as running though:

Code:

netconsole      0:off   1:off   2:off   3:off   4:off   5:off   6:off
netfs           0:off   1:off   2:on    3:on    4:on    5:on    6:off
network         0:off   1:off   2:on    3:on    4:on    5:on    6:off
nfs             0:off   1:off   2:on    3:on    4:on    5:on    6:off
nfslock         0:off   1:off   2:on    3:on    4:on    5:on    6:off
nscd            0:off   1:off   2:on    3:on    4:on    5:on    6:off
ntpd            0:off   1:off   2:off   3:off   4:off   5:off   6:off
ntpdate         0:off   1:off   2:off   3:off   4:off   5:off   6:off

In case I had issues with iptables I set them accordingly and tried 'service nfs restart'

Code:

[root@HPWorkstation rules.d]# service nfs restart
Restarting nfs (via systemctl):  Job failed, see system logs for details.
                                                           [FAILED]

The message I get in /var/log/messages is:

Code:

May 31 20:57:29 HPWorkstation init[1]: nfs.service operation timed out. Terminating.
May 31 20:57:29 HPWorkstation init[1]: Unit nfs.service entered failed state.

As another symptom I am noticing a very long boot time into Fc14, looking at the verbose output it hangs for over a minute at "Bringing up Loopback Interface". Perhaps this is part of the same problem? Needless to say I am perplexed and any help would be appreciated.

Best wishes
//Simon

**jpollard** · 31st May 2011, 09:16 PM

What does "rpcinfo" show?

If it fails, then you likely forgot the rpcbind process (chkconfig rpcbind on) which is needed for NFS.

Also check the firewall and make sure portmap(port111) is available.

**scott32746** · 31st May 2011, 09:37 PM

Hello,

You said your network in not working ? Without network NFS is not going to work

POST:
# ifconfig -a
#lspci |grep -i eth
# ls -l /etc/sysconfig/network-scripts/ifcfg-*

**SimonWEC** · 31st May 2011, 09:45 PM

Hello,

just checked and rpcbind is on; rpcinfo gives this:

Code:

  100000    4    tcp6      ::.0.111               portmapper superuser
    100000    3    tcp6      ::.0.111               portmapper superuser
    100000    4    udp6      ::.0.111               portmapper superuser
    100000    3    udp6      ::.0.111               portmapper superuser
    100000    4    tcp       0.0.0.0.0.111          portmapper superuser
    100000    3    tcp       0.0.0.0.0.111          portmapper superuser
    100000    2    tcp       0.0.0.0.0.111          portmapper superuser
    100000    4    udp       0.0.0.0.0.111          portmapper superuser
    100000    3    udp       0.0.0.0.0.111          portmapper superuser
    100000    2    udp       0.0.0.0.0.111          portmapper superuser
    100000    4    local     /var/run/rpcbind.sock  portmapper superuser
    100000    3    local     /var/run/rpcbind.sock  portmapper superuser
    100024    1    udp       0.0.0.0.15.163         status     29
    100024    1    tcp       0.0.0.0.15.163         status     29
    100024    1    udp6      ::.15.163              status     29
    100024    1    tcp6      ::.15.163              status     29

Here's the output of iptables -nvL:

Code:

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
 4694 2186K ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
    0     0 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0           
 1695  247K ACCEPT     all  --  eth+   *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  ippp+  *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0           udp dpt:111 state NEW 
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:111 state NEW 
    0     0 ACCEPT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0           udp dpts:4002:4006 state NEW 
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpts:4002:4006 state NEW 
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:2049 
    0     0 ACCEPT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW udp dpt:137 
    0     0 ACCEPT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW udp dpt:138 
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:139 
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:445 
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22 
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:80 
    0     0 REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited 

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
    0     0 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  eth+   *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  ippp+  *       0.0.0.0/0            0.0.0.0/0           
    0     0 REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited 

Chain OUTPUT (policy ACCEPT 3037 packets, 1296K bytes)
 pkts bytes target     prot opt in     out     source               destination

---------- Post added at 09:45 PM ---------- Previous post was at 09:37 PM ----------

ifconfig -a:

Code:

eth0      Link encap:Ethernet  HWaddr 00:11:85:AE:DD:AC  
          inet addr:192.168.1.25  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::211:85ff:feae:ddac/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9572 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6229 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3222007 (3.0 MiB)  TX bytes:1851890 (1.7 MiB)
          Interrupt:21 Base address:0x8000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:579 errors:0 dropped:0 overruns:0 frame:0
          TX packets:579 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:80814 (78.9 KiB)  TX bytes:80814 (78.9 KiB)

lspci | grep -i eth:

Code:

00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)

ls -l /etc/sysconfig/network-scripts/ifcfg-*:

Code:

-rw-r--r--. 3 root root 429 Sep 13  2010 /etc/sysconfig/network-scripts/ifcfg-eth0
-rw-r--r--. 1 root root 254 Feb 25 20:23 /etc/sysconfig/network-scripts/ifcfg-lo

I do have a net connection, just not NFS - as I said it isn't responding to 'service nfs restart'.
Thanks for the response by the way!!

**SimonWEC** · 1st June 2011, 07:53 PM

I have no idea what the issue was, but suspect it was related to the bootloader...

Looking at the support documents for 'Preupgrade' one finds that the process saves various configuration files on the system with '.rmpnew' or '.rpmsave' depending upon whether or not it updates locally modified files. Thinking that I might have conflicting network scripts I knocked up a quick and dirty bit of Python to rename all the 'file_name.rpmnew' config files to 'file_name'.

I then rebooted, but to no avail as the problem persisted.

My last resort was a clean install so I put in the Fc10 DVD, which gave me the option of updating a previous installation, so I tried, just in case. After a menu where you select boot and storage drives it then gives the option of updating the bootloader, so I gave that a try... it chugged away for a bit, went off and thought about something for a minute or so and then came back saying installation was finished and offered a reboot prompt.

So I rebooted... and... everything is fine! Iptables, nfs, loopback all working. I just had to reset inittab to default 5 and recover my nfs config files from back up and all is well.

I hope this might help anyone else with the same issue.
Best wishes

//Simon

**jobarjo** · 14th July 2011, 08:59 PM

Hi

I have the same problem after upgrading from fedora12 to 14, nfs won't start.
Nothing in /var/log/message except:

Code:

nfs.service operation timed out. Terminating.
Unit nfs.service entered failed state.

I haven't understood what you did with your fedora 10 dvd. Did you reinstall FC10??

rpcinfo:

Code:

# rpcinfo
   program version netid     address                service    owner
    100000    4    tcp6      ::.0.111               portmapper superuser
    100000    3    tcp6      ::.0.111               portmapper superuser
    100000    4    udp6      ::.0.111               portmapper superuser
    100000    3    udp6      ::.0.111               portmapper superuser
    100000    4    tcp       0.0.0.0.0.111          portmapper superuser
    100000    3    tcp       0.0.0.0.0.111          portmapper superuser
    100000    2    tcp       0.0.0.0.0.111          portmapper superuser
    100000    4    udp       0.0.0.0.0.111          portmapper superuser
    100000    3    udp       0.0.0.0.0.111          portmapper superuser
    100000    2    udp       0.0.0.0.0.111          portmapper superuser
    100000    4    local     /var/run/rpcbind.sock  portmapper superuser
    100000    3    local     /var/run/rpcbind.sock  portmapper superuser

**jpollard** · 15th July 2011, 12:38 PM

Are you on Fedora 14 or 15?

IF fourteen, then try manually starting nfs - "service nfs start", and then see if the service is running ("rpcinfo" will do that).

If that works, then you need to enable NFS for boot - "chkconfig nfs on"

Next you will need to check the server from a client - "rpcinfo -p <server>", and you should see the same list of services as you see on the server.

If you don't, then it is likely the firewall is blocking you.

Another potential problem is that SELinux is blocking - you need to enable NFS, usually only one of "nfs_export_all_ro" or "nfs_export_all_rw" is needed.

One last thing... If your export is for a separate filesystem you may need to reset the SELinux labels. A "restorecon <path-to-export>" should do the trick. There are some label changes since Fedora 10, and these can cause problems.

**jobarjo** · 15th July 2011, 01:17 PM

I'm on fedora 14
I did start the nfs service manually.

It simply fails.

The firewall is disabled (service iptables stop)
I don't see why the firewall would prevent the service from starting.

selinux is also disabled.

The strange thing is that I tried to execute directly /usr/sbin/rpc.nfsd (that is in the /etc/init.d/nfs script), and it seems to work.

So I tried to add some logger instruction into the nfs script, and it seems that they are not executed by service nfs start.

But when I execute the init script directly, it works.
Then I do a service nfs stop, it works.
but it won't start again, unless I launch the nfs script.

It seems that the problem is related to the new service starting mechanism, which seems complicated and problematic.

I also can't start libvirtd.
How can I debug this system? What is the name of this new starting mechanism?

EDIT:
After investigating a little, it seems that I have both upstart and systemd rpms installed.

Code:

# service nfs status
rpcsvcgssd.service - LSB: Starts the RPCSEC GSS server daemon
          Loaded: loaded (/etc/rc.d/init.d/rpcsvcgssd)
          Active: active (exited) since [Fri, 15 Jul 2011 14:15:54 +0200; 28min ago]
         Process: 30892 (/etc/rc.d/init.d/rpcsvcgssd stop, code=exited, status=6/NOTCONFIGURED)
         Process: 31021 (/etc/rc.d/init.d/rpcsvcgssd start, code=exited, status=6/NOTCONFIGURED)
          CGroup: name=systemd:/systemd-1/rpcsvcgssd.service
nfs.service - LSB: Start up the NFS server sevice
          Loaded: loaded (/etc/rc.d/init.d/nfs)
          Active: failed since [Fri, 15 Jul 2011 14:15:54 +0200; 28min ago]
         Process: 30855 (/etc/rc.d/init.d/nfs stop, code=exited, status=0/SUCCESS)
         Process: 30903 (/etc/rc.d/init.d/nfs start, code=killed, signal=TERM)
          CGroup: name=systemd:/systemd-1/nfs.service
nfs.service - LSB: Start up the NFS server sevice
          Loaded: loaded (/etc/rc.d/init.d/nfs)
          Active: failed since [Fri, 15 Jul 2011 14:15:54 +0200; 28min ago]
         Process: 30855 (/etc/rc.d/init.d/nfs stop, code=exited, status=0/SUCCESS)
         Process: 30903 (/etc/rc.d/init.d/nfs start, code=killed, signal=TERM)
          CGroup: name=systemd:/systemd-1/nfs.service
nfs.service - LSB: Start up the NFS server sevice
          Loaded: loaded (/etc/rc.d/init.d/nfs)
          Active: failed since [Fri, 15 Jul 2011 14:15:54 +0200; 28min ago]
         Process: 30855 (/etc/rc.d/init.d/nfs stop, code=exited, status=0/SUCCESS)
         Process: 30903 (/etc/rc.d/init.d/nfs start, code=killed, signal=TERM)
          CGroup: name=systemd:/systemd-1/nfs.service

Is this upstart or systemd?
As it seems very different from FC12, it looks like it is systemd.
How can I disable systemd and use the standard FC14 upstart system?

Thanks

**jpollard** · 15th July 2011, 02:03 PM

Look at the file ("ls -lZ /sbin/init") and see what it is pointing to.

Normal F14 has it pointing to upstart (the full path is /sbin/upstart).

Once changed, a reboot should switch you to something that works.

From what I've been reading, a bit under half the problems are being caused by systemd. It is faster in a startup, but I think they have introduced a severe weakness at the same time.

**jobarjo** · 15th July 2011, 09:57 PM

Hi

/sbin/init is indeed pointing to ../bin/systemd

I tried what you said, changing it to /sbin/upstart, and boot failed at the moment of switching root.
By luck, a shell prompt was there and I could revert to systemd.

I saw that init could also be choosen with the kernel parameter init=/sbin/upstart
I will try this later...

I don't know why systemd was installed by pre-upgrade. It is certainly a bug.

Thanks for your help.

**SimonWEC** · 18th July 2011, 12:22 PM

Hello,

With my FC14 NFS problems - neither

Code:

service nfs restart

or

Code:

service nfs stop / start

worked, nfs simply refused to get going. I did follow the other advice given, but to no avail.

Upon re-reading my earlier post I realise I did make a typo error as my last resort was to put in the FC14 DVD ( NOT FC10 ) and try a clean install - in the end I didn't do this but chose to update. I can't remember the sequence but my earlier post was written closer to the time when it was fresh in my memory:

My last resort was a clean install so I put in the Fc14 DVD, which gave me the option of updating a previous installation, so I tried, just in case. After a menu where you select boot and storage drives it then gives the option of updating the bootloader, so I gave that a try... it chugged away for a bit, went off and thought about something for a minute or so and then came back saying installation was finished and offered a reboot prompt.

It seems like this might have been related to a boot loader issue, or some junk left over from FC10 in the start up scripts as it fixed the problem in one fell swoop.

Best wishes
//Simon

NFS not starting on Fedora 14

Thread Tools

Search Thread

Display

NFS not starting on Fedora 14

Re: NFS not starting on Fedora 14

Re: NFS not starting on Fedora 14

Re: NFS not starting on Fedora 14

Re: NFS not starting on Fedora 14

Re: NFS not starting on Fedora 14

Re: NFS not starting on Fedora 14

Re: NFS not starting on Fedora 14

Re: NFS not starting on Fedora 14

Re: NFS not starting on Fedora 14

Re: NFS not starting on Fedora 14

Similar Threads

starting in fedora

Fedora 9: NoClassDefFoundError (LogFactory) starting Tomcat from Fedora Eclipse

fedora not starting

Long delays starting up, and starting most programs.

Starting Tomcat - How to know when it finish starting up

Tags for this Thread

Posting Permissions

User Tag List