Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Oracle spacewalk client/proxy osad will not start

user8830473Nov 10 2017 — edited Nov 10 2017

I have searched the web to no avail, so I hope I can find some help here.   I have an Oracle spacewalk 2.6 setup, with a server in one location and several proxies in other data center locations, all running Oracle Linux 7.4.  Yum commands work fine, but on a proxy that also needs an http proxy to communicate with the spacewalk server, the osad daemon will not start up.   The error that I get when trying to start it using osad -N -v -v -v is:

2017-11-10 21:32:15 osad._setup_config: Updating configuration

2017-11-10 21:32:15 jabber_lib.setup_connection: Connecting to myspw.fqdn.com

2017-11-10 21:32:15 jabber_lib._get_jabber_client:

2017-11-10 21:32:15 rhn_log.log_error: Error caught:

Error caught:

2017-11-10 21:32:15 rhn_log.log_error: Traceback (most recent call last):

  File "/usr/share/rhn/osad/jabber_lib.py", line 126, in main

    c = self.setup_connection(no_fork=no_fork)

  File "/usr/share/rhn/osad/jabber_lib.py", line 266, in setup_connection

    c = self._get_jabber_client(js)

  File "/usr/share/rhn/osad/jabber_lib.py", line 323, in _get_jabber_client

    'port': int(cf['proxy_url'].split(':')[1])}

ValueError: invalid literal for int() with base 10: '//bouprxy01.internal.fqdn.com'

The contents of /etc/sysconfig/rhn/osad.conf:

[osad]

# don't change this
systemid = /etc/sysconfig/rhn/systemid

# increase for debugging output
debug_level = 0

# don't change this... used in substitutions below.
# if you get rid of the '%(server_handler)s' bits below,
# the *MUST* be replaced with this value...
server_handler = /XMLRPC

# Protocol to talk upstream
proto = https

# to use a server other than what up2date is configured to use,
# do something along the lines of:
# server_url = https://yet.another.example.org:8081/XMLRPC
server_url = %(proto)s://%(server_name)s%(server_handler)s

# the following fields are inherited from up2date's configuration,
# but are overridable in this file

enableProxy = 1
#enableProxyAuth = 1
httpProxy = http://bouprxy01.internal.fqdn.com:8080
# httpProxy = some.proxy.example.com:3030
# proxyUser = proxy_user_name
# proxyPassword = proxy_password

# Use a different certificate from what up2date is using
# This should point to the satellite certificate for
# server_name
osa_ssl_cert = /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

logfile = /var/log/osad

max_time_drift = 120

run_rhn_check = 1

# Default command to run when asked by the dispatcher
rhn_check_command = /usr/sbin/rhn_check

# By default we only use the first jabber server.
# Turn the enable_failover option to 1 if you want the connections
# to try Satellite's jabberd if Proxy's is not available.
enable_failover = 0

# Enable kernel keepalive timer on the osad client side socket
# in case the satellite/proxy side socket is closed without osad realising it
# After 'tcp_keepalive_timeout' seconds the kernel will probe the connection
# After 'tcp_keepalive_count' unsuccessful probes, the kernel will close the connection
tcp_keepalive_timeout = 1800
tcp_keepalive_count = 3

I have tried removing the 'http' from the httpProxy in the osad.conf (or just commenting out the proxy altogether), but then the connection just times out.

I appreciate any help, as I have searched and searched and can't find an issue like this one.

Thanks!

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Dec 8 2017
Added on Nov 10 2017
0 comments
600 views