[Spacewalk-list] spacecmd ports

[Bosch, Fabian (BITBW)]

May be a stupid hint but:

Have you entred your proxy in the clients up2date file?
/etc/sysconfig/rhn/up2date
Or even in the rhn.conf (if you ONLY install from spacewalk-server and not from www-sources)

Regards,

Fabian Bosch
Referat 34 – Open Source

IT Baden-Württemberg (BITBW)
Krailenshaldenstraße 44
70469 Stuttgart
Telefon: +49 711 8910-94476
Telefax: +49 711 8910-17575
E-Mail: fabian.bosch at bitbw.bwl.de<mailto:fabian.bosch at bitbw.bwl.de>
Internet: www.bitbw.de

Von: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] Im Auftrag von Matthew Madey
Gesendet: Mittwoch, 29. Juli 2015 22:42
An: spacewalk-list at redhat.com
Betreff: [Spacewalk-list] spacecmd ports

I had assumed spacecmd only used ports 80 and or 443. Is that not the case? I need to use an http/s proxy in a script to reach a Spacewalk server via spacecmd, but it just times out. After exporting the proxy in my script as a variable, I can wget the login page for the Spacewalk server, but spacecmd still fails. Is it using another port I'm not aware of? I ran netstat -tunlap | grep spacecmd while executing commands and the only port I saw was 443..

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20150730/7ed7057c/attachment.htm>