For a bit of weirdness, bouncing the spacewalk services seems to have resolved the issue. I can only assume something that was supposed to be listening on a port was not listening.
On Sun, Sep 27, 2015 at 12:17 AM, Brian Musson <[email protected]> wrote: > what happens when you curl that url from the host? > > BM > > On Sat, Sep 26, 2015 at 10:12 PM, Geoff Winans <[email protected]> wrote: > >> Howdy folks, >> >> I've been up one side and down the other with the documentation on both >> Spacewalk and rhnreg_ks. I've gone so far as to entirely purge the firewall >> rules on both sides in an attempt to get this cleared up. >> >> Here's the message I get: http://pastie.org/10446020 >> >> Lookups for all of my *.awpti.local domains work on all machines (in >> fact, the client I'm attempt to register is, in fact, the dns server!). >> Both machines can talk to one another.. >> >> I simply can't figure out what else to even look at. Documentation >> doesn't seem to touch on it and what few items I can find via search lands >> me on people having problems with routing over NAT and/or using >> spacewalk-proxy. >> >> Would appreciate any advice! >> >> Regards, >> >> Geoff W. >> >> >> >> _______________________________________________ >> Spacewalk-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/spacewalk-list >> > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
