There are some timeout issues you can see with large clusters on Torque - check
the Torque web site for explanations and instructions on what to do about it.
However, that doesn't appear to be the problem here.
If our daemon doesn't report back, it is typically due to one or more of the
followi
On Sat, May 29, 2010 at 8:19 AM, Ralph Castain wrote:
>
> >From your other note, it sounds like #3 might be the problem here. Do you
> >have some nodes that are configured with "eth0" pointing to your 10.x
> >network, and other nodes with "eth0" pointing to your 192.x network? I have
> >found
On May 29, 2010, at 11:35 AM, Rahul Nabar wrote:
> On Sat, May 29, 2010 at 8:19 AM, Ralph Castain wrote:
>
>>
>>> From your other note, it sounds like #3 might be the problem here. Do you
>>> have some nodes that are configured with "eth0" pointing to your 10.x
>>> network, and other nodes w
