Bug ID 545218: icrd might become unresponsive on a heavily loaded system.

Last Modified: Mar 14, 2021

Bug Tracker

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

Known Affected Versions:
11.5.0, 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.10, 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

Fixed In:
12.0.0, 11.6.1

Opened: Sep 10, 2015
Severity: 3-Major

Symptoms

iControl REST requests can go unanswered or return with bad responses.

Impact

Cannot use REST API.

Conditions

iControl REST daemon (icrd) starts before restjavad.

Workaround

The workaround is to restart the icrd service, making sure that restjavad is running. To do so, complete these steps: -- Run the command: bigstart status restjavad. Wait until restjavad is completely up and responding. Run the command: bigstart restart icrd.

Fix Information

The iControl REST daemon (icrd) now correctly waits until the restjavad service is completely up and responding, so icrd no longer becomes unresponsive on a heavily loaded system..

Behavior Change