Description | This article describes how to fix a 256 error code that occurs during a collector upgrade. |
Scope | FortiSIEM. |
Solution |
After a collector upgrade, the collector version remains unchanged and errors are present in the /opt/phoenix/log/collector-upgrade.log . This has been noticed on collector upgrades to 7.X.X versions. To fix this, follow the next steps:
From the /opt/phoenix/log/collector-upgrade.log file or after a manual installation with /usr/bin/python /opt/phoenix/phscripts/bin/phcollectorimageinstaller.py FortiSIEM |tee -a /opt/phoenix/log/collector-upgrade.log, lines like the following should be observed: ... [PH_MODULE_EXIT_OK]:[eventSeverity]=PHL_INFO,[procName]=phtools,[fileName]=phBaseProcess.cpp,[lineNumber]=391,[phLogDetail]=Module exited gracefully ... configureFSM.py returns 256
This means that python3.9 packages are missing.
pip3.9 list | grep psycopg pip3.9 list | wc -l
If commands are not reporting the psycopg package or the 0 package is present, the following steps are required.
Install requirements from the upgrade archive:
cd /opt/upgrade rpm2cpio FSM_Upgrade_All_7.*/FortiSIEM-7.*/FortiSIEM-7.*.rpm | cpio -iv --to-stdout ./opt/phoenix/requirements-3.9.txt > /tmp/requirements-3.9.txt ./opt/phoenix/requirements-3.9.txt pip3.9 install -r /tmp/requirements-3.9.txt
To confirm the installation succeeded, renew the 'Check python3.9 packages' steps where the psycopg package should be listed, along with around 181 packages.
Now, the collector upgrade will be possible to process again.
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.