[Spacewalk-list] How to test Spacewalk Proxy

Jon Miller jonebird at gmail.com
Thu Jul 11 23:04:59 UTC 2013


michael.mraka at redhat.com writes:
> Jon Miller wrote:
> % I just completed an install of spacewalk proxy. I tried testing by
> % taking a URL to a kickstart file, I know that works on my main
> % spacewalk server, and changed the host to my proxy. I get the
> % following entries in /var/log/rhn/rhn_proxy_broker.log:
> % 2013/07/05 15:07:00 -07:00 15525 0.0.0.0:
> % proxy/apacheServer.__call__('New request, component proxy.broker',)
> % 2013/07/05 15:07:00 -07:00 15525 129.46.72.178: broker/rhnBroker.handler
> % 2013/07/05 15:07:00 -07:00 15525 129.46.72.178: proxy/rhnShared._serverCommo
> % 2013/07/05 15:09:00 -07:00 15525 129.46.72.178:
> % proxy/apacheHandler.cleanupHandler
> % 
> % The webpage eventually returns and provides the following error:
> % XML Parsing Error: no element found
> % Location: http://spacewalk-dmz.example.com/ks/cfg/org/3/label/base
> % Line Number 1, Column 1:
> % 
> % I have verified that my firewall is allowing ports 80, 443, 5269 via
> % some telnet tests.
> % 
> % Here is what squid is seeing via it's access.log:
> % 1373062140.709 120023 127.0.0.1 TCP_MISS/000 0 GET
> % http://spacewalk-dmz.example.com/ks/cfg/org/3/label/base -
> % DIRECT/spacewalk-dmz.example.com -
> % 
> % I'm not that familiar with squid but that almost reads to me like
> % Squid is trying to retrieve the resource from the same dmz machine vs.
> % my internal Spacewalk server. Should I be propagating the same DNS
> % name in the dmz for my proxy as what I have internally?
>
> Hi Jon,
>
> the easiest way to test spacewlak proxy is to register a client to the
> proxy.
>
> As for DNS - if you can see proxy registered in spacewalk's webUI and it
> can update itself from the spacewalk then DNS setup is OK.
I had originally registered my DMZ machine with the base organization
and have since re-registered it with another active org and re-ran the
configure-proxy.sh script. That completed and I now see the DMZ proxy
machine listed in my proxy section with the internal Spacewalk UI. 

I have returned to my test of using a known, working kickstart URL to test the
functionality of the DMZ and I'm still getting the XML error returned to
the browser after a timeout period.

Does the proxy actually support imaging machines directly from it as I
would from the internal Spacewalk server?

Thanks,
Jon Miller




More information about the Spacewalk-list mailing list