Bug ID 843801: Like-named previous Signature Update installations block Live Update usage after upgrade

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IP ASM, Install/Upgrade(all modules)

Known Affected Versions:
14.1.0,,,,,, 14.1.2,,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,

Fixed In:
16.0.0, 15.1.1,

Opened: Oct 29, 2019

Severity: 2-Critical


Signature Update installations using ASU files with the same name on versions before 14.1.0 block Live Update usage after upgrade to 14.1.0 or later.


Signature Update cannot be installed using Live Update, and errors appear in logs.


The same Signature Update file is installed multiple times on the device when running a version earlier than 14.1.0.


1. Delete the file: /var/lib/hsqldb/live-update/live-update-import.yaml. 2. Restart tomcat: bigstart restart tomcat This causes pre-upgrade records for Signature Update to be lost, but does not have any other functional impact. ** Another Workaround incase the above does not solve the issue: 1. stop the tomcat server: > bigstart stop tomcat 2. clean the live update db : > cd /var/lib/hsqldb/live-update > rm -f liveupdatedb.* 3. remove all *.im files which are not genesis file (factory-default files): 3.1 get the list of genesis files: > less /etc/live-update-genesis.yaml | grep genes | cut -d":" -f2 3.2 go to update file directory: > cd /var/lib/hsqldb/live-update/update-files 3.3 manually remove the *.im files that are not genesis 4. restart the tomcat server: > bigstart start tomcat

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips