On 11/14/2013 08:50 AM, Mitja Mihelič wrote:
One of the consumers has crashed again and I have attached the stacktrace.
Four hous later it crashed again.

I do hope there is something in the stacktraces, so that something can be done to prevent future crashes.

Unfortunately, not enough.  Looks like there is still some mismatch between the version of the package and the version of the debuginfo package.

rpm -q 389-ds-base 389-ds-base-debuginfo openldap openldap-debuginfo db4 db4-debuginfo nss nss-debuginfo nspr nspr-debuginfo glibc glibc-debuginfo

Also, if you are seeing the message:
ber_flush skipped because the connection was marked to be closed or abandoned

This means you are running with the CONNS error log level, which means you may have a lot of useful information in your errors log.  Would you be able to provide that?


The last log message in errors log was both times:
ber_flush skipped because the connection was marked to be closed or abandoned

The following versions 389ds packages were installed at the time:
389-admin-1.1.29-1.el6.x86_64
389-admin-console-1.1.8-1.el6.noarch
389-admin-console-doc-1.1.8-1.el6.noarch
389-adminutil-1.1.15-1.el6.x86_64
389-console-1.1.7-1.el6.noarch
389-ds-1.2.2-1.el6.noarch
389-ds-base-1.2.11.15-22.el6_4.x86_64
389-ds-base-libs-1.2.11.15-22.el6_4.x86_64
389-ds-console-1.2.6-1.el6.noarch
389-ds-console-doc-1.2.6-1.el6.noarch
389-dsgw-1.1.10-1.el6.x86_64

Reragds, Mitja


On 17. 07. 2013 09:52, Mitja Mihelič wrote:


It may be best if I removed all 389DS related data from both of the consumer servers and start fresh. If they crash again I will send the relevant stack traces.