Cannot start workspace #1226

ukman · 2016-05-11T09:24:17Z

I downloaded eclipse-che-4.2.0 and started it.
When I try to create/run workspace it displays in browser

Starting workspace agent
Agents provide RESTful services like intellisense and SSH
[STDOUT] Listening for transport dt_socket at address: 4403
[STDOUT] 2016-05-11 08:59:06,527[main] [INFO] [o.a.c.s.VersionLoggerListener 89] - Server version: Apache Tomcat/8.0.32
[STDOUT] 2016-05-11 08:59:06,540[main] [INFO] [o.a.c.s.VersionLoggerListener 91] - Server built: Feb 2 2016 19:34:53 UTC
[STDOUT] 2016-05-11 08:59:06,541[main] [INFO] [o.a.c.s.VersionLoggerListener 93] - Server number: 8.0.32.0
[STDOUT] 2016-05-11 08:59:06,542[main] [INFO] [o.a.c.s.VersionLoggerListener 95] - OS Name: Linux
[STDOUT] 2016-05-11 08:59:06,543[main] [INFO] [o.a.c.s.VersionLoggerListener 97] - OS Version: 3.16.0-4-amd64
[STDOUT] 2016-05-11 08:59:06,543[main] [INFO] [o.a.c.s.VersionLoggerListener 99] - Architecture: amd64
[STDOUT] 2016-05-11 08:59:06,544[main] [INFO] [o.a.c.s.VersionLoggerListener 101] - Java Home: /opt/jre1.8.0_65
[STDOUT] 2016-05-11 08:59:06,554[main] [INFO] [o.a.c.s.VersionLoggerListener 103] - JVM Version: 1.8.0_65-b17
[STDOUT] 2016-05-11 08:59:06,560[main] [INFO] [o.a.c.s.VersionLoggerListener 105] - JVM Vendor: Oracle Corporation
[STDOUT] 2016-05-11 08:59:06,561[main] [INFO] [o.a.c.s.VersionLoggerListener 107] - CATALINA_BASE: /home/user/che/ws-agent
[STDOUT] 2016-05-11 08:59:06,562[main] [INFO] [o.a.c.s.VersionLoggerListener 109] - CATALINA_HOME: /home/user/che/ws-agent
[STDOUT] 2016-05-11 08:59:06,563[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.config.file=/home/user/che/ws-agent/conf/logging.properties
[STDOUT] 2016-05-11 08:59:06,564[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
[STDOUT] 2016-05-11 08:59:06,566[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xms256m
[STDOUT] 2016-05-11 08:59:06,568[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xmx1024m
[STDOUT] 2016-05-11 08:59:06,568[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.security.egd=file:/dev/./urandom
[STDOUT] 2016-05-11 08:59:06,569[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.logs.dir=/home/user/che/ws-agent/logs
[STDOUT] 2016-05-11 08:59:06,569[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -agentlib:jdwp=transport=dt_socket,address=4403,server=y,suspend=n
[STDOUT] 2016-05-11 08:59:06,574[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote
[STDOUT] 2016-05-11 08:59:06,580[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.ssl=false
[STDOUT] 2016-05-11 08:59:06,581[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.authenticate=false
[STDOUT] 2016-05-11 08:59:06,581[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.local.conf.dir=/mnt/che/conf
[STDOUT] 2016-05-11 08:59:06,582[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.endorsed.dirs=/home/user/che/ws-agent/endorsed
[STDOUT] 2016-05-11 08:59:06,582[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.base=/home/user/che/ws-agent
[STDOUT] 2016-05-11 08:59:06,583[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.home=/home/user/che/ws-agent
[STDOUT] 2016-05-11 08:59:06,583[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.io.tmpdir=/home/user/che/ws-agent/temp
[STDOUT] 2016-05-11 08:59:06,949[main] [INFO] [o.a.c.http11.Http11NioProtocol 425] - Initializing ProtocolHandler ["http-nio-4401"]
[STDOUT] 2016-05-11 08:59:06,985[main] [INFO] [o.a.t.util.net.NioSelectorPool 72] - Using a shared selector for servlet write/read
[STDOUT] 2016-05-11 08:59:07,000[main] [INFO] [o.a.catalina.startup.Catalina 591] - Initialization processed in 1284 ms
[STDOUT] 2016-05-11 08:59:07,041[main] [INFO] [c.m.JmxRemoteLifecycleListener 332] - The JMX Remote Listener has configured the registry on port 32002 and the server on port 32102 for the Platform server
[STDOUT] 2016-05-11 08:59:07,108[main] [INFO] [o.a.c.core.StandardService 435] - Starting service Catalina
[STDOUT] 2016-05-11 08:59:07,109[main] [INFO] [o.a.c.core.StandardEngine 259] - Starting Servlet Engine: Apache Tomcat/8.0.32
[STDOUT] 2016-05-11 08:59:07,265[ost-startStop-1] [INFO] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/user/che/ws-agent/webapps/ide.war
[STDOUT] Wed May 11 08:59:19 UTC 2016 - [localhost-startStop-1] Product-specified preferences called before plugin is started
[STDOUT] 2016-05-11 08:59:20,449[rrest.WSClient1] [INFO] [.c.a.c.n.WSocketEventBusClient 223] - Open connection to ws://che-host:8080/ide/api/eventbus/?token=dummy_token.
[STDOUT] 2016-05-11 08:59:20,793[ost-startStop-1] [INFO] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/user/che/ws-agent/webapps/ide.war has finished in 13,527 ms
[STDOUT] 2016-05-11 08:59:20,796[ost-startStop-1] [INFO] [o.a.c.startup.HostConfig 1030] - Deploying web application directory /home/user/che/ws-agent/webapps/ROOT
[STDOUT] 2016-05-11 08:59:20,944[ost-startStop-1] [INFO] [o.a.c.startup.HostConfig 1142] - Deployment of web application directory /home/user/che/ws-agent/webapps/ROOT has finished in 147 ms
[STDOUT] 2016-05-11 08:59:20,953[main] [INFO] [o.a.c.http11.Http11NioProtocol 470] - Starting ProtocolHandler ["http-nio-4401"]
[STDOUT] 2016-05-11 08:59:20,976[main] [INFO] [o.a.catalina.startup.Catalina 642] - Server startup in 13974 ms
[STDOUT] 2016-05-11 08:59:21,442[nio-4401-exec-1] [WARN ] [i.ContainerResponse$BodyWriter 90] - Client has aborted connection. Response writing omitted.
[STDOUT] 2016-05-11 08:59:21,442[nio-4401-exec-4] [WARN ] [i.ContainerResponse$BodyWriter 90] - Client has aborted connection. Response writing omitted.
[STDOUT] 2016-05-11 08:59:21,450[nio-4401-exec-3] [WARN ] [i.ContainerResponse$BodyWriter 90] - Client has aborted connection. Response writing omitted.

...and freezes.

When I try to open workspace from workspace list, it pops up

Error: Can't load project types: Error
at Object.window.IDE.eventHandlers.initializationFailed (http://XXXXXXX:8080/ide/WS_JAVA_1?uid=712513:39:27)
at Idb (_app-0.js:1781:44)
at Vdb (_app-0.js:1786:380)
at _.Wn (_app-0.js:4291:317)
at eval (_app-0.js:1316:278)

Any ideas?

ghost · 2016-05-11T12:08:23Z

How did you start Che? If it is started in a VM you need to use -r:$IP flag where $IP is IP of your VM

ukman · 2016-05-11T14:39:08Z

Yes, I start it on VM and if I specify -r:$PUBLIC_IP then last log lines are

[STDOUT] 2016-05-11 13:21:36,477[main] [INFO] [o.a.catalina.startup.Catalina 642] - Server startup in 13185 ms
[ERROR] Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.

If I specify -r:$PRIVATE_IP last log lines are

[STDOUT] 2016-05-11 14:28:33,746[main] [INFO] [o.a.c.http11.Http11NioProtocol 470] - Starting ProtocolHandler ["http-nio-4401"]
[STDOUT] 2016-05-11 14:28:33,758[main] [INFO] [o.a.catalina.startup.Catalina 642] - Server startup in 13891 ms
[STDOUT] 2016-05-11 14:28:34,269[nio-4401-exec-1] [WARN ] [i.ContainerResponse$BodyWriter 90] - Client has aborted connection. Response writing omitted.
[STDOUT] 2016-05-11 14:28:34,272[nio-4401-exec-3] [WARN ] [i.ContainerResponse$BodyWriter 90] - Client has aborted connection. Response writing omitted.
[STDOUT] 2016-05-11 14:28:34,281[nio-4401-exec-4] [WARN ] [i.ContainerResponse$BodyWriter 90] - Client has aborted connection. Response writing omitted.

So it does not start Workspace...

ghost · 2016-05-12T05:43:51Z

If Che server is launched on a remote VM, this parameter is mandatory.

Can you verify that ports 32768-65535 are open for inbound connections?

In the first case, Che server cannot ping ws-agent, probably because the right ports are blocked.

In the second case, Che server can ping ws-agent, but then your browser cannot connect to ws-agent because it is a private IP.

How to fix it? Make sure port range 32768-65535 is opened.

ukman · 2016-05-12T06:34:55Z

Right... Ports were closed... Thanks

ukman · 2016-05-16T12:32:22Z

Hi again... Everything was fine when Che and Docker was on the same machine.
I moved docker to another VM... The problem absolutely the same... I double checked all my ports, but it freezes after starting WS-Agent inside container.

[STDOUT] 2016-05-16 11:36:03,479[main] [INFO] [o.a.catalina.startup.Catalina 642] - Server startup in 11083 ms
[ERROR] Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.

ghost · 2016-05-16T13:19:06Z

Did you export DOCKER_HOST env on the instance where Che server is being launched?

Can you share server logs? Also, did you run Che with -r parameter?

ukman · 2016-05-16T13:50:35Z

I exported DOCKER_HOST

export DOCKER_HOST=tcp://EXTERNAL_DOCKER_IP:2375
I started with -r params
che -r:EXTERNAL_CHE_IP

Here last log lines (full log is in private message)

2016-05-16 11:35:45,535[nio-8080-exec-2] [INFO ] [o.e.c.a.w.s.WorkspaceManager 675] - Workspace 'che:WS-9' with id 'workspacegi15e3f55xjozcul' created by user 'che'
2016-05-16 11:35:48,544[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 162] - Creating machine [ws = workspacegi15e3f55xjozcul: env = WS-9: machine = ws-machine]
2016-05-16 11:35:50,382[kspaceManager-0] [INFO ] [c.p.d.m.DockerInstanceProvider 447] - Machine with id 'machinezanc4f1x51bkqg37' backed by container '302bd0b23ede3a310b2126710c20dc6f701e3ac52896e6599c5b648e5c36ed2f' has been deployed on node 'XXX.XXX.XXX.XXX'
2016-05-16 11:36:50,461[kspaceManager-0] [ERROR] [.c.a.m.s.w.WsAgentLauncherImpl 111] - Fail pinging ws agent. Workspace ID:workspacegi15e3f55xjozcul. Url:http://XXX.XXX.XXX.XXX:32790/api/ext/. Timestamp:{}
2016-05-16 11:36:50,614[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 538] - Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
org.eclipse.che.api.machine.server.exception.MachineException: Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:405) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:342) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:166) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.createMachine(WorkspaceRuntimes.java:490) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:411) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:368) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:180) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:522) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.2.0.jar:4.2.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_72-internal]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_72-internal]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_72-internal]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
at org.eclipse.che.api.machine.server.wsagent.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:112) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:375) ~[che-core-api-machine-4.2.0.jar:4.2.0]
... 11 common frames omitted

ghost · 2016-05-16T13:51:34Z

che -r:EXTERNAL_CHE_IP should be che -r:EXTERNAL_DOCKER_IP

ukman · 2016-05-16T15:01:40Z

Right, thanks! Workspace is opened

But now it displays popup.

Connection Failed With Terminal
Some error happened with Terminal WebSocket connection

Any ideas?

ghost · 2016-05-16T16:59:40Z

@ukman When a workspace starts, Che mounts ws-agent.zip and terminal into a container and then starts them. Since ws-agent has started you copied ws-agent.zip onto a Docker VM. You should do the same for terminal.

Just copy terminal to your Docker VM and set its location in /conf/properties - machine.server.terminal.path_to_archive.linux_amd64=/path/on/docker/vm/terminal

ghost · 2016-05-31T07:10:23Z

@ukman any update on this?

ukman · 2016-05-31T13:04:19Z

Sorry for the delay... I am going to check it this week...

stoneqsl · 2016-06-14T02:42:40Z

I have the same problem,but I run it in Centos7.How to fix it? please help me,thanks!

ghost · 2016-06-14T04:06:21Z

@stoneqsl can you share your server and ws agent logs? And you need to start Che with -r:$IP where $IP is an external IP of your server. Also, ephemeral port range needs to be opened - 32768-65535

stoneqsl · 2016-06-14T04:20:59Z

yes.
[root@localhost bin]# sh che.sh run -s:uid -r:192.168.99.100

############## HOW TO CONNECT YOUR CHE CLIENT ###############
After Che server has booted, you can connect your clients by:

Open browser to http://localhost:8080, or:
Open native chromium app.
#############################################################

Using CATALINA_BASE: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
Using CATALINA_HOME: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
Using CATALINA_TMPDIR: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/temp
Using JRE_HOME: /etc/jvm/jdk1.8.91
Using CLASSPATH: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/conf/:/etc/jvm/jdk1.8.91/lib/tools.jar:/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/bin/bootstrap.jar:/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/bin/tomcat-juli.jar
2016-06-14 11:03:05,857[main] [INFO ] [o.a.c.s.VersionLoggerListener 89] - Server version: Apache Tomcat/8.0.32
2016-06-14 11:03:05,858[main] [INFO ] [o.a.c.s.VersionLoggerListener 91] - Server built: Feb 2 2016 19:34:53 UTC
2016-06-14 11:03:05,858[main] [INFO ] [o.a.c.s.VersionLoggerListener 93] - Server number: 8.0.32.0
2016-06-14 11:03:05,859[main] [INFO ] [o.a.c.s.VersionLoggerListener 95] - OS Name: Linux
2016-06-14 11:03:05,859[main] [INFO ] [o.a.c.s.VersionLoggerListener 97] - OS Version: 3.10.0-327.el7.x86_64
2016-06-14 11:03:05,859[main] [INFO ] [o.a.c.s.VersionLoggerListener 99] - Architecture: amd64
2016-06-14 11:03:05,859[main] [INFO ] [o.a.c.s.VersionLoggerListener 101] - Java Home: /etc/jvm/jdk1.8.91/jre
2016-06-14 11:03:05,859[main] [INFO ] [o.a.c.s.VersionLoggerListener 103] - JVM Version: 1.8.0_91-b14
2016-06-14 11:03:05,859[main] [INFO ] [o.a.c.s.VersionLoggerListener 105] - JVM Vendor: Oracle Corporation
2016-06-14 11:03:05,859[main] [INFO ] [o.a.c.s.VersionLoggerListener 107] - CATALINA_BASE: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
2016-06-14 11:03:05,859[main] [INFO ] [o.a.c.s.VersionLoggerListener 109] - CATALINA_HOME: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
2016-06-14 11:03:05,860[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.config.file=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/conf/logging.properties
2016-06-14 11:03:05,860[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
2016-06-14 11:03:05,860[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xms256m
2016-06-14 11:03:05,860[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xmx1024m
2016-06-14 11:03:05,860[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.security.egd=file:/dev/./urandom
2016-06-14 11:03:05,861[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dport.http=8080
2016-06-14 11:03:05,861[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.home=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0
2016-06-14 11:03:05,861[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.logs.dir=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/logs/
2016-06-14 11:03:05,861[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote
2016-06-14 11:03:05,861[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.ssl=false
2016-06-14 11:03:05,861[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.authenticate=false
2016-06-14 11:03:05,861[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.local.conf.dir=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/conf/
2016-06-14 11:03:05,862[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.endorsed.dirs=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/endorsed
2016-06-14 11:03:05,862[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.base=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
2016-06-14 11:03:05,862[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.home=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
2016-06-14 11:03:05,862[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.io.tmpdir=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/temp
2016-06-14 11:03:05,943[main] [INFO ] [o.a.c.http11.Http11NioProtocol 425] - Initializing ProtocolHandler ["http-nio-8080"]
2016-06-14 11:03:05,952[main] [INFO ] [o.a.t.util.net.NioSelectorPool 72] - Using a shared selector for servlet write/read
2016-06-14 11:03:05,954[main] [INFO ] [o.a.catalina.startup.Catalina 591] - Initialization processed in 254 ms
2016-06-14 11:03:05,999[main] [INFO ] [c.m.JmxRemoteLifecycleListener 332] - The JMX Remote Listener has configured the registry on port 32001 and the server on port 32101 for the Platform server
2016-06-14 11:03:05,999[main] [INFO ] [o.a.c.core.StandardService 435] - Starting service Catalina
2016-06-14 11:03:05,999[main] [INFO ] [o.a.c.core.StandardEngine 259] - Starting Servlet Engine: Apache Tomcat/8.0.32
2016-06-14 11:03:06,032[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/dashboard.war
2016-06-14 11:03:06,206[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/dashboard.war has finished in 173 ms
2016-06-14 11:03:06,207[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ide.war
2016-06-14 11:03:08,233[ost-startStop-1] [WARN ] [p.DockerExtConfBindingProvider 51] - DockerExtConfBindingProvider
2016-06-14 11:03:08,982[ost-startStop-1] [INFO ] [.c.p.d.c.DockerRegistryChecker 43] - Probing registry 'http://localhost:5000'
2016-06-14 11:03:08,988[ost-startStop-1] [WARN ] [.c.p.d.c.DockerRegistryChecker 50] - Docker registry http://localhost:5000 is not available, which means that you won't be able to save snapshots of your workspaces.
How to configure registry?
Local registry -> https://docs.docker.com/registry/
Remote registry -> set up 'docker.registry.auth.*' properties
2016-06-14 11:03:09,148[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ide.war has finished in 2,941 ms
2016-06-14 11:03:09,148[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/swagger.war
2016-06-14 11:03:09,174[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/swagger.war has finished in 26 ms
2016-06-14 11:03:09,177[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 1030] - Deploying web application directory /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ROOT
2016-06-14 11:03:09,205[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 1142] - Deployment of web application directory /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ROOT has finished in 28 ms
2016-06-14 11:03:09,211[main] [INFO ] [o.a.c.http11.Http11NioProtocol 470] - Starting ProtocolHandler ["http-nio-8080"]
2016-06-14 11:03:09,216[main] [INFO ] [o.a.catalina.startup.Catalina 642] - Server startup in 3260 ms
2016-06-14 11:03:16,785[nio-8080-exec-9] [WARN ] [i.ContainerResponse$BodyWriter 90] - Client has aborted connection. Response writing omitted.
2016-06-14 11:03:17,485[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 162] - Creating machine [ws = workspace5939m6h0iv9vur2i: env = default: machine = ws-machine]
2016-06-14 11:03:31,499[kspaceManager-0] [INFO ] [c.p.d.m.DockerInstanceProvider 447] - Machine with id 'machinecd6il56pn1jbh1jg' backed by container '47d392d992babb4478c4f627318d7b1a0617c48b0daffa7c1f18a2cbbac31524' has been deployed on node 'localhost'
2016-06-14 11:04:31,559[kspaceManager-0] [ERROR] [.c.a.m.s.w.WsAgentLauncherImpl 111] - Fail pinging ws agent. Workspace ID:workspace5939m6h0iv9vur2i. Url:http://192.168.99.100:32799/api/ext/. Timestamp:{}
2016-06-14 11:04:34,564[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 538] - Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
org.eclipse.che.api.machine.server.exception.MachineException: Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:405) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:342) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:166) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.createMachine(WorkspaceRuntimes.java:490) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:411) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:368) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:180) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:522) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.2.0.jar:4.2.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
at org.eclipse.che.api.machine.server.wsagent.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:112) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:375) ~[che-core-api-machine-4.2.0.jar:4.2.0]
... 11 common frames omitted
2016-06-14 11:29:17,782[kspaceManager-1] [INFO ] [o.e.c.a.m.s.MachineManager 162] - Creating machine [ws = workspace5939m6h0iv9vur2i: env = default: machine = ws-machine]
2016-06-14 11:29:38,812[kspaceManager-1] [INFO ] [c.p.d.m.DockerInstanceProvider 447] - Machine with id 'machinefl7kjfeaz9m1f0ld' backed by container 'cf9d8568bc29e60e01d2b03df519c53252a2bf2757d6204b0962f71832cbf46c' has been deployed on node 'localhost'
2016-06-14 11:30:38,866[kspaceManager-1] [ERROR] [.c.a.m.s.w.WsAgentLauncherImpl 111] - Fail pinging ws agent. Workspace ID:workspace5939m6h0iv9vur2i. Url:http://192.168.99.100:32806/api/ext/. Timestamp:{}
2016-06-14 11:30:41,895[kspaceManager-1] [ERROR] [o.e.c.a.w.s.WorkspaceManager 538] - Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
org.eclipse.che.api.machine.server.exception.MachineException: Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:405) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:342) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:166) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.createMachine(WorkspaceRuntimes.java:490) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:411) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:368) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:180) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:522) ~[che-core-api-workspace-4.2.0.jar:4.2.0]
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.2.0.jar:4.2.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.
at org.eclipse.che.api.machine.server.wsagent.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:112) ~[che-core-api-machine-4.2.0.jar:4.2.0]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:375) ~[che-core-api-machine-4.2.0.jar:4.2.0]
... 11 common frames omitted

STDOUT] Listening for transport dt_socket at address: 4403
[STDOUT] 2016-06-14 03:29:39,772[main] [INFO] [o.a.c.s.VersionLoggerListener 89] - Server version: Apache Tomcat/8.0.32
[STDOUT] 2016-06-14 03:29:39,776[main] [INFO] [o.a.c.s.VersionLoggerListener 91] - Server built: Feb 2 2016 19:34:53 UTC
[STDOUT] 2016-06-14 03:29:39,777[main] [INFO] [o.a.c.s.VersionLoggerListener 93] - Server number: 8.0.32.0
[STDOUT] 2016-06-14 03:29:39,777[main] [INFO] [o.a.c.s.VersionLoggerListener 95] - OS Name: Linux
[STDOUT] 2016-06-14 03:29:39,777[main] [INFO] [o.a.c.s.VersionLoggerListener 97] - OS Version: 3.10.0-327.el7.x86_64
[STDOUT] 2016-06-14 03:29:39,777[main] [INFO] [o.a.c.s.VersionLoggerListener 99] - Architecture: amd64
[STDOUT] 2016-06-14 03:29:39,778[main] [INFO] [o.a.c.s.VersionLoggerListener 101] - Java Home: /opt/jdk1.8.0_45/jre
[STDOUT] 2016-06-14 03:29:39,778[main] [INFO] [o.a.c.s.VersionLoggerListener 103] - JVM Version: 1.8.0_45-b14
[STDOUT] 2016-06-14 03:29:39,778[main] [INFO] [o.a.c.s.VersionLoggerListener 105] - JVM Vendor: Oracle Corporation
[STDOUT] 2016-06-14 03:29:39,778[main] [INFO] [o.a.c.s.VersionLoggerListener 107] - CATALINA_BASE: /home/user/che/ws-agent
[STDOUT] 2016-06-14 03:29:39,778[main] [INFO] [o.a.c.s.VersionLoggerListener 109] - CATALINA_HOME: /home/user/che/ws-agent
[STDOUT] 2016-06-14 03:29:39,779[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.config.file=/home/user/che/ws-agent/conf/logging.properties
[STDOUT] 2016-06-14 03:29:39,780[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
[STDOUT] 2016-06-14 03:29:39,780[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xms256m
[STDOUT] 2016-06-14 03:29:39,780[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xmx1024m
[STDOUT] 2016-06-14 03:29:39,780[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.security.egd=file:/dev/./urandom
[STDOUT] 2016-06-14 03:29:39,782[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.logs.dir=/home/user/che/ws-agent/logs
[STDOUT] 2016-06-14 03:29:39,782[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -agentlib:jdwp=transport=dt_socket,address=4403,server=y,suspend=n
[STDOUT] 2016-06-14 03:29:39,782[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote
[STDOUT] 2016-06-14 03:29:39,783[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.ssl=false
[STDOUT] 2016-06-14 03:29:39,787[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.authenticate=false
[STDOUT] 2016-06-14 03:29:39,787[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.local.conf.dir=/mnt/che/conf
[STDOUT] 2016-06-14 03:29:39,787[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.endorsed.dirs=/home/user/che/ws-agent/endorsed
[STDOUT] 2016-06-14 03:29:39,787[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.base=/home/user/che/ws-agent
[STDOUT] 2016-06-14 03:29:39,787[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.home=/home/user/che/ws-agent
[STDOUT] 2016-06-14 03:29:39,788[main] [INFO] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.io.tmpdir=/home/user/che/ws-agent/temp
[STDOUT] 2016-06-14 03:29:39,884[main] [INFO] [o.a.c.http11.Http11NioProtocol 425] - Initializing ProtocolHandler ["http-nio-4401"]
[STDOUT] 2016-06-14 03:29:39,895[main] [INFO] [o.a.t.util.net.NioSelectorPool 72] - Using a shared selector for servlet write/read
[STDOUT] 2016-06-14 03:29:39,898[main] [INFO] [o.a.catalina.startup.Catalina 591] - Initialization processed in 349 ms
[STDOUT] 2016-06-14 03:29:39,936[main] [INFO] [c.m.JmxRemoteLifecycleListener 332] - The JMX Remote Listener has configured the registry on port 32002 and the server on port 32102 for the Platform server
[STDOUT] 2016-06-14 03:29:39,936[main] [INFO] [o.a.c.core.StandardService 435] - Starting service Catalina
[STDOUT] 2016-06-14 03:29:39,936[main] [INFO] [o.a.c.core.StandardEngine 259] - Starting Servlet Engine: Apache Tomcat/8.0.32
[STDOUT] 2016-06-14 03:29:39,976[ost-startStop-1] [INFO] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/user/che/ws-agent/webapps/ide.war
[STDOUT] Tue Jun 14 03:29:43 UTC 2016 - [localhost-startStop-1] Product-specified preferences called before plugin is started
[STDOUT] 2016-06-14 03:29:43,468[rrest.WSClient1] [INFO] [.c.a.c.n.WSocketEventBusClient 223] - Open connection to ws://che-host:8080/ide/api/eventbus/?token=dummy_token.
[STDOUT] 2016-06-14 03:29:43,632[ost-startStop-1] [INFO] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/user/che/ws-agent/webapps/ide.war has finished in 3,656 ms
[STDOUT] 2016-06-14 03:29:43,635[ost-startStop-1] [INFO] [o.a.c.startup.HostConfig 1030] - Deploying web application directory /home/user/che/ws-agent/webapps/ROOT
[STDOUT] 2016-06-14 03:29:43,675[ost-startStop-1] [INFO] [o.a.c.startup.HostConfig 1142] - Deployment of web application directory /home/user/che/ws-agent/webapps/ROOT has finished in 39 ms
[STDOUT] 2016-06-14 03:29:43,683[main] [INFO] [o.a.c.http11.Http11NioProtocol 470] - Starting ProtocolHandler ["http-nio-4401"]
[STDOUT] 2016-06-14 03:29:43,688[main] [INFO] [o.a.catalina.startup.Catalina 642] - Server startup in 3789 ms
[ERROR] Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.

I don't know how to check my ephemeral port in Centos7.Can you help me? @eivantsov

ghost · 2016-06-14T04:26:29Z

@stoneqsl You are running Che in a Virtual machine, correct?

In your case, Che server cannot reach a workspace agent at http://192.168.99.100:32806/api/ext/

It can be a blocked port issue or a Docker issue, when you cannot reach any process in a container.

Are you using Virtual Box? 192.168.99.100 is the VM IP? And you use this IP to access Che?

stoneqsl · 2016-06-14T04:29:51Z

NO，I run it in Centos7,not in a Virtual machine.I just try to fix my problem. @eivantsov

ghost · 2016-06-14T04:35:56Z

If you run it natively, there's no need in -r parameter. Drop it and run Che as che.sh run.

stoneqsl · 2016-06-14T04:40:06Z

I run this command .

[root@localhost bin]# sh che.sh run -s:uid

############## HOW TO CONNECT YOUR CHE CLIENT ###############
After Che server has booted, you can connect your clients by:

Open browser to http://localhost:8080, or:
Open native chromium app.
#############################################################

Using CATALINA_BASE: Using CATALINA_HOME: Using CATALINA_TMPDIR: Using JRE_HOME: Using CLASSPATH: 2016-06-14 12:31:03,674[main] 2016-06-14 12:31:03,675[main] 2016-06-14 12:31:03,675[main] 2016-06-14 12:31:03,675[main] 2016-06-14 12:31:03,676[main] 2016-06-14 12:31:03,676[main] 2016-06-14 12:31:03,676[main] 2016-06-14 12:31:03,676[main] 2016-06-14 12:31:03,676[main] 2016-06-14 12:31:03,676[main] 2016-06-14 12:31:03,676[main] 2016-06-14 12:31:03,676[main] 2016-06-14 12:31:03,677[main] 2016-06-14 12:31:03,677[main] 2016-06-14 12:31:03,677[main] 2016-06-14 12:31:03,677[main] 2016-06-14 12:31:03,677[main] 2016-06-14 12:31:03,677[main] 2016-06-14 12:31:03,677[main] 2016-06-14 12:31:03,678[main] 2016-06-14 12:31:03,678[main] 2016-06-14 12:31:03,678[main] 2016-06-14 12:31:03,678[main] 2016-06-14 12:31:03,678[main] 2016-06-14 12:31:03,678[main] 2016-06-14 12:31:03,678[main] 2016-06-14 12:31:03,678[main] 2016-06-14 12:31:03,763[main] 2016-06-14 12:31:03,772[main] 2016-06-14 12:31:03,774[main] 2016-06-14 12:31:03,825[main] 2016-06-14 12:31:03,825[main] 2016-06-14 12:31:03,826[main] 2016-06-14 12:31:03,863[ost-startStop-1] 2016-06-14 12:31:04,046[ost-startStop-1] 2016-06-14 12:31:04,048[ost-startStop-1] 2016-06-14 12:31:06,106[ost-startStop-1] 2016-06-14 12:31:06,879[ost-startStop-1] 2016-06-14 12:31:06,886[ost-startStop-1] How to configure registry?
Local registry -> Remote registry -> 2016-06-14 12:31:07,022[ost-startStop-1] 2016-06-14 12:31:07,022[ost-startStop-1] 2016-06-14 12:31:07,053[ost-startStop-1] 2016-06-14 12:31:07,059[ost-startStop-1] 2016-06-14 12:31:07,093[ost-startStop-1] 2016-06-14 12:31:07,095[main] 2016-06-14 12:31:07,100[main] 2016-06-14 12:31:15,307[kspaceManager-0] 2016-06-14 12:31:26,806[kspaceManager-0] 2016-06-14 12:31:32,857[kspaceManager-0] 2016-06-14 12:31:32,858[kspaceManager-0] /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/temp
/etc/jvm/jdk1.8.91
/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/conf/:/etc/jvm/jdk1.8.91/lib/tools.jar:/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/bin/bootstrap.jar:/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/bin/tomcat-juli.jar
[INFO ] [o.a.c.s.VersionLoggerListener 89] - Server version: Apache Tomcat/8.0.32
[INFO ] [o.a.c.s.VersionLoggerListener 91] - Server built: Feb 2 2016 19:34:53 UTC
[INFO ] [o.a.c.s.VersionLoggerListener 93] - Server number: 8.0.32.0
[INFO ] [o.a.c.s.VersionLoggerListener 95] - OS Name: Linux
[INFO ] [o.a.c.s.VersionLoggerListener 97] - OS Version: 3.10.0-327.el7.x86_64
[INFO ] [o.a.c.s.VersionLoggerListener 99] - Architecture: amd64
[INFO ] [o.a.c.s.VersionLoggerListener 101] - Java Home: /etc/jvm/jdk1.8.91/jre
[INFO ] [o.a.c.s.VersionLoggerListener 103] - JVM Version: 1.8.0_91-b14
[INFO ] [o.a.c.s.VersionLoggerListener 105] - JVM Vendor: Oracle Corporation
[INFO ] [o.a.c.s.VersionLoggerListener 107] - CATALINA_BASE: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
[INFO ] [o.a.c.s.VersionLoggerListener 109] - CATALINA_HOME: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.config.file=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/conf/logging.properties
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xms256m
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xmx1024m
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.security.egd=file:/dev/./urandom
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dport.http=8080
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.home=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.logs.dir=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/logs/
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.ssl=false
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.authenticate=false
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.local.conf.dir=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/conf/
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.endorsed.dirs=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/endorsed
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.base=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.home=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
[INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.io.tmpdir=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/temp
[INFO ] [o.a.c.http11.Http11NioProtocol 425] - Initializing ProtocolHandler ["http-nio-8080"]
[INFO ] [o.a.t.util.net.NioSelectorPool 72] - Using a shared selector for servlet write/read
[INFO ] [o.a.catalina.startup.Catalina 591] - Initialization processed in 261 ms
[INFO ] [c.m.JmxRemoteLifecycleListener 332] - The JMX Remote Listener has configured the registry on port 32001 and the server on port 32101 for the Platform server
[INFO ] [o.a.c.core.StandardService 435] - Starting service Catalina
[INFO ] [o.a.c.core.StandardEngine 259] - Starting Servlet Engine: Apache Tomcat/8.0.32
[INFO ] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/dashboard.war
[INFO ] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/dashboard.war has finished in 183 ms
[INFO ] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ide.war
[WARN ] [p.DockerExtConfBindingProvider 51] - DockerExtConfBindingProvider
[INFO ] [.c.p.d.c.DockerRegistryChecker 43] - Probing registry 'http://localhost:5000'
[WARN ] [.c.p.d.c.DockerRegistryChecker 50] - Docker registry http://localhost:5000 is not available, which means that you won't be able to save snapshots of your workspaces.
https://docs.docker.com/registry/
set up 'docker.registry.auth.*' properties
[INFO ] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ide.war has finished in 2,974 ms
[INFO ] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/swagger.war
[INFO ] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/swagger.war has finished in 31 ms
[INFO ] [o.a.c.startup.HostConfig 1030] - Deploying web application directory /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ROOT
[INFO ] [o.a.c.startup.HostConfig 1142] - Deployment of web application directory /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ROOT has finished in 34 ms
[INFO ] [o.a.c.http11.Http11NioProtocol 470] - Starting ProtocolHandler ["http-nio-8080"]
[INFO ] [o.a.catalina.startup.Catalina 642] - Server startup in 3326 ms
[INFO ] [o.e.c.a.m.s.MachineManager 162] - Creating machine [ws = workspace5939m6h0iv9vur2i: env = default: machine = ws-machine]
[INFO ] [c.p.d.m.DockerInstanceProvider 447] - Machine with id 'machinexz38jamxwfgi7rvx' backed by container '407ac44df61fc702dd4d31e54d84a2157cc4146887ea2d7fab2ef8b1fe1fec6b' has been deployed on node 'localhost'
[INFO ] [o.e.c.a.m.s.MachineManager 171] - Machine [ws = workspace5939m6h0iv9vur2i: env = default: machine = ws-machine] was successfully created, its id is 'machinexz38jamxwfgi7rvx'
[INFO ] [o.e.c.a.w.s.WorkspaceManager 523] - Workspace 'che:default' with id 'workspace5939m6h0iv9vur2i' started by user 'che'

The browser send the following message:

window.IDE.eventHandlers.initializationFailed@http://192.168.0.189:8080/ide/default?uid=610695:39:27
nbb@_app-0.js:1763:21
xbb@_app-0.js:1767:383
_.pn@_app-0.js:4220:412
lT/<@_app-0.js:1305:209

ghost · 2016-06-14T04:41:41Z

@stoneqsl what host or IP do you use to access Che?

Also, what happens when you start a workspace? Can you share a screenshot?

According to server logs, the server has been able to reach a workspace agent. So, now I am interested in workspace agent logs or anything you can share that is related to workspace start.

stoneqsl · 2016-06-14T04:49:16Z

@eivantsov I use the DHCP IP address 192.168.0.189. But I do not set IP to access Che.

ghost · 2016-06-14T04:51:53Z

@stoneqsl why not localhost if you run it locally?

Also, can you share ws-agent log or a screenshot of what happens when you run a workspace?

stoneqsl · 2016-06-14T05:09:12Z

@eivantsov I don't know how to localhost. I just run it with this:

[root@localhost bin]# sh ./che.sh -s:uid

############## HOW TO CONNECT YOUR CHE CLIENT ###############
After Che server has booted, you can connect your clients by:

Open browser to http://localhost:8080, or:
Open native chromium app.
#############################################################

Using CATALINA_BASE: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
Using CATALINA_HOME: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
Using CATALINA_TMPDIR: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/temp
Using JRE_HOME: /etc/jvm/jdk1.8.91
Using CLASSPATH: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/conf/:/etc/jvm/jdk1.8.91/lib/tools.jar:/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/bin/bootstrap.jar:/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/bin/tomcat-juli.jar
2016-06-14 13:01:16,360[main] [INFO ] [o.a.c.s.VersionLoggerListener 89] - Server version: Apache Tomcat/8.0.32
2016-06-14 13:01:16,361[main] [INFO ] [o.a.c.s.VersionLoggerListener 91] - Server built: Feb 2 2016 19:34:53 UTC
2016-06-14 13:01:16,361[main] [INFO ] [o.a.c.s.VersionLoggerListener 93] - Server number: 8.0.32.0
2016-06-14 13:01:16,361[main] [INFO ] [o.a.c.s.VersionLoggerListener 95] - OS Name: Linux
2016-06-14 13:01:16,362[main] [INFO ] [o.a.c.s.VersionLoggerListener 97] - OS Version: 3.10.0-327.el7.x86_64
2016-06-14 13:01:16,362[main] [INFO ] [o.a.c.s.VersionLoggerListener 99] - Architecture: amd64
2016-06-14 13:01:16,362[main] [INFO ] [o.a.c.s.VersionLoggerListener 101] - Java Home: /etc/jvm/jdk1.8.91/jre
2016-06-14 13:01:16,362[main] [INFO ] [o.a.c.s.VersionLoggerListener 103] - JVM Version: 1.8.0_91-b14
2016-06-14 13:01:16,362[main] [INFO ] [o.a.c.s.VersionLoggerListener 105] - JVM Vendor: Oracle Corporation
2016-06-14 13:01:16,362[main] [INFO ] [o.a.c.s.VersionLoggerListener 107] - CATALINA_BASE: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
2016-06-14 13:01:16,362[main] [INFO ] [o.a.c.s.VersionLoggerListener 109] - CATALINA_HOME: /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
2016-06-14 13:01:16,363[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.config.file=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/conf/logging.properties
2016-06-14 13:01:16,363[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
2016-06-14 13:01:16,363[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xms256m
2016-06-14 13:01:16,363[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xmx1024m
2016-06-14 13:01:16,363[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.security.egd=file:/dev/./urandom
2016-06-14 13:01:16,363[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dport.http=8080
2016-06-14 13:01:16,364[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.home=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0
2016-06-14 13:01:16,364[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.logs.dir=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/logs/
2016-06-14 13:01:16,364[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote
2016-06-14 13:01:16,364[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.ssl=false
2016-06-14 13:01:16,364[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.authenticate=false
2016-06-14 13:01:16,364[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.local.conf.dir=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/conf/
2016-06-14 13:01:16,364[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.endorsed.dirs=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/endorsed
2016-06-14 13:01:16,364[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.base=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
2016-06-14 13:01:16,365[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.home=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat
2016-06-14 13:01:16,365[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.io.tmpdir=/home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/temp
2016-06-14 13:01:16,452[main] [INFO ] [o.a.c.http11.Http11NioProtocol 425] - Initializing ProtocolHandler ["http-nio-8080"]
2016-06-14 13:01:16,459[main] [INFO ] [o.a.t.util.net.NioSelectorPool 72] - Using a shared selector for servlet write/read
2016-06-14 13:01:16,460[main] [INFO ] [o.a.catalina.startup.Catalina 591] - Initialization processed in 262 ms
2016-06-14 13:01:16,509[main] [INFO ] [c.m.JmxRemoteLifecycleListener 332] - The JMX Remote Listener has configured the registry on port 32001 and the server on port 32101 for the Platform server
2016-06-14 13:01:16,509[main] [INFO ] [o.a.c.core.StandardService 435] - Starting service Catalina
2016-06-14 13:01:16,509[main] [INFO ] [o.a.c.core.StandardEngine 259] - Starting Servlet Engine: Apache Tomcat/8.0.32
2016-06-14 13:01:16,546[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/dashboard.war
2016-06-14 13:01:16,726[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/dashboard.war has finished in 180 ms
2016-06-14 13:01:16,728[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ide.war
2016-06-14 13:01:18,765[ost-startStop-1] [WARN ] [p.DockerExtConfBindingProvider 51] - DockerExtConfBindingProvider
2016-06-14 13:01:19,535[ost-startStop-1] [INFO ] [.c.p.d.c.DockerRegistryChecker 43] - Probing registry 'http://localhost:5000'
2016-06-14 13:01:19,543[ost-startStop-1] [WARN ] [.c.p.d.c.DockerRegistryChecker 50] - Docker registry http://localhost:5000 is not available, which means that you won't be able to save snapshots of your workspaces.
How to configure registry?
Local registry -> https://docs.docker.com/registry/
Remote registry -> set up 'docker.registry.auth.*' properties
2016-06-14 13:01:19,701[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ide.war has finished in 2,973 ms
2016-06-14 13:01:19,701[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 910] - Deploying web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/swagger.war
2016-06-14 13:01:19,728[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 974] - Deployment of web application archive /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/swagger.war has finished in 27 ms
2016-06-14 13:01:19,729[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 1030] - Deploying web application directory /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ROOT
2016-06-14 13:01:19,761[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 1142] - Deployment of web application directory /home/stone/下载/eclipse-che-latest/eclipse-che-4.2.0/tomcat/webapps/ROOT has finished in 32 ms
2016-06-14 13:01:19,763[main] [INFO ] [o.a.c.http11.Http11NioProtocol 470] - Starting ProtocolHandler ["http-nio-8080"]
2016-06-14 13:01:19,771[main] [INFO ] [o.a.catalina.startup.Catalina 642] - Server startup in 3309 ms
2016-06-14 13:01:31,859[nio-8080-exec-9] [INFO ] [o.e.c.a.w.s.WorkspaceManager 314] - Workspace 'workspace5939m6h0iv9vur2i' removed by user 'che'
2016-06-14 13:01:37,463[nio-8080-exec-4] [INFO ] [o.e.c.a.w.s.WorkspaceManager 675] - Workspace 'che:default' with id 'workspaces05cn8g4710k9unc' created by user 'che'
2016-06-14 13:01:40,498[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 162] - Creating machine [ws = workspaces05cn8g4710k9unc: env = default: machine = ws-machine]
2016-06-14 13:01:47,278[kspaceManager-0] [INFO ] [c.p.d.m.DockerInstanceProvider 447] - Machine with id 'machinetc1czoafpkw740to' backed by container '5856128e3cb01514f5cd4340196a0c79ab4ea20d83d00c26316f97a05104bd0e' has been deployed on node 'localhost'
2016-06-14 13:01:56,183[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 171] - Machine [ws = workspaces05cn8g4710k9unc: env = default: machine = ws-machine] was successfully created, its id is 'machinetc1czoafpkw740to'
2016-06-14 13:01:56,199[kspaceManager-0] [INFO ] [o.e.c.a.w.s.WorkspaceManager 523] - Workspace 'che:default' with id 'workspaces05cn8g4710k9unc' started by user 'che'

And show this message:

window.IDE.eventHandlers.initializationFailed@http://192.168.0.140:8080/ide/che/secondjava?uid=584758:39:27
ssb@_app-0.js:1975:143
Fsb@_app-0.js:1980:454
_.ep@_app-0.js:4243:317
HM/<@_app-0.js:940:128

If I click Ok,I can go into the page .But It show me the message loading Starting workspace agent.

My English is not good.Sorry for that.I hope U can help me fix it.

ghost · 2016-06-14T05:23:27Z

@stoneqsl What IP or hostname do you type when you access Che? Do you run it locally?On your machine?

Can you share a screenshot of what happens after you start a workspace? Your workspace has started successfully, according to server logs.

What is 192.168.0.140 IP? Is this the IP you use to access Che?

stoneqsl · 2016-06-14T05:59:25Z

@eivantsov show this message:

window.IDE.eventHandlers.initializationFailed@http://192.168.0.189:8080/ide/che/secondjava?uid=584758:39:27
ssb@_app-0.js:1975:143
Fsb@_app-0.js:1980:454
_.ep@_app-0.js:4243:317
HM/<@_app-0.js:940:128

If I click Ok,I can go into the page .But It show me the message loading Starting workspace agent.

ghost · 2016-06-14T06:02:33Z

Are you running Che on localhost or not?

stoneqsl · 2016-06-14T06:07:37Z

@eivantsov Just run on localhost.

stoneqsl · 2016-06-14T09:16:33Z

stoneqsl · 2016-06-14T09:21:06Z

can I have your email address please? it would be more convenient .

ghost · 2016-06-14T09:23:43Z

Can you try it in Chrome, Network tab?

stoneqsl · 2016-06-14T09:36:53Z

ghost · 2016-06-14T09:40:33Z

It should be localhost, not the IP. Did you use -r param this time? Do you have DOCKER_HOST env exported in the system?

ghost · 2016-06-14T09:45:58Z

Give it a shot with https://install.codenvycorp.com/che/eclipse-che-nightly.tar.gz

stoneqsl · 2016-06-14T09:46:01Z

Yes, I use this.
sh ./che.sh -s:uid -r:192.168.0.189
I don't have DOCKER_HOST env .How to do?

ghost · 2016-06-14T09:46:23Z

Do not use -r if you access Che on localhost. It's not necessary in this case.

stoneqsl · 2016-06-14T09:51:30Z

OK.

stoneqsl · 2016-06-14T09:53:55Z

I didn't use -r. The version of che is 4.2.0

stoneqsl · 2016-06-14T09:59:30Z

@eivantsov I run nightly che.

2016-06-14 17:56:33,849[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 159] - Creating machine [ws = workspace9mrmu2wkrkeyufd7: env = che: machine = ws-machine]
2016-06-14 17:56:33,855[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 549] - Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:395) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:334) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:163) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:582) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:458) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:216) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:533) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.util.RecipeDownloader.getRecipe(RecipeDownloader.java:80) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.util.RecipeRetriever.getRecipe(RecipeRetriever.java:52) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.createInstance(DockerInstanceProvider.java:290) ~[che-plugin-docker-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:358) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
... 10 common frames omitted
2016-06-14 17:57:05,944[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 159] - Creating machine [ws = workspace9mrmu2wkrkeyufd7: env = che: machine = ws-machine]
2016-06-14 17:57:05,946[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 549] - Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:395) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:334) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:163) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:582) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:458) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:216) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:533) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.util.RecipeDownloader.getRecipe(RecipeDownloader.java:80) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.util.RecipeRetriever.getRecipe(RecipeRetriever.java:52) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.createInstance(DockerInstanceProvider.java:290) ~[che-plugin-docker-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:358) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
... 10 common frames omitted
2016-06-14 17:57:09,829[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 159] - Creating machine [ws = workspace9mrmu2wkrkeyufd7: env = che: machine = ws-machine]
2016-06-14 17:57:09,831[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 549] - Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:395) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:334) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:163) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:582) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:458) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:216) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:533) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.util.RecipeDownloader.getRecipe(RecipeDownloader.java:80) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.util.RecipeRetriever.getRecipe(RecipeRetriever.java:52) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.createInstance(DockerInstanceProvider.java:290) ~[che-plugin-docker-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:358) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
... 10 common frames omitted
2016-06-14 17:57:31,735[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 159] - Creating machine [ws = workspace9mrmu2wkrkeyufd7: env = che: machine = ws-machine]
2016-06-14 17:57:31,743[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 549] - Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:395) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:334) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:163) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:582) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:458) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:216) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:533) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.util.RecipeDownloader.getRecipe(RecipeDownloader.java:80) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.util.RecipeRetriever.getRecipe(RecipeRetriever.java:52) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.createInstance(DockerInstanceProvider.java:290) ~[che-plugin-docker-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:358) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
... 10 common frames omitted
2016-06-14 17:57:48,734[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 159] - Creating machine [ws = workspace9mrmu2wkrkeyufd7: env = che: machine = ws-machine]
2016-06-14 17:57:48,738[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 549] - Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:395) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:334) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:163) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:582) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:458) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:216) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:533) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.util.RecipeDownloader.getRecipe(RecipeDownloader.java:80) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.util.RecipeRetriever.getRecipe(RecipeRetriever.java:52) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.createInstance(DockerInstanceProvider.java:290) ~[che-plugin-docker-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:358) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
... 10 common frames omitted
2016-06-14 17:57:57,771[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 159] - Creating machine [ws = workspace9mrmu2wkrkeyufd7: env = che: machine = ws-machine]
2016-06-14 17:57:57,773[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 549] - Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:395) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:334) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:163) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:582) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:458) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:216) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:533) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.util.RecipeDownloader.getRecipe(RecipeDownloader.java:80) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.util.RecipeRetriever.getRecipe(RecipeRetriever.java:52) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.createInstance(DockerInstanceProvider.java:290) ~[che-plugin-docker-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:358) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
... 10 common frames omitted
2016-06-14 17:58:03,543[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 159] - Creating machine [ws = workspace9mrmu2wkrkeyufd7: env = che: machine = ws-machine]
2016-06-14 17:58:03,544[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 549] - Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:395) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:334) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:163) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:582) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:458) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:216) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:533) ~[che-core-api-workspace-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute
at org.eclipse.che.api.machine.server.util.RecipeDownloader.getRecipe(RecipeDownloader.java:80) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.util.RecipeRetriever.getRecipe(RecipeRetriever.java:52) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.createInstance(DockerInstanceProvider.java:290) ~[che-plugin-docker-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:358) ~[che-core-api-machine-4.3.0-RC2-SNAPSHOT.jar:4.3.0-RC2-SNAPSHOT]
... 10 common frames omitted

ghost · 2016-06-14T12:07:57Z

@stoneqsl do you start an existing workspace or a new one?

I cannot reproduce any of the errors. The websocket error is likely to be caused by some network config.

No idea at the moment on what have have caused URI error. It's the first time this one is reported.

stoneqsl · 2016-06-14T14:00:27Z

@eivantsov Thanks for your response.If I use the version of nightly che ,this error is coming.I don't know how to fix it.So I use che 14.2.0.But there is a error. Can't connected to terminal. I think that there is something wrong with the Port.Can U know how to deal with my port.

 If you can, can you tell me the tutorial environment and need to configure the action.

 I want to deploy Centos7 Che, as server-side. Others my Che can be accessed network services. Such intentions can achieve this? Don't know if you ever deployed, and if so, I would like to ask how to implement. Thank you so much for your help, it is very important to me.

ghost · 2016-06-14T19:23:54Z

@stoneqsl I've run out of suggestions that may help. You may contact me at support@codenvy.com and we'll organize a screenshare/teamviewer session.

stoneqsl · 2016-06-15T01:15:11Z

Thanks for your help.I want you organize a teamviewer session.But I don't know how to operate. I‘m trying to install teamviewer .what do U need? I will tell u. @eivantsov

stoneqsl · 2016-06-15T01:56:27Z

teamviewer ID 499 087 676 Password i4t88w @eivantsov

ghost · 2016-06-16T05:41:15Z

@stoneqsl let's track another issue you have created - #1507

@ukman Any update on progress you have made?

stoneqsl · 2016-06-16T06:27:46Z

@eivantsov It's the same problem.Can you organize a screenshare/teamviewer session?

ghost · 2016-06-16T06:42:26Z

@stoneqsl I mean let's use #1507 not this issue

ddementieva · 2016-06-16T10:02:00Z

@stoneqsl Concerning Can't start machine ws-machine because machine recipe downloading failed. Recipe url . Error: URI is not absolute error, have you tried to open Che in an incognito mode or just clear cache?

stoneqsl · 2016-06-17T00:44:42Z

@ddementieva I found that the REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable from the iptable COULD be troublesome. Please help me fix it.

ghost · 2016-06-17T10:28:06Z

@stoneqsl please follow this issue #1507

This original issue isn't the same problem that you face

TylerJewell · 2016-07-11T05:19:27Z

Closing this issue - so that it can be tracked in #1507.

imveejay · 2017-05-30T08:59:41Z

How did you start Che? If it is started in a VM you need to use -r:$IP flag where $IP is IP of your VM

@eivantsov hi, how to add the public IP when running a docker container on a VM in Docker version 17.03 and Eclipse Che 5.10?

ghost · 2017-05-30T11:37:52Z

@imveejay can you elaborate? I do not quite understand the question.

imveejay · 2017-05-31T02:05:39Z

@eivantsov you mentioned on your previous post, to start Eclipse Che in a VM environment, it is needed to use '-r:$IP' flag. Wherein $IP is the public IP of the VM. My question is how use that flag in Eclipse Che 5.10 onwards?

ghost · 2017-05-31T09:07:54Z

Use -e CHE_HOST=$IP

ghost closed this as completed May 12, 2016

ghost reopened this May 16, 2016

ghost added the kind/question Questions that haven't been identified as being feature requests or bugs. label May 17, 2016

TylerJewell closed this as completed Jul 11, 2016

imveejay mentioned this issue May 31, 2017

How To Start Eclipse Che 5.10 or onwards in a VM Environment #5244

Closed

bucs-fan813 mentioned this issue Feb 2, 2018

Che server is unable to ping your workspace, RHEL7, Browser => Workspace Agent (localhost): Connection failed #8595

Closed

Cannot start workspace #1226

Cannot start workspace #1226

Comments

ukman commented May 11, 2016

ghost commented May 11, 2016

ukman commented May 11, 2016 • edited Loading

ghost commented May 12, 2016

ukman commented May 12, 2016

ukman commented May 16, 2016

ghost commented May 16, 2016

ukman commented May 16, 2016

ghost commented May 16, 2016

ukman commented May 16, 2016

ghost commented May 16, 2016 • edited by ghost Loading

ghost commented May 31, 2016

ukman commented May 31, 2016

stoneqsl commented Jun 14, 2016

ghost commented Jun 14, 2016

stoneqsl commented Jun 14, 2016

ghost commented Jun 14, 2016

stoneqsl commented Jun 14, 2016

ghost commented Jun 14, 2016

stoneqsl commented Jun 14, 2016

ghost commented Jun 14, 2016 • edited by ghost Loading

stoneqsl commented Jun 14, 2016 • edited Loading

ghost commented Jun 14, 2016

stoneqsl commented Jun 14, 2016 • edited Loading

ghost commented Jun 14, 2016

stoneqsl commented Jun 14, 2016

ghost commented Jun 14, 2016

stoneqsl commented Jun 14, 2016 • edited Loading

stoneqsl commented Jun 14, 2016

stoneqsl commented Jun 14, 2016

ghost commented Jun 14, 2016

stoneqsl commented Jun 14, 2016

ghost commented Jun 14, 2016

ghost commented Jun 14, 2016

stoneqsl commented Jun 14, 2016

ghost commented Jun 14, 2016

stoneqsl commented Jun 14, 2016

stoneqsl commented Jun 14, 2016

stoneqsl commented Jun 14, 2016 • edited Loading

ghost commented Jun 14, 2016

stoneqsl commented Jun 14, 2016 • edited Loading

ghost commented Jun 14, 2016

stoneqsl commented Jun 15, 2016

stoneqsl commented Jun 15, 2016

ghost commented Jun 16, 2016

stoneqsl commented Jun 16, 2016

ghost commented Jun 16, 2016

ddementieva commented Jun 16, 2016

stoneqsl commented Jun 17, 2016

ghost commented Jun 17, 2016 • edited by ghost Loading

TylerJewell commented Jul 11, 2016

imveejay commented May 30, 2017 • edited Loading

ghost commented May 30, 2017

imveejay commented May 31, 2017

ghost commented May 31, 2017 • edited by ghost Loading

ukman commented May 11, 2016 •

edited

Loading

ghost commented May 16, 2016 •

edited by ghost

Loading

ghost commented Jun 14, 2016 •

edited by ghost

Loading

stoneqsl commented Jun 14, 2016 •

edited

Loading

stoneqsl commented Jun 14, 2016 •

edited

Loading

stoneqsl commented Jun 14, 2016 •

edited

Loading

stoneqsl commented Jun 14, 2016 •

edited

Loading

stoneqsl commented Jun 14, 2016 •

edited

Loading

ghost commented Jun 17, 2016 •

edited by ghost

Loading

imveejay commented May 30, 2017 •

edited

Loading

ghost commented May 31, 2017 •

edited by ghost

Loading