Wednesday, June 27, 2012
Optima install error on linux: "cannot open shared object file"
Q: Installing Optima 2.7 on Fedora and getting this error:
Launching the Enea Installation Program on display :0.0...
Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/ose_NBsvM5/jre_linux/lib/i386/xawt/libmawt.so: libXext.so.6: cannot open shared object file: No such file or directory
... followed by a long stack trace from the java.lang.ClassLoader. I have Java installed in /usr/bin/java and mine includes the JRE:
$ java -version
java version "1.6.0"
OpenJDK Runtime Environment (build 1.6.0-b09)
OpenJDK 64-bit Server VM (build 1.6.0-b09, mixed mode)
so why didn't it find it?
A: If you have your own java and/or the JRE installed, sometimes the installer is looking in a different place for it. This is often the case on Linux distros not in the list of "official" supported distros. The best way around this is to invoke the installer script directly on the command line and referencing the java release path on your system in the same command:
$ cd /media/Optima2.7
$ which java
/usr/bin/java
$./install.sh -j /usr/bin/java
Labels: installation, java, Linux
Monday, June 11, 2012
Cannot connect to Gateway and/or Optima from SFK
Q: Trying to connect to Optima 2.4 from a soft kernel running OSE5.4.x on a Window host. I'm getting errors from the OSE Gateway and indications that it can't connect . I have WinPCap running and Optima and the SFK seem to be working otherwise.
A: Whenever using WinPCap , it's very important that you disable hardware check
summing in your Windows network device driver. (Refer to the section "Network Access on Windows"in the OSE Core User's Guide
for more information on this.) Troubleshoot this on both ends of the connection, from both the host command line and also the SFK using the gateway command:
C:/OSE/OSE5.4.1_PPC/bin/win32/osegwcmd -s tcp://177.77.7.77:21768 -e100,100
replacing the IP "177..." with your the remote address in question. If one of the connection returns errors, then on your Windows system check in
Control panel -> system -> device manager -> (local area network) -> Properties......
and look for something called "checksum" or "checksum offload" or "Rx Checksum Offload" or similar. If it is set "on" , flip it to "off", restart the SFK and Optima and try again. Generally hardware checksumming only needs to be disabled if the soft kernel and the other software (e.g. Optima) that communicates with the soft kernel via TCP/IP is running on the same machine. If you run the two across different systems, then this most likely isn't the problem.
Labels: Optima, osegw, sfk, win32, winxp
free invisible web counter
