[rsyslog-notify] Forum Thread: rsyslog crashes with omrelp - (Mode 'post')

[noreply at adiscon.com]

User: nottoosmart 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=25885#p25885

Message: 
----------
rsyslogd 8.8.0, compiled with:
        PLATFORM:                               x86_64-redhat-linux-gnu
        PLATFORM (lsb_release -d):
        FEATURE_REGEXP:                         Yes
        GSSAPI Kerberos 5 support:              No
        FEATURE_DEBUG (debug build, slow code): No
        32bit Atomic operations supported:      Yes
        64bit Atomic operations supported:      Yes
        memory allocator:                       system default
        Runtime Instrumentation (slow code):    No
        uuid support:                           Yes
        Number of Bits in RainerScript integers: 64

CentOS release 6.3

I have a server that both accepts syslog TLS encrypted with imrelp and
sends additional syslog to another rsyslog server using omrelp.
As soon as I added the action for omrelp I get a crash that happens VERY
often:

rsyslogd: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock ==
((ath_mutex_t) 0)' failed.

The ath.c is a reference to libgcrypt.  I have version 1.4.5-9.el6_2.2
installed on these servers.

Here are the versions of librelp and rsyslog-relp on the servers:
librelp.x86_64             1.2.7-3.el6
rsyslog-relp.x86_64        8.8.0-1.el6

Is this is known issue?