Saurabh Lahoti saurabh.astronomy@gmail.com schrieb am 22.08.2018 um 20:25 in
Nachricht CAB5-MqpWKCW+6YuzkNJ=aGK1WS1Nh5hG3ppWMOPjhe2ic5VCHQ@mail.gmail.com:
Dear Brian,
Sincere apologies but am literally clueless what to do next now because of this frequent crash & impacting routine operational task. Hence, need to get this resolved at the earliest with your (& all ) help.
This is a custom overlay build in 2006 by our ex team mate & he did the installation on older versions. This August we did a migration from old version to 2.4.46 & lmdb backend. Is it that we skipped some steps in this movement..?
I'd say yes: You should have checked that your custom module is ready for a software upgrade. Maybe go back to the software that worked until you have another that works also.
Regards, Ulrich
*Thanks & Kind Regards,* Saurabh LAHOTI. *Ideas enlighten Innovation**!!!* Please consider the environment before printing this mail..!!
On Wed, 22 Aug 2018 at 20:19, Brian Reichert reichert@numachi.com wrote:
On Wed, Aug 22, 2018 at 04:33:46PM +0200, Saurabh Lahoti wrote:
Dear,
What is you're recommendation to fix this problem on our side..? It's
been
haunting our operational activities on daily basis.. ????
Who's responsibility do you think this is?
From what I can tell, the OpenLDAP project only supplies source code.
https://www.openldap.org/software/download/Who installed those binaries? Where did they come from?
*Thanks & Kind Regards,* Saurabh LAHOTI. *Mob: +32.499.82.37.88* *Ideas enlighten Innovation**!!!* Please consider the environment before printing this mail..!!
On Fri, 17 Aug 2018 at 16:43, Brian Reichert reichert@numachi.com
wrote:
On Thu, Aug 16, 2018 at 02:00:20PM +0200, Saurabh Lahoti wrote:
Dear,
Today, received below error in /var/log/messages with OpenLDAP
instance
crashing.
That looks like either:
- You have a bad SIM (very unlikely)
- You have a corrupted uniquemember.so.0.0.0 shared library.
- You may have conflated OpenLDAP packages installed that have a
critical
incompatibility amidst the installed binaries/libraries.
It did write a core file; there are many tutorials about exploring a core file to help understand why the segfault occurred.
Aug 16 13:21:07 muledeer kernel: slapd[29253]: segfault at 0 ip 00007fbeddf3af09 sp 00007fb72effc480 error 4 in uniquemember.so.0.0.0[7fbeddf3a000+2000] Aug 16 13:21:08 muledeer abrt[24629]: Saved core dump of pid 16470 (/usr/app/ldap/openldap2.4.46/libexec/slapd) to /var/spool/abrt/ccpp-2018-08-16-13:21:07-16470 (472973312 bytes) Aug 16 13:21:08 muledeer abrtd: Directory
'ccpp-2018-08-16-13:21:07-16470'
creation detected Aug 16 13:21:08 muledeer abrtd: Executable '/usr/app/ldap/openldap2.4.46/libexec/slapd' doesn't belong to any
package
and ProcessUnpackaged is set to 'no' Aug 16 13:21:08 muledeer abrtd: 'post-create' on '/var/spool/abrt/ccpp-2018-08-16-13:21:07-16470' exited with 1 Aug 16 13:21:08 muledeer abrtd: Deleting problem directory '/var/spool/abrt/ccpp-2018-08-16-13:21:07-16470'
Could you please guide us in finding probable root of this error..?
*Thanks & Kind Regards,* Saurabh LAHOTI. *Ideas enlighten Innovation**!!!* Please consider the environment before printing this mail..!!
-- Brian Reichert reichert@numachi.com BSD admin/developer at large
-- Brian Reichert reichert@numachi.com BSD admin/developer at large