search

docker-archive / classicswarm

Swarm Classic: a container clustering system. Not to be confused with Docker Swarm which is at https://github.com/docker/swarmkit
Apache License 2.0
5.75k stars 1.08k forks source link

nil pointer deference panic #1821

Closed CRogers closed 8 years ago

CRogers commented 8 years ago

We're getting a random nil pointer dereference error with swarm-1.1.0 and docker 1.10.1:

panic: runtime error: invalid memory address or nil pointer dereference

Full stacktrace here: http://pastebin.com/7p1JjQaG.

Docker info:

[swarm-master] $ docker info
Containers: 21
 Running: 1
 Paused: 0
 Stopped: 20
Images: 17
Server Version: 1.10.1
Storage Driver: devicemapper
 Pool Name: docker-253:1-537303656-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 214.7 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 282.5 MB
 Data Space Total: 107.4 GB
 Data Space Available: 107.1 GB
 Metadata Space Used: 1.651 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.146 GB
 Udev Sync Supported: false
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /opt/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /opt/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.82 (2013-10-04)
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 3.10.0-327.4.4.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.451 GiB
Name: <redacted>
ID: OJPN:67W2:W6BB:3R2X:F2LR:S4MX:FY6G:4LL7:BSW3:DBRH:4K2X:DI64
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Identical configuration on swarm nodes.

The container died:

[swarm-master] $ docker ps -a
7b129c9e968a        swarm:1.1.0         "/swarm manage token:"   42 minutes ago      Exited (2) 10 minutes ago                               trusting_wilson

This just seems to randomly happen after a period of time; not sure what's going on.

abronan commented 8 years ago

Thanks @CRogers, seems like this issue was fixed in master (#1805), we planned to release an 1.1.1 soon. Can you give it a try and let us know if that fixes the issue? (if using the Image you can pull dockerswarm/swarm:master)

CRogers commented 8 years ago

Ok, I've installed the latest master. Will leave to see if it crashes again after a couple of days of use.

vieux commented 8 years ago

@CRogers verdict ?

amitshukla commented 8 years ago

@CRogers closing this issue as it looks like you didn't hit the issue with 1.1.1