Hi All
I am having the same issue as other users, the slaves launch and quit. any other solutions other than unplugging the ethernet cable?
I am setting up slaves on a single machine at work
Mac OS 10.4.11
Dual Core
6GB RAM
There is one other user that has that problem. We need to know what is specific about your network that is causing the problem. Are you using a proxy server? Is there a Directory Services system in place?
Thank you for your fast response and there are other users with the same problem and you answered to one of them and the solution was to unplug the ethernet cable from the computer on the other cases. I cant believe we have the exact same network setup also I had the same setup with version 6.6.2 and it worked just fine. Here are the links to the other users having the same problem
i dont think I am using a proxy server. Under Network/Proxies
I have Configure Proxies: Manually but with nothing checked or filled in except Use Passive FTP Mode (PASV)..
About the Direct Services System, I dont know.
There must be some sort of unique situation that is causing this. Can you bring up your network preferences and do a screen capture of the main page and the configuration pages. Then send the to
I just got them to work
I trashed the cache for the user
and ran the disk utilities and Repaired Pemisions
I launched one of the slaves and it worked fine, tried to launch the second slave but it would just crash, until I changed the ip number for the first slave and the same for the third slave (i am running 3 of them)
Now what i am getting is this error message
“An error was encountered at slave 172.17.6.146:1617: Coulnd’t access slave machine”
if a preview is rendering while you send a job to Renderama, something goes wrong with this job.
All slaves on all machines crashes.
If you close the preview camera and send the job again - all works fine.
Looks like a bug in Renderama ?
if a preview is rendering while you send a job to Renderama, something goes wrong with this job.
All slaves on all machines crashes.
If you close the preview camera and send the job again - all works fine.
Looks like a bug in Renderama ?
A simple thing/test that (maybe) forgotten: run RenderamaSlave from folder where your Animator and Camera are. If it has same port (1617 for example) as one of slaves - so, yes, you cannot use such slave together with preview. In other words, Camera running with preview/regular render is also identified in network on same machine, need to provide unique port ID for it as well.
thank you for your response.
That is not what I mean.
I´m working with a 4 processor Mac - 4 Cameras, 4 Slaves (all with different IDs off course) + other slave machines.
So I´m using Camera 1 for preview purpose (not within Renderama), 2,3+4 as Renderama slaves.
So, I think, this should work properly (and it did before EI7) - but now it doesn´t ?!
On the other hand the used memory of cameras seems to set back to 128 MB (by itself?) sometime unnoticed.
May be this can be the problem?
As Gianluca pointed out, it seems, though I will wait for further confirmation, that 701 is incompatible with the Apple system firewall (in System Prefs). Turning this off on all machines has fixed a few (I’d say 6 of 10) Renderama problems....