On 03/12/2016 04:02 PM, Andrew E. Bruno wrote:
On Wed, Mar 09, 2016 at 06:08:04PM +0100, Ludwig Krispenz wrote:
On 03/09/2016 05:51 PM, Andrew E. Bruno wrote:
On Wed, Mar 09, 2016 at 05:21:50PM +0100, Ludwig Krispenz wrote:
[09/Mar/2016:11:33:03 -0500] NSMMReplicationPlugin - changelog program -
_cl5NewDBFile: PR_DeleteSemaphore:
/var/lib/dirsrv/slapd-CBLS-CCR-BUFFALO-EDU/cldb/ed35d212-2cb811e5-af63d574-de3f6355.sema;
NSPR error - -5943
if ds is cleanly shutdown this file should be removed, if ds is killed it
remains and should be recreated at restart, which fails. could you try
another stop, remove the file manually and start again ?
We had our replicas crash again. Curious if it's safe to delete the
other db files as well:
ls -alh /var/lib/dirsrv/slapd-CBLS-CCR-BUFFALO-EDU/cldb/
30 DBVERSION
6.8G ed35d212-2cb811e5-af63d574-de3f6355_55a95591000000040000.db
0 ed35d212-2cb811e5-af63d574-de3f6355.sema
18M f32bb356-2cb811e5-af63d574-de3f6355_55a955ca000000600000.db
0 f32bb356-2cb811e5-af63d574-de3f6355.sema
Should all these files be deleted if the ds is cleanly shutdown? or should we
only remove the *.sema files.
the *.db file contains the data of the changelog, if you delete them you
start with a new cl and could get into replication problems requiring
reinitialization. you normally shoul not delete them.
The .sema is used to control how many threads can concurrently access
the cl, it should be recreated at restart, so it is safe to delete them
after a crash.
If you getting frequent crashes, we shoul try to find the reason for the
crashes, could you try to get a core file ?
http://www.port389.org/docs/389ds/FAQ/faq.html#debugging-crashes
Thanks,
--Andrew
--
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael
O'Neill
--
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go to http://freeipa.org for more info on the project