Forum Replies Created
-
29th June 2015 at 6:59 am #15267It was a User issue / linux issue, where as I thought that if you disable the firewall, all ports will be open. but apparently you have to open some ports manually and that did fix my issue.
1st July 2014 at 1:10 pm #15252Fixed:
“C:/PROGRA~1/Virtual Vertex/Muster 8/Mrtool.exe” -b -s 192.168.1.226 -port 9781 -u test -p “” -e 100 -n name -f W:/projects/project/sequences/001/Shot0050/3d/maya/renderScenes/a_defaultRenderLayer_960x540_exr.mb -sf 1.0 -ef 10.0 -bf 1 -se 1.0 -st 1 -attr ARNOLDMODE 0 ARNOLDMODE
20th March 2014 at 8:18 am #15246from support:
You shoud use:
“.*Failed OpenEXR write.*” instead of “*Failed OpenEXR write*”
and that works:-)
19th March 2014 at 5:58 pm #15245I’m not sure I get it.
If I’m trying to cause it to fail when this appears in the log: “Failed OpenEXR write” or this: “Invalid argument.”
Shouldn’t this work then?
ADD ERROR “translator
” “*Failed to write pixel data to image file*” “*Failed OpenEXR write*” “Invalid argument.” “Error: line 1: Error reading file.” “Maya binary file parse error:” “error” “ERROR” “Error”
27th September 2013 at 7:36 am #15235Thanks Andrew.
Yes that is what I did too.
I’ve send emails about this thread to Virtual Vertex and will post the respnse here when I get it.
28th August 2013 at 2:54 pm #15230Seriously? noone has one?
Not even a commandline one? say if I want to just do an ECHO “whatever”
20th August 2013 at 7:14 am #15229Hmm.. I’ve been checking my individual instances on the farm (rightclick on instance -> configuration -> behaviours)
there is an Affinity mask there and it seems like it is doing what it should be doing (It divides the affinity based on however many instances the given computer has beensplit up into)One of my computers looks like this in here:
Instance ID 1
Priority 1
Process Priority Normal
Instance affinity mask 0x3Instance ID 2
Priority 1
Process Priority Normal
Instance affinity mask 0xcInstance ID 3
Priority 1
Process Priority Normal
Instance affinity mask 0x30Instance ID 4
Priority 1
Process Priority Normal
Instance affinity mask 0xc0when I click modify on these the affinity seems to be mapped to the correct procs/threads but whenever I launch a job on muster and look at the mayabatch or nuke process, the affinity is set to all my procs/threads.. so it seems like the processes doesnt listen to the affinity configuration in my rendernodes?
Any thoughts?
14th August 2013 at 1:12 pm #15228This is what I’ve done so far, it gives me all the folders with their corresponding IDs (feels like there should be a better way though)
(This is in python)
dispatcherIP = ‘192.168.0.151’
user = ‘XXX’
musterMRToolPath = ‘C:/PROGRA~1/”Virtual Vertex”/”Muster 7″/Mrtool.exe’
command = musterMRToolPath + ‘ -q j -jobengine “” -s ‘ + dispatcherIP + ‘ -u ‘ +userfolders = {}
import subprocess
proc = subprocess.Popen(command,stdout=subprocess.PIPE, shell=True)
while True:
line = proc.stdout.readline()
if line != ”:
try:
print line.rstrip() + ‘n’
folders[line.rstrip().replace(‘ ‘, ”).split(‘|’)[1]] = line.rstrip().replace(‘ ‘, ”).split(‘|’)[0]
print line.rstrip().replace(‘ ‘, ”).split(‘|’)[0], line.rstrip().replace(‘ ‘, ”).split(‘|’)[1]
except:
pass
else:
break
print foldersMy problem now is the syntax to create a folder through commandline (I’m running Windows 7):
Mrtool.exe -b -s 192.168.0.151 -u XXX -folder – results in: Missing folder name.
Mrtool.exe -b -s 192.168.0.151 -u XXX -folder Name – results in:Invalid flag(7): Name
Mrtool.exe -b -s 192.168.0.151 -u XXX -folder “Name” – results in:Invalid flag(7): Name
Mrtool.exe -b -s 192.168.0.151 -u XXX -folder ‘Name’ – results in:Invalid flag(7): ‘Name’Any thoughts?
-
