Hello.

I have rsyslog 5.6.2 and I just tried to receive messages via TCP. The
sender is syslog-ng, I don't know exactly which version, not under my
control. The transfer mostly works, as far as I can see without strict
testing.

But in rsyslog's log file I see several messages which look like this:

   rsyslogd-2105: Tearing down TCP Session - see previous messages for reason(s)
   [try http://www.rsyslog.com/e/2105 ]

And then there is no previous message which is different than this one and
if I go back far enough there is the startup message. There's nothing
else in the log (produced by the *.* selector at the end of the config file).

I tried to check the URL above, but I'm getting an error page with says:

   Fatal error: Call to undefined function SendEmailToAdiscon() in
   /home/adisconweb/www/kb.monitorware.com/kbeventdb.php on line 217

That's generated by
http://kb.monitorware.com/kbeventdb-list-1-Adiscon-rsyslog-rsyslogd-2105.html

I checked the source and the only file with the above message is
plugins/imgssapi/imgssapi.c in the

   if(tcps_sess.DataRcvd(pSess, buf, ret) !  = RS_RET_OK)

block. I didn't even know I was using gssapi plugin. My configuration
related to TCP is:

$ModLoad imtcp
$InputTCPServerBindRuleset indata
$InputTCPServerRun 514

and the rest is setup for the UDP receiver and storing messages. I checked
with Google and rsyslog bug tracker for "Tearing down TCP Session", but
with zero results (except for the source code matches).

I am willing to debug this and submit a patch (which would at least log
the missing previous message), but before I do, I'd just like to ask if
someone has seen this before or has any idea what's going on. I'm a bit
confused with gssapi module being used. My OS is CentOS 5.5, if that's
relevant.

-- 
 .-.   .-.    Yes, I am an agent of Satan, but my duties are largely
(_  \ /  _)   ceremonial.
     |
     |        [email protected]
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to