Bug ID 1036169: VCMPD rsync server max connection limit: guest "Exit flags for PID 17299: 0x500".

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP vCMP(all modules)

Known Affected Versions:
15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6

Fixed In:

Opened: Jul 26, 2021

Severity: 3-Major


Guestagentd will log the message "Exit flags for PID <PID>:0x500" in guest ltm log, if vcmp host rsync server current active connection is more than 4.


Guest LTM logs fill with "Exit flags for PID <PID>: 0x500".


-- vCMP guest. -- Rsync transfer frequency is 10 seconds between vCMP guest to vCMP host. -- more than 4 vCMP guests.



Fix Information

A software version that conmtains this fix needs to be installed and running on the vCMP host. The vCMP guest software version doesn't matter in the context of this issue. The changes below will need to be carried out on vCMP host only, and the final step is service affecting, restarting the vCMP guests. To set the rsync connection limit to highest number of guests that blade supports, and so avoid issue of this bug: tmsh modify sys db vcmp.dynamic_rsync_conn_allowed value true (from bash shell) To change back to original default rsync connection limit of four: tmsh modify sys db vcmp.dynamic_rsync_conn_allowed value false The next step is service affecting, and will restart the vCMP guests. If possible failover guests to peers on another vCMP host before carrying out this step. clsh should be used on multi-blade chassis. Restart vcmpd by running 'clsh bigstart restart vcmpd'

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips