Cifsclient problem (NFS getattr failed for server) !

[Ivan Azuara]

Hi !

I have a samba client configuration scheme between a Windows 2000 Server and HPUX 11.00 server.

The samba version on hpux is:

# cifsclient status
Path: /opt/cifsclient/sbin/cifsclientd
Version: FILESET HP CIFS CLIENT: Version: A.01.08
Compiled on HP-UX B.11.00, s800/R390, 02/07/12 11:40:52
cifsclientd: ver_id=4223346723
cksum: 3571780244
Status: CIFS Client daemon is up; process id 21723, started 18:55:27.

I have a directory from Windows Server mounted over the hpux server. Recently i'm receiving the next messages:

NFS getattr failed for server binssvonb02.banco.gfi.mx: RPC: Timed out
NFS fsstat failed for server binssvonb02.banco.gfi.mx: RPC: Timed out

In the information through the dmesg command show me the next:

NFS getattr failed for server binssvonb02.banco.gfi.mx: RPC: Timed out

Where cai i check if that messages appears for a network comunication problem ?.

Thank's in advance !

[RAC_1]

rpcinfo -p "windows_host"
Do you see nfs programs??

a contineous ping to windows host will also help.

Anil

[Ivan Azuara]

This is the information of the recomended commands:

(by hostname)
# rpcinfo -p binssvonb02.banco.gfi.mx
rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecifi
ed error)

(by ip)
# rpcinfo -p 130.80.1.63
rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecifi
ed error)

(by ip)
a_inb_02# ping 130.80.1.63
PING 130.80.1.63: 64 byte packets
64 bytes from 130.80.1.63: icmp_seq=0. time=4. ms
64 bytes from 130.80.1.63: icmp_seq=1. time=0. ms
2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/2/4

(by hostname)
# ping binssvonb02.banco.gfi.mx
PING binssvonb02.banco.gfi.mx: 64 byte packets
64 bytes from 130.80.1.63: icmp_seq=0. time=0. ms
64 bytes from 130.80.1.63: icmp_seq=1. time=0. ms

In fact, the shared resource between the servers continuously sends the original messages and the directory can't be access, but after a large period or time the shared resource is recovered again.

Some sugestion ?.

[RAC_1]

Check the following document. Though is applies to NFS, CIFS basically uses NS. So this should help you.

http://www1.itrc.hp.com/service/cki/search.do?searchString=KBRC00012324&docType=EngineerNotes&searchCrit=allwords&search.x=21&admit=-682735245+1124299133369+28353475&category=c0&mode=id&search.y=8

[Ivan Azuara]

The URL doesn't exist anymore !. Another link?

Thank's !

[RAC_1]

The document is this.

NFS mount command over TCP fails: "NFS getattr failed for server"
DocId: KBRC00012324 Updated: 5/13/03 9:45:00 AM
PROBLEM

NFS Mounting a remote filesystem on a local disk using the default TCP
mounts from HP-UX 11.11 NFS client gives the following error:

NFS getatter failed for server {hostname} : RPC(Unknown failure)

The mounts fail.

CONFIGURATION

HP-UX 11.11
Superdome
NFS using soft TCP mounts

RESOLUTION

The error indicates a problem with the TCP port for NFS between the
NFS client and the NFS server.

Use the following diagnostic commands to determine if a process is
using the port that is needed for the NFS mount over TCP:


1. Use the ping command against the NFS Server name or IP address.
If it does not respond, network connectivity is the reason for the
failure.

2. Use rpcinfo -t server program command


# rpcinfo -t nfs_server 100005 ( 100005 is the program for rpc.mountd )
rogram 100005 version 1 ready and waiting
rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3
program 100005 version 2 is not available
program 100005 version 3 ready and waiting

# rpcinfo -t nfs_server 100003 ( 100003 is the program number for nfs )
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting


If this generates an error, then there is likely a problem on
the NFS Server side, or setup. Consult the NFS debugging
document NETUXKBRC00006283 for tips.

3. Use netstat -an|grep 2049|grep xxx.yyy
where xxx.yyy=last few digits of the IP address of the NFS Server.
If you see a TCP socket from the client to the NFS Server being
stuck in a "CLOSE_WAIT" or "FIN_WAIT" status, then that indicates
the TCP socket being used for NFS communciations to that NFS Server
is hung. Unfortunately,the present design of HP-UX 11.11 NFS Client
does not select another socket for the same NFS server IP address.

Example:
hp-clnt #netstat -an|grep 2049 | grep 192.168.1.1

tcp 0 0 192.168.100.100.547 192.168.1.1.2049 CLOSE_WAIT

The following workarounds can be tried:

1. Try using another IP address from the NFS Server, if available, in the
mount command, in place of the server name. For example:

mount -osoft 192.168.200.1:/export/mnt /mnt

2. Try specifying UDP mounts until the system can be rebooted. To do this
add the proto=udp to the mount option string. For example:

mount -osoft,proto=udp server:/export/mnt /mnt

Where "server" is the name of the NFS Server.

3. Reboot to clear the port, and go back to using TCP mounts.
--------------------------------------------------------------------------

[John Dvorchak]

I looks like the Windows server quite serving NFS. The RPC (Remote Procedure Call) error is the tip off. If the RPC isn't running on any NFS server, you won't get a status or connection.

[Ivan Azuara]

I was checking the information about NFS, but that's recommendations can be applied for a CIFS (samba) environment,like me ?.

Thank's in advance !

[Fernando Jose P de Souz]

Try to update the Cifs

Download www.software.hp.com

Fernando.

[Fernando Jose P de Souz]

Try to update de Cifs

download: www.software.hp.com