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

Unable to Create Workspace #253

Closed
ghost opened this issue Feb 2, 2016 · 16 comments
Closed

Unable to Create Workspace #253

ghost opened this issue Feb 2, 2016 · 16 comments
Labels
kind/question Questions that haven't been identified as being feature requests or bugs.

Comments

@ghost
Copy link

ghost commented Feb 2, 2016

capture

I am using Windows 10, 64 bit. This is the nightly build on 2/1/2016. It says that the workspace does not respond, so I cannot create any projects at all.

Thanks

@ghost
Copy link
Author

ghost commented Feb 2, 2016

How did you start Che and create the project?

Can you provide ws-agent logs? You should have seen them when starting a workspace.

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

ghost commented Feb 3, 2016

@eivantsov I started che by running che.bat. I opened the ide by using a browser and going to localhost:8080. I created the workspace by doing new workspace. Here are the logs in a zip file (from the tomcat/logs). The ws-agent folder is zipped, so the logs folder is empty. Do I need to unzip the folder?

logs.zip

@jcao219
Copy link

jcao219 commented Feb 3, 2016

I have the same issue on Windows 10.

I would like to ssh into the thing, so that I can provide ws-agent logs, but I don't know the port.

--edit: Managed to ssh into it.

----edit: Problem resolved itself after restarting host machine.

@ghost
Copy link
Author

ghost commented Feb 3, 2016

The problem was fixed for you by restarting the machine? I tried restarting, but I still have the same problem.

@ghost
Copy link
Author

ghost commented Feb 3, 2016

Please see this comment: #264 (comment)

@ghost
Copy link
Author

ghost commented Feb 3, 2016

@eivantsov I just grabbed the latest nightly, and made sure I have java 1.8.0.71. I also tried deleting the VM in Virtualbox, following that comment, and rerunning che.bat. This still produces the same error.

@TylerJewell
Copy link

@shivengupta If you are up for a live debugging session, I am available for the next 60 minutes and happy to do a google hangout.

@ghost
Copy link
Author

ghost commented Feb 4, 2016

@TylerJewell Ok sure.

@TylerJewell
Copy link

Yes - please post email and I'll send an invite.

@ghost
Copy link
Author

ghost commented Feb 4, 2016

shiven.gupta@gmail.com

@ghost
Copy link
Author

ghost commented Feb 4, 2016

I cannot do a video call right now. This laptop doesn't have a video camera.

@TylerJewell
Copy link

@eivantsov: I did a 30 minute diagnostic. Here are the results. Che is working as specified. But the issue is that on @shivengupta's Windows 10 computer, Virtual Box is running very slowly. It took nearly 4 minutes to create the default VM. And when Che would start, it would take 35 seconds for Tomcat to activate. When the agent was being activated, the IDE.war was taking nearly a minute to deploy and then the timeout error.

Fix: We should make the ws-agent timeout configurable in che.properties. This would solve this problem.

@ghost
Copy link
Author

ghost commented Feb 4, 2016

@eivantsov @TylerJewell After you told me the problem was with VirtualBox, I did a quick Google Search, and found this . I just changed power mode from HP Recommended to High Performance, and VirtualBox sped up. Now Che opens quickly, and opens the workspace!

@ghost ghost closed this as completed Feb 4, 2016
@TylerJewell
Copy link

💯

@ghost
Copy link
Author

ghost commented Feb 4, 2016

For future readers-

After you change your power plan to High Performance, you either need to only run Che when plugged into the charger, or go edit High Performance and change the min CPU level to 80%-90%,

@ghost
Copy link
Author

ghost commented Feb 4, 2016

Tried to reproduce it on my HP laptop but it's probably too powerful to be CPU greedy in a power saving mode, although default machine and workspace agent start was considerably slower. For instance, deployment of ide.war for ws-agent was completed in 9 seconds, vs 40 seconds in a power saving mode.

This issue was closed.
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.
Projects
None yet
Development

No branches or pull requests

3 participants