Le 29/12/2015 00:55, David Hawes a écrit :
On 28 December 2015 at 01:31, Jephte Clain jephte.clain@univ-reunion.fr wrote:
hello all,
I upgraded to OpenLDAP 2.4.43 three weeks ago. It runs on debian squeeze 64bits lts it is built from sources with the fix from ITS#8330
Since the upgrade, it keeps crashing regularly (I would say once every 2 to 5 days) However, there isn't anything in the logs: no message, no error, no nothing
slapd no longer runs, I restart it, and it runs ok until the next crash
now I don't know how to debug that. I could downgrade to the previous version (2.4.41) which worked fine, but as our university is closed until 01/11, this is the perfect time to investigate. I still don't know if it's a bug in 2.4.43 or a misconfiguration for which previous versions was forgiving
What are your advice to track down the cause for the crash?
PS: here is a bit of context: one master with 2 mdb databases: one accesslog, one for the data two slaves (I mean complete replication, even cn=config) the master has crashed only once the slaves keep crashing regularly the slaves are complete replicas of the master, and I wonder if it could be a source of problems: I'll give details in another thread
Do you have accesslog purge configured?
I ran into this on an accesslog purge with 2.4.43:
http://www.openldap.org/its/index.cgi/Software%20Bugs?id=8336;selectid=8336
If you start slapd with '-d 1', you should be able to see if it is the issue.
The fix referenced in that ITS worked for me.
hello,
thanks for the response. no, purge is not configured, but this is a nice suggestion... without purge, I guess the accesslog database would keep growing forever :-(
thanks again, regards, Jephté CLAIN
--On Tuesday, December 29, 2015 10:05 AM +0400 Jephte Clain jephte.clain@univ-reunion.fr wrote:
Le 29/12/2015 00:55, David Hawes a écrit :
On 28 December 2015 at 01:31, Jephte Clain jephte.clain@univ-reunion.fr wrote:
hello all,
I upgraded to OpenLDAP 2.4.43 three weeks ago. It runs on debian squeeze 64bits lts it is built from sources with the fix from ITS#8330
Since the upgrade, it keeps crashing regularly (I would say once every 2 to 5 days) However, there isn't anything in the logs: no message, no error, no nothing
slapd no longer runs, I restart it, and it runs ok until the next crash
now I don't know how to debug that. I could downgrade to the previous version (2.4.41) which worked fine, but as our university is closed until 01/11, this is the perfect time to investigate. I still don't know if it's a bug in 2.4.43 or a misconfiguration for which previous versions was forgiving
What are your advice to track down the cause for the crash?
PS: here is a bit of context: one master with 2 mdb databases: one accesslog, one for the data two slaves (I mean complete replication, even cn=config) the master has crashed only once the slaves keep crashing regularly the slaves are complete replicas of the master, and I wonder if it could be a source of problems: I'll give details in another thread
Do you have accesslog purge configured?
I ran into this on an accesslog purge with 2.4.43:
http://www.openldap.org/its/index.cgi/Software%20Bugs?id=8336;selectid=8 336
If you start slapd with '-d 1', you should be able to see if it is the issue.
The fix referenced in that ITS worked for me.
hello,
thanks for the response. no, purge is not configured, but this is a nice suggestion... without purge, I guess the accesslog database would keep growing forever :-(
Yes, you generally want to configure a purge interval.
David,
Why haven't you reported this to the ITS?
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
Le 29/12/2015 10:18, Quanah Gibson-Mount a écrit :
--On Tuesday, December 29, 2015 10:05 AM +0400 Jephte Clain jephte.clain@univ-reunion.fr wrote:
Le 29/12/2015 00:55, David Hawes a écrit :
On 28 December 2015 at 01:31, Jephte Clain jephte.clain@univ-reunion.fr wrote:
hello all,
I upgraded to OpenLDAP 2.4.43 three weeks ago. It runs on debian squeeze 64bits lts it is built from sources with the fix from ITS#8330
Since the upgrade, it keeps crashing regularly (I would say once every 2 to 5 days) However, there isn't anything in the logs: no message, no error, no nothing
slapd no longer runs, I restart it, and it runs ok until the next crash
now I don't know how to debug that. I could downgrade to the previous version (2.4.41) which worked fine, but as our university is closed until 01/11, this is the perfect time to investigate. I still don't know if it's a bug in 2.4.43 or a misconfiguration for which previous versions was forgiving
What are your advice to track down the cause for the crash?
PS: here is a bit of context: one master with 2 mdb databases: one accesslog, one for the data two slaves (I mean complete replication, even cn=config) the master has crashed only once the slaves keep crashing regularly the slaves are complete replicas of the master, and I wonder if it could be a source of problems: I'll give details in another thread
Do you have accesslog purge configured?
I ran into this on an accesslog purge with 2.4.43:
http://www.openldap.org/its/index.cgi/Software%20Bugs?id=8336;selectid=8
336
If you start slapd with '-d 1', you should be able to see if it is the issue.
The fix referenced in that ITS worked for me.
hello,
thanks for the response. no, purge is not configured, but this is a nice suggestion... without purge, I guess the accesslog database would keep growing forever :-(
Yes, you generally want to configure a purge interval.
David,
Why haven't you reported this to the ITS?
ahah... I'm an idiot I had configured a purge interval... I don't know how I could miss that
I guess I have to wait for the next purge to be sure.
about the fix that solved the problem for you... the ITS above just says "fixed in mdb.master" Do you have the commit #id?
TIA, regards, Jephté CLAIN
--On Monday, December 28, 2015 10:18 PM -0800 Quanah Gibson-Mount quanah@zimbra.com wrote:
David,
Why haven't you reported this to the ITS?
Discussed with Howard. It isn't in 0.9 yet because it hasn't been confirmed if the fix is good or not. David, if that fix has resolved the issue, *please* follow up with the ITS noting that to be the case.
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-technical@openldap.org
-
Jephte Clain -
Quanah Gibson-Mount