Problem: An attempt to connect to AcuServer times out, or your application gets a time-out error during execution.
A typical time-out error message looks like:
File error 9D,14 on @condor:/usr2/bsmith/fio_seq.dat condor: Timed out
Time-out errors occur when the server is down, the server crashes while your program is running, or network conditions produce very protracted response times (the result of an overburdened network, or faulty network hardware/software).
From your client system use "ping" to query the server:
Ping will return:
hostname is alive
no answer from hostname
If there is no answer from the server, determine the cause of the failure (machine down; network connection faulty) and restore the server. With ping, confirm that the network connection is working.
If the service is not running, click Start.
If acuserve is running, the command will return a summary of AcuServer's current status. For example:
0 file(s) in use by acuserve on: hostname
If acuserve is not running the command will return:
acuserve is not running on hostname
If acuserve is not running, start acuserve and repeat the acuserve -info test.
Once acuserve is running, rerun your application on the client. If the connection still times out, proceed to step three.
If the connection succeeds, analyze your network for the cause of the prolonged connection time. You should investigate network capacity, collision and retransmission rates, and network hardware or software malfunction.
If necessary, repair your network and confirm its proper operation. Reset DEFAULT_TIME_OUT to its default setting of 25 seconds and rerun your application.