March 1, 20179 yr Server started to get slow this evening and my dockers seem to have crashed, and I get a Server Execution error when I try to restart them. Attatched are my Diagnostics Log. tower-diagnostics-20170228-2245.zip Also it seems that I have reboot my unraid server every few days. Edited March 1, 20179 yr by deaerator
March 1, 20179 yr Server started to get slow this evening and my dockers seem to have crashed, and I get a Server Execution error when I try to restart them. Attatched are my Diagnostics Log.tower-diagnostics-20170228-2245.zip Also it seems that I have reboot my unraid server every few days.My tablet is having a brain fart trying to open the syslog1.txt in the diagnostics but the docker.log is basically nothing but complaint after complaint that the docker.img is read only. If I remember I'll try to look at the diagnostics again on a computer, but you're probably going to have to delete the docker.img file and then readd the apps either via CA's previous apps section or using the my* templates. Possible causes could just plain and simple corruption or possibly the image is full. You should be able to tell that from the settings, docker.If it's full then go through the docker faq and try and figure out why. Sent from my SM-T560NU using Tapatalk
March 2, 20179 yr Nothing within syslog1.txt meaningful except that you're running the ControlR app on your phone / tablet, and when you reset your server you've also got to restart? the app so that the log doesn't get inundated with wrong_csrf errors. So it's still the docker.img completely full (some app downloading within the image?) or its corrupt (could be caused by being full)
March 2, 20179 yr Author Just deleted my docker.img file and re-adding apps through my templates. fingers crossed
March 2, 20179 yr Author This is my cache drive When I click to get information about my cache drive It appears to be almost full My docker settings
March 2, 20179 yr @johnnie.black is the expert here. The numbers don't add up to my eyes but I don't use btrfs
March 2, 20179 yr Cache device is almost all allocated, that can result in out of space errors, run a balance to remove mostly empty chunks: btrfs balance start -dusage=50 /mnt/cache
March 4, 20179 yr Author On 3/2/2017 at 9:57 AM, johnnie.black said: Cache device is almost all allocated, that can result in out of space errors, run a balance to remove mostly empty chunks: btrfs balance start -dusage=50 /mnt/cache Curious if this should be setup as a scheduled job. I've been watching my cache drive ever since to see if it's being filled.
March 4, 20179 yr This issue is less common with latest kernels, still it's good to keep an eye on "btrfs filesystem show" and if/when used space comes close to device size run a balance to clear the unused and little used chunks.
March 25, 20179 yr Author I find myself running this command on a weekly basis now. Curious if there could be anything else wrong with my setup. Log attached. tower-diagnostics-20170325-1436.zip
March 25, 20179 yr Do you frequently fill up your cache completely ? Current allocated space is about half the device's size: devid 1 size 931.51GiB used 515.51GiB path /dev/sdh1 How high does it usually go? It requires attention only if it gets very close to the device size, like above 900GiB, and it remains like that. In my experience the empty chunks left (e.g., after running the mover) are automatically recovered, but it can take some time, like one or more days. Edited March 25, 20179 yr by johnnie.black
Archived
This topic is now archived and is closed to further replies.