[torqueusers] using non-privileged ports
"Carlos M. Cámara"
carlos.camara at wimasis.com
Wed Nov 2 02:31:22 MDT 2011
I use Torque without privports and Munge and it works fine. The first
reason that comes to my mind is that you compile the client with
--disable-privports, but somehow not the server or that in your server
is still working the privport version.
Another good reason for this to not work could be a firewall rule that
is avoiding the communication.
On 10/28/2011 10:57 PM, torqueusers-request at supercluster.org wrote:
> Date: Fri, 28 Oct 2011 10:39:56 -0700
> From: Martin Siegert<siegert at sfu.ca>
> Subject: [torqueusers] using non-privileged ports
> To:torqueusers at supercluster.org
> Message-ID:<20111028173956.GB5953 at stikine.sfu.ca>
> Content-Type: text/plain; charset=us-ascii
> we just recompiled torque with
> (since we constantly ran out of ports). Now we have a different
> problem which is just as bad:
> # qstat -an1
> Connection timed out
> qstat: cannot connect to server b0 (errno=110) Connection timed out
> This does not appear right away after starting the server, but after
> a few hours of running. As far as I can tell the only way to get the
> server out of this state is to restart it.
> But there must be many sites that run torque with --disable-privports.
> Thus: what am I missing?
> -- Martin Siegert Head, Research Computing Simon Fraser University
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the torqueusers