DDOSpot memory leak

[LFBernardo]

Before you post your issue make sure it has not been answered yet and provide basic support information if you come to the conclusion it is a new issue.

• 🔍 Use the search function first
• 🧐 Check our WIKI
• 📚 Consult the documentation of 💻 Debian, 🐳 Docker, the 🦌 ELK stack and the 🍯 T-Pot Readme.
• ⚠️ Provide basic support information or similiar information with regard to your issue or we can not help you and will close the issue without further notice

⚠️ Basic support information (commands are expected to run as root)

• What version of the OS are you currently using lsb_release -a and uname -a? No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye

Linux shiveringsynergy 5.10.0-26-amd64 #1 SMP Debian 5.10.197-1 (2023-09-29) x86_64 GNU/Linux

• What T-Pot version are you currently using? 22.04

• What edition (Standard, Nextgen, etc.) of T-Pot are you running? Standard

• What architecture are you running on (i.e. hardware, cloud, VM, etc.)? VM (ESXi 6.7)

• Did you have any problems during the install? If yes, please attach /install.log /install.err. none

• How long has your installation been running? 2 weeks

• Did you install upgrades, packages or use the update script? updates through webuit

• Did you modify any scripts or configs? If yes, please attach the changes. no

• Please provide a screenshot of glances and htop.

• How much free disk space is available (df -h)?

• What is the current container status (dps.sh)?

• What is the status of the T-Pot service (systemctl status tpot)?

• What ports are being occupied? Stop T-Pot systemctl stop tpot and run netstat -tulpen NA

• If a single container shows as DOWN you can run docker logs <container-name> for the latest log entries NA

all services cease to function unless host is rebooted or an existing cockpit window is open and the system journal flush is restarted. Performing a "docker restart ddospot" resolves the memory leak temporarily.

[t3chn0m4g3]

Thanks. Based on the information it seems that the reason for the memory leak is caused by too many events. We recommend removing ddospot from the tpot.yml as a service (see #1415). If you think Ddospot is responsible, please open an issue on their repository, once fixed we can include the changes made.

[LFBernardo]

Thanks, will remove it from my config