|
On 10/10/2017 10:27 AM,
tdarby@xxxxxxxxxxxxxxxxx wrote:
First you need to make sure cores are allowed to be generated:When the server crashes do you get a core dump or similar? That would really help.Where do I find a core dump? http://www.port389.org/docs/389ds/FAQ/faq.html#sts=Debugging%C2%A0Crashes Where the core file gets written can vary on OS/OS config. It is sometimes found here: /var/spool/abrt/*/coredump or /var/lib/systemd/coredump/ You could also just search the filesystem for "core". Once you find it, attach gdb and get a stack trace. See the doc above for more info on that as well. Regards, Mark I think the issue with the lastUpdated type is that this is a custom element of your schema - I can't find any references to it at all in our code base. Can you send me your schema definiton for this attribute?This is the entry that after I deleted it enabled the server to start up again: dn: cn=grouperstatus, ou=People,dc=eds,dc=arizona,dc=edu objectClass: edsstatus objectClass: top cn: grouperstatus It contains the multi-valued attributes lastUpdated and lastStarted, both strings. _______________________________________________ 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
