On 10/20/2017 12:32 PM, tdarby@xxxxxxxxxxxxxxxxx wrote: >> I spent a lot of time yesterday trying different ideas for reproducing the crash and >> haven't found the right sequence of events yet. I did discover that I was able to >> bring back a failed server instance by deleting a different entry, cn=grouperfeeds, which >> like cn=grouperstatus contains the lastUpdated and lastStarted attributes. >> >> I'm testing now with 1.3.7.6, built from source, on Fedora 26. > It was looking good until both test servers crashed again this morning: > > 389-ds-base-libs-1.3.7.6-1.fc26.x86_64 > 389-ds-base-1.3.7.6-1.fc26.x86_64 > > I see hundreds of these errors: > [20/Oct/2017:01:55:11.852720430 -0700] - ERR - valueset_value_syntax_cmp - slapi_attr_values2keys_sv failed for type lastStarted > > So, it's happening on both the lastStarted and lastUpdated attributes of cn=grouperstatus. Is there a core file you get a stack trace from? What are the schema definitions for lastUpdated & lastStarted? 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? Are there any other errors messages at the time you see: "valueset_value_syntax_cmp - slapi_attr_values2keys_sv failed for type lastStarted"? Mark > > What I know for sure is that this never happened on 389 1.2.11.15 and has happened on 1.3.6.1, 1.3.6.8, and 1.3.7.6 > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
