October 4, 201510 yr I get the same e-mails, however mine go all the way up to 100% and never say " Have gone back to normal". The kicker here... I don't have Docker enabled, never have. I'm slightly confused. Would you have time to create a Defect Report, outlining what you are seeing and the exact content of the messages, and include your diagnostics, so the settings/variables can be confirmed/checked? unRAID OS Version: unRAID Server Plus 6.1.3 Description: I get error messages about my docker image disk utilization when docker isn't enabled How to reproduce: Seems to happen only when myself or someone else is using plex from what i can tell? Expected results: n/a Actual results: n/a Other information: There doesn't seem to be any sort or performance issues when this is happening. Nothing stutters/lags etc nor do any of my disks appear to be full when this is happening. My Plugins are: Preclear Disks Powerdown Package Dynamix System Statistics Dynamix System Information Dynamix Active Streams Plex - still the old way starting from flash/extra/ Diag attached. Thanks ! Moderator edit: changed subject heading and icon beafy-diagnostics-20151004-0952.zip
October 5, 201510 yr The implication above is that there is a function ignoring the fact that Docker is disabled, and writing to docker.img. There appear to be other reports of this too (I think). My own report is different, but may be related. I needed a SATA port, and the only one available was in use by the Cache drive (containing docker.img), so I disabled Dockers and unassigned the Cache drive. Since then I get the following lines in my syslogs - (I've seen the same error messages in other users' syslogs too) ***Docker is disabled*** Sep 29 11:22:47 JacoBack emhttp: Starting Docker... Sep 29 11:22:47 JacoBack logger: /usr/bin/docker not enabled Sep 29 11:22:47 JacoBack logger: Updating templates... Updating info... Sep 29 11:22:47 JacoBack logger: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 490 Sep 29 11:22:47 JacoBack logger: Couldn't create socket: [2] No such file or directory Done. The same syslog section when Docker was enabled - ***Docker is enabled*** Sep 22 09:12:52 JacoBack emhttp: Starting Docker... Sep 22 09:12:52 JacoBack kernel: BTRFS: device fsid 4a371ec8-677a-4c03-8505-b999f499c162 devid 1 transid 2792 /dev/loop0 Sep 22 09:12:52 JacoBack kernel: BTRFS info (device loop0): disk space caching is enabled Sep 22 09:12:52 JacoBack kernel: BTRFS: has skinny extents Sep 22 09:12:52 JacoBack logger: Resize '/var/lib/docker' of 'max' Sep 22 09:12:52 JacoBack logger: starting docker ... Sep 22 09:12:52 JacoBack kernel: BTRFS: new size for /dev/loop0 is 10737418240 ... Sep 22 09:12:55 JacoBack logger: Updating templates... Updating info... Done. The implication again is that there is an independent function that isn't getting the message (that Docker is disabled), and is attempting Docker related activities. This function is using the 'logger' tag for logging. I'll also bring this to the attention of Squid, in case Community Applications is responsible.
October 5, 201510 yr Author Thanks so much for your time. If there's anything else I can do to assist, please don't hesitate to ask !
October 5, 201510 yr The implication above is that there is a function ignoring the fact that Docker is disabled, and writing to docker.img. There appear to be other reports of this too (I think). My own report is different, but may be related. I needed a SATA port, and the only one available was in use by the Cache drive (containing docker.img), so I disabled Dockers and unassigned the Cache drive. Since then I get the following lines in my syslogs - (I've seen the same error messages in other users' syslogs too) ***Docker is disabled*** Sep 29 11:22:47 JacoBack emhttp: Starting Docker... Sep 29 11:22:47 JacoBack logger: /usr/bin/docker not enabled Sep 29 11:22:47 JacoBack logger: Updating templates... Updating info... Sep 29 11:22:47 JacoBack logger: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 490 Sep 29 11:22:47 JacoBack logger: Couldn't create socket: [2] No such file or directory Done. The same syslog section when Docker was enabled - ***Docker is enabled*** Sep 22 09:12:52 JacoBack emhttp: Starting Docker... Sep 22 09:12:52 JacoBack kernel: BTRFS: device fsid 4a371ec8-677a-4c03-8505-b999f499c162 devid 1 transid 2792 /dev/loop0 Sep 22 09:12:52 JacoBack kernel: BTRFS info (device loop0): disk space caching is enabled Sep 22 09:12:52 JacoBack kernel: BTRFS: has skinny extents Sep 22 09:12:52 JacoBack logger: Resize '/var/lib/docker' of 'max' Sep 22 09:12:52 JacoBack logger: starting docker ... Sep 22 09:12:52 JacoBack kernel: BTRFS: new size for /dev/loop0 is 10737418240 ... Sep 22 09:12:55 JacoBack logger: Updating templates... Updating info... Done. The implication again is that there is an independent function that isn't getting the message (that Docker is disabled), and is attempting Docker related activities. This function is using the 'logger' tag for logging. I'll also bring this to the attention of Squid, in case Community Applications is responsible. Its not CA. Not one piece of code within CA is executed UNLESS you actually enter the docker tab (which you can't if docker is disabled). Best guess (guess at that) is that the background task responsible for checking for updated templates within dockerMan isn't getting the message that docker isn't running.
October 5, 201510 yr Best guess (guess at that) is that the background task responsible for checking for updated templates within dockerMan isn't getting the message that docker isn't running. That's a very good guess Currently the task for checking for docker updates doesn't verify whether docker is enabled or not. That needs to be added...
October 6, 201510 yr Its not CA. Not one piece of code within CA is executed UNLESS you actually enter the docker tab (which you can't if docker is disabled). Best guess (guess at that) is that the background task responsible for checking for updated templates within dockerMan isn't getting the message that docker isn't running. Thanks, Squid, I had to ask! And that guess sounds very plausible. Can either of you speculate whether it's possible that that update checking function is writing to the docker.img? Maybe using temp space on it?
October 6, 201510 yr Its not CA. Not one piece of code within CA is executed UNLESS you actually enter the docker tab (which you can't if docker is disabled). Best guess (guess at that) is that the background task responsible for checking for updated templates within dockerMan isn't getting the message that docker isn't running. Thanks, Squid, I had to ask! And that guess sounds very plausible. Can either of you speculate whether it's possible that that update checking function is writing to the docker.img? Maybe using temp space on it? No, it doesn't write anything to the docker image and is harmless. As a temporary workaround you can disable (set to never check) the docker update checking under Notification settings.
October 10, 201510 yr Author Its not CA. Not one piece of code within CA is executed UNLESS you actually enter the docker tab (which you can't if docker is disabled). Best guess (guess at that) is that the background task responsible for checking for updated templates within dockerMan isn't getting the message that docker isn't running. Thanks, Squid, I had to ask! And that guess sounds very plausible. Can either of you speculate whether it's possible that that update checking function is writing to the docker.img? Maybe using temp space on it? No, it doesn't write anything to the docker image and is harmless. As a temporary workaround you can disable (set to never check) the docker update checking under Notification settings. I tried this and i'm still getting the warning e-mails. Just an FYI Thanks.
October 11, 201510 yr I have never used or enabled Docker in my Unraid 6.1.3 system, but from time to time I receive email notifications like this: Event: Docker critical image disk utilization Subject: Alert [TOWER] - Docker image disk utilization of 100% Description: Docker utilization of image file Importance: alert Whenever these notifications get to 100% utilization, if I am watching something in Plex, it will pause for a few seconds. I using PhAzE's Plex plugin. In fact all my plugins are PhAzE's(Plex, Transmission, Sickbeard, Sabnzbd). There is nothing Docker related in the syslog when this happens. The only thing in the syslog is the info from sSMTP stating that it has sent an email notification. The only reference to Docker in my syslog doesn't even happen when the notifications occur. They usually happen when the array starts: Oct 10 20:00:43 Tower logger: stopping docker ... Oct 10 20:02:43 Tower logger: /usr/bin/docker not enabled Oct 10 20:02:43 Tower logger: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 490
Archived
This topic is now archived and is closed to further replies.