Pat Riehecky wrote, On 12-10-2007 16:29:
Hello,
I followed the instructions at http://metanav.uninett.no/InstallingOnRHEL4
[root@stats networkDiscovery]# which java /usr/bin/java [root@stats networkDiscovery]# `which java` -version java version "1.5.0_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05) Java HotSpot(TM) Client VM (build 1.5.0_13-b05, mixed mode) [root@stats networkDiscovery]# rpm -qa |grep sun java-1.5.0-sun-1.5.0.13-1jpp.1.el4 java-1.5.0-sun-jdbc-1.5.0.13-1jpp.1.el4 # ls -l `which java` lrwxrwxrwx 1 root root 22 Oct 2 03:32 /usr/bin/java -> /etc/alternatives/java [root@stats bin]# ls -l /etc/alternatives/java lrwxrwxrwx 1 root root 35 Oct 12 09:13 /etc/alternatives/java -> /usr/lib/jvm/jre-1.5.0-sun/bin/java
I also have the slightly older java recommended by the instructions, but I get the same error either way.
Still looks fishy to me, when the java command appears not to understand the regular arguments. There's a lot of things we could check here:
* What is your JAVA_HOME environment variable set to? * Can you confirm this is the value set for the cronjob? * What is JAVA_HOME set to in nav.conf? * Are there any other JVMs installed? ("rpm -qa | grep java" and "update-alternatives --display java") * What Java VM is running getDeviceData? (ps axuwww|grep getDeviceData)
Is networkDiscovery the only NAV process which gives you this problem? Nothing wrong with getDeviceData, eventEngine or getBoksMacs?
-
morten.brekkevoldļ¼ uninett.no