Jump to content

Kaspersky Endpoint Security for Linux stops reverse proxy functioning


Recommended Posts

Lourens Nieuwoudt
Posted

I'm currently running Kaspersky Endpoint Security 11.2.0 for Linux on a Ubuntu 20.04.4 LTS with Apache installed to act as an reverse proxy. Everything seems to run fine, but after a couple of days reverse proxy function stops and I need to restart the KESL service to get everything to work again. What can I do to get more information logged on why Kaspersky will cause the reverse proxy to stop functioning?

  • 6 months later...
LandonCantrell
Posted

Hey there. Have you found a solution? One thing you could try is looking into the log files for Kaspersky and Apache to see if there's any specific error message or indication of what's causing the issue. My friend, who uses Kasperksy all the time, advised me about it.

Posted

You can enable verbose logging in Kaspersky Endpoint Security for Linux by making a change to the configuration file. Here are the steps you can follow:

  1. Open the Kaspersky Endpoint Security for Linux configuration file, located at /opt/kaspersky/kesl/bin/kesl.conf
  2. Find the line that starts with "debug=" and change the value to "yes"
  3. Save and close the file
  4. Restart the Kaspersky Endpoint Security for Linux service by running the following command: "systemctl restart kesl"

With verbose logging enabled, you should see more detailed information about what is happening with the Kaspersky Endpoint Security for Linux service in the logs, which can help you identify the issue causing the reverse proxy to stop functioning. The logs can be found at /var/log/kesl/.

  • 1 year later...
Алексей Рыбянец
Posted

Good afternoon 
Did you manage to find the cause of the problem?

I have the same mistake. And only the reload of Kesl eliminates the error

Renan Corassa
Posted

Have you considered the possibility of deactivating component by component until you reach one that could be causing the problem?

Алексей Рыбянец
Posted

The fact is that the problem occurs once a month.  
Last time, the disconnection of the component "Protection against network threats" helped.  But what exactly could be the reason for the problem, I never found out. 

At the moment, I wrote a script that, with inaccessibility, URL collects logs using Collect.sh and restarts the antivirus. After that I plan to send the received data in support.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now


×
×
  • Create New...