Not sure whats been going on, but Ive been having huge issues with trying to stop, restart, or update docker . I thought it was related to v6.4.0_rc10b so I downgraded to the previous. For some reason after a day I loose all access to my dockers, and have to do a hard reset of the server to get it back. Trying to restart, stop, or update dockers just results in a hang....Trying to to a clean shutdown of the server, or stopping docker never completes. Attached Diag. Looking at the docker log in diag, it seems that the dockers fail to shut down....

test-diagnostics-20171111-1124.zip

Edited November 11, 20178 yr by clowrym

I thought it was running fine for about a day, but it seems its a consistant issue....and there upon reboot, Once dockers start, i cant stop them, nor can I stop the arra for a reboot, or stop docker manager in general....

 

Nov 11 18:26:43 Test nginx: 2017/11/11 18:26:43 [error] 13299#13299: *895 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.107, server: , request: "GET /plugins/dynamix.docker.manager/include/CreateDocker.php?updateContainer=true&ct[]=sonarr HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.11", referrer: "http://192.168.0.11/Docker"

Nov 11 18:26:43 Test nginx: 2017/11/11 18:26:43 [error] 13299#13299: *895 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.107, server: , request: "GET /plugins/dynamix.docker.manager/include/CreateDocker.php?updateContainer=true&ct[]=sonarr HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.11", referrer: "http://192.168.0.11/Docker"

When i try a force update, or do an update, or just try and stop a container it hangs at stopping container, & I end up with number of errors in the syslog

 

Nov 11 18:20:14 Test kernel: CIFS VFS: Free previous auth_key.response = ffff8801f5fb4700
Nov 11 18:20:14 Test kernel: CIFS VFS: Free previous auth_key.response = ffff8801c84a0a00
Nov 11 18:20:14 Test kernel: CIFS VFS: Free previous auth_key.response = ffff8801465acd00
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -104 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:21 Test kernel: cifs_vfs_err: 29 callbacks suppressed
Nov 11 18:20:21 Test kernel: CIFS VFS: Free previous auth_key.response = ffff8801465ac280

Attached fresh DIag after a restart

 

test-diagnostics-20171111-1834.zip

Edited November 12, 20178 yr by clowrym

Im having the same problem.. For me it is always sonarr that makes it freeze..

 

Any solution?

 

Quote

Dec 11 13:40:56 Workilus kernel: CIFS VFS: Send error in read = -11
Dec 11 13:40:56 Workilus kernel: CIFS VFS: Error -32 sending data on socket to server
Dec 11 13:40:56 Workilus kernel: CIFS VFS: Error -32 sending data on socket to server
Dec 11 13:40:56 Workilus kernel: CIFS VFS: Error -32 sending data on socket to server
Dec 11 13:40:56 Workilus kernel: CIFS VFS: Error -32 sending data on socket to server
Dec 11 13:40:56 Workilus kernel: CIFS VFS: Error -32 sending data on socket to server
Dec 11 13:40:56 Workilus kernel: CIFS VFS: Error -32 sending data on socket to server
Dec 11 13:40:56 Workilus kernel: CIFS VFS: Error -32 sending data on socket to server
Dec 11 13:40:56 Workilus kernel: CIFS VFS: Error -32 sending data on socket to server
Dec 11 13:40:56 Workilus kernel: CIFS VFS: Error -32 sending data on socket to server

 

And after that, the Sonarr Docker freeze. I can't do anything and have to force restart my server by pulling the plug.

 

Not even "docker kill sonarr" works, and the terminal just sits there, loading.

 

The other dockers will keep working, however i cannot turn any of them off.

Edited December 11, 20178 yr by AndreasLindroth

On 2017-11-12 at 2:26 AM, clowrym said:

I thought it was running fine for about a day, but it seems its a consistant issue....and there upon reboot, Once dockers start, i cant stop them, nor can I stop the arra for a reboot, or stop docker manager in general....

 

Nov 11 18:26:43 Test nginx: 2017/11/11 18:26:43 [error] 13299#13299: *895 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.107, server: , request: "GET /plugins/dynamix.docker.manager/include/CreateDocker.php?updateContainer=true&ct[]=sonarr HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.11", referrer: "http://192.168.0.11/Docker"

Nov 11 18:26:43 Test nginx: 2017/11/11 18:26:43 [error] 13299#13299: *895 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.107, server: , request: "GET /plugins/dynamix.docker.manager/include/CreateDocker.php?updateContainer=true&ct[]=sonarr HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.11", referrer: "http://192.168.0.11/Docker"

When i try a force update, or do an update, or just try and stop a container it hangs at stopping container, & I end up with number of errors in the syslog

 

Nov 11 18:20:14 Test kernel: CIFS VFS: Free previous auth_key.response = ffff8801f5fb4700
Nov 11 18:20:14 Test kernel: CIFS VFS: Free previous auth_key.response = ffff8801c84a0a00
Nov 11 18:20:14 Test kernel: CIFS VFS: Free previous auth_key.response = ffff8801465acd00
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -104 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:14 Test kernel: CIFS VFS: Error -32 sending data on socket to server
Nov 11 18:20:21 Test kernel: cifs_vfs_err: 29 callbacks suppressed
Nov 11 18:20:21 Test kernel: CIFS VFS: Free previous auth_key.response = ffff8801465ac280

Attached fresh DIag after a restart

 

test-diagnostics-20171111-1834.zip

 

 

 

This fixed it for me. Give it a try!

2 hours ago, AndreasLindroth said:

 

 

 

This fixed it for me. Give it a try!

 

 

I'll give it a try, Would one not just be able to mount it via NFS instead? I've never used NFS for any of my mounts, so I dont know if there are any performance benifits?

30 minutes ago, clowrym said:

I've never used NFS for any of my mounts, so I dont know if there are any performance benifits?

Apparently there are  https://ferhatakgun.com/network-share-performance-differences-between-nfs-smb/ on synthetic tests.  But those gains may or may not be realized in the real world.

16 hours ago, Squid said:

But those gains may or may not be realized in the real world.

 

INteressting, Might be worth some testing!!

On 12/12/2017 at 12:29 AM, Squid said:

Apparently there are  https://ferhatakgun.com/network-share-performance-differences-between-nfs-smb/ on synthetic tests.  But those gains may or may not be realized in the real world.

I have seen quite significant improvements using NFS instead of SMB in some streaming situations, so NFS is definitely worth testing.

NFS is definitely better than CIFS/SMB.

Performance is the reason they still use it with the big name Fileservers and Hypervisors

Companies selling switches and routers use FTP and NFS as a benchmark of throughput as both are simple protocols that can easily do near wirespeed.