[syslog-ng] program dies

[janth at moldung.no]

On Fri, Oct 14, 2005 at 08:40:52AM -0700, Jeff DiNisco wrote:
> I'm running syslog-ng on solaris 10.  I have a destination defined as - destination d_alert {
> program("/usr/local/admin/syslog-ng/alert.bash"); }; 
> 
> when syslog-ng is started, these processes also start...
> /bin/bash /usr/local/admin/syslog-ng/alert.bash
> /bin/sh -c /usr/local/admin/syslog-ng/alert.bash
> 
> About an hour later, for no apparent reason, the 2 alert.bash processes die but the syslog-ng
> process continues to run.  I've implemented a watchdog script to alert and restart syslog-ng when
> they die.  It's interesting to note that they seem to die exactly 1 hour after being restarted.
> 
> command used to start syslog-ng -  /usr/local/sbin/syslog-ng -f /usr/local/etc/syslog-ng.conf >>
> ${logfile} 2>&1
> 
> alert.bash script...
> #!/bin/bash
> 
> export mailaddr=jeff at xxxxxx.com
> 
> while read input
> do
>   hostname=`echo ${input} |awk '{print $4}' |sed 's|/.*||'`
>   program=`echo ${input} |awk '{print $5}' |sed 's|[[(].*||'`
> 
>   echo ${input} | mailx -s "${program} alert on ${hostname}" ${mailaddr}
> done
> 
> Any help would be greatly appreciated. 

What does set | grep TMOUT says?
>From man bash(1):

TMOUT  If set to a value greater than zero, TMOUT is treated as the default timeout for the read builtin.  The select command terminates if input
        does not arrive after TMOUT seconds when input is coming from a terminal.  In an interactive shell, the value is interpreted as the number
        of seconds to wait for input after issuing the primary prompt.  Bash terminates after waiting for that number of seconds if input does not
        arrive.

--
Jan Thomas Moldung