On 10/20/2017 07:58 PM, tdarby@email.arizona.edu wrote:

On 10/20/2017 12:32 PM, tdarby(a)email.arizona.edu wrote:
Is there a core file you get a stack trace from?

Not sure how to set up to get a core dump in a docker container.

Me neither, but once the server is up and running can you follow the steps outlined here:

http://www.port389.org/docs/389ds/FAQ/faq.html#sts=Debugging%C2%A0Crashes

Make sure debug symbols are installed (the degbuinfo pacakge). Unless you build it yourself with debugging enabled (enable-debug) a configure option, and "-g" for C flags.

CFLAGS='-g -pipe -Wall -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic' CXXFLAGS='-g -pipe -Wall -O0 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic' ../389-ds-base/configure --enable-autobind --with-selinux --with-openldap --with-tmpfiles-d=/etc/tmpfiles.d --with-systemdsystemunitdir=/usr/lib/systemd/system --with-systemdsystemconfdir=/etc/systemd/system --enable-debug --with-systemdgroupname=dirsrv.target --with-fhs --libdir=/usr/lib64 --enable-tcmalloc--with-systemd

What are the schema definitions for lastUpdated & lastStarted?

As I said earlier, these are standard directory string attributes, multi-valued, nothing special. They are used in 3 different entries.

The error indicates that there is no syntax plugin for these attributes - even in the code says its not sure how that could even happen, that's why I'm asking what syntax they used. But is keeps happening with just these two attributes.

So you are saying its syntax is: 1.3.6.1.4.1.1466.115.121.1.15

Can you reproduce this in a non-production environment where you could
run it under valgrind?
Or can you run it under gdb so we can catch the crash live?

If I can figure out how to do this I will, but again, this is a difficult thing to reproduce. The 1.3.7 servers ran for a week before it happened.

I know its hard, but unfortunately it might be the only way we are going to fix the crash. Unless we get a good core file where we can dive in a see whats going on. We might also need to run the server under valgrind if its some type of memory corruption - this can be disruptive to a production environment that's why if we can reproduce it in house that would be better for everyone.

Are there any other errors messages at the time you see: 
"valueset_value_syntax_cmp - slapi_attr_values2keys_sv failed for type
lastStarted"?

These were the only errors.
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org