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

Che does not respond #484

Closed
fnkr opened this issue Feb 23, 2016 · 7 comments
Closed

Che does not respond #484

fnkr opened this issue Feb 23, 2016 · 7 comments

Comments

@fnkr
Copy link

fnkr commented Feb 23, 2016

Eclipse Che is running, and curl can connect to port 8080, but I get no response.

asciicast

Logs: https://gist.github.com/fnkr/beebe07b0332934611f2

@fnkr fnkr changed the title No response Che Che does not respond Feb 23, 2016
@ghost
Copy link

ghost commented Feb 23, 2016

Hello,

What if you go to localhost:8080 in your browser?

@fnkr
Copy link
Author

fnkr commented Feb 23, 2016

Same thing, page keeps loading forever.

@ghost
Copy link

ghost commented Feb 23, 2016

What is your environment? Where are you running Che? According to the logs, ide.war hasn't been deployed.

@fnkr
Copy link
Author

fnkr commented Feb 23, 2016

I'm running Che on a fresh Ubuntu 14.04 instance on Digital Ocean. Here is what I've done:

  1. Installed Oracle Java 8
  2. Set JAVA_HOME
  3. Installed docker
  4. Started docker registry
  5. Created a new user for che (name che id 1000)
  6. Added the che user to the docker group
  7. Logged in as che (su che)
  8. Downloaded/extracted the latest che release from https://www.eclipse.org/che/download/ (RC3)
  9. Started it (bin/che.sh)

@ghost
Copy link

ghost commented Feb 23, 2016

Here's what you can do:

sudo sed -i 's/random/urandom/g' $JAVA_HOME/lib/security/java.security

If the path is not correct, look for the right location of java.security in $JAVA_HOME

Alternatively, you may run che with Djava.security.egd=file:/dev/urandom argument.

@fnkr
Copy link
Author

fnkr commented Feb 23, 2016

Thanks, that works!

@fnkr fnkr closed this as completed Feb 23, 2016
@ghost
Copy link

ghost commented Feb 23, 2016

FYI, this is a known issue with DO droplets, so we'll add this argument in Tomcat's setenv.sh by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant