On Fri, Jul 5, 2013 at 10:28 AM, Rainer Gerhards <[email protected]>wrote:
> > On Fri, Jul 5, 2013 at 10:06 AM, Schmidauer Martin <[email protected] > > wrote: > >> Unfortunately, I cannot make the whole debug file to the public, because >> there are customer mail logs in it. I'm not sure how to remove the msg >> part >> of the log lines without destroying the debug content. >> The zipped file is about 360k big, can I send it to you directly? >> >> > Yes, pls do. I'll keep it private. I just can't guarantee I'll have more > than a quick look today, but in any case soon. > Looking at the log, it looks like MSSQL is continously failing as long as the log runs. Rsyslog retries, then tries to begin a new transaction and then MSSQL returns an error state (at least this is what it looks ;)). Can you see anything in some MSSQL tools to see if there is a new connect? It looks like we have one of three options a) bug in rsyslog's omlibdbi b) problem in libdbi's MSSQL driver and reconnect c) problem with MSSQL itself I hope it's a) and will have some more look at the code. I'll probably create a special version for your use. If so, can you build from source and execute that version? I am asking because without that, creating instrumented code makes little sense ;) Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
