Bug ID 532365: lsndb cores with "Assertion `size < bin_key_size' failed"

Last Modified: May 14, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP CGN(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2

Fixed In:
12.1.0, 12.0.0 HF3, 11.6.1 HF2

Opened: Jul 08, 2015
Severity: 3-Major

Symptoms

When there are many entries in the session database and a user attempts to delete them with "lsndb del all", this can cause lsndb to core with "Assertion 'size < bin_key_size' failed". The user may see lots of "Error: Connection to internal DB failed (err: Cannot assign requested address [99])" messages displayed to the console. In addition not all of the session database entries will be deleted.

Impact

- Session database cannot be properly cleared using the lsndb util.

Conditions

- LSN is configured with persistence, inbound-connections automatic, or PBA enabled. - There are over 100,000+ Session database entries (e.g. persistence, inbound, or PBA entries). - User attempts to manually delete all entries with "lsndb del all"

Workaround

None

Fix Information

lsndb no longer cores while deleting large amounts of session database entries.

Behavior Change