> you can always get the latest (upstream) version. If you could at least > test this on Fedora with the latest version of 389 so we can rule out if > its a known issue or a new one. > This is now fixed upstream on Fedora (26 and > up) I'm testing this in a docker container and the latest container image is Fedora 26 and the only package it offers me is 1.3.6.8. I was testing a new install of this last night on two instances and the failure happened again with the same errors and now 389 server won't stay up. It will run for a few minutes, then generate hundreds of slapi_attr_values2keys_sv failed for type lastUpdated errors and then die. Again, this didn't seem to bother the two 1.2 servers that were replicating with them. I tried setting up the system for core dumps but I can't find a core dump when it dies. Is there anything you want me to look at while it's in this state? _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
