Render Farm Build 30

DISCLAIMER: This is a continuing series detailing the painful story of a DIY render farm build.  It is terribly technics and
somewhat frustrating.  Those who are unprepared for such “entertainment” are advised to ignore these posts.

I reconfigured the slave.conf file and restarted.  The slave was now running!  I manually configured the environment variables:

DRQUEUE_LOGS, 
DRQUEUE_DB, 
DRQUEUE_TMP, 
PATHS

and that seemed to do it.  But I had to do this by hand in the terminal before running the slave.  That would be OK for this test, but I needed this to happen every time the machine started up.

And now the slave ran, but it did not seem to be connecting to the master.  I thought I should hardwire the IPs in the network – if for no other reason than that I could remember where everything was.

  1. Cyclops: 10.1.1.1
  2. Gog: 10.1.1.2
  3. Magog: 10.1.1.3
  4. Mystery: 10.1.1.4
  5. Babylon: 10.1.1.5
  6. Wormwood: 10.1.1.6
  7. Whore: 10.1.1.7
  8. Beast: 10.1.1.8

And so on.  I haven’t actually made any of the other computers, but it’s good to plan.

Though Cyclops and Gog had been renamed and given IPs, it still seemed as though the slave did not see the master.  The problem was probably in the config files, and most likely had something to do with whether or not the slave was configured to see the shared folders properly.  I would need more time to poke around with it.  If I had more knowledge of how this sort of thing works, I probably would have been done by now.  Somewhere a Unix head is reading this and is laughing right now.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.