Milsy

While not necessarily an issue, per se, is there a reason that Ripper has updates basically daily? If it is for incremental changes, that's fine, but seems to be the container that wants to update far more frequently than anything else, and not really able to pinpoint why.

Resurrecting a bit of an oldie here, but came up when I was searching for this error message. Had the same thing pop up when I was checking the log after a restart after a (standard) power-down triggered by my UPS. Tried the easiest solution first (removing GPUstat) and it worked, errors gone, log now useful again and not filling up by the second. It's an older GPU so I can't update the drivers on that side, and didn't want to check the BIOS first as it would require plugging stuff into my headless server, but interesting that it worked so well.