Luigi Tommaseo wrote:
is there any way we can have time stamp on the logs? what we would like
to do here is to create a network and server performance log and
correlate it to the logs of the render boxes to see if the problems we
are having in the conversion to mentalray are indeed related to network
performance or something else.
Hi Luigi,
Which logs, the frame logs, or the cpu accounting logs?
There are several time stamps in the frame logs:
o The file's date stamp on the log itself
o The file's 'Started:' date stamp from the log, ie:
% grep Started: /path/to/log/0001
-- Started: Thu Jan 05 14:46:14 2006
In the cpu accounting logs (rush/var/cpu.acct), there's date stamps
on all the entries in time(2) format.
You should be able to come up with a simple script to dive into
all the cpu.acct logs, sort the entries by date, and then easily
be able to cross reference the frames that rendered vs. the errors
in your server performance log.
I'd go for the cpu.acct logs on the remotes; those are easy to
collect and sort, and has all the job title/owner/frame#/exit code
info in them.
You might also cross reference errors with your system logs on
each render machine, ie. /var/log/messages (LINUX),
/var/log/system.log (OSX), or the windows event manager logs.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)
|