TECHZEN Zenoss User Community ARCHIVE  

Docker container getting hanged frequently

Subject: Docker container getting hanged frequently
Author: Uday Jeevan Leo
Posted: 2017-10-12 09:22

Hi,

Docker container getting hanged frequently , i had to manually start service of both docker and core.

below are the logs.

[435802.620902] docker0: port 30(vethea56af9) entered disabled state

[435802.626194] device vethea56af9 left promiscuous mode

[435802.626225] docker0: port 30(vethea56af9) entered disabled state

[435802.652809] XFS (dm-29): Unmounting Filesystem

[435802.733769] XFS (dm-26): Unmounting Filesystem

[435802.798029] XFS (dm-43): Unmounting Filesystem

[435802.880643] XFS (dm-21): Unmounting Filesystem

[435802.962263] XFS (dm-17): Unmounting Filesystem

[435803.046233] XFS (dm-23): Unmounting Filesystem

[435803.149042] XFS (dm-35): Unmounting Filesystem

[435803.255171] XFS (dm-33): Unmounting Filesystem

[435803.397211] XFS (dm-25): Unmounting Filesystem

[435803.436984] docker0: port 34(veth6c6df82) entered disabled state

[435803.476540] docker0: port 34(veth6c6df82) entered disabled state

[435803.479573] device veth6c6df82 left promiscuous mode

[435803.479612] docker0: port 34(veth6c6df82) entered disabled state

[435803.520256] XFS (dm-39): Unmounting Filesystem

[435803.837274] docker0: port 26(veth9efe4d0) entered disabled state

[435803.849531] docker0: port 26(veth9efe4d0) entered disabled state

[435803.852528] device veth9efe4d0 left promiscuous mode

[435803.852567] docker0: port 26(veth9efe4d0) entered disabled state

[435803.909167] XFS (dm-32): Unmounting Filesystem

[435805.841162] docker0: port 38(vethc4d66b1) entered disabled state

[435805.880569] docker0: port 38(vethc4d66b1) entered disabled state

[435805.883843] device vethc4d66b1 left promiscuous mode

[435805.883872] docker0: port 38(vethc4d66b1) entered disabled state

[435805.947591] XFS (dm-44): Unmounting Filesystem

[435806.327893] docker0: port 39(veth5623471) entered disabled state

[435806.411673] docker0: port 39(veth5623471) entered disabled state

[435806.415129] device veth5623471 left promiscuous mode

[435806.415162] docker0: port 39(veth5623471) entered disabled state

[435806.500590] XFS (dm-41): Unmounting Filesystem

[435836.051741] docker0: port 9(vethf749fdb) entered disabled state

[435836.066494] docker0: port 9(vethf749fdb) entered disabled state

[435836.069334] device vethf749fdb left promiscuous mode

[435836.069378] docker0: port 9(vethf749fdb) entered disabled state

[435836.117828] XFS (dm-15): Unmounting Filesystem



------------------------------
Uday
------------------------------


Subject: RE: Docker container getting hanged frequently
Author: Mohammed Irshad
Posted: 2017-10-13 17:54

Hi,

Please paste the output of below commands from the host which has issues with docker:

$ docker version
$ docker info 
$ uname -a

Stop serviced and check for any stale containers, if so delete them after you stop serviced.

systemctl stop serviced

docker ps -qa
rm $(docker ps -qa)

Restart docker: systemctl restart docker
Start serviced : systemctl start serviced
restart nfs : systemctl restart nfs

Let me know.


 


------------------------------
Irshad
------------------------------


Subject: RE: Docker container getting hanged frequently
Author: Uday Jeevan Leo
Posted: 2017-10-17 03:43

Hi,

Please find the below outputs.

[root@ibcczenoss ccuser]# docker version
Client:
Version: 17.03.1-ce
API version: 1.27
Go version: go1.7.5
Git commit: c6d412e
Built: Mon Mar 27 17:05:44 2017
OS/Arch: linux/amd64

Server:
Version: 17.03.1-ce
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: c6d412e
Built: Mon Mar 27 17:05:44 2017
OS/Arch: linux/amd64
Experimental: false
[root@ibcczenoss ccuser]#
[root@ibcczenoss ccuser]# docker info
Containers: 40
Running: 39
Paused: 0
Stopped: 1
Images: 15
Server Version: 17.03.1-ce
Storage Driver: devicemapper
Pool Name: docker-253:0-134625034-pool
Pool Blocksize: 65.54 kB
Base Device Size: 48.32 GB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 5.056 GB
Data Space Total: 107.4 GB
Data Space Available: 28.07 GB
Metadata Space Used: 16.48 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.131 GB
Thin Pool Minimum Free Space: 10.74 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.107-RHEL7 (2015-10-14)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.0-327.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.67 GiB
Name: ibcczenoss.ibcc.net
ID: LYEP:NPR7:MAEV:EEQC:2DNN:HWJD:QTTG:CC3J:5AP2:VQLJ:RJLJ:QMXY
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Experimental: false
Insecure Registries:
172.16.106.107:5000
127.0.0.0/8
Live Restore Enabled: false
[root@ibcczenoss ccuser]# uname -a
Linux ibcczenoss.ibcc.net 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@ibcczenoss ccuser]#


------------------------------
Uday Jeevan Leo
------------------------------


< Previous
UDP port monitoring in Core 4.2.5
  Next
Broken Device - Completely unable to remove and cannot install zenpack
>