Redis connections are not cleared

[tico24]

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

When using a redis monitor, it appears to create a new connection every time it runs a ping, and it does not clear old connections out.

In the grafana graph, I set up the Uptime Kuma connection just before 16:00 and left it running overnight. By the morning, uptime-kuma was holding 1000 connections to redis. I terminated the uptime kuma pod and the connections immediatelly dropped (shown at approx 07:00), before climbing again.

Pausing the redis monitor is not enough to free up the connections. I have to restart the uptime-kuma pod to achieve this.

👟 Reproduction steps

Set up a redis monitor and leave it running for 24h.

👀 Expected behavior

The pings are frequent enough that I would expect them to use the same connection each time. But at a minimum, older connections should be closed gracefully.

😓 Actual Behavior

Uptime Kuma creates a new connection every time it runs a ping, and it does not clear old connections out.

🐻 Uptime-Kuma Version

1.20.0

💻 Operating System and Arch

Amazon linux 2

🌐 Browser

Firefox 109.0.1

🐋 Docker Version

EKS 1.24

🟩 NodeJS Version

n/a

📝 Relevant log output

I could not find any relevant logging.