Oktober 2010 - Nav-users - lister.unit.no

use the /etc/hosts file
by Tor Pretorius 30 Okt '10

30 Okt '10

Hi How can I set the NAV 3.6, to use /etc/hosts file instead of dns server names in the column Name in the report. Med vennlig hilsen / Best Regards Tor Pretorius Senior konsulent Data Instrumenttjenesten AS Frederik A. Dahlsvei 20 1432 Ås 91716759 / 64949840 www.it-as.no<http://www.it-as.no/>

5 6

I'm getting a error when trying to delete device in seed database ?
by Tor Pretorius 26 Okt '10

26 Okt '10

Hi Running nav 3.6 on a Debian installation Its upgrade from nav 3.5.6 This error came when I'm trying to delete a device. ------------------------------------------------------ MOD_PYTHON ERROR ProcessId: 16175 DocumentRoot: '/usr/share/nav/htdocs' URI: '/seeddb/netbox/edit' Location: None Directory: '/usr/share/nav/htdocs/seeddb/' Filename: '/usr/share/nav/htdocs/seeddb/netbox' PathInfo: '/edit' Phase: 'PythonHandler' Handler: 'seeddb' Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1537, in HandlerDispatch default=default_handler, arg=req, silent=hlist.silent) File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1229, in _process_target result = _execute_target(config, req, object, arg) File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1128, in _execute_target result = object(arg) File "/usr/share/nav/htdocs/seeddb/seeddb.py", line 165, in handler output = editPage(req,pageList[table](),request,unicodeError) File "/usr/share/nav/htdocs/seeddb/seeddb.py", line 461, in editPage status = page.delete(selected,status) File "/usr/share/nav/htdocs/seeddb/seeddb.py", line 1617, in delete error += '%s is referenced in another table' % (self.name,) AttributeError: pageNetbox instance has no attribute 'name' ------ end print ------ Med vennlig hilsen / Best Regards Tor Pretorius Senior konsulent Data Instrumenttjenesten AS Frederik A. Dahlsvei 20 1432 Ås 91716759 / 64949840 www.it-as.no<http://www.it-as.no/>

2 1

Announcement: NAV 3.6.1 released
by Morten Brekkevold 25 Okt '10

25 Okt '10

NAV 3.6.1 is now available for download at Launchpad: https://launchpad.net/nav/3.6/3.6.1 See the abovementioned URL for changelog and release notes. 11 reported bugs have been resolved, and some improvements have been made to ipdevpoll. At least one bug concerns itself with the database schema, so this release also updates the schema. A problem in TwistedSNMP can cause issues with SNMP bombardment of slow SNMP agents. The bug has been reported upstream at [1] - the patch that solves the problem has also been included in NAV's contrib/patches directory. Please reports bugs at https://bugs.launchpad.net/nav :-) A binary package for Debian 5 (Lenny) will be made available as soon as possible. The Debian package is maintained by Morten Werner Forsbring, on commission From UNINETT. Happy NAVing everyone! [1] http://sourceforge.net/tracker/index.php?func=detail&aid=3083670&group_id=1… -- Morten Brekkevold UNINETT

1 0

3.6.0 mcc character encoding
by Sigurd Mytting 12 Okt '10

12 Okt '10

Hi, upgraded to 3.6.0 yesterday - it looks great! But there is a small problem: it seems mcc won't handle norwegian characters in port descriptions. 2010-10-09 09:35:58,708: [ERROR] nav.mcc.utils - Could not encode KVM Str�mskinne 1 to latin-1: 'latin-1' codec can't encode character u'\ufffd' in position 7: ordinal not in range(256) I don't really care about the description beeing correctly displayed, but mcc stops after this and no more cricket config is generated. Looks like this happens when convert_unicode_to_latin1 in nav/mcc/utils.py returns the unicode object instead of a latin-1 string. My workaround is to just return an empty string instead of the unicode object. Thanks for all the work you guys put into NAV, truly exceptional software solving everyday problems for a lot of us! Cheers, -Sigurd

2 4

Issues with database upgrade from 3.5 to 3.6
by Morten Brekkevold 12 Okt '10

12 Okt '10

Hi, This is a notice to those who have previously upgraded NAV from 3.4 to 3.5 and will be upgrading to 3.6 now. We've received some reports from users on IRC about errors during the attempt to upgrade the SQL schema from NAV 3.5 to 3.6. As we're on the brink of upgrading multiple deployments of NAV among our customers, we're seeing the same problems ourselves. During the upgrade from 3.4 to 3.5, a lot changed in the database. Most notably, the multiple databases were merged into one. But also, several indexes were renamed. For some reason, not all of these renames have stuck with some PostgreSQL installations. We really have no idea why; all the rename statements are present in the upgrade script 3.5.0.sql, and they're all run in the same transaction. If any of them failed, the entire transaction should have been rolled back and all the changes thrown away, and we would have heard of it. If you receive an error that looks like this while upgrading the schema to 3.6.0, you are affected by the problem: psql:3.6.0b1.sql:433: ERROR: constraint "accountnavbar_pkey" does not exist The problem can be fixed by re-issuing all the index renaming statements from 3.5.0.sql using psql almost the same way as you would during the upgrade. Connect to the nav database using "psql <navdb> <navuser> <password>" (the db name, user name and password can be found in db.conf), and issue the following ALTER statements: ALTER INDEX logger.message_pkey RENAME TO log_message_pkey; ALTER INDEX logger.message_origin_btree RENAME TO log_message_origin_btree; ALTER INDEX logger.message_time_btree RENAME TO log_message_time_btree; ALTER INDEX logger.message_type_btree RENAME TO log_message_type_btree; ALTER INDEX logger.type_pkey RENAME TO log_message_type_pkey; ALTER INDEX logger.type_priority_key RENAME TO log_message_type_priority_key; ALTER INDEX account_pk RENAME TO account_pkey; ALTER INDEX brukernavn_uniq RENAME TO account_login_key; ALTER INDEX accountgroup_pk RENAME TO accountgroup_pkey; ALTER INDEX alarmadresse_pk RENAME TO alertaddress_pkey; ALTER INDEX brukerprofil_pk RENAME TO alertprofile_pkey; ALTER INDEX preference_pk RENAME TO alertpreference_pkey; ALTER INDEX tidsperiode_pk RENAME TO timeperiod_pkey; ALTER INDEX utstyrgruppe_pk RENAME TO filtergroup_pkey; ALTER INDEX utstyrfilter_pk RENAME TO filter_pkey; ALTER INDEX matchfield_pk RENAME TO matchfield_pkey; ALTER INDEX filtermatch_pk RENAME TO expression_pkey; ALTER INDEX queue_pkey RENAME TO accountalertqueue_pkey; ALTER INDEX navbarlink_pk RENAME TO navbarlink_pkey; ALTER INDEX accountnavbar_pk RENAME TO accountnavbar_pkey; ALTER INDEX privilege_pk RENAME TO privilege_pkey; ALTER INDEX privilegename_uniq RENAME TO privilege_privilegename_key; Some of them may fail with an error message like 'relation "xxx" does not exist', but that is just an indication that the rename stuck the first time around. Exit psql and try the schema upgrade again. -- Morten Brekkevold UNINETT

1 0

Announcement: NAV 3.6.0 released
by Morten Brekkevold 08 Okt '10

08 Okt '10

Finally, NAV 3.6.0 is available for download at Launchpad: https://launchpad.net/nav/3.6/3.6.0 See the abovementioned URL for changelog and release notes. If you are upgrading from 3.5, be aware that there are multiple SQL upgrade scripts from the various beta releases, so look for the 3.6.0*.sql upgrade scripts. There are undoubtedly bugs (lets not kid ourselves); if you find any, please report them at https://bugs.launchpad.net/nav :-) A binary package for Debian 5 (Lenny) will be made available as soon as possible. The Debian package is maintained by Morten Werner Forsbring, on commission From UNINETT. A big thanks to everyone involved in making this release happen, happy NAVing everyone! -- Morten Brekkevold UNINETT

3 2

nav 3.5.6 and Catalyst 6500 VSS
by Ørjan Sæbø 05 Okt '10

05 Okt '10

Hi Having migrat3e to VSS (2xcat 6509), NAV is not longer able to recognize any interfaces/modules/etc. Is there a way to make this work? The system identifies as type "catalyst65xxVirtualSwitch" and has OID 1.3.6.1.4.1.9.1.896 Regards, Ørjan Sæbø

2 2