> Hi, > > When I put the database on read only mode(nsslapd-readonly : on) while > changes are coming to the server, “ns-slapd” process abort > Does it produce a core dump, or just exit? Why are you trying to put the db into read-only mode? What platform? What version of 389-ds-base? > > abnormally with the following error message. > > “NSMMReplicationPlugin - replica_write_ruv: failed to update RUV > tombstone for o=SWIFT; LDAP error – 53” > This seems correct - if the database is in read-only mode, it cannot process the update operation, which includes writing the replication state information (the RUV tombstone). But it shouldn't exit and it definitely should not core dump. > > Below is the one pattern which is from error log where I see this > occurring. > > ====================================== > > [15/Nov/2011:11:57:59 +051800] - do_modify: dn (cn=userRoot,cn=ldbm > database,cn=plugins,cn=config) > > [15/Nov/2011:11:57:59 +051800] - modifications: > > [15/Nov/2011:11:57:59 +051800] - replace: nsslapd-readonly > > [15/Nov/2011:11:57:59 +051800] - mtn_lock : lock count : 1 > > [15/Nov/2011:11:57:59 +051800] - mapping tree selected backend : > frontend-internal > > [15/Nov/2011:11:57:59 +051800] - mtn_unlock : lock count : 0 > > [15/Nov/2011:11:57:59 +051800] - mtn_lock : lock count : 1 > > [15/Nov/2011:11:57:59 +051800] - mapping tree selected backend : > frontend-internal > > [15/Nov/2011:11:57:59 +051800] - mtn_unlock : lock count : 0 > > [15/Nov/2011:11:57:59 +051800] - mapping tree release backend : > frontend-internal > > [15/Nov/2011:11:57:59 +051800] - nsslapd-readonly: on > > [15/Nov/2011:11:57:59 +051800] - replace: nsslapd-readonly > > [15/Nov/2011:11:57:59 +051800] - - > > [15/Nov/2011:11:57:59 +051800] - modifiersname: cn=directory manager > > [15/Nov/2011:11:57:59 +051800] - replace: modifiersname > > [15/Nov/2011:11:57:59 +051800] - - > > [15/Nov/2011:11:57:59 +051800] - modifytimestamp: 20111115062759Z > > [15/Nov/2011:11:57:59 +051800] - replace: modifytimestamp > > [15/Nov/2011:11:57:59 +051800] - - > > [15/Nov/2011:11:57:59 +051800] - mtn_lock : lock count : 1 > > [15/Nov/2011:11:57:59 +051800] - mapping tree selected backend : > frontend-internal > > [15/Nov/2011:11:57:59 +051800] - mtn_unlock : lock count : 0 > > [15/Nov/2011:11:57:59 +051800] - nsState: > > [15/Nov/2011:11:58:00 +051800] - replace: nsState > > [15/Nov/2011:11:58:00 +051800] - - > > [15/Nov/2011:11:58:00 +051800] - modifiersname: cn=Multimaster > Replication Plugin,cn=plugins,cn=config > > [15/Nov/2011:11:58:00 +051800] - replace: modifiersname > > [15/Nov/2011:11:58:00 +051800] - - > > [15/Nov/2011:11:58:00 +051800] - modifytimestamp: 20111115062759Z > > [15/Nov/2011:11:58:00 +051800] - replace: modifytimestamp > > [15/Nov/2011:11:58:00 +051800] - - > > [15/Nov/2011:11:58:00 +051800] - mtn_lock : lock count : 1 > > [15/Nov/2011:11:58:00 +051800] - mapping tree selected backend : userRoot > > [15/Nov/2011:11:58:00 +051800] - mtn_unlock : lock count : 0 > > [15/Nov/2011:11:58:00 +051800] NSMMReplicationPlugin - > replica_write_ruv: failed to update RUV tombstone for dc=ind, dc=hp, > dc=com; LDAP error – 53 > > ==================== > > While database put on the read only mode and the same time replica > state is getting updated which is in-tern try to update the replica > RUV, it gets into this issue. > > Anybody has any thought into this issue why it’s happening? > The code doesn't expect the database to be in read-only mode while it is receiving updates? > > When the “nsState” do gets updated for the replica? > When it needs to be. > > Regards, > > Jyoti > -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
