Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

redline to Qmater?

Actually scrub that because it's a G5 it wont be will it. Not sure if you can or not. You wont be able to install Redline thats for sure, but I am not sure if you need to on every node anyway as I believe it uses your main ingest machine for that. Try adding it to your cluster and see.
 
Thanks to Visual Processing Japan (metaSAN distributor) and Comtecs (Infotrend dealer), now I have metaSAN running with two Mac Pros, so I will scale down to two machines, place the R3D files on metaSAN volume, and the output location to be on the metaSAN.
Also fix the cluster name.

I'll let you know Simon.
 
So I've gathered bits and pieces of this but I think I am missing something, is there anyway anyone could post or direct me to a detailed step-by-step breakdown of this process? I have an 8core and a quadcore set as my cluster... I've saved the redline.sh script in a redline folder and can get qmaster to render redrushes scripts on the ingest machine only.
 
dj3 said:
So I've gathered bits and pieces of this but I think I am missing something, is there anyway anyone could post or direct me to a detailed step-by-step breakdown of this process? I have an 8core and a quadcore set as my cluster... I've saved the redline.sh script in a redline folder and can get qmaster to render redrushes scripts on the ingest machine only.
Click to expand...

Each machine in the cluster must have all the same network paths mounted in exactly the same way. Open a terminal and type in mount this will show the drives or network paths mounted. Check this on both machines to see if they match. If the files are located on the ingest machine that could be the problem. They are best put on a network were all machines can access them in the same way. Not having the input and output path correctly mounted causes the biggest issue with Qmaster. If you are working from a local drive it will not be the same path on the other machine. As the redrushes makes the script from you ingest machine it uses the path mounted on that machine which will be completely different on the other node. To check for errors open up quadministrator it usually flags it in there if a network issue or other problems. Also check Qmaster app to ensure that all nodes are in the cluster and you have set your ingest machine as the controller.
 
Simon,

I'm finding that metaSAN changes how Qmaster works and can't seem to get the cluster working with metaSAN. Cluster seems to work only with locally attached volumes. I can't even assign any network disks through ethernet, the Qmaster in the System Preference denis using network disk. I read up some stuff and it was mentioned that Qmaster had issues with XSAN, so metaSAN part is probably something similar happening but how did you mount your network volume to you cluster? Ah, maybe NFS?
 
Kaku Ito said:
Simon,

I'm finding that metaSAN changes how Qmaster works and can't seem to get the cluster working with metaSAN. Cluster seems to work only with locally attached volumes. I can't even assign any network disks through ethernet, the Qmaster in the System Preference denis using network disk. I read up some stuff and it was mentioned that Qmaster had issues with XSAN, so metaSAN part is probably something similar happening but how did you mount your network volume to you cluster? Ah, maybe NFS?
Click to expand...

All our Network drives are mounted via SMB. Each node has the server/s mounted in the same way using the standard connect to server option in the finder GO menu. Your ingest machine and Qmaster manager must also have the server mounted in the same way. You are not changing any of the paths in Qmaster are you? Because you should just leave them as default. I would double check you Qmaster setup and test it manually using the Qmaster application other than that I do not know what is wrong. Perhaps it might be time to uninstall Qmaster and try again from scratch.
 
You must log in or register to reply here.
Back
Top