I just pushed a new branch v4.6.4-omprogTest to rsyslog's public git. It has the additional instrumentation and should provide more insight.
Rainer > -----Original Message----- > From: Mark Olliver [mailto:m...@thermeon.com] > Sent: Thursday, February 10, 2011 2:13 PM > To: Rainer Gerhards > Cc: rsyslog-users > Subject: Re: [rsyslog] OMPROG Doccumentation > > Hi, > > Yes I should be able to build from a GIT tree ok. > > Regards > > Mark > > On 10 February 2011 13:06, Rainer Gerhards <rgerha...@hq.adiscon.com> > wrote: > > mhhh... I can see that omprog is called, and everything looks like it > should > > be. But that could be absence of debug information. I could probably > add some > > more instrumentation so that we get more insight. Could you build it > from a > > git tree? > > > >> -----Original Message----- > >> From: Mark Olliver [mailto:m...@thermeon.com] > >> Sent: Thursday, February 10, 2011 1:53 PM > >> To: Rainer Gerhards > >> Subject: Re: [rsyslog] OMPROG Doccumentation > >> > >> Hi Rainer, > >> > >> Here is the logfile as requested. > >> > >> Thanks > >> > >> Mark > >> > >> On 10 February 2011 12:44, Rainer Gerhards > <rgerha...@hq.adiscon.com> > >> wrote: > >> > I have now looked at the code. I can clearly see that a write to > the > >> pipe fd > >> > is done for every message. Could you provide a debug log? That > would > >> be > >> > useful. Google for "rsyslog debug", that should bring up the > relevant > >> page > >> > (usually at position 1). > >> > > >> > Raienr > >> > > >> >> -----Original Message----- > >> >> From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog- > >> >> boun...@lists.adiscon.com] On Behalf Of Mark Olliver > >> >> Sent: Thursday, February 10, 2011 12:46 PM > >> >> To: rsyslog-users > >> >> Subject: Re: [rsyslog] OMPROG Doccumentation > >> >> > >> >> Hi Rainer > >> >> > >> >> Yep that is what it appears to be, I have a Ruby script listening > >> >> which is executed by omprog, which is set to send an sms with the > >> >> error message however, as the moment i have the script set to > dump > >> to > >> >> a file what it reads from STDIN. Only when rsyslog is shutdown > does > >> >> the file get populated with data but as soon as the log message > is > >> >> sent to the log the script is hit and the file opened. So it > would > >> >> appear the omprog is not closing its handle or not flushing the > data > >> >> until rsyslog closes. > >> >> > >> >> I am currently using rsyslog 4.6.4 (backported with omprog > manually > >> >> builtin) on ubuntu 10.04 > >> >> > >> >> Thanks for you help > >> >> > >> >> Mark > >> >> > >> >> > >> >> On 10 February 2011 11:40, Rainer Gerhards > >> <rgerha...@hq.adiscon.com> > >> >> wrote: > >> >> > > >> >> >> -----Original Message----- > >> >> >> From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog- > >> >> >> boun...@lists.adiscon.com] On Behalf Of Mark Olliver > >> >> >> Sent: Thursday, February 10, 2011 12:38 PM > >> >> >> To: rsyslog-users > >> >> >> Subject: Re: [rsyslog] OMPROG Doccumentation > >> >> >> > >> >> >> Hi, > >> >> >> > >> >> >> I have been playing more with OMPROG and have it working > nearly > >> the > >> >> >> way i want now in that it it now passes the correct message to > my > >> >> >> external script by the pipe however, OMPROG seems to only > flush > >> the > >> >> >> data out to the pipe when rsyslog is shutdown, until that > point > >> it > >> >> >> just keeps the pipe/script open. > >> >> > > >> >> > You mean no data is sent until shutdown? I'll try to have a > look > >> this > >> >> > afternoon... > >> >> > > >> >> > Rainer > >> >> > Is there a way to force OMPROG to > >> >> >> flush each line to the pipe and then close the pipe or is > there a > >> >> >> better way to do this? > >> >> > > >> >> >> > >> >> >> So far i have: > >> >> >> $template smsBody,"%programname% 44788900000 %hostname% > %rawmsg%" > >> >> >> $ModLoad omprog > >> >> >> $actionomprogbinary /usr/bin/alert1 > >> >> >> if $programname == 'FILLER' then :omprog:;smsBody > >> >> >> & ~ > >> >> >> > >> >> >> Thanks > >> >> >> > >> >> >> Mark > >> >> >> _______________________________________________ > >> >> >> rsyslog mailing list > >> >> >> http://lists.adiscon.net/mailman/listinfo/rsyslog > >> >> >> http://www.rsyslog.com > >> >> > _______________________________________________ > >> >> > rsyslog mailing list > >> >> > http://lists.adiscon.net/mailman/listinfo/rsyslog > >> >> > http://www.rsyslog.com > >> >> > > >> >> _______________________________________________ > >> >> rsyslog mailing list > >> >> http://lists.adiscon.net/mailman/listinfo/rsyslog > >> >> http://www.rsyslog.com > >> > _______________________________________________ > >> > rsyslog mailing list > >> > http://lists.adiscon.net/mailman/listinfo/rsyslog > >> > http://www.rsyslog.com > >> > > > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
