Jason Spangler
2016-11-04 14:39:01 UTC
Hi all,
Just fyi to folks - there appears to be a hang bug in 389 dirsrv (aka
ns-slapd) which, in my install at least, was being tickled by a large
batch of messages being processed by wallaced. This led to no email
being received, processed, or sent by my Kolab installation (even after
multiple restarts).
Bug entries:
https://bugzilla.redhat.com/show_bug.cgi?id=1370121
https://bugzilla.redhat.com/show_bug.cgi?id=1329061
It appears the fix is only available to RedHat customers currently:
https://rhn.redhat.com/errata/RHSA-2016-2594.html
I'm running 389-ds-base-1.3.4.0-33.el7_2.x86_64 (the EL7 rpm).
In my instance, the call stack in dirsrv matched the one from the hang
bug entry.
To get around the dirsrv hang, I had to disable wallaced processing in
/etc/postfix/master.cf for now (until the dirsrv fix is released).
Hope this helps someone else and saves them some time.
- Jason
Just fyi to folks - there appears to be a hang bug in 389 dirsrv (aka
ns-slapd) which, in my install at least, was being tickled by a large
batch of messages being processed by wallaced. This led to no email
being received, processed, or sent by my Kolab installation (even after
multiple restarts).
Bug entries:
https://bugzilla.redhat.com/show_bug.cgi?id=1370121
https://bugzilla.redhat.com/show_bug.cgi?id=1329061
It appears the fix is only available to RedHat customers currently:
https://rhn.redhat.com/errata/RHSA-2016-2594.html
I'm running 389-ds-base-1.3.4.0-33.el7_2.x86_64 (the EL7 rpm).
In my instance, the call stack in dirsrv matched the one from the hang
bug entry.
To get around the dirsrv hang, I had to disable wallaced processing in
/etc/postfix/master.cf for now (until the dirsrv fix is released).
Hope this helps someone else and saves them some time.
- Jason