Reply
NES
Explorer
Posts: 12
Registered: ‎07-03-2017

ContainerCreating: Creating engine container

hi

 

i followed below steps to create project

Setting Up a Scala Project

  1. Open Cloudera Data Science Workbench.
  2. Select New Project.
  3. Enter a Project Name.
  4. Choose whether the Project Visibility is Private or Public.
  5. Under Initial Setup, choose the Template tab.
  6. Select any Scala/python/R.
  7. Click Create Project. Your new project displays sample files.
  8. Click Open Workbench.
  9. Select any Scala/python/R engine.
  10. Click Launch Session.

the session launching never complete with status of "ContainerCreating: Creating engine container" and scheduling

 

Regards

Nkonzo

NES
Explorer
Posts: 12
Registered: ‎07-03-2017

Re: ContainerCreating: Creating engine container

there was a problem with wildcard dns.

 

i built my own dns server and i went though and image and containers are created.

 

i can created and launch the projects.

NES
Explorer
Posts: 12
Registered: ‎07-03-2017

Re: ContainerCreating: Creating engine container

the images/containers cannot resolve hostname with names but IP. scala project comes with error.

Setting default log level to "ERROR".
To adjust logging level use sc.setLogLevel(newLevel). For SparkR, use setLogLevel(newLevel).
17/07/10 08:26:54 ERROR spark.SparkContext: Error initializing SparkContext.
java.lang.IllegalArgumentException: java.net.UnknownHostException: CDH-MN-511-CE1.EOH.COM
	at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:406)
	at org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310)
	at org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider$DefaultProxyFactory.createProxy(ConfiguredFailoverProxyProvider.java:68)

if i use terminal, i cannot ping the server with their names but i can with IPs

cdsw@zx991teec5q9o67g:~$ cat /etc/hosts
# Kubernetes-managed hosts file.
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
fe00::0 ip6-mcastprefix
fe00::1 ip6-allnodes
fe00::2 ip6-allrouters
100.66.0.9 zx991teec5q9o67g
100.77.0.130 cdsw.domainz.com
100.77.0.130 models.cdsw.domainz.com
100.77.0.130 assets.cdsw.domainz.com
100.77.0.130 consoles.cdsw.domainz.com
100.77.0.129 livelog.cdsw.domainz.com
cdsw@zx991teec5q9o67g:~$
cdsw@zx991teec5q9o67g:~$
cdsw@zx991teec5q9o67g:~$ ping master
ping: unknown host cdh-mn-511-ce1
cdsw@zx991teec5q9o67g:~$ ping 10.10.51.216
PING 10.10.51.216 (10.10.51.216) 56(84) bytes of data.
64 bytes from 10.10.51.216: icmp_seq=1 ttl=63 time=0.220 ms
64 bytes from 10.10.51.216: icmp_seq=2 ttl=63 time=0.209 ms
^C
--- 10.10.51.216 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.209/0.214/0.220/0.015 ms

 

 

Explorer
Posts: 9
Registered: ‎03-29-2017

Re: ContainerCreating: Creating engine container

How to check the engine status in the backend ?

 

I have installed Cloudera Data Science Workbench after fulfilling prerequisites.

cdsw status and cdsw validate doesn't show any errors or warnings. But, when i open the workbench and try to start a scala,python or R sessions, it's showing the "ContainerCreating: Creating engine container" forever with red cursor at the bottom input box.

when i go back to projects and reopen the session, it's showing green.

But it doesn't take any input after that.

I somehow tried to check with "docker ps" command which shows only docker containers which are created when i submit the job which is not much informative.

 

I'm curious to check the logs about what's happening in the backend.

 

Can someone help the approach to troubleshoot this issue ?

 

Does anyone know how exactly it works in the backend ?

 

Explorer
Posts: 9
Registered: ‎03-29-2017

Re: ContainerCreating: Creating engine container

[ Edited ]

Screen Shot 2017-09-18 at 5.10.51 PM.png

 

 

this is the error appeared on the web ui after restarting the cdsw.

 

and cdsw validate gives the following error:

 

WARNING: Unable to bring up pods tagged as 'k8s-app' in the kube-system cluster.

ERROR::
WARNING: Unable to bring up kube-system cluster.: 1

 

Announcements