RPC timeout error displays on Brisque when transferring files with a Mac


Product		Brisque™ 4.0 Brisque™ Serve 4.0 Timna™ 3.0
Platform		E30—Victory 43P-140—Tiger1 43P-150—Tiger2 44P-170—Hammerhead F50—Wildcat (2 and 4 CPUs) 6F1— Condor (2,4, and 6 CPUs)
Operating system		IBM^® AIX 4.2.1 or IBM AIX 4.3.3

Error		`RPC time-out`

Symptoms		On Brisque, an RPC timeout error displays when you transfer files with a Macintosh computer. If Brisque afpsrv processes are running during the RPC timeout, the Mac OS Chooser lists the name of the Brisque volume as unavailable. When this event occurs, the Brisque volume's files can still be read. However, Brisque files can not be created, deleted, renamed, moved or trashed.

Cause		RPC time-outs are caused by high input/output (I/O) loads on the Brisque NFS (Network File System) server, slow I/O-devices, and network communication problems.

Solution		Investigate and correct all of the following possible causes: High I/O loads occurring on the server—use the Topas utility to check the load. Slow I/O devices—use the Topas utility to check the load. Network communication problems. If the RPC timeout still occurs, run the following scripts to restart EtherShare services on the server: `/usr/local/es/stop-atalk now` `/usr/local/es/start-atalk`

Technical contact(s)		Lev Weissman
Submitted by		Lev Weissman
Date submitted		02 Oct 2002