Bug ID 1075045: Proxy initialization failed, Defaulting to DENY, after applying additional profile to a virtual server

Last Modified: May 06, 2025

Affected Product(s):
BIG-IP All(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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 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.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1

Opened: Jan 21, 2022

Severity: 3-Major

Symptoms

Connections are reset when accessing a virtual server, with an F5 reset cause of "Port denied". Messages in /var/log/ltm: err tmm[<PID>]: 01010008:3: Proxy initialization failed for <virtual server>. Defaulting to DENY. err tmm[<PID>]: 01010008:3: Listener config update failed for <virtual server>: ERR:ERR_MEM

Impact

All connections to the virtual server are immediately reset.

Conditions

-- A virtual server is configured with 23 hudchain elements, and an attempt is made to add one or more further elements, caused by a large number of attached profiles -- The number of 'hudchain' elements does not directly correspond to the number of profiles, as some profiles add more than one hud chain element - particularly with APM, and some elements are enabled through other settings, such as compression with the http profile -- To find the number of elements on a virtual server, set the db variable "tmm.verbose" to 'enable', add or remove a profile to/from the affected virtual server, then check the tmm log file for a line similar ot the following -- A log line similar to the one below will be produced, which describes the hud chain elements ont the clientside flow, the proxy in the middle, and the elements on the serverside flow. The limitation of 24 includes all the elements in either the clientside or serverside flows, as well as the proxy in the middle (the proxy is counted on both the clientside and serverside flows) <13> Oct 1 08:33:09 bigip1.local notice (L:/Common/test) hn :TCP -> SSL -> HTTP -> INFLATE -> DEFLATE -> SATELLITE -> <TCP> <- SATELLITE <- DEFLATE <- INFLATE <- HTTP <- SSL <- TCP: In this case, the clientside flow has 6 elemnents plus the proxy, totalling 7, and the serverside flow also has 7. Either of those numbers can not exceed a fixed upper limit of 23.

Workaround

Reduce the number of profiles applied to the virtual server.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips