Operating System - HP-UX
1836519 Members
2935 Online
110101 Solutions
New Discussion

Re: Error NFS server (pid570@/net) not responding still trying

 
Eduardo Alfaia
Occasional Contributor

Error NFS server (pid570@/net) not responding still trying

Hi all, I had a big problem
I changed the IP number of the Network Interface and when initialize HP-UX get this error "NFS server (pid570@/net) not responding still trying" and the system remain trying and nothing.
What do I do?
Thanks
4 REPLIES 4
TTr
Honored Contributor

Re: Error NFS server (pid570@/net) not responding still trying

Check if the old IP is still in any of the files below and update it with the new IP.
/etc/hosts
/etc/rc.config.d/netconf
/etc/rc.config.d/nfsconf
/etc/exports
DNS maps in your DNS server

If you make any changes in any of the files above, ensure that you update the service that is related to it.
Dave Olker
Neighborhood Moderator

Re: Error NFS server (pid570@/net) not responding still trying

Hi Eduardo,

Does this system even use Automount/AutoFS? If not, you can simply disable it and never see this message again. I'm not sure which version of HP-UX you're running, but the method of disabling the automounter is nearly the same on all versions - set the AUTOFS variable to 0 in the /etc/rc.config.d/nfsconf file.

Regards,

Dave


I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Pedro Cirne
Esteemed Contributor

Re: Error NFS server (pid570@/net) not responding still trying

Hi Eduardo,

If you have changed the IP adress of the NFS server you'll need to unmount and mount again your NFS filesystems.

Regards,

Pedro

Rasheed Tamton
Honored Contributor

Re: Error NFS server (pid570@/net) not responding still trying

Hi,

If you have changed the IP address, then you first make sure you can resolve the name resolution/reverse lookup from both server and client.

Try ping from both ends and if you get issues make sure that you updated all the config files.

From the server side, it is better to re-run the exportfs command.

As Pedro said, from the client side, try to unmount the FS and re-mount it.

regards.