error on running swarm [manager stopped: can't initialize raft node: WAL error cannot be repaired: unexpected EOF]

[foxundermoon]

manager node docker info

Containers: 35
 Running: 14
 Paused: 0
 Stopped: 21
Images: 77
Server Version: 17.09.0-ce
Storage Driver: overlay
 Backing Filesystem: xfs
 Supports d_type: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: error
 NodeID:
 Error: manager stopped: can't initialize raft node: WAL error cannot be repaired: unexpected EOF
 Is Manager: false
 Node Address: 10.10.10.62
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 06b9cb35161009dcb7123345749fef02f7cea8e0
runc version: 3f2f8b84a77f73d38244dd690525642a72156c64
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: 32
Total Memory: 46.77GiB
Name: BJ-H03-12-cm.getui
ID: 34OK:O5JK:V3PU:SMDX:6SJS:ZT76:CIZ4:AHX7:OKAT:U2SK:LFGR:7T2S
Docker Root Dir: /app/docker/dataroot
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Registry Mirrors:
 https://kohnnhik.mirror.aliyuncs.com/
Live Restore Enabled: false

WARNING: overlay: the backing xfs filesystem is formatted without d_type support, which leads to incorrect behavior.
         Reformat the filesystem with ftype=1 to enable d_type support.
         Running without d_type support will not be supported in future releases.
WARNING: bridge-nf-call-ip6tables is disabled

[stowns]

same issue here on RHEL. Unable to --force-new-cluster

docker swarm init  --force-new-cluster
Error response from daemon: manager stopped: can't initialize raft node: WAL error cannot be repaired: unexpected EOF

docker node ls
Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.

docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 665
Server Version: 17.09.0-ce
Storage Driver: devicemapper
 Pool Name: vg_docker-thinpool_s
 Pool Blocksize: 65.54kB
 Base Device Size: 10.74GB
 Backing Filesystem: xfs
 Data file:
 Metadata file:
 Data Space Used: 54.4GB
 Data Space Total: 102GB
 Data Space Available: 47.61GB
 Metadata Space Used: 118.4MB
 Metadata Space Total: 1.074GB
 Metadata Space Available: 955.3MB
 Thin Pool Minimum Free Space: 10.2GB
 Udev Sync Supported: true
 Deferred Removal Enabled: true
 Deferred Deletion Enabled: true
 Deferred Deleted Device Count: 0
 Library Version: 1.02.140-RHEL7 (2017-05-03)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 06b9cb35161009dcb7123345749fef02f7cea8e0
runc version: 3f2f8b84a77f73d38244dd690525642a72156c64
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-693.2.1.el7.x86_64
Operating System: Red Hat Enterprise Linux Server 7.4 (Maipo)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.26GiB
Name: vdcalq05504
ID: HS2R:CIYG:CKW3:6IGG:6OWP:O5X6:3UEV:JM6B:NZ5I:Z5EU:G62I:J336
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

[nishanttotla]

@foxundermoon please open this issue on https://www.github.com/docker/swarmkit. Sorry for the trouble.