GitHub user wohali opened a pull request:
https://github.com/apache/couchdb-chttpd/pull/139
Drop logging level for "no record of user %s"
This warning is tripped primarily when an admin is defined in local.ini
and has no associated _users document. This can happen fairly often in
development and testing setups, meaning that every other line in the
logfile is "no record of user admin".
The right thing to do here might be to check if the currently defined
user is a local admin and only complain in that situation, but presently
chttpd only directly depends on couch_auth_cache and to do so would
require unencapsulating how couch_auth_cache handles ini file defined
admin users vs. authentication database users, which feels wrong.
Change suggested by @janl in #couchdb-dev IRC.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wohali/couchdb-chttpd
2.0-suppress-user-not-found-warning
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-chttpd/pull/139.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #139
----
commit e01cc4098c312758025c830214385aa74cedd489
Author: Joan Touzet <woh...@users.noreply.github.com>
Date: 2016-09-02T03:58:37Z
Drop logging level for "no record of user %s"
This warning is tripped primarily when an admin is defined in local.ini
and has no associated _users document. This can happen fairly often in
development and testing setups, meaning that every other line in the
logfile is "no record of user admin".
The right thing to do here might be to check if the currently defined
user is a local admin and only complain in that situation, but presently
chttpd only directly depends on couch_auth_cache and to do so would
require unencapsulating how couch_auth_cache handles ini file defined
admin users vs. authentication database users, which feels wrong.
Change suggested by @janl in #couchdb-dev IRC.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
