tjrobinson opened a new issue, #4077:
URL: https://github.com/apache/couchdb/issues/4077

   ## Description
   
   After the following error, the server won't start and the `_dbs.couch` file 
is zero bytes.
   
   ```
   [notice] 2022-06-21T20:12:22.766823Z 
[[email protected]](mailto:[email protected]) <0.15742.6857> 6b430e88a3 
52.158.43.32:5984 51.142.253.239 undefined GET / 401 ok 0
   [notice] 2022-06-21T21:02:57.099484Z 
[[email protected]](mailto:[email protected]) <0.371.0> -------- 
couch_replicator_scheduler: Job 
{"52a8eeedef822cfeb63311b33862f6ea","+create_target"} started as <0.22297.6858>
   [notice] 2022-06-21T21:03:01.009956Z 
[[email protected]](mailto:[email protected]) <0.18144.6858> 2b0a3dab49 
couchdev.northeurope.cloudapp.azure.com:5984 52.158.43.32 undefined POST 
/_session 200 ok 2
   [notice] 2022-06-21T21:03:01.026533Z 
[[email protected]](mailto:[email protected]) <0.18144.6858> d35d41db0e 
couchdev.northeurope.cloudapp.azure.com:5984 52.158.43.32 admin GET /sessions/ 
404 ok 12
   [error] 2022-06-21T21:03:01.028105Z 
[[email protected]](mailto:[email protected]) <0.22297.6858> -------- 
throw:{db_not_found,<<"could not open 
http://couchdev.northeurope.cloudapp.azure.com:5984/sessions/";>>}: Replication 
52a8eeedef822cfeb63311b33862f6ea+create_target failed to start 
http://couchdev.northeurope.cloudapp.azure.com:5984/sessions/ -> 
http://couchdev.northeurope.cloudapp.azure.com:5984/sessionIndex/ doc 
<<"shards/80000000-ffffffff/_replicator.1627909308">>:<<"66bdbf9229bcacfe4155170f87cecd1b">>
 
stack:[{couch_replicator_api_wrap,db_open,3,[{file,"src/couch_replicator_api_wrap.erl"},{line,114}]},{couch_replicator_scheduler_job,init_state,1,[{file,"src/couch_replicator_scheduler_job.erl"},{line,572}]}]
   [info] 2022-06-22T01:18:13.344895Z 
[[email protected]](mailto:[email protected]) <0.239.0> -------- Preflight 
check: Asserting Admin Account
   [info] 2022-06-22T01:18:13.372870Z 
[[email protected]](mailto:[email protected]) <0.239.0> -------- Apache CouchDB 
3.1.1 is starting.
   [info] 2022-06-22T01:18:13.373174Z 
[[email protected]](mailto:[email protected]) <0.240.0> -------- Starting 
couch_sup
   [info] 2022-06-22T01:18:14.036249Z 
[[email protected]](mailto:[email protected]) <0.239.0> -------- Apache CouchDB 
has started. Time to relax.
   [notice] 2022-06-22T01:18:14.161367Z 
[[email protected]](mailto:[email protected]) <0.272.0> -------- rexi_server : 
started servers
   [notice] 2022-06-22T01:18:14.188250Z 
[[email protected]](mailto:[email protected]) <0.276.0> -------- rexi_buffer : 
started servers
   [error] 2022-06-22T01:18:14.478062Z 
[[email protected]](mailto:[email protected]) <0.286.0> -------- Could not open 
file /bitnami/couchdb/data/_nodes.couch: permission denied
   [info] 2022-06-22T01:18:14.478482Z 
[[email protected]](mailto:[email protected]) <0.285.0> -------- open_result 
error {error,eacces} for _nodes
   ```
   
   ## Steps to Reproduce
   
   Unknown.
   
   ## Expected Behaviour
   
   The server starts as expected and `_dbs.couch` file is not empty.
   
   ## Your Environment
   
   * CouchDB version used: 3.1.1
   * Browser name and version: N/A
   * Operating system and version: Bitnami Azure VM store image (Debian 
GNU/Linux 10 (buster)) with CouchDB pre-installed
   
   ## Additional Context
   
   [TIP]:  # ( Add any other context about the problem here. )
   
   We're unable to use curl to get any additional information as the server 
won't start up.
   
   The `_nodes.couch` looks to be intact, and there are `.couch` files for the 
databases inside the `shards` directory.
   
   ```bash
   bitnami@LDC-AZU-COU2:/bitnami/couchdb/data$ ls -l
   total 16
   -rw-r--r-- 1 root root    0 Apr  4 17:58 _dbs.couch
   -rw-r--r-- 1 root root 8389 Apr  4 17:55 _nodes.couch
   drwxr-xr-x 3 root root 4096 Apr  4 17:55 shards
   ```
   
   Is there any way to rebuild the `_dbs.couch` file? We don't have backups.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to