Firewall rules for distributed simulations on a renderfarm

   240   0   1
User Avatar
Member
16 posts
Joined: Sept. 2017
Offline
Hello,

I am working on using our Tractor farm to run simtracker.py tracked distributed (sliced) simulations. The only way I have been able to get it to work is to turn off the firewall for all nodes - which is obviously not acceptable in a production environment. Opening up all ports of the entire render farm to each other (as hinted at in this 10 year old post [www.sidefx.com]) is also not acceptable in modern secure networks, as far as I am aware, as an attacker who gains entry to one node will then have control of the entire farm (please correct me if I am wrong here or if renderfarms are an exception to this level of protection).

Could you kindly direct me to information of specific port numbers or the like that I can configure my firewall with, to enable distributed simulations with simtracker? If my firewall is on, and with rules to allow the simtrackers port and webport, I still get these errors with simtracker:

Exception in thread Thread-12:
Traceback (most recent call last):
  File "/opt/hfs19.5/python/lib/python3.9/threading.py", line 973, in _bootstrap_inner
    self.run()
  File "/opt/hfs19.5/houdini/python3.9libs/simtracker.py", line 381, in run
    sendmessage(peer, message)
  File "/opt/hfs19.5/houdini/python3.9libs/simtracker.py", line 450, in sendmessage
    rs.connect( (peer['address'], peer['port']) )
OSError: [Errno 113] No route to host

...


File "/opt/hfs19.5/houdini/python3.9libs/simtracker.py", line 450, in sendmessage
    TimeoutError: [Errno 110] Connection timed outrs.connect( (peer['address'], peer['port']) )
TimeoutError: [Errno 110] Connection timed out
    rs.connect( (peer['address'], peer['port']) )
TimeoutError: [Errno 110] Connection timed out

Also on the node that renders its slice, it always hangs on frame 2, and doesn't move forward.
  • Quick Links