You may notice that the bebopd does not seem to be updating the
[4]resources_available.size attribute of the server. Perhaps this
is because the qmgr client it is invoking can't reach the server.
(Incidentally, the bebopd should log this problem in /var/log/cplant).
Or a user may tell you that qsub is failing to contact the server.
These are examples of PBS clients that can not contact the PBS server.
Verify that the server is running and you can ping it's node on the network being used by PBS. Check the server's log file to see if it received and then rejected the request, or never received it at all.
If the server never received the request, check the
[4]/tmp/pbs/working/PBSserver file on the client
node. This is the
file that clients (and the scheduler and MOMs) look in to find the
hostname of the server. Verify that the hostname in this file is
the hostname on which the server is running. You may need to modify
the name (add or delete a domain name, for example) to get it to work.
The next thing to check is that the acl_hosts attribute of the PBS server includes the client node. The PBS server will only accept messages for hosts in this list. If the hostname does appear on the list, make sure that it exactly matches the hostname the server got from the incoming connection. (The server writes to it's log file the name of the incoming host of the request that it rejected.) You may need to add or delete a domain name, for example, from the hostname in the acl list.
In the case of the bebopd invoking qmgr, verify that root on the bebopd node is listed as a manager in the PBS server attributes. Only managers can set resource information.