> orion at cora.nwra.com wrote: >>> Looks like a problem on the admin server side - check your admin server >>> access and error logs. >>> >> >> Looks like this is probably the issue: >> >> [Fri Feb 22 15:33:11 2008] [notice] [client 192.168.0.8] >> admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.0.8 >> >> But I really don't know why it wouldn't be able to resolve. >> >> # host 192.168.0.8 >> 8.0.168.192.in-addr.arpa domain name pointer earth.cora.nwra.com. >> > No, that's just a [notice] - that's benign. Anything else in the error > log? In the access log, do you see 500 or 404 or 403 or other HTTP > error status codes (i.e. anything other than 200)? Nothing other than 200's in access. The only messages in error from that time are: [Fri Feb 22 15:32:08 2008] [notice] [client 192.168.0.8] admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.0.8 [Fri Feb 22 15:32:08 2008] [notice] [client 192.168.0.8] admserv_check_authz(): passing [/admin-serv/authenticate] to the userauth handler [Fri Feb 22 15:33:11 2008] [notice] [client 192.168.0.8] admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.0.8 [Fri Feb 22 15:33:11 2008] [notice] [client 192.168.0.8] admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.0.8
