> INIT_Processeses(), could not establish the default
> connection to the WindowServer.--- shake: terminated by signal 6
Sounds like shake is trying to access the window manager
when it shouldn't be.
The two most common causes of this:
1) User error -- the shake file is trying to render
to the screen, instead of rendering to a file.
2) Bad OS library (eg. quicktime) loaded by shake
that is trying to manipulate the window manager.
Regaring #1, try running the same shake command from a terminal
to see if it opens a GUI. If it does, that's the problem.
If it doesn't, then it's probably #2, which means some OSX library
(that shake is loading) is trying to access the window manager when
the library is loaded and initialized.
In the past I've seen QuickTime libraries cause this, where someone
either updated the quicktime libs from Apple with buggy libs causing
the problem, or a recent OS re-install from CDs that DIDN'T take the
latest updates from Apple.
> This is only happening on 3 machines, the others are fine.
Check the patch level of the machines (ie. run 'sw_vers' on each box)
You can probably replicate this problem by ssh'ing into the same machine
that rendered the frame and failed, and logging in as the same user the
rush render was running shake as. This user likely doesn't match the user
logged into the window manager, and thus the error about being unable to
connect to the window manager.
Shake renders should not be trying to access the window manager
unless something is wrong.. ie. #1 or #2 above.
Dylan Penhale wrote:
[posted to rush.general]
Has anyone seen the following error when trying to render shake jobs
through rush?
Executing: shake -exec
/var/tmp/.RUSH_TMP.42/re_245_330_x005sc_F003.shk -t 26-26
-proxyscale Base -vv -cpus 2
INIT_Processeses(), could not establish the default
connection to the WindowServer.--- shake: terminated by signal 6
This is only happening on 3 machines, the others are fine.
The 3 machines are able to resolve DNS, and get the UID/GID of the
submitting user.
Shake runs fine on these boxes.
I notice that this may be similar to the AE issue listed here:
http://seriss.com/rush-current/issues-afterfx-6.5/index.html
Should I change the shake owner to 0:0 on the problem hosts? I can't
figure why only some boxes have the problem.
Regards
Dylan Penhale
Systems Administrator
Fuel International
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|