Forum Replies Created
-
-
25th May 2007 at 6:44 pm #14676You’ve to write a new template.
the easiest way to perform what you’re asking for is running a batch file (.cmd).To run batch files, you’ve invoke the windows cmd.exe command line utility.
If you step inside the template folder of your installation, you’ll find an example folder with a template able to launch a chkdsk. You may modify that one to meet your needs.
regards
Leonardo.
25th May 2007 at 6:43 pm #14675You’re writing inside /var/log/muster. Be sure that the account that’s starting the renderclient is able to write into that folder or redirect the logs in another folder.
Regards.
Leonardo.
25th May 2007 at 6:41 pm #14674There has been an error in the installer posted in the first publishing day. The MCMC error has been addressed, you can simply redownload the installer from our web site.
We sent an alert e-mails to the ones that downloaded it during the first hours, but in seams that anti-spam are growing bigger in those days.
regarding the explorer freeze problem, could you be a little more specific ? We are not aware of such kind of issue.
regards.
Leonardo.
25th May 2007 at 6:38 pm #14673Thanks for your suggestion.
We add it in the list of future enhancements.
Regards.
Leonardo.
22nd May 2007 at 12:22 am #14666Disable automatic drive mapping and set the Renderclient to statically map a drive on startup.
Muster uses a string-based comparation. If you map a drive using the IP address (in your example \192.168.1.239) and then submission a job from an host that has the drive mapped using a UNC name, they will raise an exception.
Off course, you can get an headache normalizing your mappings on your network…
22nd May 2007 at 12:14 am #14665Version 5.2 includes embedded manifests and privileges settings required by Windows Vista. We also provide a registry hack to allow the start of the MSI installer using the “Run as Administrator” function.
If you cannot map drives, check the privileges of the user assigned to the services.
Also try to start the renderclient as a console application first and watch the results.
22nd May 2007 at 12:13 am #14663Check the latest version (5.2). It has been built with GLIBC 2.5 and we provide native 64 bit executables.
We tested intensively Fedora 6 and were not able to reproduce the problem. I think it could be dued to different version of the LIBC.
If you type:
ldd –version
what version to you get ?
22nd May 2007 at 12:11 am #14662Check the renderclient.log file. At the beginning of each packet, there’s always a path dumped with the full file pathname of the log.
22nd May 2007 at 12:10 am #14661The problem you get is not related to the environment variable. If the connector starts, it means you’ve a MUSTER var configured. Good or bad, you’ll see it later when mrtool is invoked.
Regarding the error, did you specify a publishing directory ? The connector assumes you’re going to publish your work remotely somewhere on your network..
22nd May 2007 at 12:06 am #14659We actually certify Fusion 5+ only with Muster 5.X
22nd May 2007 at 12:05 am #14658The Muster behaviour is normal. If it detects an hard error in the job, it adds the job to the temporary client EXCLUSION LIST and do not process it further. The feature has the purpose to avoid keeping nodes with faulty scenes.
If the scene fails at random, you should locate the render log PACKET of that particular chunk that caused the exception and locate the reason of the problem.
22nd May 2007 at 12:03 am #14657There’s a known bug in 5.12 and previous that has about 0.1% chance to put 2 or more threads in a race condition ending in a Dispatcher lock. This value raises during very busy phases.
5.2 Address the problem.
Regards.
22nd May 2007 at 12:02 am #14656If you experience the same issue in 4.5 and 5.12, the solution has to be found inside your network policies.
The user actually assigned to the Renderclient IS NOT able to access your shared resources. As you said, you’re working on a domain, it is possible that the default installer was not able to create a WORKING ACCOUNT. Check the “User permissions” section on the online manual or get in touch with vvsupport@vvertex.com.
Regards.
-
