- This topic has 7 replies, 3 voices, and was last updated 18 years, 4 months ago by
Leonardo Bernardini.
-
Posted in: Linux
-
23rd February 2007 at 5:18 pm #14159
Im running several machines with Maya and Muster on Fedora Core 6. The thing is that after running for about an hour, the Muster processes just dies for no apparent reason. The log files just stop. There is no indication of an error. Anybody else having this problem?
17th March 2007 at 8:19 pm #14631Are we talking about the server or the clients ?
30th March 2007 at 2:27 pm #14637We are not aware of such kind of problem even we didn’t test with Fedora Core 6. We’ll setup a test installation with this release to see if it’s a problem with this distro.
28th April 2007 at 12:29 pm #14641Hello Leonardo,
I did have a mail discussion with you on the 9th of January 2007 about this exakt same problem.//Jonas
8th May 2007 at 4:17 pm #14644Hey Joans, did you have any kind of a fix? I tried creating a shell script to ressurect Muster whenever it crashed. It kinda works, but the problem is that you still have clients spontaneously dying. Anyways here it is.
#!/bin/sh
#This baby keeps Muster alive.
#Variables
running=”$ (ps -aux | grep rc_linux) “#Functions
while[true]
do
if[ -n !”$running”]; then
rc_linux
fi
doneSo what I did here was have ps output all of the running process, and I piped it into grep so that it could check to see if muster is running. I stored this into a variable, and if it isn’t running, then it restarts the render client. Its not the best fix in the world, and I have a feeling that it could have been constructed better. Either way, enjoy.
~Chris22nd 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 ?
9th June 2007 at 1:59 am #14687Related to this issue:
We find a problem when starting the clients in daemon mode, I hope that kind of problems happens when forcing Muster to run using the -d.
If that’s positive, then version 5.2 address the problem on the renderclient. Also we are going to release 5.21 in the next days that address the entire daemoning sequence.The problem is dued to some broken pipes that stay opens after firing as daemon. Under certain circumnstances, the processes get the SIG_PIPE signal that’s actually unhandled and dies spountaneous.
Regarding previous versions, running the base process forcing background processing (i.e. dispatcher& ) will fix the issue.
-
You must be logged in to reply to this topic.