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
------------------------------