[rsyslog-notify] Forum Thread: Re: RELP - "protocol family not supported"? - (Mode 'reply')

[noreply at adiscon.com]

User: gazpacho 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=25024#p25024

Message: 
----------
I'm getting more information, but I don't feel like I'm closing in on
anything.  :-(

Attached below are two full debug logs.  The only difference between the
runs was whether or not the rsyslog.conf file had the line providing
"tls.myCert".  If it's there, then rsyslog poops out with the error noted
above about 10046.

It's interesting to notice that aside from time stamps and memory
locations, the two logs are nearly identical right up to the point of the
error.  This tells me that the code flow is really the same for both up to
that point.

The very last [i:3raoytxf]pThis->pEngine->dbgprint()[/i:3raoytxf] that
comes out is early in the function
[i:3raoytxf]relpTcpLstnInit()[/i:3raoytxf], as found in the file tcp.c.  No
other error conditions seem to trigger in that function, which leaves me a
bit confused.  Suspicion at this point has me looking at the
[i:3raoytxf]listen()[/i:3raoytxf] calls in that funciton, but again... the
error handlers don't seem to be triggering.  It's also interesting (to me)
that the error that does come out appears to be well before any attempt to
actually look at the *.pem file.  I get the same problem if I specify a
real cert file, or a file that doesn't even exist.