I can see in the rockstor.log some references on 1/9/24 around postgres connection issues. There is one exception today related (in that log at least) to a connection being already closed. I assume, you’ve rebooted at least between yesterday and today.
On the nginx error log I see many error messages, without knowing what they indicate (sorry for my ignorance). Comparing it to my system on the stable version, the last time I had some similar errors of failed connections in mid-December and nothing at this scale.
On the gunicorn error log I can see some warnings around DateTimeField format related to Poolscrub.eta but not sure whether that would cause this CPU consumption level you’re seeing. I suspect those error messages are also a couple of months old (would be good if there was a date/time stamp on the gunicorn entries, too).
In the standard gunicorn log there is mentioning of the data-collector which we’ve had some issue with a long time ago (CentOS days):
but that does not seem to be the issue here, as it doesn’t show up as the top-consumer …