Pat Riehecky wrote, On 03-10-2007 15:01:
Is there any way to ask NAV why it believes a particular service is down?
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.
I have a samba server that is always reported as down, yet smbclient from the very same host reports no problems at all.
# smbclient -L \\fileshare -U user -p 139 Password: Domain=[FILESHARE] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
Sharename Type Comment --------- ---- ------- IPC$ IPC Remote IPC
Server Comment --------- -------
Workgroup Master --------- -------
Where should I look to see why NAV is upset? NAV 3.2.2, RHEL4
servicemon.log is the place to look when you are wondering what the service monitor is doing. Also, servicemon.conf can be used to configure the debug level of this log. I'm looking at the SmbChecker plugin now, and it doesn't look good to me, though. It parses the output of the following command to verify the status of a samba server: /usr/bin/smbclient -L %s -p %i %s 2>/dev/null %s is the server IP address (or host name configured when adding the service handler), %i is the configured port (139). If you've entered a username and password in the service handler config, %s will be "-U username%password", and if you configured a workgroup, it will also contain "-W workgroup". This also means that your smbclient program must be located in /usr/bin/smbclient , since this is hard coded into the plugin :-( If your smbclient is not located in /usr/bin, or your version of smbclient does not support the above mentioned arguments, then I guess you will have trouble with this plugin. -- mvh Morten Brekkevold UNINETT
From morten.brekkevold at uninett.no Fri Oct 12 11:17:29 2007 From: morten.brekkevold at uninett.no (Morten Brekkevold) Date: Fri Oct 12 10:18:15 2007 Subject: [Nav-users] Traffic Map will not display In-Reply-To: <3987.207.61.90.34.1191436754.squirrel@webmail.niagara.com> References: <3987.207.61.90.34.1191436754.squirrel@webmail.niagara.com> Message-ID: <470F2D99.2080109@uninett.no>
rkillick@niagara.com wrote, On 03-10-2007 20:39:
The Traffic Map will not display and simply shows an empty box where the map should be, and a lone remark in the status bar at the bottom left "Applet vlanPlot notinted". Note: The "IP address scope - graphical view" works fine. I have placed 6 x GSW (C3750s) into the '_Top' map container.
Any ideas as to where to begin looking for the problem would be appreciated.
Hi Bob, My first question is: Does the Network Explorer work for you? When the traffic map applet has problems, you should enable your Java Console and load the applet again, to see what is logged in the console. I can't give you an exact account of how to enable the Java Console, as this depends on both your OS and browser, and I don't know which you're using. If you can't figure it out by yourself, tell me which os/browser you are using, and I'll help you. Typical problems with the traffic map are: * The tomcat servlet container isn't running, so the traffic map cannot fetch it's data. * The apache server is accessed under a different host name than what is configured in the ServerName apache config option. The traffic map will attempt to fetch its data from a an URL with the ServerName in the host part, but the java applet security model will not allow applets to access anything but the same hostname the applet was loaded from. -- mvh Morten Brekkevold UNINETT
From morten.brekkevold at uninett.no Fri Oct 12 11:23:24 2007 From: morten.brekkevold at uninett.no (Morten Brekkevold) Date: Fri Oct 12 10:23:29 2007 Subject: [Nav-users] Could not connect to servlet In-Reply-To: <58B7A531794E6A49B3BAD57E333225440249A320@engexc11.archstonesmith.com> References: <58B7A531794E6A49B3BAD57E333225440249A320@engexc11.archstonesmith.com> Message-ID: <470F2EFC.1090408@uninett.no>
Pabon, Nestor wrote, On 08-10-2007 19:09:
When attempting selecting the Network Explorer I get the following: [snip] error: (111, 'Connection refused')
This is a packaged installation of NAV 3.2.2. on a Debian Etch 4.0.
Hi Nestor, Either your Tomcat servlet container is not running, or it is listening to the wrong port (which I doubt, unless you've changed your Tomcat config). Check the tomcat status using "invoke-rc.d tomcat5.5 status". If it's not running, you can start it using "invoke-rc.d tomcat5.5 start" (as root, of course). -- mvh Morten Brekkevold UNINETT
From morten.brekkevold at uninett.no Fri Oct 12 11:31:34 2007 From: morten.brekkevold at uninett.no (Morten Brekkevold) Date: Fri Oct 12 10:31:37 2007 Subject: [Nav-users] Java error In-Reply-To: <1191965071.15629.17.camel@thales.iwu.edu> References: <1191965071.15629.17.camel@thales.iwu.edu> Message-ID: <470F30E6.1010401@uninett.no>
Pat Riehecky wrote, On 09-10-2007 23:24:
I am getting the following error in the networkDiscovery log:
Warning: -Xmx256m not understood. Ignoring. Warning: -jar not understood. Ignoring. Exception in thread "main" java.lang.NoClassDefFoundError: networkDiscovery.jar at gnu.gcj.runtime.FirstThread.run() (/usr/lib/libgcj.so.5.0.0) at _Jv_ThreadRun(java.lang.Thread) (/usr/lib/libgcj.so.5.0.0) at _Jv_RunMain(java.lang.Class, byte const, int, byte const, boolean) (/usr/lib/libgcj.so.5.0.0) at __gcj_personality_v0 (/usr/local/nav/lib/java/networkDiscovery/java.version=1.4.2) at __libc_start_main (/lib/tls/libc-2.3.4.so) at _Jv_RegisterClasses (/usr/local/nav/lib/java/networkDiscovery/java.version=1.4.2)
How do I fix this... I am not a java person.....
NAV 3.2.2, RHEL4
Hi Pat, Did you follow Roger Aas' howto from MetaNAV for installing on RHEL4? To me it looks like you aren't using Sun's Java, but some other vendor's Java (The java command does not seem to understand the -Xmx and -jar options, which is pretty strange). What do the following two commands output on your system? which java java -version -- mvh Morten Brekkevold UNINETT
From morten.brekkevold at uninett.no Fri Oct 12 11:47:51 2007 From: morten.brekkevold at uninett.no (Morten Brekkevold) Date: Fri Oct 12 10:47:54 2007 Subject: [Nav-users] postgres and "nonstandard use of \\" In-Reply-To: <200710101055.l9AAthe9025671@barnetv.cc.uit.no> References: <200710101055.l9AAthe9025671@barnetv.cc.uit.no> Message-ID: <470F34B7.7020806@uninett.no>
Ingeborg Hellemo wrote, On 10-10-2007 12:55:
My postgres 8.2 is whining about "WARNING: nonstandard use of \\ in a string literal at character NN" "HINT: Use the escape string syntax for backslashes, e.g., E'\\'."
I think I have located the source of the warnings to be these lines in /usr/local/nav/doc/sql/navprofiles.sql (NAV 3.3.0)
INSERT INTO AccountGroupPrivilege (accountgroupid, privilegeid, target) VALUES (2, 2, '^/toolbox\\b'); [snip] Are the lines supposed to look like this?
Yes, PostgreSQL has always interpreted a backslash as an escape character, so these INSERT statements escape the backslash that we want to store in the database using a backslash, i.e. \\ to store one \ . But it seems PostgreSQL is going to change this behaviour in the future, so I guess they added a warning about in in 8.2. Google yielded this: http://www.mydatabasesupport.com/forums/1004812-post2.html This is probably going to be a problem for many software packages, including NAV, since most database drivers tend to escape special characters in strings using backslashes. I'm sure you'll see more of these warnings in the logs while NAV is running. If you want to get rid of them, I suggest adding "escape_string_warning = off" to your postgresql.conf, as one of the suggested solutions in the above URL reads. -- mvh Morten Brekkevold UNINETT
From prieheck at iwu.edu Fri Oct 12 10:29:09 2007 From: prieheck at iwu.edu (Pat Riehecky) Date: Fri Oct 12 16:29:14 2007 Subject: [Nav-users] Java error In-Reply-To: <470F30E6.1010401@uninett.no> References: <1191965071.15629.17.camel@thales.iwu.edu> <470F30E6.1010401@uninett.no> Message-ID: <1192199349.10913.32.camel@thales.iwu.edu>
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. Pat On Fri, 2007-10-12 at 10:31 +0200, Morten Brekkevold wrote:
Pat Riehecky wrote, On 09-10-2007 23:24:
I am getting the following error in the networkDiscovery log:
Warning: -Xmx256m not understood. Ignoring. Warning: -jar not understood. Ignoring. Exception in thread "main" java.lang.NoClassDefFoundError: networkDiscovery.jar at gnu.gcj.runtime.FirstThread.run() (/usr/lib/libgcj.so.5.0.0) at _Jv_ThreadRun(java.lang.Thread) (/usr/lib/libgcj.so.5.0.0) at _Jv_RunMain(java.lang.Class, byte const, int, byte const, boolean) (/usr/lib/libgcj.so.5.0.0) at __gcj_personality_v0 (/usr/local/nav/lib/java/networkDiscovery/java.version=1.4.2) at __libc_start_main (/lib/tls/libc-2.3.4.so) at _Jv_RegisterClasses (/usr/local/nav/lib/java/networkDiscovery/java.version=1.4.2)
How do I fix this... I am not a java person.....
NAV 3.2.2, RHEL4
Hi Pat,
Did you follow Roger Aas' howto from MetaNAV for installing on RHEL4? To me it looks like you aren't using Sun's Java, but some other vendor's Java (The java command does not seem to understand the -Xmx and -jar options, which is pretty strange).
What do the following two commands output on your system?
which java java -version