Admin server error log contains errors:
configuration error: couldn't check access. No groups file?:
Steps to Reproduce:
1. Restart admin server from console, /var/log/dirsrv-admin/error contains:
[Fri Apr 26 15:50:13 2013] [notice] caught SIGTERM, shutting down
[Fri Apr 26 15:50:14 2013] [notice] SELinux policy enabled; httpd running as
[Fri Apr 26 15:50:15 2013] [notice] Access Host filter is: .example.com
[Fri Apr 26 15:50:15 2013] [notice] Access Address filter is:
[Fri Apr 26 15:50:16 2013] [notice] Apache/2.2.15 (Unix) configured -- resuming
[Fri Apr 26 15:50:16 2013] [notice] Access Host filter is: .example.com
[Fri Apr 26 15:50:16 2013] [notice] Access Address filter is:
[Fri Apr 26 15:50:17 2013] [notice] [client 192.168.122.184]
admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.122.184
[Fri Apr 26 15:50:17 2013] [crit] [client 192.168.122.184] configuration error:
couldn't check access. No groups file?: /tasks/Operation/Restart
You don't have to use the console - you can reproduce like this:
Author: Rich Megginson firstname.lastname@example.org
Date: Tue Oct 22 13:49:01 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:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)
to comment on this ticket.