> 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").
Turns out this was the problem being advertised in the rushd.log:
02/29,15:50:58 INFO jobdonecommand 'python //agnes/resources/tech/admin/jobdone.py' failed for jobid=sierra2.890: unknown uid 11002
..which means the submitting user's uid/gid on the job server
was different from the uid/gid for his account on the machine
he was submitting from, the discrepancy causing this error.
Solution is for the sysadmin to reconfigure his account on
the job server to have matching uid/gid values to his account
on the submit host.
|