-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Che force closes #239
Comments
We need diagnostic deals. Os, Java configuration, any outputs. The more details you can provide the better. |
Windows 10 |
Is there anything if you do --debug when running? What about trying --image? |
Which Java you are using, Oracle or OpenJDK? |
Can you also copy and share logs for us to find some clues where the script fails? |
@garagatyi I'm using Oracle, and @TylerJewell running the shortcut to start the server. |
@balloman Please run che on the command line, following the Usage instructions in the docs. Go into the directory where Che was installed and use the che scripts to see the output. If you installed Che on windows with a directory that has a space in it, there is a known issue, solved by this pull request which has not been merged yet. #241 |
241 has been merged. |
I believe the pull request #241 solves this issue. Closing. Reopen if issue reappears. |
Well, I got an error that says |
This is a different kind of issue. Can you talk about how you started Che and the os you are on? We may have a pull request to address this issue. |
I used powershell because when i used the docs, git bash gave me a no directory error, and i got no command from cmd. I am on windows 10 |
I have never seen a no directory error from git bash.
|
Ahhh, simple fix. If you want to run Che in bash you have to use bash syntax :) |
I still get the same error |
Are there files in the /bin directory? |
Yes |
Another approach would be to type "bash --login -i <path-to-che.sh>". You need to provide the full path to che.sh. If you still get no such file or directory, I'd need to see your console in a live screen share to understand better. |
Yes, but I don't think this is the problem |
It does this in PowerShell too |
Well, @balloman you'll need to provide very specific steps to try and recreate this issue, or invite one of our engineers into a screen share. You will have to document each step you take. But generally if the shell is saying no file found, then the command line parameter is not being entered properly. |
Ok, I open power shell, I CD to the Che directory, and I run the bin/Che run command, it runs but I get the running docker succeeded but docker ps failed error |
The details are not enough to reproduce. Can you provide the output of the console and /or a screencast of the execution. |
Sorry for the long time to reply @TylerJewell |
Can you try removing your default machine and give it another shot? It looks like Docker deamon isn't running in a VM (you may run I think default machine removal should help. Also, I can see that your laptop is running on battery. Do you have a power-saving mode on when unplugged? Some users have noticed that power-saving mode makes Virtual Box very slow if not unresponsive. You may want to take a look at this issue #253 |
That particular exception means that you have something else running on your system that is already bound to localhost:8080. This link gives some ideas on how to figure out what else is running. |
Well, I used your suggestion, stopped the program, ran the commands again in powershell, and it works! |
Woot! Great job in diagnosing and figuring it out. |
…clipse-che#239) This is important, because now the `openshift-connector-wip` branch, that we still use, might have the same che version number than more recent snapshots available from the upstream che maven repository. Signed-off-by: David Festal <dfestal@redhat.com>
I can't seem to run it, because every time I start the server it loads for around 3 seconds and then closes.
The text was updated successfully, but these errors were encountered: