- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Unable to Start Docker after Running cdsw init
Created on 06-11-2017 10:12 PM - edited 09-16-2022 04:44 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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...
Created 06-13-2017 01:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The problem is fixed by finally creating a new VM with CDH 5.8 installed.
Created 06-12-2017 01:54 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can see more information using:
systemctl status docker
journalctl -u docker
Please let us know what you find.
Created 06-12-2017 07:08 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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 --
Created 06-12-2017 08:44 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It appears your installation was interrupted. Please try `cdsw reset` followed by `cdsw init`.
Created 06-12-2017 08:52 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have tried many times to run "cdsw reset" and "cdsw init" but the result is the same.
Created 06-13-2017 01:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The problem is fixed by finally creating a new VM with CDH 5.8 installed.
