Getting a stacktrace/core file would be very useful. Check out the link
below so you can catch the next crash.
http://www.port389.org/docs/389ds/FAQ/faq.html#sts=Debugging%C2%A0Crashes
Mark
On 01/11/2016 07:47 AM, Todor Petkov wrote:
Hello,
few days ago, as today, the ldap process crashed. I found this in
/var/log/messages:
Jan 6 17:26:24 ds1 kernel: ns-slapd[18010] trap invalid opcode
ip:7f1372fabd60 sp:7f13499e7518 error:0 in
libfreeblpriv3.so[7f1372f59000+72000]
Jan 11 14:28:41 ds1 kernel: ns-slapd[14263] trap invalid opcode
ip:7f852c56fd60 sp:7f85037ea518 error:0 in
libfreeblpriv3.so[7f852c51d000+72000]
There is no process in the memory, so I had to do "service dirsrv
restart"
Does someone else have the same problem(s)? I see there are updates
for ds-base and ds-base-libs, and I will update later.
Here is more information about my setup:
OS: Centos 6,
kernel: 2.6.32-431.17.1.el6.x86_64
389-ds packages:
389-admin-console-1.1.8-1.el6.noarch
389-ds-1.2.2-1.el6.noarch
389-ds-base-libs-1.2.11.15-65.el6_7.x86_64
389-adminutil-1.1.19-1.el6.x86_64
389-ds-console-1.2.6-1.el6.noarch
389-admin-console-doc-1.1.8-1.el6.noarch
389-admin-1.1.35-1.el6.x86_64
389-ds-base-1.2.11.15-65.el6_7.x86_64
389-console-1.1.7-1.el6.noarch
389-ds-console-doc-1.2.6-1.el6.noarch
389-dsgw-1.1.11-1.el6.x86_64
Regards,
--
389 users mailing list
389-users@%(host_name)s
http://lists.fedoraproject.org/admin/lists/[email protected]
--
389 users mailing list
389-users@%(host_name)s
http://lists.fedoraproject.org/admin/lists/[email protected]
