Cannot Execute Error on JES4 install
Ok, I'm starting from scratch here...I'm trying to install JES4 on an Admin/Directory server. Downloaded the install from the web but when I try to run the ./install...I get the following error:
/tmp/.jes_CaChE/Solaris_sparc/installer: /tmp/.jes_CaChE/Solaris_sparc/.install/j2se_jre/bin/java: cannot execute
Sun Documentation is impossible to follow OR understand! Checked the permission on the /java and changed them to allow for execute but they change back again!
Any suggestion appreciated!
[522 byte] By [
johnj2] at [2007-11-26 8:30:14]

# 1
Gotta be something pretty basic if java won't run. You did make sure to get the right architecture distribution (it looks like you got the SPARC one, you're not running on a x64 server?) "cannot execute" can be other things than permissions problems. Are you low onf swap space? (install has, at this point, just unpacked a whole JRE into /tmp, and if you have /tmp on swap which is normal for Solaris, that is going to eat a bunch of swap space.) (Btw, the reason the permissions seem to change back is that it's unpacking a whole new version every time you run ./installer.)
I note the Installation Guide does say to "navigate to the directory" and enter "./installer" . I suspect that means that entering the absolute pat won't work, did you do that?
# 2
Rich-I have just run into this same problem trying to install on an Ultra 10 (hey, it's what I have...)Is there an easy way to mount /tmp someplace other than in the swap partition? Or is the next move, "first, re-install Solaris?"-Bill
# 3
Hi,
we got similar error when run x86 installer on SPARC machine:
/tmp/.jes_CaChE/Solaris_x86/installer: /tmp/.jes_CaChE/Solaris_x86/.install/j2se_jre/bin/java: cannot execute
Are you sure you are running right architecture installer?
And regarding /tmp:
I think you can just unmount it:
umount /tmp
(Maybe better in single user mode)
Or remove /tmp entry in /etc/vfstab and reboot.
Then it wil be part of / filesystem, which could be a problem if you do not have enough space. Maybe also check permissions, it should be
# ls -ld /tmp
drwxrwxrwt 30 rootsys11066 Mar 23 11:53 /tmp