Rod,
I'm assuming you are using Unix or Linux. Is that correct? If it is Linux, which flavour of Linux (Red Hat, Ubuntu, etc)?
The error you are getting sounds like it is finding Java is starting our little test program, but for some reason it can't get enough memory to run the program. Given that the program is only small, that is odd.
Checking the environment variables
==================================
We suggest setting JAVA_HOME to your java directory (e.g. /usr/bin/java/jdk1.6.0_01/) and putting the Java bin directory (e.g. /usr/bin/java/jdk1.6.0_01/bin) on the PATH setting as it has helped in the past, but the install will often run without them.
Checking what they are set to can vary depending on which shell you are using, but normally I just log into a terminal window (ie the command line) and enter "set" to get all the environment settings.
The JDK_DIR setting is in the lams.properties file, and is normally something like /usr/bin/java/jdk1.6.0_01/.
Checking if Java is trying to take too much memory
==================================================
You mention this is a shared server. If this is the case, I assume you are running inside a virtual server? This is where they set up multiple copies of Linux (or some other operating system) on one big server and each group gets their own copy of Linux to play with.
It appears (from googling) that some of these virtual servers have problems if you don't set a maximum memory size for Java. To check this, do the following:
* Log into the command line and go to the installation directory (ie where you were running install_lams.sh).
* Run the testJava program - this is our little program that you have Java To run it, do:
$JDK_DIR/bin/java -cp bin testJava
Replacing $JDK_DIR with your JDK directory. If you have put the Java bin directory on your path, then you can just do:
java -cp bin testJava
That should give you the "Could not reserve enough space for object heap" error.
* If it does give you the error, try running this instead:
$JDK_DIR/bin/java -Xmx256m -cp bin testJava
Now does that last version work? If yes, then we will do a new install script that should run for you!
The other possibility is that the virtual server you have been allocated hasn't been allocated enough memory for the installer to run, or the one big server is overloaded. Let us hope that neither of those is the case, as that would mean talking to whoever supplied your shared server!
Fiona
Posted by Fiona Malikoff