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? -- mvh Morten Brekkevold UNINETT
From Ingeborg.Hellemo at cc.uit.no Tue Oct 16 12:29:40 2007 From: Ingeborg.Hellemo at cc.uit.no (Ingeborg Hellemo) Date: Tue Oct 16 11:29:43 2007 Subject: [Nav-users] Samba reported as down when it is not? In-Reply-To: Your message of "Fri, 12 Oct 2007 10:08:52 +0200." <470F2B94.3060304@uninett.no> Message-ID: <200710160929.l9G9TehS024614@barnetv.cc.uit.no>
morten.brekkevold@uninett.no said:
Not that I know of. The service monitor is mostly an unknown beast to the current developers, and we suspect it has many problems. Since there are so few of us, we are focusing the resources we have on the network management parts of NAV, and locally we are using other service monitoring tools, such as Hobbit.
That said, the University of Troms? has repeatedly attested their dependence on the NAV service monitor, and have claimed willing to maintain and develop it further. I have yet to see any results of this, though.
The University of Troms? is still alive and kicking, but we have been somewhat busy with other issues with NAV 3.3.0 We have now began to go through the service-monitor in ver 3.3.0 and already found a couple of issues. (So far ssh, smtp and mysql works out of the box, dns has issues, ftp does something wrong) When it comes to SmbChecker we can not help you at all since we don't have smb-shares important enough to monitor :-) --Ingeborg -- Ingeborg ?strem Hellemo -- ingeborg@cc.uit.no (Univ. of Troms?, Norway)