search for: pbs_server

Displaying 6 results from an estimated 6 matches for "pbs_server".

Did you mean: dns_server
2015 May 27
5
serious problem with torque
...e machine, and we had Issues. The first I knew was when a user reported qstat returning socket_connect_unix failed: 15137 socket_connect_unix failed: 15137 socket_connect_unix failed: 15137 qstat: cannot connect to server (null) (errno=15137) could not connect to trqauthd Attempting to restart the pbs_server did the same. Working with my manager, we found: a) torque had been updated from 2.x to 4.2.10, which is huge. b) Apparently, it no longer uses munged. Instead, it uses trqauthd, and that wasn't in the updated packages. c) We could not downgrade!!! d) My manager updated from tes...
2015 May 27
2
serious problem with torque
...qstat >> returning >> socket_connect_unix failed: 15137 >> socket_connect_unix failed: 15137 >> socket_connect_unix failed: 15137 >> qstat: cannot connect to server (null) (errno=15137) could not connect >> to trqauthd >> >> Attempting to restart the pbs_server did the same. Working with my >> manager, we found: >> a) torque had been updated from 2.x to 4.2.10, which is huge. >> b) Apparently, it no longer uses munged. Instead, it uses trqauthd, >> and >> that wasn't >> in the updated packages. >>...
2015 May 27
0
serious problem with torque
...I knew was when a user reported qstat > returning > socket_connect_unix failed: 15137 > socket_connect_unix failed: 15137 > socket_connect_unix failed: 15137 > qstat: cannot connect to server (null) (errno=15137) could not connect to > trqauthd > > Attempting to restart the pbs_server did the same. Working with my > manager, we found: > a) torque had been updated from 2.x to 4.2.10, which is huge. > b) Apparently, it no longer uses munged. Instead, it uses trqauthd, and > that wasn't > in the updated packages. > c) We could not downgrade!!! &g...
2015 May 27
0
serious problem with torque
...t;>> socket_connect_unix failed: 15137 >>> socket_connect_unix failed: 15137 >>> socket_connect_unix failed: 15137 >>> qstat: cannot connect to server (null) (errno=15137) could not connect >>> to trqauthd >>> >>> Attempting to restart the pbs_server did the same. Working with my >>> manager, we found: >>> a) torque had been updated from 2.x to 4.2.10, which is huge. >>> b) Apparently, it no longer uses munged. Instead, it uses trqauthd, >>> and >>> that wasn't >>> in the upd...
2015 May 27
0
serious problem with torque
...I knew was when a user reported qstat > returning > socket_connect_unix failed: 15137 > socket_connect_unix failed: 15137 > socket_connect_unix failed: 15137 > qstat: cannot connect to server (null) (errno=15137) could not connect to > trqauthd > > Attempting to restart the pbs_server did the same. Working with my > manager, we found: > a) torque had been updated from 2.x to 4.2.10, which is huge. > b) Apparently, it no longer uses munged. Instead, it uses trqauthd, and > that wasn't > in the updated packages. > c) We could not downgrade!!! &g...
2015 May 27
1
serious problem with torque
...t;> returning >> socket_connect_unix failed: 15137 >> socket_connect_unix failed: 15137 >> socket_connect_unix failed: 15137 >> qstat: cannot connect to server (null) (errno=15137) could not connect >> to >> trqauthd >> >> Attempting to restart the pbs_server did the same. Working with my >> manager, we found: >> a) torque had been updated from 2.x to 4.2.10, which is huge. >> b) Apparently, it no longer uses munged. Instead, it uses trqauthd, >> and >> that wasn't >> in the updated packages. >>...