[docker] Constant GETs, 100% CPU utilization

[glottisfaun0000]

What is wallos doing?

docker container logs wallos
[25-Oct-2024 17:31:35] NOTICE: [pool www] child 41936 exited with code 0 after 38.111197 seconds from start
[25-Oct-2024 17:31:35] NOTICE: [pool www] child 41950 started
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /index.php" 302
127.0.0.1 -  25/Oct/2024:17:31:35 -0700 "GET /login.php" 302
...

For the second time in the past fews days since starting running wallos, I've looked at ctop when my system seemed slow and saw the wallos container using 100% of my CPU. Where can I start to get more info on what the hell is happening? Are these GETs normal and unrelated to what wallos could possibly be using 100% of my CPU for?

Something else I noticed that could be related is that I had wallos set up in dashy with a status indicator which never seemed to resolve itself green.

[ellite]

Hi. Is it exposed to the internet?
It looks like a login brute force.

Edit:
Just noticed the dashy part. That makes sense. Wallos returns a 302 and redirects to login.php
Maybe dashy keeps trying and trying.
Change it to test directly on the login page and check

[glottisfaun0000]

With dashy set to status check /login.php, the requests still timeout in the same way. I have login disabled from wallos's admin panel.

I think you're right that dashy keeps requesting (even after disable status checking and reloading the config) because the wallos CPU load stops when I stop dashy. Sorry if this isn't a helpful issue,maybe these two just aren't compatible.

[ellite]

Ahh. I think that with the login disabled there's always a 302 redirect. If dashy can check for 302 instead of 200, it might work.

[glottisfaun0000]

Good idea, I used the statusCheckAcceptCodes option but still get the same behavior. I can't figure out how to get dashy to do debug logging but the UI says "request timed out".

[ellite]

Could you figure it out?

[ViktorTrojan]

Wallos was really slow for me, im not quite sure what the issue is. Maybe it's my fault, im not sure. I recently used version 2.37.1 and it needed really long to respond, so long sometimes that Uptime kuma couldn't reach the website and constantly switched between off/online. I switched now to 2.38.2, I will monitor and see if that fixes it