[GitHub] [couchdb] Crispy1975 commented on issue #1741: Supervisor couch_peruser_sup had child couch_peruser started with couch_peruser:start_link() at <0.30813.1> exit with reason normal in context child_terminated

[GitBox <gi...@apache.org>]

Crispy1975 commented on issue #1741:
URL: https://github.com/apache/couchdb/issues/1741#issuecomment-630032649


   I am seeing this with the official Docker image of CouchDB `3.1.0`. Exactly the same behaviour as others have described. When a user doc is deleted - along with the database that gets created with it (`couch_peruser`) - I start to see the following error messages in the CouchDB logs:
   ```
   couchdb_1         | [error] 2020-05-18T08:30:57.689442Z nonode@nohost <0.395.0> -------- Supervisor couch_peruser_sup had child couch_peruser started with couch_peruser:start_link() at <0.29782.0> exit with reason normal in context child_terminated
   couchdb_1         | [error] 2020-05-18T08:31:02.693066Z nonode@nohost <0.395.0> -------- Supervisor couch_peruser_sup had child couch_peruser started with couch_peruser:start_link() at <0.29847.0> exit with reason normal in context child_terminated
   couchdb_1         | [error] 2020-05-18T08:31:07.695809Z nonode@nohost <0.395.0> -------- Supervisor couch_peruser_sup had child couch_peruser started with couch_peruser:start_link() at <0.29909.0> exit with reason normal in context child_terminated
   ```
   I would very much like to make use of the `couch_peruser` option as it's a very nice feature to keep user data segregated etc. I've tried various options to try and clear the error, like recreating the same deleted user and database combination, restarts of the server process but nothing seems to help.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org