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
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
