-
render farm error and OSX.4.2
Render Farm error
I’m working on standardizing some AE systems but I’m running into problems getting the render farm to work on two of the computers.
Here are the specs:
5x Pentium systems make up the render farm
In addition to other Windows PCs that can invoke the farm, I’ve got several G5s and one G4 that I am trying to get hooked into the farm. Of these Apple systems, two are successfully sending to the farm with no issues. The other two (one is a G5, the other is a G4 laptop) will neither recognize the watch folder nor invoke the farm. I keep getting the following message when I try to send to the farm from these two bad guys:AE error: flushing file “name_RCF.txt – disk error (I/O error; bad media) (-36)
This error repeats 5x, which equals the number of systems in the farm. This error repeats on only two of the four Apple computers that I’m using to access the farm.
Additionally, if I try to call up the watch folder on these two machines I get the message
AE error: You do not have read/write permissions for this folder.
This error is particularly confusing because I created the folder for the render project on the same server using the Apple that is giving me this error. Not only that, the project that I am using for my tests was created by this same computer so, obviously, I can read/write to this disk.
Any ideas on what might be causing this blockage? On what might cause two of the four computers to work fine while the other two choke?
All AEs are at 6.5.1, plugins have been standardized, and two of the CPUs have already successfully rendered this project using the farm. I simply cannot figure out why the other two will not do the same.
Addendum: ?I have discovered a difference between the computers that will render and those that won’t. ??The CPUs that won’t access the render farm are running 10.4.2 ?The CPUs that will access the render farm are running 10.4.1 and 10.3.9 ??Don’t know if that is the cause of the problem, but it is the only consistency I’ve found. ??db
Sorry, there were no replies found.