Forum Discussion
mikegray_198028
Cirrus
Feb 28, 2017memory error
Hello team,
we were facing the below error and we lost the connection to all vips and making primary to force offline all the connection restored. any idea
01 :03:51 slot1/Device-1 err tmm[10168]: 01010004:3: Memory allocation failed: ssl_hs_m
01 :03:51 slot1/Device-1 err tmm[10168]: 01010004:3: Memory allocation failed: ssl_hs_m
01 :03:51 slot1/Device-1 err tmm[10168]: 01010004:3: Memory allocation failed: ssl_hs_m
01 :03:51 slot1/Device-1 err tmm[10168]: 01010004:3: Memory allocation failed: ssl_hs_m
01 :03:51 slot1/Device-1 err tmm[10168]: 01010004:3: Memory allocation failed: ssl_hs_m
01 :03:51 slot1/Device-1 err tmm[10168]: 01010004:3: Per-invocation log rate exceeded; throttling.
01 :03:52 slot1/Device-1 warning tmm[10168]: 011e0003:4: Aggressive mode sweeper: 78 Connections killed
01 :03:54 slot1/Device-1 warning tmm[10168]: 011e0003:4: Aggressive mode sweeper: 72 Connections killed
01 :03:55 slot1/Device-1 warning tmm[10168]: 011e0001:4: Limiting open port RST response from 501 to 500 packets/sec
01 :03:56 slot1/Device-1 warning tmm[10168]: 011e0003:4: Aggressive mode sweeper: 49 Connections killed
01 :03:57 slot1/Device-1 notice mcpd[7113]: 0107143c:5: Connection to CMI peer 192.168.10.20 has been removed
01 :03:57 slot1/Device-1 notice mcpd[7113]: 0107143a:5: CMI reconnect timer: enabled
01 :03:57 slot1/Device-1 notice mcpd[7113]: 01071431:5: Attempting to connect to CMI peer 192.168.10.20 port 6699
01 :03:57 slot1/Device-1 err mcpd[7113]: 0107142f:3: Can't connect to CMI peer 192.168.10.20, port:6699, Transport endpoint is not connected
01 :03:58 slot1/Device-1 warning tmm[10168]: 011e0003:4: Aggressive mode sweeper: 32 Connections killed
01 :04:00 slot1/Device-1 warning tmm[10168]: 011e0003:4: Aggressive mode sweeper: 25 Connections killed
01 :04:02 slot1/Device-1 warning tmm[10168]: 011e0003:4: Aggressive mode sweeper: 37 Connections killed
01 :04:02 slot1/Device-1 notice mcpd[7113]: 01071431:5: Attempting to connect to CMI peer 192.168.10.20 port 6699
01 :04:02 slot1/Device-1 notice mcpd[7113]: 01071432:5: CMI peer connection established to 192.168.10.20 port 6699
01 :04:02 slot1/Device-1 notice mcpd[7113]: 0107143c:5: Connection to CMI peer 192.168.10.20 has been removed
01 :04:04 slot1/Device-1 warning tmm[10168]: 011e0003:4: Aggressive mode sweeper: 26 Connections killed
01 :04:06 slot1/Device-1 warning tmm[10168]: 011e0003:4: Aggressive mode sweeper: 34 Connections killed
01 :04:07 slot1/Device-1 notice mcpd[7113]: 01071431:5: Attempting to connect to CMI peer 192.168.10.20 port 6699
01 :04:07 slot1/Device-1 notice mcpd[7113]: 01071432:5: CMI peer connection established to 192.168.10.20 port 6699
1 Reply
- Vijay_E
Cirrus
See if coredump file exists in /shared/core. I would recommend that you open up a case with F5 asap.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects