cannot execute binary file issue on od receiver restart

Nandha_Polaris

Hi All,

We tried to install OD Receiver 7.2.0 (IWOVOpenDeployRcvr-Linux-7.2.0.tar.gz) in

SUSE Linux Enterprise Server 10 (s390x) 32 bit
VERSION = 10
PATCHLEVEL = 4

The gz was extracted and we initiated the installation with ./startinstall_od, the installation completed successfully.

But when we try to execute the below command to get the license we got the below error:

Command:
/uivrreg2/opendeploy/OpenDeployNG/jre/bin/java -cp /uivrreg2/opendeploy/OpenDeployNG/lib/odng.jar com.interwoven.license.LicInfo -f /tmp/ODlicinfo.txt -p OD

Error:
/uivrreg2/opendeploy/OpenDeployNG/lib/iwodclt: line 140: /uivrreg2/opendeploy/OpenDeployNG/jre/bin/java: cannot execute binary file


The same command executed successfully when the java path was mapped to IBM WebSphere java/bin/java path which was available in the same server as shown below:

/java/bin/java -cp /uivrreg2/opendeploy/OpenDeployNG/lib/odng.jar com.interwoven.license.LicInfo -f /tmp/ODlicinfo.txt -p OD

On OD Restart again the same issue after placing the license.

IBM JRE 1.5 is installed in the server and class path is also set:

IBM jre 1.5: java-1_5_0-ibm-32bit-1.5.0_sr13.0-0.5.1
Installed Location: /usr/lib/jvm/jre-1.5.0-ibm

Class Path:
JRE_HOME=/usr/lib/jvm/jre
PATH=/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/usr/lib/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/var/security/login/bin:/usr/local/bin:/usr/bin:/bin:/usr/lib/java/jre/bin:/var/security/login/bin:/sbin:/usr/sbin:/optware/oracle/dba:/opt/pb/bin:/opt/pb/bin
JAVA_BINDIR=/usr/lib/jvm/jre/bin
JAVA_HOME=/usr/lib/jvm/jre
JAVA_ROOT=/usr/lib/jvm/jre

Please help to solve the issue.

Regards,
Nandha K

nipper

It looks like you have the wrong binaries


execute these commands:

file /uivrreg2/opendeploy/OpenDeployNG/jre/bin/java

ls -l /uivrreg2/opendeploy/OpenDeployNG/jre/bin/java

and maybe

chmod +x /uivrreg2/opendeploy/OpenDeployNG/jre/bin/java (as root)



However if that works, it makes me wonder if the install went correctly or not. You may want to talk to the sys admins, I have had an issue similar because /tmp was mounted with no-execute so the binaries lost that flag.