So here's an odd one.
I can connect to the cachemgr menu just fine. When I do so, I see an entry in
Apache's access.log stating that I accessed the cgi. I also see an entry in
Squid's cache log stating that the cgi accessed the menu.
All of my other cgi scripts are working fine, so I don't think it is an
Apache/firewall/rights issue.
But when I click on any of the links on the cachemgr.cgi main menu, the
connection times out.
I've watched the traffic with wireshark, and I can see my browser sending
queries out. (I've tried IE8, Firefox 3.5.1 on Windows, Iceweasel 3.0.6 on
Debian, and Konqueror on Debian.)
But there is simply NO response.
With tcpdump on the squid box, I see the queries coming in, but Apache does not
log anything, either in the access log or error log and there are no further
entries in squid's cache.log. It is like the cachemgr.cgi is just eating the
replies.
Using squidclient on the squid server to request cache manger objects works
fine, and those requests are logged normally.
So I am fairly sure that:
Apache is configured correctly to serve cgi scripts from it's
configured cgi-bin.
The cachemgr.cgi script can be run by the Apache user (since it can run
the authentication dialog, and then present the main menu)
Iptables on the squid server allows traffic to Apache
/etc/squid/cachemgr.conf is configured correctly (since it can run the
authentication dialog, and then present the main menu)
/etc/squid/squid.conf is set to allow cachemgr.cgi to request cache
manager objects from localhost, which works with squidclient and to retrieve
the main menu.
The cachemgr.cgi worked fine about a month ago when I last used it.
Squid 2.7STABLE3 Debian Lenny, everything current on patches.
Is there anything obvious I am missing?
James Zuelow....................CBJ MIS (907)586-0236
Network Specialist...Registered Linux User No. 186591
