[ 
https://issues.apache.org/jira/browse/DIRSERVER-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101499#comment-16101499
 ] 

Guillaume Lefranc commented on DIRSERVER-2203:
----------------------------------------------

But the database isn't corrupted, that's the thing. There was no operation
at all when the shutdown happened. It was in the middle of the night...
The data is still there only under  the wrong DN. In my opinion that's a
major issue because the repair function broke something.

Le mer. 26 juil. 2017 à 12:18, Emmanuel Lecharny (JIRA) <[email protected]> a



> Server crashed, data repair completed but no data shows up in ADS
> -----------------------------------------------------------------
>
>                 Key: DIRSERVER-2203
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-2203
>             Project: Directory ApacheDS
>          Issue Type: Bug
>            Reporter: Guillaume Lefranc
>
> Hi,
> we recently had one of our ADS server suffering a power loss. On restart the 
> DB was successfully repaired but our root DN data doesn't show up. The 
> toplevel DN shows up but nothing under it. 
> However the entries in our root DN seem to have been repaired somehow 
> according to the logs:
> INFO   | jvm 1    | 2017/07/20 10:19:17 | Service started.
> INFO   | jvm 1    | 2017/07/20 10:19:17 | Repairing the database.
> INFO   | jvm 1    | 2017/07/20 10:19:17 | Repairing partition dir 
> /var/lib/apacheds-2.0.0-M23/default/partitions
> INFO   | jvm 1    | 2017/07/20 10:19:21 | Re-building indices...
> INFO   | jvm 1    | 2017/07/20 10:19:21 | Read entry cn=eng with ID 
> 111f527f-5cdd-4133-87e3-ddfaaaf0db97 and parent ID 
> 6311d9b9-5833-437e-8a1a-d2a96596f75b
> INFO   | jvm 1    | 2017/07/20 10:19:21 | Read entry uid=mg with ID 
> 1188dbf7-be5b-43e3-97d1-2cc32de8f0c6 and parent ID 
> 4cf26ac6-0e62-4a7e-883d-6661da47071c
> INFO   | jvm 1    | 2017/07/20 10:19:21 | Read entry uid=yg with ID 
> 39a90b24-f4de-4dae-9473-bce54a52df52 and parent ID 
> 4cf26ac6-0e62-4a7e-883d-6661da47071c
> INFO   | jvm 1    | 2017/07/20 10:19:21 | Read entry uid=mk with ID 
> 3cf2b57b-f533-4dfb-ab1f-ceb8f57fd16e and parent ID 
> 4cf26ac6-0e62-4a7e-883d-6661da47071c
> INFO   | jvm 1    | 2017/07/20 10:19:21 | Read entry cn=ops with ID 
> 3cf697e3-913b-4ee5-88c7-b74927300cf0 and parent ID 
> 6311d9b9-5833-437e-8a1a-d2a96596f75b
> ... truncated ...
> INFO   | jvm 1    | 2017/07/20 10:19:21 | Updating the RDN index counters...
> INFO   | jvm 1    | 2017/07/20 10:19:22 | Total entries present in the 
> partition 34
> INFO   | jvm 1    | 2017/07/20 10:19:22 | Repair complete
> INFO   | jvm 1    | 2017/07/20 10:19:22 | Database repaired.
> Please advise. Thanks!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to