Displaying 6 results from an estimated 6 matches for "socket_connect_unix".
2015 May 27
5
serious problem with torque
Hi, folks,
The other admin updated torque without testing it on one 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...
2015 May 27
2
serious problem with torque
Johnny Hughes wrote:
> On 05/27/2015 09:07 AM, m.roth at 5-cent.us wrote:
>> Hi, folks,
>>
>> The other admin updated torque without testing it on one 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
>> mana...
2015 May 27
0
serious problem with torque
On 05/27/2015 09:07 AM, m.roth at 5-cent.us wrote:
> Hi, folks,
>
> The other admin updated torque without testing it on one 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) to...
2015 May 27
0
serious problem with torque
...On 05/27/2015 09:07 AM, m.roth at 5-cent.us wrote:
>>> Hi, folks,
>>>
>>> The other admin updated torque without testing it on one 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. Worki...
2015 May 27
0
serious problem with torque
...'t read often, so I might go AWOL)
On Wed, May 27, 2015 at 10:07 AM, <m.roth at 5-cent.us> wrote:
> Hi, folks,
>
> The other admin updated torque without testing it on one 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) tor...
2015 May 27
1
serious problem with torque
...gt;
>
>
> On Wed, May 27, 2015 at 10:07 AM, <m.roth at 5-cent.us> wrote:
>> Hi, folks,
>>
>> The other admin updated torque without testing it on one 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
>...