aaPanel_Kern
Version 6.8.26 on Ubuntu 20.04, and the system its self is responsive, all the sites work, little to no load, its just the panel that decides it doesn't want to respond.
You can sit there and watch the system via top and see no real activity, but the panel will be unresponsive until its restarted or it'll take 2-3 minutes then suddenly load the page all while the system is idle other than the 10% CPU use from the error above.
I thought it was an issue with the first install, but I've been playing around with aaPanel on various systems from multiple providers and I've encountered the same thing every time, usually after a day or two of running even if the system has no sites, no open ports to the outside world, etc, it just sort of hangs.... it decides it doesn't want to generate any new pages until the service gets kicked and restarted, then it acts fine again. Its a mild annoyance, but certainly /an/ annoyance.
As for the error above, is there a recommended/approved method of disabling the mysql quota generation until the issue is resolved? I have a random system running the current beta to see if its affected but I'd wager to guess that its not?
Also to clarify, the panel isn't slow, its snappy and instantaneous until its not, none of these systems see almost /any/ use at all, its just that the panel goes from working perfectly to completely hung, you'll be using it, then you'll try to go back to the dashboard, etc.... and it'll never load, you can try and load it up on another browser, same thing, it just hangs until its restarted. Happens most often when it decides to log the user out, the login page will work great, but once you login it'll never show the dashboard, just be stuck at the login prompt, then if you restart the service it'll suddenly load /right/ into the dashboard like nothing happened.
