Redis died with Connection refused after 48hs of running

[eldraco]

Describe the bug
Slips running in an interface for 48hs, suddendly is dead

Ask me where the logs are

errors.log

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.10/threading.py", line 953, in run
    self._target(*self._args, **self._kwargs)
  File "/StratosphereLinuxIPS/slips_files/core/database/redis_db/timewindow_updater_thread/tw_updater.py", line 16, in timewindow_updater
    db.set_current_timewindow(cur_tw)
  File "/StratosphereLinuxIPS/slips_files/core/database/database_manager.py", line 849, in set_current_timewindow
    return self.rdb.set_current_timewindow(*args, **kwargs)
  File "/StratosphereLinuxIPS/slips_files/core/database/redis_db/profile_handler.py", line 1106, in set_current_timewindow
    self.r.set(self.constants.CURRENT_TIMEWINDOW, timewindow)
  File "/usr/local/lib/python3.10/dist-packages/redis/commands/core.py", line 2335, in set
    return self.execute_command("SET", *pieces, **options)
  File "/usr/local/lib/python3.10/dist-packages/redis/client.py", line 559, in execute_command
    return self._execute_command(*args, **options)
  File "/usr/local/lib/python3.10/dist-packages/redis/client.py", line 565, in _execute_command
    conn = self.connection or pool.get_connection(command_name, **options)
  File "/usr/local/lib/python3.10/dist-packages/redis/connection.py", line 1422, in get_connection
    connection.connect()
  File "/usr/local/lib/python3.10/dist-packages/redis/connection.py", line 363, in connect
    raise ConnectionError(self._error_message(e))
redis.exceptions.ConnectionError: Error 111 connecting to localhost:32768. Connection refused.

Branch
sebas-fix-error-update

Environment (please complete the following information):

• OS: linux
• Are you running slips in docker or locally? docker
• Docker version (if running slips in docker) Docker version 28.0.4, build b8034c0
• Commit hash: ( git rev-parse --short HEAD )6565210ab5ad157a4c436c901d326bcc74ddaf5a

[AlyaGomaa]

Recreated this issue in my docker, it's still happening.

the first seen redis error in slips logs was
2026/01/30 04:08:30.783300 [DB] Error in add_tuple in database.py line 1258 Connection closed by server.
2026/01/30 04:08:30.783394 [DB] Error in add_tuple in database.py line 1258 Connection closed by server.
2026/01/30 04:08:30.787509 [DB] Error in add_tuple in database.py line 1274 Error while reading from localhost:32769 : (104, 'Connection reset by peer')

Is it an OOM kill by the OS?
root@kilimanjaro:/StratosphereLinuxIPS# cat /sys/fs/cgroup/memory.max 2>/dev/null || cat /sys/fs/cgroup/memory/memory.limit_in_bytes
8589934592
root@kilimanjaro:/StratosphereLinuxIPS# cat /sys/fs/cgroup/memory.peak 2>/dev/null || cat /sys/fs/cgroup/memory/memory.max_usage_in_bytes
8590254080

8590254080 - 8589934592
319488
Max RAM was somehow exceeded by 0.3047 MB

Checking OOM kills
root@kilimanjaro:/StratosphereLinuxIPS# cat /sys/fs/cgroup/memory.events
low 0
high 0
max 60269
oom 5
oom_kill 3
oom_group_kill 0

Checking redis Max mem
root@kilimanjaro:/StratosphereLinuxIPS# redis-cli -p 32769 INFO memory | grep human
used_memory_human:704.77K
used_memory_rss_human:5.08M
used_memory_peak_human:704.77K
total_system_memory_human:23.37G
used_memory_lua_human:32.00K
used_memory_vm_total_human:66.00K
used_memory_scripts_human:232B
maxmemory_human:0B

this Redis instance did not crash because of memory pressure. Not even close.

testing the memory with redis

redis-server --test-memory 23935
this is ~ 23.37 Gigabytes

[AlyaGomaa]

found this
https://devcenter.heroku.com/articles/ah-redis-stackhero#:~:text=The%20error%20%E2%80%9Credis.,and%20the%20connection%20closes%20automatically