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

Re: [Condor-users] SuSEFirewall2

Have you remembered to open the firewalls between all submit nodes and all execute
nodes across the 2 pools? It isn't sufficient just to open the firewall between
the 2 central nodes.

Other potential problems:

* FLOCK_TO and FLOCK_FROM both setup on both machines if bidirectional
  flocking required.
* HOST* (READ/WRITE/etc) might be blocking the hosts

Finally (it might be this actually having read your post again)
* As well as high ports being open (and appropriate classAd set for this),
  you also need the 9614 and 9618 fixed ports opening, again probably for
  tcp AND udp on both machines.

I hope something above gives you a hint.



> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of Jenny Barna
> Sent: Tuesday, January 09, 2007 2:08 PM
> To: condor-users@xxxxxxxxxxx
> Subject: [Condor-users] SuSEFirewall2
> I have found that while it is easy enough to make a hole with the Suse
> Yast2 GUI in the firewall for ports 9600-9700 for udp and tcp 
> that allows
> condor to work within one pool there is something else 
> stopping flocking.
> It works fine with the firewall off but various edits to the file
> /etc/sysconfig/SuSEfirewall2, that cannot be effected within 
> have not worked. If anyone could post me a SuSEfirewall2 file 
> that works
> for flocking between pools I would be extremely grateful. I have tried
> inserting separately made iptables rules based on successes 
> on non Suse
> machines but also not got these right it appears.
> _______________________________________________
> 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 either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR