On 18/09/2020 09.38, Suhail Siddiqui, HCL wrote:
Hi,
After updated those packages now some services not starting .
[...]
● spacewalk-wait-for-taskomatic.service - Spacewalk wait for taskomatic Loaded: loaded (/usr/lib/systemd/system/spacewalk-wait-for-taskomatic.service; static; vendor preset: disabled) Active: active (exited) since Fri 2020-09-18 09:51:31 EEST; 46min ago Process: 7290 ExecStart=/usr/sbin/spacewalk-startup-helper wait-for-taskomatic (code=exited, status=0/SUCCESS) Main PID: 7290 (code=exited, status=0/SUCCESS)
OK so this is expected and not really a problem.
● spacewalk.target - Spacewalk Loaded: loaded (/usr/lib/systemd/system/spacewalk.target; enabled; vendor preset: disabled) Active: inactive (dead)
This is a target, so it fails because some other unit has failed.
● jabberd.service - Jabber Server Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled; vendor preset: disabled) Active: inactive (dead) since Fri 2020-09-18 09:49:30 EEST; 48min ago Main PID: 3398 (code=exited, status=0/SUCCESS)
● osa-dispatcher.service - OSA Dispatcher daemon
Loaded: loaded (/usr/lib/systemd/system/osa-dispatcher.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Fri 2020-09-18 09:49:30 EEST; 48min ago
Main PID: 3466 (code=killed, signal=TERM)
Here we have a problem I would say. First of all please try restarting those services, and report the output of `systemctl status <SERVICE>` again. More clues might be found in `journalctl -u <SERVICE>` or log files, specifically /var/log/rhn/osa-dispatcher.log. Do you notice anything strange in there? Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org