[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] condor port problems



_CONDOR_BOO=HOO is just a shortcut for appending BOO=HOO to Condor configuration from the environment.

http://www.cs.wisc.edu/condor/manual/v7.2/3_3Configuration.html#SECTION00431100000000000000

Best,


matt

Cole Uhlman wrote:
No, they're the right way around. condor_config has them defined as:
HIGHPORT = 50199
LOWPORT = 50000

And I haven't got any "Sock::bindWithin" messages in any of my logs.

However, "_CONDOR_LOWPORT" and "_CONDOR_HIGHPORT" are not defined in my
env.  Is condor_master supposed to set these environment variables from
condor_config?  Or does the shadow read condor_config and only define
them locally?  Where are they supposed to be set, and is this what the
daemons actually look for?

Thanks

-Cole


On Fri, 2009-03-27 at 14:08 -0500, Matthew Farrellee wrote:
$ condor_version
$CondorVersion: 7.2.1 Mar 20 2009 BuildID: RH-7.2.2-0.8.el5 $
$CondorPlatform: I386-LINUX_F10 $

$ for i in $(seq 1000); do env _CONDOR_LOWPORT=10000 _CONDOR_HIGHPORT=10005 condor_shadow -t -f 2>&1 | grep "Command Socket" | awk '{print $7}' | sed 's/[^:]*:\(.*\)>/\1/'; done | sort | uniq -c
     160 10000
     165 10001
     167 10002
     178 10003
     167 10004
     163 10005

Is it possible you've flipped LOW/HIGHPORT? If you set LOWPORT to 10006 above you'll see it is ignored, and the ports are randomly distributed.

If you don't have any free ports in the range you'll see:

Sock::bindWithin - failed to bind any port within (10000 ~ 10005)

(You can simulate used ports with "nc -l localhost 10000"...)

You can

Best,


matt


Cole Uhlman wrote:
Perhaps I should clarify my problem.  I setup iptables to let through
the same port range I put in LOWPORT/HIGHPORT (50000 - 50199).  But for
some reason, the shadow daemon is taking it's random port outside this
range.  For example, in ShadowLog:

3/16 15:54:20 DaemonCore: Command Socket at <x.x.x.x:59521>

So the firewall blocks communication to the shadow and my VM job doesn't
run.  The only time I've had it run is when I left in in the queue long
enough to retry enough times to randomize to a valid port.

Does anyone have an idea why condor_shadow would be ignoring my
HIGH/LOWPORT settings?  Please help.

-Cole

On Mon, 2009-03-16 at 17:28 -0700, Cole Uhlman wrote:
Hi, all.

I am still having the same problem from a little while ago
("[Condor-users] running a xen vm universe job"), but I know a little
more now.

It looks to me like condor_shadow is not following my port restrictions.
I have HIGHPORT and LOWPORT set in condor_config.  However, ShadowLog on
the submitter/centralmanager shows it using ports outside my set range;
and StarterLog on the execute machine shows my jobs failing because it
can't communicate with the shadow.

So, is this a bug?  Is there some way I can fix it to actually follow my
HIGHPORT/LOWPORT settings?  Btw, I am running condor 7.2.1.  Does anyone
know about this?

Thanks

-Cole

_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at: https://lists.cs.wisc.edu/archive/condor-users/
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at: https://lists.cs.wisc.edu/archive/condor-users/
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at: https://lists.cs.wisc.edu/archive/condor-users/

_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at: https://lists.cs.wisc.edu/archive/condor-users/