> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Aaron Wiebe > Sent: Wednesday, November 04, 2009 2:09 PM > To: rsyslog-users > Subject: Re: [rsyslog] Queuing bug (4.5.5) / Problem in production > > On Wed, Nov 4, 2009 at 1:34 AM, Rainer Gerhards > <[email protected]> wrote: > > > > I add the capability to send the debug log out via UDP syslog (not > via the > > usual channels, but rather via a special send function inside the > debug > > printf system). Then, when a problem occurs, we could enable the > debug printf > > (which is present in production builds as well) and make it output > the data > > to a remote server (or a special listener, even netcat, running on > the local > > machine). > > > > I could turn on/off this via a signal (as we currently do for sending > debug > > message to stdout). > > That could work - I could see that being an acceptable step for some > of our environments here.
OK, that sounds good. Will see what I can do (I think this could be generally useful). > > > Alternatively, one could load imdiag into a suspect instance and use > that to > > gain more in-depth information. However, I am not sure if that would > be > > suitable for use in production, at least it is questionable from a > security > > POV. > > Is there more docs on imdiag and the enhancements you've made to it > recently kicking around? I'll see if I can't make use if it in my > efforts to reproduce the issue (which probably won't start until next > week). No, actually not. Initially it was intended to be a thing mostly for Rainer and the testbench ;) I'll see that I do a write-up on production troubleshooting and include it. Any more feedback from anyone on this issue is appreciated. Rainer > > -Aaron > _______________________________________________ > 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
