Anton Blomberg wrote:
> C:\Rush\bin>rush.exe -ljf jobserver.709
> Jobid: jobserver.709
> [..]
> LogDir: //logserver/logs/rush/jobserver.709
> [..]
> JobDoneCommand: python //tools/jobdone.py
Hmm, that all looks OK, provided the directory
//logserver/logs/rush/jobserver.709/
..and the path
//tools/jobdone.py
..are both accessible from host "jobserver"
(which is where the jobdonecommand is invoked).
eg. login to machine 'jobserver' as anton.blomberg,
open a DOS window and invoke these two commands:
dir \\logserver\logs\rush\jobserver.709
dir \\tools/jobdone.py
..if they both work, then I'm stumped (see below).
If they fail, then that's the problem; the paths
have to resolve on the jobserver as well as the
render nodes.
BTW, the fact I'm showing backslashes (\) in that dir command
instead of frontslashes (/) is just to serve the purposes of
DOS; the frontslashes you have submitted with are fine.
I'm sure it's /trying/ to run the command, but my guess
offhand is it can't because maybe it can't reach either
of those two directories from the machine "jobserver".
Take a look in jobserver's c:\rush\var\Orushd.log
to see if there are any errors about the command or the
log directory. If rush couldn't run the command, and couldn't
create the log, it would advertise the problem in the rushd.log
on the job server machine (in this case, "jobserver").
Look in the Orushd.log (as opposed to the rushd.log) because
the command tried to run yesterday (02/21), and the rushd.log
rotates out at midnight ever night.
If need be, contact me directly via private email, and
we can arrange an interactive chat so we can try a few
things in realtime.
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|