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.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"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"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
20 December 2023
UID
ibm17096362