Sporadic timeouts seen in Cloudron box logs: "Getting logs for box" [...] "Response timeout"

[d19dotca]

I've recently noticed this any time I open up the system logs viewer... I hadn't noticed this previously. What does this mean, is this a system error / defect in Cloudron or is this indicating an issue with my server?

Dec 19 22:50:05box:disks Getting logs for box
time consumed: 18.152s
processes terminated with: code=exited/status=0
[ServiceUnavailableError]: Response timeout
runtime: 1min 211ms
Object]
Object]

It's the "response timeout" that worries me, it seems to suggest something is timing out at the 1 minute mark (though I'm a bit puzzled by the "time consumed: 18.152s" portion) since the runtime is "1min 211ms", suggesting a timeout somewhere of 60 seconds / 1 minute.

[nebulon]

So some REST call to fetch stats is too slow on your system which makes it time out. You should see the failing route in the webinspector. It is probably nothing fatal.

[d19dotca]

@nebulon Is it the result of a slow server, or something in Cloudron? My server seems quite quick, so I'd be surprised this is an issue with the server but happy to look into that further if there are perhaps some recommended tests you'd like me to run to validate if this is a server issue or a Cloudron issue.

[nebulon]

In Cloudron essentially all responses to REST calls are limited to 1 minute and will timeout afterwards. This is intentional as such things should not take that long and usually there is some underlying problem if so.

If I read the logs correctly, it really just tails the box.log file here, which should not take that long arguably. Is this reproducible still?

[d19dotca]

It seems the issue here may have been a lot of CPU steal on my VPS, my provider has moved my VPS to a different host server and now it seems to be no longer timing out. Still monitoring, but seems to be the situation.