December 4, 20196 yr Been spending way to much time trying to correct my setup on my own... lol. Ran through multiple tests and setups as suggested in forum posts. Hardware looks OK and my best guess is RAM issues so been trying best to troubleshoot but I'm far from techy. Server has random crashing after Parity checks. My sync errors corrected are now growing as I try to fix up stuff on my own but seems like I'm going in circles. Just now crashed during parity check. Latest Diagnostic att tower-diagnostics-20191204-2236.zip also att is directly from usb flash tower-diagnostics-20191203-1458 - from usb flash.zip Edited December 4, 20196 yr by Tower_Of_Power added info
December 5, 20196 yr 1 hour ago, Tower_Of_Power said: Been spending way to much time trying to correct my setup on my own... lol. Ran through multiple tests and setups as suggested in forum posts. Hardware looks OK and my best guess is RAM issues so been trying best to troubleshoot but I'm far from techy. Server has random crashing after Parity checks. My sync errors corrected are now growing as I try to fix up stuff on my own but seems like I'm going in circles. Just now crashed during parity check. Latest Diagnostic att tower-diagnostics-20191204-2236.zip 88.31 kB · 0 downloads also att is directly from usb flash tower-diagnostics-20191203-1458 - from usb flash.zip 85.84 kB · 0 downloads Your server shut down pretty fast. Take a look at this and see if it helps.
December 5, 20196 yr Author I checked out your post before i uploaded and tried adding your recommended settings.. still trying to troubleshoot but this thing is giving be a headache... ;( .... Deleted 2 dockers (openVPN and DuckDNS) and updated OS to 6.8-rc8 from rc4. Just checked last reboot and no mention of unclean shutdown in the syslog. Performing parity check now and still getting sync errors.. will see what happens with next reboot Edited December 5, 20196 yr by Tower_Of_Power added
December 5, 20196 yr Author Parity Check ran its course.. a few minutes later .. it started again and im not sure why Diagnostic immediately after 1st check.. i did not see unclean shutdown in log. Now im looking through new diagnostic to see what sparked parity check.. i cancelled as soon as i seen it start What should I be looking for now? Just noticed Fix Common Problems showing Machine Check Events detected on your server tower-diagnostics-20191204-2217 1st check.zip tower-diagnostics-20191204-2243 after random parity check start.zip Edited December 5, 20196 yr by Tower_Of_Power add
Archived
This topic is now archived and is closed to further replies.