Member since
04-01-2016
10
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4518 | 06-13-2017 01:36 AM |
06-16-2017
01:51 AM
Hi Tristan, The problem is solved by your suggestion. Thanks. Polly
... View more
06-14-2017
10:38 PM
I try to start a new session to run any engine kernel, Python or Scala or R. There is a an error "target is not defined". i have run "cdsw validate" and there is no error. What target has not been defined and cause the error?
... View more
Labels:
06-13-2017
01:36 AM
The problem is fixed by finally creating a new VM with CDH 5.8 installed.
... View more
06-12-2017
08:52 PM
I have tried many times to run "cdsw reset" and "cdsw init" but the result is the same.
... View more
06-12-2017
07:10 PM
Please find OS and Kernel version as follows. Thanks. [root@localhost user]# hostnamectl Static hostname: localhost.localdomain Icon name: computer-vm Chassis: vm Machine ID: 5fdda32e3dd741bba596cdb067fd60a4 Boot ID: 619d8c7983ef4605ab0df3e0257356b1 Virtualization: vmware Operating System: CentOS Linux 7 (Core) CPE OS Name: cpe:/o:centos:centos:7 Kernel: Linux 3.10.0-327.el7.x86_64 Architecture: x86-64 [root@localhost user]# rpm --query centos-release centos-release-7-2.1511.el7.centos.2.10.x86_64
... View more
06-12-2017
07:08 PM
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 --
... View more
06-11-2017
10:12 PM
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...
... View more
Labels:
06-08-2017
01:43 AM
After changing block device to 100GB. The problem is solved. However, there is another problem is encountered. During "cdsw init", the following error is resulted. I cannot understand the error message. Do I need to pre-configure docker? thanks. ** (pkttyagent:18193): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) Error registering authentication agent: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (g-dbus-error-quark, 4) Starting docker... ERROR:: Unable to start docker: 1
... View more
06-07-2017
11:42 PM
I encounter the following error during running the command "cdsw init". The reason is "The combined size of the Docker block devices is too small". [root@localhost config]# cdsw init Using user-specified config file: /etc/cdsw/config/cdsw.conf Prechecking OS Version........[OK] Prechecking scaling limits for processes........[OK] Prechecking scaling limits for open files........[OK] Prechecking that iptables are not configured........ WARNING: Cloudera Data Science Workbench requires iptables, but does not support preexisting iptables rules. Press enter to continue Prechecking that SELinux is disabled........[OK] Prechecking configured block devices and mountpoints........[OK] Prechecking kernel parameters........[OK] Prechecking that docker block devices are of adequate size........ ERROR:: The combined size of the Docker block devices is too small: 1 ERROR:: Pre-install validation failed: 1 According to the comment in /etc/cdsw/config/cdsw.conf, the min size of docker block devices is 500GB. Is it a must? I just wanna to test out the feature of cdsw. Can I have mount point with less than 500GB? # Block device(s) for Docker images (space separated if multiple). # # These block devices cannot be partitions and should be at least 500GB. SSDs # are strongly recommended.
... View more
Labels: