Bug ID 650038: tcp connect: errno and comm_point_tmm_recv_from messages

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,

Fixed In:
14.0.0, 12.1.6,

Opened: Mar 09, 2017

Severity: 4-Minor


When unbound (DNS cache) produces an error message, it's written to /var/log/ltm as a message from tmm. However, there is no indication that the message has anything to do with DNS caching. As a result of this issue, you might see errors similar to the following: -- err tmm5[14207]: tcp connect: errno 10 -- err tmm1[14244]: comm_point_tmm_recv_from failed: Software caused connection abort -- err tmm3[11846]: recvfrom failed


Some of these messages are benign, but there is no indication of that, or the associated functionality where the message was triggered. Difficulty troubleshooting the underlying issue.


-- Unbound (DNS cache) produces an error message. -- Viewing these logged messages in /var/log/ltm.



Fix Information

Logged messages now indicate their association with DNS cache. For example: -- info tmm4[19404]: DNScache: sending query -- info tmm4[19404]: DNScache: response for example.com. A IN

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips