Error starting agent on HP-UX 11.23

[njmn_hyperic]

Hello,

HQ agent 3.2.3 EE is installed on HP-UX 11.23
(HP-UX cmxd4401 B.11.23 U ia64 0062208536 unlimited-user license)

In hq-agent.sh, HQ_JAVA_HOME is set to the IBM WAS 6.0 JVM and log level is set to debug, libsigar-ia64-hpux-11.sl is correctly installed in the pdk/lib folder.

java version is
java version "1.4.2.11"
Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.4.2.11-060824-11:11 20061117 (SR6 + 110979) )
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2 1.4.2.11-060824-19:09-IA64W IA64W, mixed mode)
IBM Java ORB build orb142ifx-20061117a (SR6)
XML build XSLT4J Java 2.6.10
XML build XmlCommonsExternal 1.2.05
XML build XML4J 4.3.8


The agent fails to start with the following stack trace

2008-04-25 10:36:01,489 INFO [main] [AgentConnection] 127.0.0.1 -> agent:ping
2008-04-25 10:36:03,153 DEBUG [main] [AgentClient] Invoking agent: [/data/WebSphere/v02/core_WebSphere/java/jre/bin/java, -client, -Dagent.propFile=agent.properties, -Dorg.hyperic.hq.b
izapp.agent.CommandsAPIInfo.camUpPort=63418, -Djava.security.auth.login.config=jaas.config, -Xmx128m, -Djava.net.preferIPv4Stack=true, -classpath, ./lib/AgentServer.jar:./lib/lather.ja
r:./pdk/lib/activation.jar:./pdk/lib/ant.jar:./pdk/lib/backport-util-concurrent.jar:./pdk/lib/commons-beanutils.jar:./pdk/lib/commons-codec-1.3.jar:./pdk/lib/commons-collections.jar:./
pdk/lib/commons-httpclient-2.0.jar:./pdk/lib/commons-logging.jar:./pdk/lib/dnsjava-2.0.3.jar:./pdk/lib/getopt.jar:./pdk/lib/hq-product.jar:./pdk/lib/hyperic-util.jar:./pdk/lib/jakarta-
oro-2.0.7.jar:./pdk/lib/jdom_b8.jar:./pdk/lib/jsch-0.1.34.jar:./pdk/lib/json.jar:./pdk/lib/junit.jar:./pdk/lib/jxla.jar:./pdk/lib/log4j-1.2.14.jar:./pdk/lib/sigar.jar:./pdk/lib/snmp4j.
jar:./pdk/lib/tomcat-jk.jar:./pdk/lib/ws-commons-util-1.0.2.jar:./pdk/lib/xalan.jar:./pdk/lib/xml-apis.jar:./pdk/lib/xmlrpc-client-3.1.jar:./pdk/lib/xmlrpc-common-3.1.jar:./pdk/lib/xpp
3_min-1.1.3.4.O.jar:./pdk/lib/xstream-1.2.1.jar, org.hyperic.hq.agent.server.AgentDaemon]
2008-04-25 10:36:03,837 INFO [main] [AgentCommandsServer] Agent commands loaded
2008-04-25 10:36:03,985 INFO [main] [AgentDaemon] Agent starting up
2008-04-25 10:36:04,029 DEBUG [main] [Sigar] Can't load library: /data/WebSphere/hqagentWAS/agent-3.2.3-EE/pdk/lib/libsigar-ia64-hpux-11.sl
org.hyperic.sigar.SigarException: Can't load library: /data/WebSphere/hqagentWAS/agent-3.2.3-EE/pdk/lib/libsigar-ia64-hpux-11.sl
at org.hyperic.sigar.Sigar.loadLibrary(Sigar.java:160)
at org.hyperic.sigar.Sigar.<clinit>(Sigar.java:90)
at org.hyperic.sigar.OperatingSystem.getInstance(OperatingSystem.java:87)
at org.hyperic.hq.product.PluginManager.<init>(PluginManager.java:66)
at org.hyperic.hq.product.ProductPluginManager.<init>(ProductPluginManager.java:160)
at org.hyperic.hq.agent.server.AgentDaemon.startPluginManagers(AgentDaemon.java:580)
at org.hyperic.hq.agent.server.AgentDaemon.start(AgentDaemon.java:700)
at org.hyperic.hq.agent.server.AgentDaemon$RunnableAgent.run(AgentDaemon.java:769)
at org.hyperic.hq.agent.server.AgentDaemon.main(AgentDaemon.java:782)
2008-04-25 10:36:04,032 ERROR [main] [AgentDaemon] Critical error running agent
java.lang.UnsatisfiedLinkError: gather
at org.hyperic.sigar.SysInfo.gather(Native Method)
at org.hyperic.sigar.OperatingSystem.getInstance(OperatingSystem.java:90)
at org.hyperic.hq.product.PluginManager.<init>(PluginManager.java:66)
at org.hyperic.hq.product.ProductPluginManager.<init>(ProductPluginManager.java:160)
at org.hyperic.hq.agent.server.AgentDaemon.startPluginManagers(AgentDaemon.java:580)
at org.hyperic.hq.agent.server.AgentDaemon.start(AgentDaemon.java:700)
at org.hyperic.hq.agent.server.AgentDaemon$RunnableAgent.run(AgentDaemon.java:769)
at org.hyperic.hq.agent.server.AgentDaemon.main(AgentDaemon.java:782)
2008-04-25 10:36:10,329 INFO [SIGINT handler] [AgentConnection] 127.0.0.1 -> agent:die



thanks for your help

[njmn_hyperic]

for information the agent starts correctly with the following Sun JVMs

java version "1.4.2.10"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2.10-060112-14:28)
Java HotSpot(TM) Server VM (build 1.4.2 1.4.2.10-060112-19:42-IA64N IA64, mixed mode)


java version "1.5.0.03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.03-_13_feb_2006_16_39)
Java HotSpot(TM) Server VM (build 1.5.0.03 jinteg:02.13.06-21:25 IA64, mixed mode)

[dougm_hyperic]

Hi Nicolas,

You should be able to monitor WebSphere 6.0 using the Sun 1.4 jre, it's WebSphere 6.1 that requires the agent to be run with the IBM jre. I don't know why the IBM jre isn't able to load the sigar library, it works fine on other platforms, though I'm not aware of anyone having tried the IBM+HPUX+ia64 combo. I recommend downloading the following tool, for tracing system calls, if you don't have it already:
ftp://ftp.cup.hp.com/dist/networking/tools/tusc.7.9.ia64.shar
sh tusc.7.9.ia64.shar

Then run the following command:
./tusc -f -o tusc.out /data/WebSphere/v02/core_WebSphere/java/jre/bin/java pdk/lib/sigar.jar version

And to get an idea where the VM is looking/what the errno is:
grep sigar tusc.out

You shouldn't have to set SHLIB_PATH, but may be worth a try:
SHLIB_PATH=pdk/lib /data/WebSphere/v02/core_WebSphere/java/jre/bin/java pdk/lib/sigar.jar version

[njmn_hyperic]

Thanks for your help Doug!

here is the output from tusc attached.
readlink returns errno 22 EINVAL => seems to be a symlink problem but I don't have root privilege to run any ln -s command.


Anyway, I tried to run the agent with IBM VM because autodiscovery didn't find my WAS 6.0.
Actually, the problem was in the install path of Websphere.
core install (bin,jre,lib...) is in /data/WebSphere/v02/core_WebSphere and profiles are in /data/WebSphere/v02/profilesWebSphere.
I set install.path property to /data/WebSphere/v02/core_WebSphere but it seems that the plugin looks for soap properties and profiles in $install.path subdirectories.
Consequently, I have updated the hq-plugin.xml in websphere-plugin.jar
<filter name="domain" value="../profilesWebSphere/%server.node%/%server.name%"/>

Now, the agent finds WebSphere Admin 6.0, WebSphere 6.0 instance and its services.

Thanks for your help

Nicolas.