Hi Chris, It will bomb out before you could do anything with the log data (e.g calling log_info()). I think this can only be done through code modification like appending the first 100 characters of the string to the error message. Or you could change the throw() to have it abort instead and then you can look at the data with a debugger.
Regards, Botond On Wed, 17 Sep 2014 14:25:42 -0400 Didjit Charlebois <didji...@gmail.com> wrote: > Hi, > > I routinely come across this error and I wanted to put in some > debugging to determine what event (log entry) is causing the issue. > > I snag the event time from every log entry and was thinking I could put > a log_info in im_Internal but that did not work. > > Any ideas how I can find out the input that is being used and some event > data so I can find the issue in the source log? I want to see if I can > just ignore this long files. > > Thank you, > > Chris ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
