[email protected] Posted May 12, 2020 Share Posted May 12, 2020 Since yesterday, there have been several times that the CPU had a few cores of 100% and then could not get down. Then WEBUI will be offline and I will need to reboot the machine. But after a while, the same thing happens again. Please help me, thank you! dragonraid-syslog-20200512-1335.zip Quote Link to comment
trurl Posted May 12, 2020 Share Posted May 12, 2020 Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post. Diagnostics includes syslog and a lot of other things that give a more complete understanding of your configuration and situation. Quote Link to comment
[email protected] Posted May 12, 2020 Author Share Posted May 12, 2020 Attach the diagnosis. dragonraid-diagnostics-20200512-1530.zip Quote Link to comment
Squid Posted May 12, 2020 Share Posted May 12, 2020 For lack of anything else, since there's currently no problem showing on your diagnostics, you can try Quote Link to comment
trurl Posted May 12, 2020 Share Posted May 12, 2020 Nothing obvious. Many of your disks are very full, more importantly your cache is very full. You typically want to avoid filling cache especially. Also your docker and VM related shares (appdata,domains,system) aren't configured ideally (should all be on cache). We can deal with all that later. Since Diagnostics (as well as current syslog) don't contain anything from before reboot, you might setup Syslog Server to store syslog somewhere you can retrieve it after you are forced to reboot again. Quote Link to comment
[email protected] Posted May 13, 2020 Author Share Posted May 13, 2020 16 hours ago, Squid said: For lack of anything else, since there's currently no problem showing on your diagnostics, you can try Thanks! I have tried it, but the same will happen. Quote Link to comment
[email protected] Posted May 13, 2020 Author Share Posted May 13, 2020 16 hours ago, trurl said: Nothing obvious. Many of your disks are very full, more importantly your cache is very full. You typically want to avoid filling cache especially. Also your docker and VM related shares (appdata,domains,system) aren't configured ideally (should all be on cache). We can deal with all that later. Since Diagnostics (as well as current syslog) don't contain anything from before reboot, you might setup Syslog Server to store syslog somewhere you can retrieve it after you are forced to reboot again. OK，Thanks! I reset these to make the cache disk have space, and then observe. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.