Linux Agent Install Problem

Hello,

Please try latest nightly build, and let me know.


robert

Hi!

I've also run into some problems when installing loadUI on my Arch Linux 64 bit machine.

This is my JRE:

$ java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)

When I run the installer with the following command

$ sudo sh loadUI-1_0_1.sh -c

it runs fine until I get to the point where I have to enter the Port for the proxy settings.
Unlike what the instructions says, I am not able to just hit enter when the Port is to be given,
but has to give an acual value, such as 80.

This is where you can enter the proxy settings that Java WebStart will use
when starting LoadUI. Leave them blank if you do not use a proxy to reach
the internet.
Proxy:
[]

Port:
[]

Port:
[]
80

the rest of the installer runs without any problems.

However, when I try to run the symlinked loadUI.sh script i get

/usr/local/bin/loadUI.sh: line 41: jre/bin/javaws: No such file or directory

which indicates that the javaws file is tried to be run relative to the current directory instead
of the /opt/eviware/loadUI-1.0.1 directory.

When instead trying to run the loadUI.sh script from the /opt/eviware/loadUI-1.0.1 directory I get this stracktrace

Exception in thread "main" java.lang.UnsatisfiedLinkError: /opt/eviware/loadUI-1.0.1/jre/lib/i386/xawt/libmawt.so: libXtst.so.6: wrong ELF class: ELFCLASS64
 at java.lang.ClassLoader$NativeLibrary.load(Native Method)
 at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1803)
 at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1699)
 at java.lang.Runtime.load0(Runtime.java:770)
 at java.lang.System.load(System.java:1003)
 at java.lang.ClassLoader$NativeLibrary.load(Native Method)
 at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1803)
 at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1720)
 at java.lang.Runtime.loadLibrary0(Runtime.java:823)
 at java.lang.System.loadLibrary(System.java:1028)
 at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.awt.Toolkit.loadLibraries(Toolkit.java:1592)
 at java.awt.Toolkit.<clinit>(Toolkit.java:1614)
 at com.sun.javaws.Main.main(Main.java:100)

which indicates that loadUI is trying to run javaws with an 32 bit JRE on my 64 bit system.

When I tried to run the javaws command for my own 64 bit JRE I ran in to the know bug
where you don't get pass the spash screen (http://www.eviware.com/Nightly-Builds/loadui-changelog.html).

I finally got it all working by downloading the latests snapshot from
http://www.eviware.com/Nightly-Builds/loadui-nightly-builds.html
and installing it with regular user permissions in my home folder and then
running

$ javaws loadUI.jnlp

from the loadUI-1.0.2-SNAPSHOT folder.
I also tried running the install script as sudo, but that did require that I also ran javaws as sudo

A also created a custom script for launching loadUI and placed it in /usr/local/bin:

#!/bin/sh
cd ~/eviware/loadUI-1.0.2-SNAPSHOT
javaws loadUI.jnlp

Now I could just enter

$ loadUI

anywhere and it starts nicely

Thanks for an awesome test tool, keep up the good work!

Thanks a lot for the detailed descriptions -- it's useful both for other users and for us!

We will have a look at the Linux installer as soon as possible (definitely before loadUI 1.5).

/Henrik
eviware.com

Hi!

Problem when port value is not supplied:

    This is where you can enter the proxy settings that Java WebStart will use
    when starting LoadUI. Leave them blank if you do not use a proxy to reach
    the internet.
    Proxy:
    []

    Port:
    []

    Port:
    []
    80

should be fixed now. You can download latest
nightly and try it.

regards!
Predrag
eviware.com

I have tried to install on Ubuntu and CentOS (virtualized) 32 bit and it works fine.

Please let us know if it's not working for you.

/Henrik
eviware

The errors we were seeing related to the install of java. I will circle back with my team and see if it is repeatable with the new CentOS virts we are instantiating.

What we're seeing right now relates to firewall issues - the CentOS machine is blocking the ports. We've enable the ones that know of - but still no joy. What are the ports that should be enabled in order for this to work. I don't think we'll have the option of disabling the firewall completely.

Well I experienced similar problem while running loadUI and I just told the application in the script folder of my $JAVA_HOME and that's it.