Forum Discussion

NetPaul's avatar
NetPaul
Level 3
8 years ago
Solved

The appliance <appliance host name> was unable to restart NFS sharing services

If anyone gets the following error from your appliance: 

 

The appliance <appliance host name> was unable to restart NFS sharing services. In order to clear the issue you way want to reboot your appliance. If the problem persists please contact support. 

 

The cause is that the rpcbind service has gone down. To solve it go to the command line and run the following commands:

 

service rpcbind start

service nfs start

 

A lot quicker and less disruptive than a reboot.

 

I can't find any technotes or bug fixes for this so I would be interested to know why rpcbind does stop. Maybe something for Veritas to investigate?

 

We are currently running Netbackup 3.0 on our appliances.

  • Hi

    I did face similar issue sometime back... here is what I got from VRTS:

    "ISSUE            : Getting alerts due to nfs service failing to restart after crash.
    ERROR CODE/MESSAGE    : unable to restart NFS sharing services
    ENVIRONMENT/CONDITIONS     : Netbackup 5230 Appliance.
    SOLUTION/WORKAROUND     :  found bug in current rpcbind package from redhat. need to update the rpcbind to latest version to fix the issue. Engineering working to release eeb to fix the issue.
    Advised to restart the nfs and rpc services through cron once in week or after problem is seen as temporary resort till eeb is released."

    I remeber I ended up installing manually rpcbind on my appliance... Check with vrts if eeb was not released already...

5 Replies

  • Hi

    I did face similar issue sometime back... here is what I got from VRTS:

    "ISSUE            : Getting alerts due to nfs service failing to restart after crash.
    ERROR CODE/MESSAGE    : unable to restart NFS sharing services
    ENVIRONMENT/CONDITIONS     : Netbackup 5230 Appliance.
    SOLUTION/WORKAROUND     :  found bug in current rpcbind package from redhat. need to update the rpcbind to latest version to fix the issue. Engineering working to release eeb to fix the issue.
    Advised to restart the nfs and rpc services through cron once in week or after problem is seen as temporary resort till eeb is released."

    I remeber I ended up installing manually rpcbind on my appliance... Check with vrts if eeb was not released already...

    • jnardello's avatar
      jnardello
      Moderator

      For anyone still having this issue, this was an issue with release 1 of ET3925629 (the giant security update to the 34 rpms).

      If you get R2 from support this particular issue is fixed.

       

    • NetPaul's avatar
      NetPaul
      Level 3

      Thanks quebek :smileyhappy:

      I will keep an eye out for that eeb