This is an example. The dbverify utility uses the ERR level for the verbose mode output. The word "ERR" may not be appropriate.
[02/Jan/2017:17:24:14.120315218 -0800] - ERR - dbverify_ext - /var/lib/dirsrv/slapd-test/db/userRoot/mail.db: ok [02/Jan/2017:17:24:14.233058862 -0800] - ERR - dbverify_ext - /var/lib/dirsrv/slapd-test/db/userRoot/telephoneNumber.db: ok [02/Jan/2017:17:24:14.286457810 -0800] - ERR - dbverify_ext - /var/lib/dirsrv/slapd-test/db/userRoot/cn.db: ok .... [02/Jan/2017:17:24:15.154115725 -0800] - ERR - dbverify_ext - /var/lib/dirsrv/slapd-test/db/NetscapeRoot/aci.db: ok DB verify: Passed
I agree, and it looks like other tasks also use ERR instead of INFO. This was such a large refactoring job that some of these slipped through the cracks.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1410207
attachment 0001-Ticket-49075-Adjust-log-severity-levels.patch
Thanks, Mark!!
360d797..9fc1027 master -> master commit 9fc1027 Author: Mark Reynolds mreynolds@redhat.com Date: Wed Jan 4 16:54:20 2017 -0500
Metadata Update from @nhosoi: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.6 backlog
Further adjust sev levels:
<img alt="0001-Ticket-49075-Adjust-logging-severity-levels.patch" src="/389-ds-base/issue/raw/files/a987f8d9d4667cd56f4af61fa0a548ba3f5fa51fea42f156c18e24d61907f020-0001-Ticket-49075-Adjust-logging-severity-levels.patch" />
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to review (was: ack) - Issue status updated to: Open (was: Closed)
Ack, these messages are fine.
One day we have to agree on a column width ;)
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to ack (was: review)
Ack, these messages are fine. One day we have to agree on a column width ;)
Even on my 1080p widescreen monitor the logging is still out of scope. So yes, I adjust lines so they fit in my monitor/IDE
<img alt="Screenshot_from_2017-05-04_09-55-51.png" src="/389-ds-base/issue/raw/files/4c53fe78fb69e4b751635beade7bce0752299e2da243ce3555cf7f9bc754dd69-Screenshot_from_2017-05-04_09-55-51.png" />
46011e2..0762e39 master -> master
d518a45..2ae1521 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue set to the milestone: 1.3.6.0 (was: 1.3.6 backlog) - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2134
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.