https://bugzilla.redhat.com/show_bug.cgi?id=846448 (Fedora)
Description of problem: /var/log/dirsrv/admin-serv/error is growing at about one-message/second with messages like: [Tue Aug 07 10:51:44 2012] [notice] [client 130.8.46.114] admserv_host_ip_check: ap_get_remote_host could not resolve 130.8.46.114 I seen the suggestion to use IP address instead of FQDN, but thats a work-around, not a bug fix. The host can resolve itself forward and backwards using nslookup locally. Version-Release number of selected component (if applicable): 389-admin-1.1.29-1.fc17.x86_64 How reproducible: 100% Steps to Reproduce: 1. start-dirserv 2. server dirsrc-admin start 3. tail -f /var/log/dirsrv/admin-serv/error Actual results: errors messages about once/second Expected results: no errors Additional info:
Added initial screened field value.
0001-Ticket-434-admin-serv-logs-filling-with-admserv_host.patch 0001-Ticket-434-admin-serv-logs-filling-with-admserv_host.patch
commit d35d14f7b599ebbc927cf7c6a6d8b163917e70df Author: Rich Megginson rmeggins@redhat.com Date: Mon Oct 21 14:43:02 2013 -0600
Metadata Update from @rmeggins: - Issue assigned to rmeggins - Issue set to the milestone: 389-admin,console 1.1.36
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/434
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.