Last Modified: Aug 08, 2019
See more info
Known Affected Versions:
13.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.1.1, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.3, 14.0.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 14.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 15.0.0, 15.0.1
Opened: May 02, 2018
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.
This issue may hinder F5 Support efforts to diagnose memory leaks or other issues affecting the icrd_child process.
iControl REST requests are sent to the BIG-IP system using non-administrative (or resource admin) user accounts.
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.