[Spacewalk-list] Migreating servers to new Spacewalk server

[Paul Deveau]

Hi,


Two things:


  1.  What is the best way to migrate Spacewalk clients to a new server?
  2.  Have created a new Spacewalk server and have deleted Spacewalk clients from the original server and re-registered the servers to the new server. OSAD no longer starts. I get the following error:


# systemctl status osad.service
● osad.service - OSAD daemon
   Loaded: loaded (/usr/lib/systemd/system/osad.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2019-01-25 15:00:00 EST; 5s ago
  Process: 13335 ExecStart=/usr/sbin/osad --pid-file /var/run/osad.pid (code=exited, status=1/FAILURE)
 Main PID: 5067 (code=exited, status=0/SUCCESS)

Jan 25 15:00:00 CAP-D100 osad[13335]: Error: [('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')]
Jan 25 15:00:00 CAP-D100 osad[13335]: 2019-01-25 15:00:00 rhn_log.log_error: Traceback caught:
Jan 25 15:00:00 CAP-D100 osad[13335]: 2019-01-25 15:00:00 rhn_log.log_error: Traceback (most recent call last):
Jan 25 15:00:00 CAP-D100 osad[13335]: File "/usr/share/rhn/osad/jabber_lib.py", line 662, in connect
Jan 25 15:00:00 CAP-D100 osad[13335]: ssl.do_handshake()
Jan 25 15:00:00 CAP-D100 osad[13335]: Error: [('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')]
Jan 25 15:00:00 CAP-D100 systemd[1]: osad.service: control process exited, code=exited status=1
Jan 25 15:00:00 CAP-D100 systemd[1]: Failed to start OSAD daemon.
Jan 25 15:00:00 CAP-D100 systemd[1]: Unit osad.service entered failed state.
Jan 25 15:00:00 CAP-D100 systemd[1]: osad.service failed.



Thank you.


--
Paul Deveau
Analyste de systèmes principal|Senior Systems Analyst
Technologies de l’information|Information Technology
Université d’Ottawa|University of Ottawa
613-562-5800 (3774)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20190128/584b23bd/attachment.htm>