Ubuntu
eucalyptus package

-cloud and -cc init scripts don't set JAVA_HOME

Bug #365156 reported by Loïc Minier
2
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Hi

eucalyptus-cloud doesn't start for me because JAVA_HOME isn't set, in /var/log/eucalyptus/cloud-output.log:
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-6-sun/bin/java

adding:
export JAVA_HOME=/usr/lib/jvm/default-java
after JAVA in /etc/init.d/eucalyptus-cloud allows the service to start (with some non-root warnings, and some fds remains open warnings)

Bye

Revision history for this message
Loïc Minier (lool) wrote :

(Also JAVA seems unused)

Changed in eucalyptus (Ubuntu):
importance: Undecided → High
Revision history for this message
Loïc Minier (lool) wrote :

You might also want to depend on default-jre since this init script calls java. Something like:
Depends: default-jre (>= 1.4) | default-jre-headless (>= 1.4) | java2-runtime | java2-runtime-headless

Revision history for this message
Loïc Minier (lool) wrote :

It seems the -cc init script has the same issue

summary: - -cloud init script doesn't set JAVA_HOME
+ -cloud and -cc init scripts don't set JAVA_HOME
Revision history for this message
graziano obertelli (graziano.obertelli) wrote :

The CC isn't using java, so it shouldn't need it.

Revision history for this message
Soren Hansen (soren) wrote :

I'm not entirely sure I understand the problem. Everything works fine on a fresh, default install. It looks for "java" in the path, and uses that.

Changed in eucalyptus (Ubuntu):
status: New → Incomplete
Revision history for this message
Matt Zimmerman (mdz) wrote :

Reading the script, and Loic's error output, it looks like perhaps Loic had JAVA_HOME set to /usr/lib/jvm/java-6-sun, but had no JVM there. As Soren says, the script finds java in $PATH and this works in all of our tests.

Please reopen if I've got it wrong and there's a bug here.

Changed in eucalyptus (Ubuntu):
status: Incomplete → Invalid
importance: High → Medium
Revision history for this message
Loïc Minier (lool) wrote :

Ack, I checked and indeed found a bogus environment in one of root's two shell environment configs which is why I was only seeing it in some cases; sorry for the bogus report

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.