Troubleshooting
Problem
After a successful patch installation on a console or a Managed Host, QRadar initiates an automatic reboot. However, if the automatic reboot does not happen, you can manually attempt a reboot by using the reboot command (if the patch has completed successfully).
In some cases, running the reboot command results in a "Failed to start reboot.target: Connection timed out" error.
Symptom
The patch installation log at /var/log/setup-xxxx-xx-xxxx/patches.log will have entries that confirm a successful upgrade:
Patch Report for x.x.x.x, appliance type: xxxx
<hostname>: patch test succeeded.
<hostname.: patch succeeded.
However, if a manual reboot is attempted, the error is encountered:
root@x.x.x.x~]# reboot
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.
Resolving The Problem
If the system fails to reboot, it is safe to force a reboot by using the following systemctl command:
systemctl --force --force reboot
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwtdAAA","label":"Upgrade"}],"ARM Case Number":"TS013162637","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
20 December 2023
UID
ibm17096362