The workspace agent has attempted to start, but it is unable to ping the Che server at http://che-host:8080/ide/api/ #684
Comments
|
Hi @kolotyluk. I believe this is a netowrking configuration issue that you are running into. Any chance that you are running Che on a server that has different networks and IP addresses? It looks like Che is having a hard time resolving certain addresses. You can see more about certain non-standard configurations here. You wrote a great issue by the way. Very clear and provides all the background information. |
This means there's no connection to Docker deamon running insude a VM. However, the workspace has attempted to start anyway. I see There are several ways to debug/fix this:
If this does not help, in /conf/che.properties edit the following property: machine.docker.che_api.endpoint=https://yourVMIP:8080/ide/api Re-run Che. This way, a workspace agent will use your endpoint to connect to Che server |
|
@TylerJewell here is my network configuration. I have VMWare Workstation installed which uses various bridged addresses. Could that be a problem? C:\Users\Eric>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : vc.shawcable.net Ethernet adapter VirtualBox Host-Only Network: Connection-specific DNS Suffix . : Ethernet adapter VirtualBox Host-Only Network #2: Connection-specific DNS Suffix . : Ethernet adapter Ethernet: Connection-specific DNS Suffix . : Ethernet adapter Ethernet 2: Connection-specific DNS Suffix . : Tunnel adapter isatap.{25A57C09-C1AE-4B14-B631-687D1F7857E6}: Media State . . . . . . . . . . . : Media disconnected Tunnel adapter isatap.{4F33A72D-98A9-42C1-8A6E-E82274609F8C}: Media State . . . . . . . . . . . : Media disconnected Tunnel adapter isatap.vc.shawcable.net: Media State . . . . . . . . . . . : Media disconnected Tunnel adapter isatap.{746AA24B-336E-45D4-9C2B-78F9FFB6F95C}: Media State . . . . . . . . . . . : Media disconnected Tunnel adapter isatap.{05237794-0A36-4169-8ED7-ECC7F66EF0A0}: Media State . . . . . . . . . . . : Media disconnected C:\Users\Eric> |
|
@eivantsov I don't really have any docker experience, nor much VirtualBox experience either, Mostly I use VMWare Workstation. I'll try to follow your advice and see how far I get. If worse comes to worse, I can always fire up Ubuntu in VMWare, and run Che in there. |
|
@eivantsov I tried the 3 steps, but that did not help. I have tried changing but that does not help either. From my browser, I can get both 99.1 and 56.1, and they display a "Create Workspace" dialog. Apparently Che does not support /ide/api/ping, or is there some other ping resource? |
|
Sorry, I have misled you with https. It should be http: I am not sure about Did you try removing the VM and host-only network interfaces in VBox? |
|
@eivantsov Do you mean remove all the network interfaces in VBox? This can only be done after the new VM is created, but then they get recreated when I restart the che server. On the console it says "Docker is configured to use docker-vbox machine default with IP 192.168.99.102" I tried that in the che.properties, but same problem. Sadly, I cannot copy paste from the Windows console because che puts out formatting characters that disable the 'mark' function in the console. This is a serious defect that needs to be corrected, otherwise reporting and troubleshooting is significantly more difficult. At this point, troubleshooting this is beyond my ability. I would suggest someone set up a time when we can use Skype or Google Hangouts to share the screen and poke around. It would be nice to get the MS Windows problems sorted out before 4.0.0-RC. |
|
@kolotyluk I am interested in fixing this. I will hangout on a google hangout for the next hour here. If you can join, I'd like to investigate. |
|
[STDOUT] Listening for transport dt_socket at address: 4403 |
|
@garagatyi @eivantsov So in a debugging session we were able to get the system to work. However, the solution was not obvious and this could be an improvement we add to the system.
Perhaps we should cycle through the IP addresses of all adapters? |
TylerJewell
added
kind/question
|
The problem is that 192.168.99.1:8080 returns nothing. On my Win machine, I can either go to localhost:8080 or 192.168.99.1:8080 to access Che. |
|
I am having same issue like @kolotyluk had. What was the configuration updates made in che.properties to work the system? |
|
where ${eth0} is IP of your eth0 network interface |
|
@eivantsov i can share entire stacktrace if that helpful to you. But it is identical to the one shared above. I will give a try what you suggested. |
|
@pavan5000 If you are on windows, please do an ipconfig and get the list of all IP addresses for your adapters. The issue that @kolotyluk had was that the default IP address returned by virtualbox for the newly created VM is not the IP address that your system is using. So you want to update |
|
For some reason the default 192.168.99.1 does not work on some Win systems, especially with multiple network adapters. |
|
Ethernet adapter VirtualBox Host-Only Network: Connection-specific DNS Suffix . : Ethernet adapter VirtualBox Host-Only Network #2: Connection-specific DNS Suffix . : I had two virtual hosts in my PC. After switching Ip address to 192.168.56.1:8080 it started working fine. Thanks for the help. |
|
@pavan5000 Hey - I am really happy to see this working for you. I am going to close the issue. |
Description of problem:
Che version:
Che install directory:
Docker version:
Java version:
Environment details (AWS, VirtualBox, physical, etc.):
How reproducible:
Steps to Reproduce:
Actual Results:
Observations:
The text was updated successfully, but these errors were encountered: