Valeri Galtsev wrote:
>
> On Wed, May 27, 2015 10:55 am, Zachary Giles wrote:
>> Mark, You might really want to compile torque from source (into an RPM
>> if you'd like) and redistribute that. Every version is a little wonky
>> and those of us that use(d) it often will poke around until we find a
>
On Wed, May 27, 2015 10:55 am, Zachary Giles wrote:
> Mark, You might really want to compile torque from source (into an RPM
> if you'd like) and redistribute that. Every version is a little wonky
> and those of us that use(d) it often will poke around until we find a
> version / patch-set that ma
Mark, You might really want to compile torque from source (into an RPM
if you'd like) and redistribute that. Every version is a little wonky
and those of us that use(d) it often will poke around until we find a
version / patch-set that makes us happy and stick with that for a bit.
It's not an exact
On Wed, May 27, 2015 9:46 am, m.r...@5-cent.us wrote:
> Johnny Hughes wrote:
>> On 05/27/2015 09:07 AM, m.r...@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
>>>
Johnny Hughes wrote:
> On 05/27/2015 09:07 AM, m.r...@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_u
m.r...@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
On 05/27/2015 09:07 AM, m.r...@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_co
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)
8 matches
Mail list logo