The most common cause we typically see around local auto updates for "is not a proper manifest file" error is a missing symlink. As the file is local, the auto update tries to pull in the files, but there is something wrong with the location of the extracted files or the symlink is missing.
ln -s /storetmp/ /opt/qradar/www/autoupdates
If you extracted the files to a different directory, for example /store/AU_download, your symlink needs to reflect the location of the extracted files.
Reference article for others who might hit this issue in the future: https://www.ibm.com/support/pages/qradar-how-manually-install-qradar-weekly-auto-update-bundle
------------------------------
Jonathan Pechta
IBM Security - Community of Practice Lead
jonathan.pechta1@ibm.com
------------------------------
Original Message:
Sent: Fri March 08, 2024 01:57 AM
From: ishwor shrestha
Subject: Getting error on manual auto update
Dear Team,
We are trying to manually update the auto-update on QRadar 7.5.0 UP 3 but getting an error as "is not a proper manifest file. The most common reason this occurs is due to internet issues (ex: Internet Proxy settings not being set properly)".
We followed every step defined on the link:
https://www.ibm.com/support/pages/qradar-how-manually-install-qradar-weekly-auto-update-bundle
We ran the command: /opt/qradar/bin/UpdateConfs.pl -testConnect 1 0 and the download was successful.
Any help would be appreciated.
Regard,
Ishwor
------------------------------
ishwor shrestha
------------------------------