> I think I found the culprit: errors on Begin/End Transaction did not close the
> session, so it was always reused (and so most probably always got the
> "connection broken" state back, which initiated another roundtrip...).
>
> This is the patch:
> http://git.adiscon.com/?p=rsyslog.git;a=commi
> Tried to be too quick with my feedback. Maybe this even points to the root
> cause. Hold on with your testing, I'll see that I provide yet another
patch,
> probably I am able to nail it down (but may take a short while).
Very good.
> Just be warned that whatever I do you need to runtime test it
> > What do you want me to do exactly?
> it is best to run rsyslog interactively. You can then simply say - in a
terminal
> window:
> $ valgrind /path/to/rsyslogd -n ...regular options-- 2> valgrind.log
> You need to
>
> $ kill rsyslog-pid
There are some errors. See attachment.
Martin
valgrin
> 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 ;)).
That is interesting. I cannot see any tcp SYN packet, once the TCP
connect
tag, 04. Juli 2013 18:59
> An: rsyslog-users
> Betreff: Re: [rsyslog] reconnection to database server problem
>
> On Thu, Jul 4, 2013 at 6:56 PM, Schmidauer Martin
> wrote:
>
> > The connection was broken for about 5 minutes, I waited 10 to 15
minutes.
> >
> >
&g
; Rainer
>
>
> On Thu, Jul 4, 2013 at 6:32 PM, Schmidauer Martin
> wrote:
>
> > Hello,
> >
> > I am using rsyslog to log into a MSSQL DB with omlibdbi and freetds.
> > I wanted to test the reliability and removed the network connection to
> > the DB ser
Hello,
I am using rsyslog to log into a MSSQL DB with omlibdbi and freetds.
I wanted to test the reliability and removed the network connection to the
DB server (with a host route to localhost) on the rsyslog server. After a
while all connections to the DB server terminate. After removing the host
et: Dienstag, 02. Juli 2013 12:12
> An: rsyslog-users
> Betreff: Re: [rsyslog] libdbi error
>
> On Tue, Jul 2, 2013 at 12:05 PM, Schmidauer Martin
> wrote:
>
> > > > rsyslog-libdbi-7.4.1-1.el6.x86_64
> > > > rsyslog-7.4.1-1.el6.x86_64
> > > > lib
> > rsyslog-libdbi-7.4.1-1.el6.x86_64
> > rsyslog-7.4.1-1.el6.x86_64
> > libdbi-0.8.3-4.el6.x86_64
> > libdbi-drivers-0.8.3-5.1.el6.x86_64
>
> Are you sure those libdbi packages provide freetds/MSSQL support?
I'm not completely sure. I found in the Chanchelog file oft he Centos
libdbi-drivers pac
Hello,
I am trying to set up a syslog server to log into a MSSQL DB with freetds.
The connection test with tsql is succeeding.
I am using CentOS 6.4 with the rsyslog yum repository from rsyslog.com. The
following packages are installed:
rsyslog-libdbi-7.4.1-1.el6.x86_64
rsyslog-7.4.1-1.el6.x86_6
> Have you configured mysql to use ANSI standard escaping? Usually, \' is
> required in mysql (unfortunately).
We are using MSSQL, not MySQL. Obviously \' is used in our present rsyslog
configuration. The template looks like:
$template MSSQL-exim_out,"exec dbo.insertEmail_Out @host='%HOSTNAME%',
We use rsyslog to fill our MSSQL database with exim mail logs. Sometimes in
msg there is a ' character (39 dez) wich the MSSQL interprets. The solution
on the MSSQL side is to escape the ' with a secon one. Is there a
possibility to change the content oft he msg in this way?
Thanks, Martin
sm
12 matches
Mail list logo
