Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Unable to Start Docker after Running cdsw init

Solved Go to solution

Unable to Start Docker after Running cdsw init

Explorer

After running command cdsw init, the following screen is printed out. Docker cannot be started. Is there any way to check up the problem? What cause docker cannot be started up?

 

Creating docker thinpool if it does not exist
--- Logical volume ---
LV Name thinpool
VG Name docker
LV UUID pJd0MH-JXC7-tNmY-1vR6-nwDd-nF3c-l1j8Fs
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2017-06-08 01:38:17 -0700
LV Pool metadata thinpool_tmeta
LV Pool data thinpool_tdata
LV Status available
# open 0
LV Size 95.00 GiB
Allocated pool data 0.00%
Allocated metadata 0.01%
Current LE 24319
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:2

Docker thinpool already configured.
Initialize application storage at /var/lib/cdsw
Disabling node with IP [192.168.37.129]...
Node [192.168.37.129] removed from nfs export list successfully.
Stopping rpc-statd...
Stopping nfs-idmapd...
Stopping rpcbind...
Stopping nfs-server...
Removing entry from /etc/fstab...
Unmounting [/dev/sdc]...
Skipping format since volumes are already set correctly.
Adding entry to /etc/fstab...
Mounting [/var/lib/cdsw]...
Starting rpc-statd...
Enabling rpc-statd...
Starting nfs-idmapd...
Enabling nfs-idmapd...
Starting rpcbind...
Enabling rpcbind...
Starting nfs-server...
Enabling nfs-server...
Enabling node with IP [192.168.37.129]...
Node [192.168.37.129] added to nfs export list successfully.
Starting rpc-statd...
Enabling rpc-statd...
Starting nfs-idmapd...
Enabling nfs-idmapd...
Starting rpcbind...
Enabling rpcbind...
Starting nfs-server...
Enabling nfs-server...
Starting docker...

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Unable to Start Docker after Running cdsw init

Explorer

The problem is fixed by finally creating a new VM with CDH 5.8 installed. 

5 REPLIES 5

Re: Unable to Start Docker after Running cdsw init

Rising Star

You can see more information using:

 

systemctl status docker

journalctl -u docker

 

Please let us know what you find.

Re: Unable to Start Docker after Running cdsw init

Explorer

Please find the result of systemctl status docker and journalctl -u docker

 

[root@localhost user]# systemctl status docker
● docker.service - docker
Loaded: loaded (/etc/systemd/system/docker.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Docs: https://docs.docker.com
[root@localhost user]# journalctl -u docker
-- No entries --

Re: Unable to Start Docker after Running cdsw init

Rising Star

It appears your installation was interrupted.  Please try `cdsw reset` followed by `cdsw init`.

 

Re: Unable to Start Docker after Running cdsw init

Explorer

I have tried many times to run "cdsw reset" and "cdsw init" but the result is the same. 

Re: Unable to Start Docker after Running cdsw init

Explorer

The problem is fixed by finally creating a new VM with CDH 5.8 installed.