JWMutant Posted September 28, 2023 Share Posted September 28, 2023 Hello all, I seem to have a problem that has started to appear. The GUI will randomly become nonresponsive no matter what computer I try to access it from. So, I have no choice but to do a hard reset. When it comes back online, I find that the docker is set to off. Can anyone point me in the right direction? Cheers tower-diagnostics-20230927-1614.zip Quote Link to comment
itimpi Posted September 28, 2023 Share Posted September 28, 2023 The diagnostics you post show docker set to enabled and being started so not showing your problem. By default the syslog in the diagnostics only shows what happened since the last boot. To get a syslog that survives a reboot so we can see what lead up to your problem. you should enable the syslog server with one of the last two options set. Easiest is normally the mirror to flash option. 1 Quote Link to comment
JWMutant Posted September 28, 2023 Author Share Posted September 28, 2023 I will give it a go when I get home from work. Thanks for the help in advance. Quote Link to comment
JWMutant Posted September 29, 2023 Author Share Posted September 29, 2023 @itimpi I have done as you suggested and enabled syslog server. Hopefully it gives a little more info. The first log is straight after a hard reset due to having no GUI access. As per usual when this happens the docker is turned off. The second log is after I have turned the docker back on. tower-diagnostics-20230930-0744.zip tower-diagnostics-20230930-0752-after-docker-startup.zip Quote Link to comment
itimpi Posted September 29, 2023 Share Posted September 29, 2023 The syslog server file is not part of the diagnostics. You need to post that file separately. Quote Link to comment
JWMutant Posted September 30, 2023 Author Share Posted September 30, 2023 @itimpi I think I found it syslog.zip Quote Link to comment
JorgeB Posted September 30, 2023 Share Posted September 30, 2023 There's nothing relevant logged, suggesting a hardware issue, IIRC there was a user with the same or similar board that solved the problem by disabling C-States in the BIOS, also take a look here. 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.