Bug ID 638215: iHealth auto-upload script may get stuck in unusual circumstances

Last Modified: Oct 01, 2018

Bug Tracker

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

Known Affected Versions:
13.0.0

Fixed In:
13.0.0 HF1

Opened: Jan 10, 2017
Severity: 3-Major

Symptoms

If iHealth auto-upload is correctly configured, and an upload in progress is aborted due to power loss, or other such calamity, the state for future invocations will result in the iHealth script being non-functional, and displaying the message"ihealth is already executing (2). Exiting."

Impact

the iHealth script is not usable, and the System-Support page cannot be used to create a qkview.

Conditions

auto-upload to iHealth is correctly configured, and an upload in progress is aborted due to power loss. When the BIG-IP is restarted, iHealth is no longer reachable.

Workaround

Execute the command, guishell -c "update diags_ihealth_request set ihealth_status=0"

Fix Information

None

Behavior Change