Permission denied on some ignite clients but not all

[Mike Keys]

Ignite has been working great up until yesterday. Out of 8 clients, 5 will backup fine. 3 of my clients now give me the dreaded "Permission Denied" error when attempting to mount the local ignite directory for that client to the /var/opt/ignite/recovery/arch_mnt directory on the client.

I have verified that the /etc/exports file looks fine and have exported this using exportfs -av more times than I can shake a stick at. I have also verified that all critical directories have bin:bin ovnership.

I went to a good client and manually mounted the ignite server directory for the client to the arch_mnt directory on the client.

mount hpp1:/ignites/hpm1 /var/opt/ignite/recovery/arch_mnt

When I tried the same thing from one of the bad clients, I get the permission denied error.

Everything looks good, syslog.log on the client and ignite server shows nothing.


Should I bounce NFS? What else can I try?

[Fabian Briseño]

Hell Mike.
Have you done something to the failing servers since yesterday ?, patches ? or some kind of modification ?

What O.S do the clients have ?

What Ignite Version ?

[Fabian Briseño]

Mike.
Run command showmount -e on the clients that are failing, what do you see ?

[Mike Keys]

No modifications.

Ignite version on clients that are bad are C.7.8.201 and the same on the Ignite server.

A 'showmount -e' command on a bad client shows this:

showmount: pimprod: RPC: Program not registered

A 'showmount -e' command on a good client does not return the 'Program not registered' error.

What could be the cause of this?

[Mike Keys]

I bounced the NFS services on both the Igntie server and the clients. Now, NOTHING will run. The error I get when trying to do a Create Network Recovery Archive is that the NFS service not responding. It is timing out.

Do I need to reboot the Ignite server?

[Bill Hassell]

Try re-exporting everything on the Ignite server:

exportfs -av

[Mike Keys]

Bill: Tried that many, many times.

I'm downloading new Ignite version and will probably install on server and test server and try this again as well as rebooting the Ignite server.

[Fabian Briseño]

Hello Mike.
check out /etc/xtab are your exported filesystems there ?

what does command rpcinfo -p
shows ???

[Mike Keys]

# rpcinfo -p
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100068 2 udp 49153 cmsd
100068 3 udp 49153 cmsd
100068 4 udp 49153 cmsd
100068 5 udp 49153 cmsd
100083 1 tcp 49152 ttdbserver
100005 1 udp 52960 mountd
100005 3 udp 52960 mountd
100005 1 tcp 51688 mountd
100005 3 tcp 51688 mountd
100024 1 tcp 51778 status
100024 1 udp 53037 status
100021 1 tcp 51779 nlockmgr
100021 1 udp 53038 nlockmgr
100021 3 tcp 51780 nlockmgr
100021 3 udp 53039 nlockmgr
100021 4 tcp 51781 nlockmgr
100021 4 udp 53040 nlockmgr
100020 1 udp 4045 llockmgr
100020 1 tcp 4045 llockmgr
100021 2 tcp 51782 nlockmgr

[Mike Keys]

Rebooted Ignite server and all is well.

When in doubt, reboot.

Thread closed.