Re^2: General perl question. Multiple servers.

++ Much better than my idea below, but there would need to be a reliable way to identify the cases where any of the 150 processes fail before they get to the point of sending their UDP packet to the log server. Not hard to handle, just easy to forget...

update: On second thought, if the log data from each host is anything more than a single summary report printed at the end of each job, I would still kinda prefer my approach. If the jobs are printing progress reports at intervals, the entries submitted to a central syslog server will tend to be interleaved, and will need to be sorted out. Not a big deal, obviously, but it might be handier to have the stuff "pre-sorted" by harvesting from each machine.

Comment on Re^2: General perl question. Multiple servers.

Replies are listed 'Best First'.
Re^3: General perl question. Multiple servers. by shmem (Chancellor) on Oct 06, 2007 at 18:03 UTC
there would need to be a reliable way to identify the cases where any of the 150 processes fail A 'job started' message could be sent by a wrapper which cares about the process and reports its exit status. the entries submitted to a central syslog server will tend to be interleaved syslog is configurable, and one could send the the log messages to different files based on level/facility and host. Anyways, the log line is marked with the host sending the log message, so sorting things out is as easy as grepping the log file for a host. --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply]

Replies are listed 'Best First'.

Re^3: General perl question. Multiple servers.
by shmem (Chancellor) on Oct 06, 2007 at 18:03 UTC

there would need to be a reliable way to identify the cases where any of the 150 processes fail

A 'job started' message could be sent by a wrapper which cares about the process and reports its exit status.

the entries submitted to a central syslog server will tend to be interleaved

syslog is configurable, and one could send the the log messages to different files based on level/facility and host. Anyways, the log line is marked with the host sending the log message, so sorting things out is as easy as grepping the log file for a host.

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

[reply]