Displaying 6 results from an estimated 6 matches for "trqauthd".
2015 May 27
5
serious problem with torque
...ated 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, 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 downgra...
2015 May 27
2
serious problem with torque
...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...
2015 May 27
1
serious problem with torque
...bit.
> It's not an exact science and newer / higher versions are not always
> better.
My experience exactly. We used version 2 for quite a while. Never managed
to upgrade to version 3 (tried a few times, but didn't invest much of
effort). Then we went directly to version 4. Starting trqauthd was the
most notable difference. We never use rpms, we just compile torque on
master and compute nodes. Compilation is always so straightforward, and
never failed, so we didn't bother to package it...
Valeri
>
> As for the downgrade comment: Perhaps you can't, but, Torque, when
>...
2015 May 27
0
serious problem with torque
...ne 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...
2015 May 27
0
serious problem with torque
...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,
>>> a...
2015 May 27
0
serious problem with torque
...ne 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 p...