Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error creating a project in eclipse che on desktop #261

Closed
tikaa opened this issue Feb 3, 2016 · 17 comments
Closed

Error creating a project in eclipse che on desktop #261

tikaa opened this issue Feb 3, 2016 · 17 comments
Labels
kind/question Questions that haven't been identified as being feature requests or bugs. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

Comments

@tikaa
Copy link

tikaa commented Feb 3, 2016

I have Eclipse Che running on my desktop and when I try to create a project in it I get the exception [1].

Any idea how to solve this?

[1] Creating machine [ws = workspacec3uqzvrq98trmwr5: env = wksp-vo1e: machine = ws-machine]
Exception in thread "WorkspaceManager-0" java.lang.RuntimeException: java.lang.IllegalArgumentException: protocol = http host = null
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1455)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2979)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:489)
at org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.doRequest(DefaultHttpJsonRequest.java:225)
at org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.request(DefaultHttpJsonRequest.java:136)
at org.eclipse.che.api.machine.server.WsAgentLauncherImpl.pingWsAgent(WsAgentLauncherImpl.java:122)
at org.eclipse.che.api.machine.server.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
at com.sun.proxy.$Proxy52.startWsAgent(Unknown Source)
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:370)
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:337)
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:168)
at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.createMachine(RuntimeWorkspaceRegistry.java:451)
at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.startEnvironment(RuntimeWorkspaceRegistry.java:319)
at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.start(RuntimeWorkspaceRegistry.java:145)
at org.eclipse.che.api.workspace.server.WorkspaceManager.performSyncStart(WorkspaceManager.java:642)
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$9(WorkspaceManager.java:613)
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: protocol = http host = null
at sun.net.spi.DefaultProxySelector.select(DefaultProxySelector.java:176)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1099)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1513)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
... 22 more

@TylerJewell
Copy link

@garagatyi --- Please offer some ideas.

@garagatyi
Copy link

@tikaa Please change logging level to debug (/tomcat/conf/logback.xml) and restart che. Then provide output (/tomcat/logs/2016/...catalina-....log). It should be the most recent log file.

@ddementieva ddementieva added the kind/question Questions that haven't been identified as being feature requests or bugs. label Feb 3, 2016
@raviv
Copy link

raviv commented Feb 4, 2016

Hi @garagatyi
got the same error. changing log level to debug , didn't provide more info about this.
It fails when running workspace on

2016-02-04 22:23:53,959[kspaceManager-0]  [ERROR] [o.e.c.a.w.s.WorkspaceManager 615]    - Can't start machine ws-machine. protocol = http host = null
org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine ws-machine. protocol = http host = null
    at org.eclipse.che.api.machine.server.MachineManager.getRecipeByLocation(MachineManager.java:989) ~[che-core-api-machine-4.0.0-RC1-SNAPSHOT.jar:4.0.0-RC1-SNAPSHOT]
    at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:293) ~[che-core-api-machine-4.0.0-RC1-SNAPSHOT.jar:4.0.0-RC1-SNAPSHOT]
    at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:168) ~[che-core-api-machine-4.0.0-RC1-SNAPSHOT.jar:4.0.0-RC1-SNAPSHOT]
    at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.createMachine(RuntimeWorkspaceRegistry.java:454) ~[che-core-api-workspace-4.0.0-RC1-SNAPSHOT.jar:4.0.0-RC1-SNAPSHOT]
    at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.startEnvironment(RuntimeWorkspaceRegistry.java:320) ~[che-core-api-workspace-4.0.0-RC1-SNAPSHOT.jar:4.0.0-RC1-SNAPSHOT]
    at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.start(RuntimeWorkspaceRegistry.java:146) ~[che-core-api-workspace-4.0.0-RC1-SNAPSHOT.jar:4.0.0-RC1-SNAPSHOT]
    at org.eclipse.che.api.workspace.server.WorkspaceManager.performSyncStart(WorkspaceManager.java:642) ~[che-core-api-workspace-4.0.0-RC1-SNAPSHOT.jar:4.0.0-RC1-SNAPSHOT]
    at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$1(WorkspaceManager.java:613) ~[che-core-api-workspace-4.0.0-RC1-SNAPSHOT.jar:4.0.0-RC1-SNAPSHOT]
    at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.0.0-RC1-SNAPSHOT.jar:4.0.0-RC1-SNAPSHOT]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_66]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_66]
    at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_66]

In case it matters, I'm running it on port 8081

Thanks.

@garagatyi
Copy link

@raviv Please provide the whole log. Debug information I'm looking for is not in those lines you've provided

@tikaa
Copy link
Author

tikaa commented Feb 9, 2016

Hello Alexander,

I tried the following methods to start eclipse Che in the DEBUG mode,

./che.sh --debug run
./che.sh -d run

Also changing the tomcat/conf logback.xml as attached herewith,

But i could not observe any log flies in the tomcat/logs folder. that
folder remains empty. You can find the full terminal logs [1].

[1] GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
5050 pts/24 S+ 0:00 /bin/bash ./che.sh run
5053 pts/24 S+ 0:00 grep che.sh
/home/awanthika/WSO2/Eclipse-Che/eclipse-che-4.0.0-beta-13
Docker is natively installed and reachable...

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

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

Starting Che server in docker container named che.
Found a container named che. Attempting restart.
Successful restart of Che container.

Docker container named che successfully started.
Launching Che app server inside the container named che.
Docker is natively installed and reachable...
2016-02-09 03:28:54,241[main] [INFO ]
[o.a.c.s.VersionLoggerListener 89] - Server version: Apache
Tomcat/8.0.28
2016-02-09 03:28:54,243[main] [INFO ]
[o.a.c.s.VersionLoggerListener 91] - Server built: Oct 7 2015
18:25:21 UTC
2016-02-09 03:28:54,243[main] [INFO ]
[o.a.c.s.VersionLoggerListener 93] - Server number: 8.0.28.0
2016-02-09 03:28:54,243[main] [INFO ]
[o.a.c.s.VersionLoggerListener 95] - OS Name: Linux
2016-02-09 03:28:54,247[main] [INFO ]
[o.a.c.s.VersionLoggerListener 97] - OS Version:
3.13.0-77-generic
2016-02-09 03:28:54,248[main] [INFO ]
[o.a.c.s.VersionLoggerListener 99] - Architecture: amd64
2016-02-09 03:28:54,248[main] [INFO ]
[o.a.c.s.VersionLoggerListener 101] - Java Home:
/opt/jre1.8.0_65
2016-02-09 03:28:54,248[main] [INFO ]
[o.a.c.s.VersionLoggerListener 103] - JVM Version: 1.8.0_65-b17
2016-02-09 03:28:54,248[main] [INFO ]
[o.a.c.s.VersionLoggerListener 105] - JVM Vendor: Oracle
Corporation
2016-02-09 03:28:54,248[main] [INFO ]
[o.a.c.s.VersionLoggerListener 107] - CATALINA_BASE:
/home/user/che/tomcat
2016-02-09 03:28:54,248[main] [INFO ]
[o.a.c.s.VersionLoggerListener 109] - CATALINA_HOME:
/home/user/che/tomcat
2016-02-09 03:28:54,249[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Djava.util.logging.config.file=/home/user/che/tomcat/conf/logging.properties
2016-02-09 03:28:54,249[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
2016-02-09 03:28:54,249[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Dport.http=8080
2016-02-09 03:28:54,249[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Dcom.sun.management.jmxremote
2016-02-09 03:28:54,249[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Dcom.sun.management.jmxremote.ssl=false
2016-02-09 03:28:54,250[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Dcom.sun.management.jmxremote.authenticate=false
2016-02-09 03:28:54,250[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Dche.local.conf.dir=/home/user/.che
2016-02-09 03:28:54,250[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Dche.home=/home/user/che
2016-02-09 03:28:54,250[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Dche.logs.dir=/home/user/che/tomcat/logs/
2016-02-09 03:28:54,250[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Djava.endorsed.dirs=/home/user/che/tomcat/endorsed
2016-02-09 03:28:54,250[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Dcatalina.base=/home/user/che/tomcat
2016-02-09 03:28:54,250[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Dcatalina.home=/home/user/che/tomcat
2016-02-09 03:28:54,250[main] [INFO ]
[o.a.c.s.VersionLoggerListener 115] - Command line argument:
-Djava.io.tmpdir=/home/user/che/tomcat/temp
2016-02-09 03:28:54,333[main] [INFO ]
[o.a.c.http11.Http11NioProtocol 424] - Initializing ProtocolHandler
["http-nio-8080"]
2016-02-09 03:28:54,343[main] [INFO ]
[o.a.t.util.net.NioSelectorPool 72] - Using a shared selector for servlet
write/read
2016-02-09 03:28:54,345[main] [INFO ]
[o.a.catalina.startup.Catalina 587] - Initialization processed in 278 ms
2016-02-09 03:28:54,395[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-02-09 03:28:54,395[main] [INFO ]
[o.a.c.core.StandardService 433] - Starting service Catalina
2016-02-09 03:28:54,395[main] [INFO ]
[o.a.c.core.StandardEngine 259] - Starting Servlet Engine: Apache
Tomcat/8.0.28
2016-02-09 03:28:54,433[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig
916] - Deploying web application archive
/home/user/che/tomcat/webapps/swagger.war
2016-02-09 03:28:54,644[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig
980] - Deployment of web application archive
/home/user/che/tomcat/webapps/swagger.war has finished in 210 ms
2016-02-09 03:28:54,645[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig
916] - Deploying web application archive
/home/user/che/tomcat/webapps/dashboard.war
2016-02-09 03:28:54,699[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig
980] - Deployment of web application archive
/home/user/che/tomcat/webapps/dashboard.war has finished in 54 ms
2016-02-09 03:28:54,701[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig
916] - Deploying web application archive
/home/user/che/tomcat/webapps/ide.war
2016-02-09 03:28:57,386[ost-startStop-1] [WARN ]
[p.DockerExtConfBindingProvider 51] - DockerExtConfBindingProvider
2016-02-09 03:28:58,368[ost-startStop-1] [INFO ]
[.c.p.d.c.DockerRegistryChecker 43] - Probing registry '
http://localhost:5000'
2016-02-09 03:28:58,375[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-02-09 03:28:58,603[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig
980] - Deployment of web application archive
/home/user/che/tomcat/webapps/ide.war has finished in 3,902 ms
2016-02-09 03:28:58,605[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig
1036] - Deploying web application directory
/home/user/che/tomcat/webapps/ROOT
2016-02-09 03:28:58,664[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig
1152] - Deployment of web application directory
/home/user/che/tomcat/webapps/ROOT has finished in 59 ms
2016-02-09 03:28:58,669[main] [INFO ]
[o.a.c.http11.Http11NioProtocol 469] - Starting ProtocolHandler
["http-nio-8080"]
2016-02-09 03:28:58,675[main] [INFO ]
[o.a.catalina.startup.Catalina 638] - Server startup in 4329 ms
2016-02-09 03:30:36,704[nio-8080-exec-7] [INFO ]
[o.e.c.a.w.s.WorkspaceManager 144] - EVENT#workspace-created#
WS#wksp-2zp0# WS-ID#workspace2ftyy8m2gxbnljm5# USER#che#
2016-02-09 03:30:37,747[kspaceManager-0] [INFO ]
[o.e.c.a.m.s.MachineManager 167] - Creating machine [ws =
workspace2ftyy8m2gxbnljm5: env = wksp-2zp0: machine = ws-machine]
Exception in thread "WorkspaceManager-0" java.lang.RuntimeException:
java.lang.IllegalArgumentException: protocol = http host = null
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1455)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at
sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2979)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:489)
at
org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.doRequest(DefaultHttpJsonRequest.java:225)
at
org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.request(DefaultHttpJsonRequest.java:136)
at
org.eclipse.che.api.machine.server.WsAgentLauncherImpl.pingWsAgent(WsAgentLauncherImpl.java:122)
at
org.eclipse.che.api.machine.server.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
at com.sun.proxy.$Proxy52.startWsAgent(Unknown Source)
at
org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:370)
at
org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:337)
at
org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:168)
at
org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.createMachine(RuntimeWorkspaceRegistry.java:451)
at
org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.startEnvironment(RuntimeWorkspaceRegistry.java:319)
at
org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.start(RuntimeWorkspaceRegistry.java:145)
at
org.eclipse.che.api.workspace.server.WorkspaceManager.performSyncStart(WorkspaceManager.java:642)
at
org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$9(WorkspaceManager.java:613)
at
org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: protocol = http host = null
at sun.net.spi.DefaultProxySelector.select(DefaultProxySelector.java:176)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1099)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1513)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
... 22 more

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791

On Fri, Feb 5, 2016 at 1:32 PM, Alexander Garagatyi <
notifications@github.com> wrote:

@raviv https://github.com/raviv Please provide the whole log. Debug
information I'm looking for is not in those lines you've provided


Reply to this email directly or view it on GitHub
#261 (comment).

@thesecondzorg
Copy link

Have anybody know solution to solve this issue ????

@TylerJewell TylerJewell added the status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. label Feb 19, 2016
@TylerJewell
Copy link

@thesecondzorg We need some help in trying to reproduce this issue. Can you provide the system, operating system, docker version, che version and any steps to reproduce?

Thanks.

@ghost
Copy link

ghost commented Feb 19, 2016

The only way I can reproduce this issue is messing up with DOCKER_HOST, for instance exporting DOCKER_MACHINE_HOST as empty string.

Can you try running Che as ./che.sh run -r:172.17.42.1?

@ghost
Copy link

ghost commented Mar 3, 2016

@tikaa Can you please follow instructions in my previous comment?

@Tacsiazuma
Copy link

I've experienced the same issue.

Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux

Docker version 1.8.1, build d12ea79

The log (this one as root, with the -s:uid option, but tried as non-root user too, same output):

root@devel:/opt/eclipse-che-4.0.0-RC11/bin# ./che.sh run --remote:ip=172.17.42.1 -s:uid

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

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

Using CATALINA_BASE: /opt/eclipse-che-4.0.0-RC11/tomcat
Using CATALINA_HOME: /opt/eclipse-che-4.0.0-RC11/tomcat
Using CATALINA_TMPDIR: /opt/eclipse-che-4.0.0-RC11/tomcat/temp
Using JRE_HOME: /opt/jdk1.8.0_65
Using CLASSPATH: /opt/eclipse-che-4.0.0-RC11/tomcat/conf/:/opt/jdk1.8.0_65/lib/tools.jar:/opt/eclipse-che-4.0.0-RC11/tomcat/bin/bootstrap.jar:/opt/eclipse-che-4.0.0-RC11/tomcat/bin/tomcat-juli.jar
2016-03-10 21:10:45,005[main] [INFO ] [o.a.c.s.VersionLoggerListener 89] - Server version: Apache Tomcat/8.0.29
2016-03-10 21:10:45,009[main] [INFO ] [o.a.c.s.VersionLoggerListener 91] - Server built: Nov 20 2015 09:18:00 UTC
2016-03-10 21:10:45,010[main] [INFO ] [o.a.c.s.VersionLoggerListener 93] - Server number: 8.0.29.0
2016-03-10 21:10:45,011[main] [INFO ] [o.a.c.s.VersionLoggerListener 95] - OS Name: Linux
2016-03-10 21:10:45,013[main] [INFO ] [o.a.c.s.VersionLoggerListener 97] - OS Version: 3.16.0-4-amd64
2016-03-10 21:10:45,032[main] [INFO ] [o.a.c.s.VersionLoggerListener 99] - Architecture: amd64
2016-03-10 21:10:45,033[main] [INFO ] [o.a.c.s.VersionLoggerListener 101] - Java Home: /opt/jdk1.8.0_65/jre
2016-03-10 21:10:45,034[main] [INFO ] [o.a.c.s.VersionLoggerListener 103] - JVM Version: 1.8.0_65-b17
2016-03-10 21:10:45,036[main] [INFO ] [o.a.c.s.VersionLoggerListener 105] - JVM Vendor: Oracle Corporation
2016-03-10 21:10:45,037[main] [INFO ] [o.a.c.s.VersionLoggerListener 107] - CATALINA_BASE: /opt/eclipse-che-4.0.0-RC11/tomcat
2016-03-10 21:10:45,038[main] [INFO ] [o.a.c.s.VersionLoggerListener 109] - CATALINA_HOME: /opt/eclipse-che-4.0.0-RC11/tomcat
2016-03-10 21:10:45,039[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.config.file=/opt/eclipse-che-4.0.0-RC11/tomcat/conf/logging.properties
2016-03-10 21:10:45,040[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
2016-03-10 21:10:45,041[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xms256m
2016-03-10 21:10:45,042[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Xmx1024m
2016-03-10 21:10:45,043[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.security.egd=file:/dev/./urandom
2016-03-10 21:10:45,044[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dport.http=8080
2016-03-10 21:10:45,045[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.home=/opt/eclipse-che-4.0.0-RC11
2016-03-10 21:10:45,046[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.logs.dir=/opt/eclipse-che-4.0.0-RC11/tomcat/logs/
2016-03-10 21:10:45,047[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote
2016-03-10 21:10:45,048[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.ssl=false
2016-03-10 21:10:45,049[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcom.sun.management.jmxremote.authenticate=false
2016-03-10 21:10:45,050[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dche.local.conf.dir=/opt/eclipse-che-4.0.0-RC11/conf/
2016-03-10 21:10:45,050[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.endorsed.dirs=/opt/eclipse-che-4.0.0-RC11/tomcat/endorsed
2016-03-10 21:10:45,051[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.base=/opt/eclipse-che-4.0.0-RC11/tomcat
2016-03-10 21:10:45,052[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Dcatalina.home=/opt/eclipse-che-4.0.0-RC11/tomcat
2016-03-10 21:10:45,053[main] [INFO ] [o.a.c.s.VersionLoggerListener 115] - Command line argument: -Djava.io.tmpdir=/opt/eclipse-che-4.0.0-RC11/tomcat/temp
2016-03-10 21:10:45,365[main] [INFO ] [o.a.c.http11.Http11NioProtocol 425] - Initializing ProtocolHandler ["http-nio-8080"]
2016-03-10 21:10:45,404[main] [INFO ] [o.a.t.util.net.NioSelectorPool 72] - Using a shared selector for servlet write/read
2016-03-10 21:10:45,419[main] [INFO ] [o.a.catalina.startup.Catalina 587] - Initialization processed in 1164 ms
2016-03-10 21:10:45,459[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-03-10 21:10:45,553[main] [INFO ] [o.a.c.core.StandardService 433] - Starting service Catalina
2016-03-10 21:10:45,554[main] [INFO ] [o.a.c.core.StandardEngine 259] - Starting Servlet Engine: Apache Tomcat/8.0.29
2016-03-10 21:10:45,742[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 916] - Deploying web application archive /opt/eclipse-che-4.0.0-RC11/tomcat/webapps/swagger.war
2016-03-10 21:10:46,440[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 980] - Deployment of web application archive /opt/eclipse-che-4.0.0-RC11/tomcat/webapps/swagger.war has finished in 697 ms
2016-03-10 21:10:46,444[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 916] - Deploying web application archive /opt/eclipse-che-4.0.0-RC11/tomcat/webapps/ide.war
2016-03-10 21:10:53,652[ost-startStop-1] [WARN ] [p.DockerExtConfBindingProvider 51] - DockerExtConfBindingProvider
2016-03-10 21:10:56,511[ost-startStop-1] [INFO ] [.c.p.d.c.DockerRegistryChecker 43] - Probing registry 'http://localhost:5000'
2016-03-10 21:10:56,536[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-03-10 21:10:57,387[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 980] - Deployment of web application archive /opt/eclipse-che-4.0.0-RC11/tomcat/webapps/ide.war has finished in 10,943 ms
2016-03-10 21:10:57,388[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 916] - Deploying web application archive /opt/eclipse-che-4.0.0-RC11/tomcat/webapps/dashboard.war
2016-03-10 21:10:57,473[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 980] - Deployment of web application archive /opt/eclipse-che-4.0.0-RC11/tomcat/webapps/dashboard.war has finished in 85 ms
2016-03-10 21:10:57,479[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 1036] - Deploying web application directory /opt/eclipse-che-4.0.0-RC11/tomcat/webapps/ROOT
2016-03-10 21:10:57,576[ost-startStop-1] [INFO ] [o.a.c.startup.HostConfig 1152] - Deployment of web application directory /opt/eclipse-che-4.0.0-RC11/tomcat/webapps/ROOT has finished in 95 ms
2016-03-10 21:10:57,591[main] [INFO ] [o.a.c.http11.Http11NioProtocol 470] - Starting ProtocolHandler ["http-nio-8080"]
2016-03-10 21:10:57,620[main] [INFO ] [o.a.catalina.startup.Catalina 638] - Server startup in 12199 ms
2016-03-10 21:12:02,181[nio-8080-exec-5] [INFO ] [o.e.c.a.w.s.WorkspaceManager 140] - EVENT#workspace-created# WS#wksp-cl1d# WS-ID#workspaceuje02yex0y4hzwrg# USER#che#
2016-03-10 21:12:03,292[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 166] - Creating machine [ws = workspaceuje02yex0y4hzwrg: env = wksp-cl1d: machine = ws-machine]
Exception in thread "WorkspaceManager-0" java.lang.RuntimeException: java.lang.IllegalArgumentException: protocol = http host = null
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1455)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2979)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:489)
at org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.doRequest(DefaultHttpJsonRequest.java:239)
at org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.request(DefaultHttpJsonRequest.java:145)
at org.eclipse.che.api.machine.server.WsAgentLauncherImpl.pingWsAgent(WsAgentLauncherImpl.java:125)
at org.eclipse.che.api.machine.server.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:98)
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:366)
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:333)
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:167)
at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.createMachine(RuntimeWorkspaceRegistry.java:421)
at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.startEnvironment(RuntimeWorkspaceRegistry.java:320)
at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.start(RuntimeWorkspaceRegistry.java:146)
at org.eclipse.che.api.workspace.server.WorkspaceManager.performSyncStart(WorkspaceManager.java:637)
at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:608)
at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: protocol = http host = null
at sun.net.spi.DefaultProxySelector.select(DefaultProxySelector.java:176)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1099)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1513)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
... 16 more

Any ideas?

@ghost
Copy link

ghost commented Mar 11, 2016

Do you have CHE_DOCKER_MACHINE_HOST env exported in your system?

env | grep DOCKER

I can reproduce this issue when exporting an empty CHE_DOCKER_MACHINE_HOST. If this variable is there, the server uses it to connect to a workspace container (namely, ws agent).

The default on Linux is localhost, so I suspect the problem may be with some localhost settings.

./che.sh run -r:${eth0_IP} - this should fix it.

@ghost
Copy link

ghost commented Mar 21, 2016

@tikaa @Tacsiazuma can you take a look at this issue - #736

Looks like you have the same problem. Your local networking config may be causing it.

@regismachado
Copy link

Hi @tikaa @Tacsiazuma

I had the same issue in a CentOS7 machine, to solve this issue I did the steps below:

  1. Config your docker enviroment variables (Centos7 steps):

Edit: /usr/lib/systemd/system/docker.service

ExecStart=/usr/bin/docker daemon -H tcp://{DOCKER_HOST_MACHINE}:4243 -H fd:// $OPTIONS

Where {DOCKER_HOST_MACHINE} is the IP of your machine running docker daemon. Ex:

ExecStart=/usr/bin/docker daemon -H tcp://172.10.1.43:4243 -H fd:// $OPTIONS
  1. Config docker host ip in your environment variables:
    Edit: ~/.bashrc
export DOCKER_HOST=tcp://{DOCKER_HOST_MACHINE}:4243

Where {DOCKER_HOST_MACHINE} is the IP of your machine running docker daemon. Ex:

export DOCKER_HOST=tcp://172.10.1.43:4243
  1. Delete all eclipse tche folders and reinstall using eclipse-che-latest.jar

@Tacsiazuma
Copy link

Thank you @eivantsov , that was the problem!

Although the ETH0_IP env variable was empty in my case, so I manually passed the docker host machine's local IP.

./che.sh run -r:{DOCKER_HOST_IP}

@ghost
Copy link

ghost commented Mar 24, 2016

@tikaa can you do the same please and confirm you can run Che?

@tikaa
Copy link
Author

tikaa commented Mar 24, 2016

Hello Eugene,

I am not currently working on the Che task. I am preoccupied with some
other engagements. Will get back to you when I get time.

Thanks for the support! appreciate it.

Regards
Awanthika

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791

On Thu, Mar 24, 2016 at 12:24 PM, Eugene Ivantsov notifications@github.com
wrote:

@tikaa https://github.com/tikaa can you do the same please and confirm
you can run Che?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#261 (comment)

@ddementieva
Copy link
Contributor

Closing the issue. Do not hesitate to reopen if you have more questions or face issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Questions that haven't been identified as being feature requests or bugs. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Development

No branches or pull requests

8 participants