Hi all,
I'm running 2.4.39 with Mirrormode replication. I've noticed that occasionally when making schema changes, a change will hang indefinitely without reason. Though (possibly as a cause), also I've found that if I try and restart one of the three servers in this replica set, it will occasionally get the following with causes it to hang indefinitely:
Oct 1 08:55:37 ldap-03 slapd[19608]: daemon: shutdown requested and initiated. Oct 1 08:55:37 ldap-03 slapd[19608]: slapd shutdown: waiting for 2 operations/tasks to finish
The other hosts show the disconnection and try and reconnect - the only way to fix it seems to be either force killing this server or restarting all the other hosts.
Any ideas? It's a fairly standard setup with mirrormode as per the doc's.
I've seen there is 2.4.40 released however haven't scheduled in an upgrade yet as there wasn't anything on the changelog that appeared to be linked.
Cheers
Hi,
On Wed, 1 Oct 2014, Bill Brigden wrote:
Hi all,
I'm running 2.4.39 with Mirrormode replication. I've noticed that occasionally when making schema changes, a change will hang indefinitely without reason. Though (possibly as a cause), also I've found that if I try and restart one of the three servers in this replica set, it will occasionally get the following with causes it to hang indefinitely:
Oct 1 08:55:37 ldap-03 slapd[19608]: daemon: shutdown requested and initiated. Oct 1 08:55:37 ldap-03 slapd[19608]: slapd shutdown: waiting for 2 operations/tasks to finish
The other hosts show the disconnection and try and reconnect - the only way to fix it seems to be either force killing this server or restarting all the other hosts.
<wild guess> do you have any statefull firewalls interfering with the tcp teardown between the servers. </wild guess>
Greetings Christian
Any ideas? It's a fairly standard setup with mirrormode as per the doc's.
I've seen there is 2.4.40 released however haven't scheduled in an upgrade yet as there wasn't anything on the changelog that appeared to be linked.
Cheers
<wild guess> do you have any statefull firewalls interfering with the tcp teardown between the servers. </wild guess>
Thanks for the guess - no, there isn't unfortunately, they all sit in the same subnet fow now as it's a dev setup.
The only difference I've noticed is that my config olcDatabase had the syncrepl set as:
type=refreshAndPersist
however my hdb olcDatabase was set as:
type=refreshOnly
I've changed the HDB over to refreshAndPersist as that is more suitable (I believe)... Would it have a knock on effect incase there there is a communication break? Finally - I guess if there had been a teardown between the servers, in this case, why does the server I've shut down hang indefinitely without hitting a timeout for "operations to finish"?
Cheers,
"Bill Brigden" bill@dotbill.co.uk schrieb am 01.10.2014 um 10:09 in Nachricht
025901cfdd4e$fe453610$facfa230$@dotbill.co.uk:
Hi all,
I'm running 2.4.39 with Mirrormode replication. I've noticed that occasionally when making schema changes, a change will hang indefinitely without reason. Though (possibly as a cause), also I've found that if I try and restart one of the three servers in this replica set, it will occasionally get the following with causes it to hang indefinitely:
Oct 1 08:55:37 ldap-03 slapd[19608]: daemon: shutdown requested and initiated. Oct 1 08:55:37 ldap-03 slapd[19608]: slapd shutdown: waiting for 2 operations/tasks to finish
I had this with an older version of OpenLDAP and BDB (hdb) backend. The problem was that a remote database was not completely in sync. So I shut down remote slapds, removed the databases, dumped the database of the remaining master and slapadded them on the shutdown nodes. Then I started up those noedes, and everything was fine since then.
The other hosts show the disconnection and try and reconnect - the only way to fix it seems to be either force killing this server or restarting all the other hosts.
Any ideas? It's a fairly standard setup with mirrormode as per the doc's.
I've seen there is 2.4.40 released however haven't scheduled in an upgrade yet as there wasn't anything on the changelog that appeared to be linked.
Cheers
openldap-technical@openldap.org
-
Bill Brigden -
Christian Kratzer -
Ulrich Windl