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

Can't start machine ws-machine because machine recipe downloading failed. #1504

Closed
prathyush-rzt opened this issue Jun 14, 2016 · 5 comments
Closed
Labels
status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

Comments

@prathyush-rzt
Copy link

prathyush-rzt commented Jun 14, 2016

I had setup a python workspace when my local ip was 192.168.48.88, by running:

~/che/assembly/assembly-main/target/eclipse-che-4.3.0-RC2-SNAPSHOT/eclipse-che-4.3.0-RC2-SNAPSHOT/bin/./che.sh --skip:uid  -r:192.168.48.88

Now my local IP address has changed to 192.168.48.35, and when I run, and launch previously created workspace,

~/che/assembly/assembly-main/target/eclipse-che-4.3.0-RC2-SNAPSHOT/eclipse-che-4.3.0-RC2-SNAPSHOT/bin/./che.sh --skip:uid  -r:192.168.48.35

I get an error stating:

[ERROR] Can't start machine ws-machine because machine recipe downloading failed. Recipe url http://192.168.48.88:8080/wsmaster/api/recipe/recipe1mf2o2in6rt85wxg/script. Error: Connection refused

How can I access my previous workspace with my new local IP?

ifconfig:

docker0   Link encap:Ethernet  HWaddr 02:42:f6:25:43:08  
          inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

enp3s0    Link encap:Ethernet  HWaddr 2c:56:dc:00:52:51  
          inet addr:192.168.48.35  Bcast:192.168.49.255  Mask:255.255.254.0
          inet6 addr: fe80::2e56:dcff:fe00:5251/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:220666 errors:0 dropped:0 overruns:0 frame:0
          TX packets:157330 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:308927775 (308.9 MB)  TX bytes:11701531 (11.7 MB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:6539 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6539 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:6368609 (6.3 MB)  TX bytes:6368609 (6.3 MB)
@ghost
Copy link

ghost commented Jun 14, 2016

@prathyush-rzt Workspace recipe is saved to workspace config and there's no user friendly way to update it. Try creating a new workspace, this should fix the issue.

@ghost ghost added the status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. label Jun 14, 2016
@prathyush-rzt
Copy link
Author

prathyush-rzt commented Jun 15, 2016

@eivantsov What will happen to my data and config of my old workspace? Is there any way wherein, I can have a new workspace with data of my old one?

@ghost
Copy link

ghost commented Jun 15, 2016

@prathyush-rzt You may go to workspaces folder and move your project to a new workspaces. This is the simplest solution.

@james10174
Copy link

@prathyush-rzt I had issues with running with --skip:uid option with workspaces and configurations not being saved. If you can try running with user with uid=1000 and remove --skip:uid to see if it helps. I also cd into eclipse-che-4.3.0-RC2-SNAPSHOT folder then run bin/che.sh -r:. Not sure if it makes a difference in che finding the workspace and storage folders.

@prathyush-rzt
Copy link
Author

prathyush-rzt commented Jun 16, 2016

@eivantsov Thnx for solving my problem.

@james10174 I do not administrative privileges for the environment and hence I cannot run without --skip-uid. Running directly from the installation path does not change a thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

2 participants