-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
NAV 3.0 RC2 is now available for download at http://metanav.ntnu.no/ . A number of small, but critical bugs were found in RC1, and have been fixed in this new release candidate. Unless critical bugs are reported in this release candidate, this will be the baseline for NAV 3.0.0.
Upgrading from beta RC1 ======================= Some OIDs have been added, and due to a fix in the OID-tester, we strongly recommend you to re-run the SQL script doc/sql/snmpoid.sql, as documented in the README file of the same directory.
CHANGES ======= Version 3.0_rc2 (released 20 July 2005)
Improvements:
* More data for the snmpoid table, please run the new snmpoid.sql to ensure your system will work after an upgrade.
* The Service Monitor's RPC plugin no longer complains loudly to stderr.
* The Messages and Report web interfaces will no longer intermittently cross-over mysteriously.
* The alert message texts have been updated to contain messages for all known alerts.
* Overlapping time periods in an alert profile will no longer cause double alerts to be sent.
* Modules that are down can now actually be found and deleted in the Device Management interface.
* The Traffic Map system and Network Explorer can now be properly configured to run without a single NAV root directory.
* Alert Profiles web pages now include the correct stylesheets, so it won't look as funny.
* Several getDeviceData-related problems were ironed out.
* The menu on Messages' maintenance list is no longer ugly.
* IP devices put on maintenance will now be taken off maintenance, instead of remaining on maintenance forever.
* Maintenance-scheduled IP devices can now be properly deleted from messages.
* Next/previous page-links in reports will now work properly even when using advanced search options. Also, advanced searching on database fields that contain underscores (like sw_ver) will now work.
* Performance improvements in the IP Device Center.
- -- Morten Vold NTNU ITEA Integrasjonsgruppen
From kreide at gmail.com Wed Jul 20 14:06:25 2005
From: kreide at gmail.com (Kristian Eide) Date: Wed Jul 20 22:06:30 2005 Subject: [Nav-users] Tomcat java (class/module) missing error & vlanPlot java error In-Reply-To: 42DE04B3.5050506@ntnu.no References: E04174B5A513E542AD2CB6C1E18D9C7D4DD55C@Exchange.admin.khio.no 200507191831.06408.kreide@gmail.com 42DE04B3.5050506@ntnu.no Message-ID: b4c110fd05072013061cfba430@mail.gmail.com
You need to copy (or symlink) the .jar files from nav/lib/java to the shared/lib tomcat directory.
That shouldn't really be necessary if you've already symlinked those jar-files to $JAVA_HOME/jre/lib/ext/ ? We certainly didn't do this on our production server, and it still works.
I think the recommended procedure is to only put the SNMP and Postgre jars in lib/ext and leave all NAV-specific jars in nav/lib/java. It is then necessary to symlink these files into the shared/lib tomcat directory.
Of course symlinking everything into lib/ext works and is simpler :)
Should we perhaps have a tomcat install guide which mentions this?
If anything were to be put in such a guide, it would be a bit about whether or not it is necessary to restart Tomcat or delete the extracted webapp directories when the NAV webapps have been upgraded. I think you're the expert on this particular subject :)
It is probably safest to delete the directories and then restart tomcat (though a better option is to use the webadmin tool to simply redeploy the web applications).