On 9 Oct 2019, at 02:41, Mark Reynolds <mreynolds(a)redhat.com>
On 10/8/19 12:01 PM, Paul Whitney wrote:
> We have discovered that one of out test LDAPS servers has been down for sometime and
we are not seeing anything that indicate why. However, when we start the slapd-config
instance up, it kicks off then dies with error "memory violation" sig=7.
"one of"? Normally when I see something like this, I would immediately assume
you have multiple servers that are built identically, and in a topology.
If only one machine is failing out of the group, perhaps it's another error that's
worth investigating. I've seen this before with failing ECC ram where it would start
to throw errors on one machine in the group only.
So it could be worth checking for things specific to that one machine.
Anything in the errors log?
Can you get a stack trace of the crash at startup?
> I tried to remedy by upgrading to the latest release in our repos,
(389-ds-base-220.127.116.11-10), same results.
> Paul M. Whitney
> 389-users mailing list --
> To unsubscribe send an email to
> Fedora Code of Conduct:
> List Guidelines:
> List Archives:
389 Directory Server Development Team
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
Senior Software Engineer, 389 Directory Server