On Tue, 29 Jul 2008 13:24:51 +0200 (MEST) Rikard Stemland Skjelsvik rskjels@pogostick.net wrote:
HTTP Status 404 - /navAdmin/servlet/navAdmin type Status report message /navAdmin/servlet/navAdmin description The requested resource (/navAdmin/servlet/navAdmin) is not available. Apache Tomcat/5.5
[snip]
The catalog /var/www/nav/vPServer, as /var/www/nav/navAdmin, includes only .htaccess and index. A find reveals that both vPServer.war and navAdmin.war is installed in /var/lib/tomcat5.5/webapps/
I would apreciate any help or pointers that could help me solve this problem.
Have you checked Tomcat's logs in /var/log/tomcat5.5 to see what the real problem is? The .war files are in the correct location, so I can't really say what the problem is without looking at the log files.
Your observation that /var/www/nav/navAdmin only contains an .htaccess file and a zero-byte index file is expected and normal. The .htaccess file tells mod_python to use a NAV proxy module, which in turn forwards requests to the local Tomcat server.
As a side note: When adding a Cisco 6509 running s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(33)SXH1, RELEASE SOFTWARE (fc3) to NAV, the cpu on the 6500 went through the roof.
Was this as you were adding it in the web interface, or after you had successfully added it? Does the cpu load spike every 6 hours after you've added it?
This could be a bug, though, i have seen CiscoWorks doing the same before. Any ideas? Is there a way to "nice" NAV on some types of equipment?
We've seen something like this happen to a Cisco 12416 (GSR) router every time NAV queries its routing table, which ends up taking about 20 minutes each time. On other identical 12416's we've not had this problem. Someone has suggested it might be a software problem in the one 12416 that displays this kind of behavior, but I'm not an expert on the equipment itself.