Bug ID 718108: It is not possible to core the icrd_child process if iControl REST requests were sent to the BIG-IP system using non-admin accounts

Last Modified: Jun 13, 2019

Bug Tracker

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 15.0.0

Opened: May 02, 2018
Severity: 3-Major

Symptoms

When trying to create a diagnostic core file of the icrd_child process (for example, using the command: kill -6 <PID>), the process restarts but does not create a core file.

Impact

This issue may hinder F5 Support efforts to diagnose memory leaks or other issues affecting the icrd_child process.

Conditions

iControl REST requests are sent to the BIG-IP system using non-administrative (or resource admin) user accounts.

Workaround

1. Switch your monitoring systems to use an admin (or resource admin) user account to send iControl REST requests to the BIG-IP system. 2. Restart the restjavad process: bigstart restart restjavad 3. Run the command to core the icrd_child process. This can now be achieved successfully.

Fix Information

None

Behavior Change