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: Dec 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, 13.1.3, 13.1.3.1, 13.1.3.2, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 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, 14.1.2, 14.1.2.1, 14.1.2.2, 15.0.0, 15.0.1, 15.1.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

There are two workarounds for this issue. Workaround #1: The problem can be avoided by making calls to iControl REST using only User IDs that have the 'Admin' or 'Resource Admin' roles. Note: If iControl REST calls have already been made with User IDs that have a role other than 'Admin' or 'Resource Admin', the 'restjavad' process must be restarted before core files can be created for icrd_child processes. Workaround #2: If iControl REST calls have already been made with User IDs that have a role other than 'Admin' or 'Resource Admin', and a core file is needed for a currently running icrd_child process, running the following two commands in the Advanced Shell (aka bash) creates the core file. 1: "echo 2 > /proc/sys/fs/suid_dumpable" 2: "pkill -6 icrd_child" Note: The commands are shown inside quotation marks but do not include the quotations marks.

Fix Information

None

Behavior Change