Hi Throne,
I have got below response from support for similar case. You may try it;
• Error messages: Couldn't initialize TCP local traffic monitor. ; Couldn't initialize TCP external traffic monitor in kernel...
Below given workaround may solve your problem
From the log analysis , it seems to be like there were memory allocation issues on the server respective to this time .
Due to memory allocation issue , the agent failed to initialize its components.
How to overcome this issue when starting the agent:
§ Stop some big process, start the agent and start that process again. Which process? That is up to the system administrator.
§ Reboot the machine so the memory fragmentation has cleared up and the agent can allocate the required memory before the rest of the processes start up.
------------------------------
cezmi çal
technical expert
Barikat Cyber Security
------------------------------
Original Message:
Sent: 03-03-2020 13:24
From: Tyrone Billups
Subject: initialize TCP
I'm getting the following errors on my servers:
Running with errors.
These are the errors:
Couldn't initialize local traffic monitor.
Couldn't initialize TCP local traffic monitor.
Couldn't initialize TCP external traffic monitor in kernel.
Process stopped. Maximum process terminations exceeded.
OS: SunOS 5.11
Kernel Patch 11.4.14.5.0
Agent version: 14.1.0.20.5.578238
Agent Camp package: 356.0.529
Platform: sun4v
These messages are showing in the log files
#AttackAnalytics
#CloudDataSecurity
#DatabaseActivityMonitoring
------------------------------
Tyrone Billups
Ally Financial
Charlotte NC
------------------------------