hngo

I'm not sure if this is helpful, but i just noticed that the "Fix Common Problems" app now has errors that state: Unable to write to cache Unable to write to Docker Image I pulled another diagnostics incase it's helpful. Thanks, unable_writecache-turtle-diagnostics-20210321-1234.zip

Thanks for your quick response yesterday Squid. I don't think i've set anything up to send data to another system. I've restarted my server and pulled 2 diagnosticss: 1. After starting the array (post-array-turtle-diagnostics-20210321-1146.zip) 2. After starting a couple of my docker containers. (post-docker-turtle-diagnostics-20210321-1154.zip) My dockers seem to be working now after the reboot, but i've experienced in the past that the dockers would run after the reboot, but after awhile it would return to the same symptom as before (the dockers stop working) post-docker-turtle-diagnostics-20210321-1154.zip post-array-turtle-diagnostics-20210321-1146.zip

I've been struggling with this for about over a month now and i cant find any guidance that i think is applicable. My issue is that all of a sudden all of my dockers don't seem to run. (Are green and show that it's running in the "Docker" tab), but when i open the web ui my browser says "This site can’t be reached" "...took too long to respond". (For clarity, my dockers did work in the past). My suspicion is that this error started after our last power outage (I now have a UPS...). This would be the first power outage i've had with a cache pool enabled. I'm not sure, but would a power outage affect my cache pool and causing this issue? I haven't done any changes/tried any fixes yet as i'm not sure where the issue is coming from. Any help is appreciated. Thanks, turtle-diagnostics-20210320-1030.zip