ZeroFrost Posted September 9, 2024 Posted September 9, 2024 (edited) Hello all, Recently started having issues with the server, it started on Saturday when i pulled out the GPU and ran the server without a GPU. After a couple of hours it would just freeze randomly, cant connect to it either from my own computer or by plugging directly to the server with a monitor and a keyboard just gives me a black screen. So I force shutdown and start it up again and the same thing happens again. It runs for an unknown amount of time then freezes. I Decided to add the GPU back in yesterday afternoon just in case that was the issue, sadly that did not help as the server crashed overnight. Attached the logs from today after booting it back up and the logs from yesterday. the one from yesterday was before adding the GPU back in, and the one from today is after (if that helps). any assistance or tips would be appreciated. thank you all. tower-diagnostics-20240909-1514.zip tower-diagnostics-20240908-0906.zip Edited September 9, 2024 by ZeroFrost Formatting Quote
ZeroFrost Posted September 9, 2024 Author Posted September 9, 2024 3 hours ago, trurl said: Applied the change, will wait and see how it goes for now. Quote
ZeroFrost Posted September 9, 2024 Author Posted September 9, 2024 5 hours ago, trurl said: Im afraid that did not work, server was working fine for 6 months or so prior to this. Quote
JorgeB Posted September 10, 2024 Posted September 10, 2024 Enable the syslog server and post that after a crash. Quote
ZeroFrost Posted September 11, 2024 Author Posted September 11, 2024 On 9/10/2024 at 11:11 AM, JorgeB said: Enable the syslog server and post that after a crash. Did this, and no crashes so far. Decided to start one docker container at a time, and changed the docker settings for the custom network type from macvlan to ipvlan. No crashes since, so went ahead and turned on all containers and its been running smoothly. I think the custom network type was the culprit here. Will see how it is in about a weeks times. Quote
Solution JorgeB Posted September 12, 2024 Solution Posted September 12, 2024 13 hours ago, ZeroFrost said: I think the custom network type was the culprit here. If you are running 6.12.10 or earlier update to latest, macvlan should no longer be an issue there. Quote
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.