Last Modified: May 12, 2026
Affected Product(s):
F5OS F5OS-A, F5OS-C
Known Affected Versions:
F5OS-A 1.5.0, F5OS-A 1.5.1, F5OS-A 1.5.2, F5OS-A 1.5.3, F5OS-A 1.5.4, F5OS-A 1.8.0, F5OS-A 1.8.1, F5OS-A 1.8.2, F5OS-A 1.8.3, F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.6.4, F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2
Opened: Aug 08, 2025 Severity: 3-Major
When generating a host qkview on F5OS, some of the journal log files are not handled properly, resulting in the output qkview missing expected log files, and the following example error log is observed in the platform.log file: panic: runtime error: index out of range [327713] with length 128
-- Resulting qkview archive is incomplete and missing log files. -- Diagnostic and support efforts may be hindered due to missing data.
The issue occurs when qkview is generated using the standard qkview-collect on F5OS with the software version 1.8.x and lower, and the system contains binary systemd journal files in /var/log/journal folder.
Edit the qkview-collect.config.yml to not collect /var/log/journal files before running qkview using the below steps and commands to collect the qkview -- Edit the file /etc/qkview-collect/qkview-collect.config.yml and add the line "- /var/log/journal" under the “excludes:" section, ensuring it follows the existing YAML syntax and indentation. -- Generate a qkview: f5sh 'system diagnostics qkview capture' -- Check the qkview status using the below command and wait for the qkview collection to complete: f5sh 'system diagnostics qkview status'
None