My Oracle Support Banner

Spacewalk: Takomatic And Osa-dispatcher Services Fail To Start After Spacewalk Server Rebooted (Doc ID 2342874.1)

Last updated on AUGUST 04, 2018

Applies to:

Linux OS - Version Oracle Linux 7.4 with Unbreakable Enterprise Kerne [4.1.12] and later
Linux x86-64


When the spacewalk server reboots the spacewalk services like taskomatic and osa-dispather may failed due to database service(s) were started after these services(in booting order)


Systemctl output referencing the booting order issue issue - osa-dispatcher tries to connect to database before it is ready:
osa-dispatcher.service - OSA Dispatcher daemon
Oct 27 15:23:21 systemd[1]: Starting OSA Dispatcher daemon...
Oct 27 15:23:22 osa-dispatcher[1888]: Spacewalk 1888 2017/10/27 15:23:22 +02:00: ('Connection attempt failed', 12541, 'ORA-12541: TNS:no listener\n')
Oct 27 15:23:22 osa-dispatcher[1888]: Spacewalk 1888 2017/10/27 15:23:22 +02:00: ('Error caught:',)

dbora.service - The Oracle Database Service
Oct 27 15:23:29[1819]: SQL> ORACLE instance started.
Oct 27 15:23:29[1819]: Total System Global Area 2.6911E+10 bytes
Oct 27 15:23:29[1819]: Fixed Size 6871768 bytes
Oct 27 15:23:29[1819]: Variable Size 1.5636E+10 bytes
Oct 27 15:23:29[1819]: Database Buffers 1.1207E+10 bytes
Oct 27 15:23:29[1819]: Redo Buffers 60235776 bytes
Oct 27 15:23:33[1819]: Database mounted.
Oct 27 15:23:39[1819]: Database opened.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.