Nav-users

nav-users@lister.sikt.no

1 participants
1378 discussions

Switchport
by odd.hauge＠hiMolde.no 03 Jul '06

03 Jul '06

Hi. I still have above 160' switch ports. HP switches not running VTP have above 60' switch ports. I also have a location in another city (Kristiansund) with another VTP. Every vlan defined in the main location (Molde) are reported on the switches in Kristiansund, even if they are not defined in Kristiansund. VLAN information is missing for ports on some switches in the sw-port report. I have tried the "netbox.uptodate field to false" and remove/add the switch without any success. I have several other identically switches without this "problem" running the same catos version. How can I debug this? - odd arne > -----Original Message----- > From: Kristian Eide [mailto:kreide@gmail.com] > Sent: Tuesday, April 04, 2006 10:05 AM > To: Hauge Odd Arne > Cc: nav-users(a)itea.ntnu.no > Subject: Re: [Nav-users] Machine tracker > > And Nav still reports that I have above 200 000 > switchports. Vlan defined in one location are shown in the > report for every location, regardless if the vlans are > active/defined or not on all switches in every location. > > I believe this is caused by a bug in the code which tries to > determine the extend of private (i.e. vlans without a router) > networks. > Unfortunately this code was not tested well enough and it > really should be disabled for now. I hope Morten can help > take care of this when he returns. > > -- > Kristian >

1 0

Tags shown instead of the page
by sommerjobb＠froisland.no 03 Jul '06

03 Jul '06

> What version of NAV are you running? This was fixed in NAV 3.0.1. > You are right I installed 3.0.0, just followed one of the red hat install guides on the wiki using a rpm for 3.0.0. Now I'm trying to install either 3.0.1 og 3.1.0, but get the same error when running make. The ./configure par works nicely, runing make I get: [marius@room nav-3.1.0]$ make make[1]: Entering directory `/home/marius/nav-3.1.0/src' Building Util ... (cd Util && ) && touch Util /bin/sh: -c: line 0: syntax error near unexpected token `)' /bin/sh: -c: line 0: `(cd Util && ) && touch Util' make[1]: *** [Util] Error 2 make[1]: Leaving directory `/home/marius/nav-3.1.0/src' make: *** [all] Error 1 Marius

1 0

Announcement: NAV 3.1.0 is out
by roar.pettersen＠uib.no 03 Jul '06

03 Jul '06

Hi ! Trying to create the database from scrath : psql:/usr/local/nav/doc/sql/manage.sql:3: ERROR: table "mem" does not exist psql:/usr/local/nav/doc/sql/manage.sql:4: ERROR: table "swportblocked" does not exist psql:/usr/local/nav/doc/sql/manage.sql:5: ERROR: table "swportallowedvlan" does not exist psql:/usr/local/nav/doc/sql/manage.sql:6: ERROR: table "swportvlan" does not exist psql:/usr/local/nav/doc/sql/manage.sql:7: ERROR: table "gwport" does not exist psql:/usr/local/nav/doc/sql/manage.sql:8: ERROR: table "vlan" does not exist psql:/usr/local/nav/doc/sql/manage.sql:9: ERROR: table "prefix" does not exist psql:/usr/local/nav/doc/sql/manage.sql:10: ERROR: table "gwportprefix" does not exist psql:/usr/local/nav/doc/sql/manage.sql:11: ERROR: table "swport" does not exist psql:/usr/local/nav/doc/sql/manage.sql:12: ERROR: table "module" does not exist psql:/usr/local/nav/doc/sql/manage.sql:13: ERROR: table "netboxcategory" does not exist psql:/usr/local/nav/doc/sql/manage.sql:14: ERROR: table "netboxinfo" does not exist psql:/usr/local/nav/doc/sql/manage.sql:15: ERROR: table "netbox" does not exist psql:/usr/local/nav/doc/sql/manage.sql:16: ERROR: table "emotd" does not exist psql:/usr/local/nav/doc/sql/manage.sql:17: ERROR: table "maintenance" does not exist psql:/usr/local/nav/doc/sql/manage.sql:18: ERROR: table "emotd_related" does not exist psql:/usr/local/nav/doc/sql/manage.sql:19: ERROR: table "cat" does not exist psql:/usr/local/nav/doc/sql/manage.sql:20: ERROR: table "device" does not exist psql:/usr/local/nav/doc/sql/manage.sql:21: ERROR: table "product" does not exist psql:/usr/local/nav/doc/sql/manage.sql:22: ERROR: table "vendor" does not exist psql:/usr/local/nav/doc/sql/manage.sql:23: ERROR: table "type" does not exist psql:/usr/local/nav/doc/sql/manage.sql:24: ERROR: table "snmpoid" does not exist psql:/usr/local/nav/doc/sql/manage.sql:25: ERROR: table "typegroup" does not exist psql:/usr/local/nav/doc/sql/manage.sql:26: ERROR: table "room" does not exist psql:/usr/local/nav/doc/sql/manage.sql:27: ERROR: table "location" does not exist psql:/usr/local/nav/doc/sql/manage.sql:28: ERROR: table "usage" does not exist psql:/usr/local/nav/doc/sql/manage.sql:29: ERROR: table "org" does not exist psql:/usr/local/nav/doc/sql/manage.sql:30: ERROR: table "port2off" does not exist psql:/usr/local/nav/doc/sql/manage.sql:32: ERROR: table "swp_netbox" does not exist psql:/usr/local/nav/doc/sql/manage.sql:33: ERROR: table "alertengine" does not exist psql:/usr/local/nav/doc/sql/manage.sql:36: ERROR: table "vp_netbox_xy" does not exist psql:/usr/local/nav/doc/sql/manage.sql:37: ERROR: table "vp_netbox_grp" does not exist psql:/usr/local/nav/doc/sql/manage.sql:38: ERROR: table "vp_netbox_grp_info" does not exist psql:/usr/local/nav/doc/sql/manage.sql:41: ERROR: sequence "netbox_netboxid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:42: ERROR: sequence "gwport_gwportid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:43: ERROR: sequence "prefix_prefixid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:44: ERROR: sequence "type_typeid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:45: ERROR: sequence "swport_swportid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:46: ERROR: sequence "swp_netbox_swp_netboxid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:47: ERROR: sequence "device_deviceid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:48: ERROR: sequence "product_productid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:49: ERROR: sequence "module_moduleid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:50: ERROR: sequence "mem_memid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:51: ERROR: sequence "emotd_emotdid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:52: ERROR: sequence "maintenance_maintenanceid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:55: ERROR: sequence "vp_netbox_grp_vp_netbox_grp_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:56: ERROR: sequence "vp_netbox_xy_vp_netbox_xyid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:60: ERROR: table "status" does not exist psql:/usr/local/nav/doc/sql/manage.sql:61: ERROR: sequence "status_statusid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:72: NOTICE: CREATE TABLE will create implicit sequence "status_statusid_seq" for serial column "status.statusid" psql:/usr/local/nav/doc/sql/manage.sql:72: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "status_pkey" for table "status" CREATE TABLE psql:/usr/local/nav/doc/sql/manage.sql:83: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "org_pkey" for table "org" CREATE TABLE psql:/usr/local/nav/doc/sql/manage.sql:89: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "usage_pkey" for table "usage" CREATE TABLE psql:/usr/local/nav/doc/sql/manage.sql:95: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "location_pkey" for table "location" CREATE TABLE psql:/usr/local/nav/doc/sql/manage.sql:105: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "room_pkey" for table "room" CREATE TABLE psql:/usr/local/nav/doc/sql/manage.sql:111: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "nettype_pkey" for table "nettype" CREATE TABLE psql:/usr/local/nav/doc/sql/manage.sql:432: ERROR: table "arp" does not exist psql:/usr/local/nav/doc/sql/manage.sql:433: ERROR: table "cam" does not exist psql:/usr/local/nav/doc/sql/manage.sql:434: ERROR: view "netboxmac" does not exist psql:/usr/local/nav/doc/sql/manage.sql:435: ERROR: view "prefix_active_ip_cnt" does not exist psql:/usr/local/nav/doc/sql/manage.sql:436: ERROR: view "prefix_max_ip_cnt" does not exist psql:/usr/local/nav/doc/sql/manage.sql:437: ERROR: view "prefixreport" does not exist psql:/usr/local/nav/doc/sql/manage.sql:438: ERROR: view "netboxreport" does not exist psql:/usr/local/nav/doc/sql/manage.sql:439: ERROR: view "allowedvlan_both" does not exist psql:/usr/local/nav/doc/sql/manage.sql:440: ERROR: view "allowedvlan" does not exist psql:/usr/local/nav/doc/sql/manage.sql:441: ERROR: table "eventtype" does not exist psql:/usr/local/nav/doc/sql/manage.sql:442: ERROR: table "range" does not exist psql:/usr/local/nav/doc/sql/manage.sql:444: ERROR: sequence "arp_arpid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:445: ERROR: sequence "cam_camid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:447: ERROR: function netboxid_null_upd_end_time() does not exist psql:/usr/local/nav/doc/sql/manage.sql:619: ERROR: table "subsystem" does not exist psql:/usr/local/nav/doc/sql/manage.sql:620: ERROR: table "rrd_file" does not exist psql:/usr/local/nav/doc/sql/manage.sql:621: ERROR: table "rrd_datasource" does not exist psql:/usr/local/nav/doc/sql/manage.sql:623: ERROR: sequence "rrd_file_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:624: ERROR: sequence "rrd_datasource_seq" does not exis psql:/usr/local/nav/doc/sql/manage.sql:719: ERROR: table "eventq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:720: ERROR: sequence "eventq_eventqid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:721: ERROR: table "eventqvar" does not exist psql:/usr/local/nav/doc/sql/manage.sql:748: ERROR: table "alertq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:749: ERROR: sequence "alertq_alertqid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:750: ERROR: table "alertqmsg" does not exist psql:/usr/local/nav/doc/sql/manage.sql:841: ERROR: table "alerthist" does not exist psql:/usr/local/nav/doc/sql/manage.sql:842: ERROR: sequence "alerthist_alerthistid_seq" does not exist psql:/usr/local/nav/doc/sql/manage.sql:843: ERROR: table "alerthistmsg" does not exist psql:/usr/local/nav/doc/sql/manage.sql:844: ERROR: table "alerthistvar" does not exist psql:/usr/local/nav/doc/sql/manage.sql:941: ERROR: table "service" does not exist psql:/usr/local/nav/doc/sql/manage.sql:942: ERROR: table "serviceproperty" does not exist psql:/usr/local/nav/doc/sql/manage.sql:943: ERROR: sequence "service_serviceid_seq" does not exist Have tried with postgresql 7.4/8.0 and 8.1, same error messages each time. -- Med vennlig hilsen / Regards; Roar Pettersen Universitetet i Bergen - The University of Bergen Nygardsgt. 5 - N-5020 BERGEN - Norway Tlf: +47 55 58 40 55 VIP: 81503 fax: +47 55 58 40 70 roar.pettersen(a)it.uib.no - IT-Avd, UiB - http://www.uib.no >From morten.vold at uninett.no Mon Jul 3 11:41:11 2006 From: morten.vold at uninett.no (Morten Vold) Date: Mon Jul 3 10:41:19 2006 Subject: [Nav-users] please help me In-Reply-To: <20060630014922.55933.qmail(a)web15907.mail.cnb.yahoo.com> References: <20060630014922.55933.qmail(a)web15907.mail.cnb.yahoo.com> Message-ID: <44A8D827.3080408(a)uninett.no> wenjun peng wrote: > the system shows: ImportError: cannot import psycopgmodule.so, the > request denied this made me go mad, I got so puzzled with it, I > thought maybe because I' m using psycopg2 instead of psycopg1, then > each time when this problem occured, I add this sentence into the > file: from psycopg2 import psycopg1 as psycopg Then the problem > solved. According to http://www.initd.org/tracker/psycopg/wiki/Migration, psycopg2 is not entirely backwards compatible with psycopg1. I cannot guarantee that NAV doesn't use features of psycopg1 that have changed in psycopg2, so I would say that you need to use psycopg1 only. > Now I can see webpages, but when I want to login as a user > named 'admin' , and using the ' admin ' as the password , the system > said no such name segment named 'admin' . "No such name segment"? Are you sure that's the exact error message you received, it sounds pretty fishy to me.. The default password of the admin user is 'admin', if that doesn't work for you, the problem is elsewhere. What do you see if you use psql to connect to the navprofiles database and issue the following SQL query: SELECT * FROM account WHERE login='admin'; You should see the account details for the admin account - the default password created at installation time will be visible in plaintext until you change it from the web interface. -- mvh Morten Vold UNINETT

1 0

psycopg2?
by wj_peng24＠yahoo.com.cn 03 Jul '06

03 Jul '06

I have installed the nav-3.0.1, instead of using psycopg1.x, I use psycopg2.0, in some configure files , it is written like this: import psycopg. then ,when I open the index page, it would say : No module named psycopg. if I change it to : from psycopg2 import psycopg1 as psycopg. then the problem will be fixed. I don't know wether it would effect the nav going well? Or the nav can only run under psycopg1? __________________________________________________ žÏ¿ì×¢²áÑÅ»¢³¬ŽóÈÝÁ¿Ãâ·ÑÓÊÏä? http://cn.mail.yahoo.comFrom odd.hauge at hiMolde.no Mon Jul 3 11:08:19 2006 From: odd.hauge at hiMolde.no (Hauge Odd Arne) Date: Mon Jul 3 10:09:36 2006 Subject: [Nav-users] Announcement: NAV 3.1.0 is out Message-ID: <8EEE7738AEDF6947B3E5508A0244D1C2A36A31(a)stam.himolde.no> Hi. I get som error messages from the 3.1.0.sql script. See below. - odd arne hauge Changing manage schema psql:3.1.0.sql:27: ERROR: column "defaultfreq" of relation "snmpoid" already exists psql:3.1.0.sql:32: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:33: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:34: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:35: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:36: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:37: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:38: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:39: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:40: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:41: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:42: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:43: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:44: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:51: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:56: ERROR: current transaction is aborted, commands ignored until end of transaction block Adding devBrowse as a subsystem to the event system psql:3.1.0.sql:59: ERROR: current transaction is aborted, commands ignored until end of transaction block Updating existing equipment types in your database psql:3.1.0.sql:62: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:63: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:64: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:65: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:66: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:67: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:68: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:69: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:70: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:71: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:72: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:73: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:74: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:75: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:76: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:77: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:78: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:79: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:80: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:81: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:82: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:83: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:84: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:85: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:86: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:87: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:88: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:89: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:90: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:91: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:92: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:93: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:94: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:95: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:96: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:97: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:98: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:99: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:100: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:101: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:102: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:103: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:104: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:105: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:106: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:107: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:108: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:109: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:110: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:111: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:112: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:113: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:114: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:115: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:116: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:117: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:118: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:119: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:120: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:121: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:122: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:123: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:124: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:125: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:126: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:127: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:128: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:129: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:130: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:131: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:132: ERROR: current transaction is aborted, commands ignored until end of transaction block psql:3.1.0.sql:133: ERROR: current transaction is aborted, commands ignored until end of transaction block Don't forget to run types.sql and snmpoid.sql to insert new vendors, types and snmp OIDs into your database ROLLBACK Granting rights to navread and navwrite for new tables. If you're running a setup without these users, you can safely ignore errors about their non-existance. nav_grant ----------- 97 (1 row) nav_grant ----------- 97 (1 row) You are now connected to database "navprofiles". BEGIN Adding new system account groups to the navprofiles database psql:3.1.0.sql:146: ERROR: duplicate key violates unique constraint "accountgroup_pk" ROLLBACK > -----Original Message----- > From: nav-users-bounces(a)itea.ntnu.no > [mailto:nav-users-bounces@itea.ntnu.no] On Behalf Of Morten Vold > Sent: Friday, June 30, 2006 4:15 PM > To: nav-users(a)itea.ntnu.no > Subject: [Nav-users] Announcement: NAV 3.1.0 is out > > NAV 3.1.0 is now available for download at SourceForge, see > http://sourceforge.net/projects/nav :-) > > Binary packages for Debian will be available at a later time. > The Debian package is maintained by Morten Werner Olsen. We > would also like someone to maintain the unofficial RPM > package, do we have any volunteers? > > This is mainly a feature release, we are still working on a > number of known bugs. We hope to see a 3.1.1 bugfix release > within a couple of months, and we've scheduled a 3.2 release > for October. > > I apologize to anyone who has not had their questions > answered these past couple of weeks - we've been very busy > preparing and attending this years's UNINETT conference, > which was held at ?lesund University College last week > (http://www.hials.no/uninett2006). Preparing this release > also took some time. I'll be answering any dangling requests > on the list just over the weekend. > > > > > -- > mvh > Morten Vold > UNINETT > > >

1 0

Announcement: NAV 3.1.0 is out
by morten.vold＠uninett.no 30 Jun '06

30 Jun '06

Skipped content of type multipart/mixed

1 0

please help me
by wj_peng24＠yahoo.com.cn 30 Jun '06

30 Jun '06

hello everyone, About 2 or 3 weeks ago, I wrote some letters , because I have got some problems about the web interface, and I found that I cannot login to the web, first, even the webpage cannot be shown in the browser, it shows the problem like this: No module named ..., but , in this root , I can find this module straightly, I don't understand why the system said like that, then I wrote a letter to the nav-user, but no one answer me. After a few days with no letter come , I did fix the problem, a new one coming, this time, the system shows: ImportError: cannot import psycopgmodule.so, the request denied this made me go mad, I got so puzzled with it, I thought maybe because I' m using psycopg2 instead of psycopg1, then each time when this problem occured, I add this sentence into the file: from psycopg2 import psycopg1 as psycopg Then the problem solved. Now I can see webpages, but when I want to login as a user named 'admin' , and using the ' admin ' as the password , the system said no such name segment named 'admin' . If I can't use ' admin ' as user, which usrname can I use? also the password? By the way, my OS is ferdora Core4 , and postgresql is 8.0.3, the Version of Nav is 3.0.1, version of Python is 2.4, Version of mod_python is 3.2.7, Version of psycopg is 2.0.2. Anything else you want to know about my OS if you can help me , please write to me. Can anyone who can help me please? --------------------------------- Mp3·è¿ñËÑ-ÐÂžèÈÈžèžßËÙÏÂ From sommerjobb at froisland.no Fri Jun 30 12:13:00 2006 From: sommerjobb at froisland.no (Marius =?iso-8859-1?Q?Fr=F8island?=) Date: Fri Jun 30 11:13:26 2006 Subject: [Nav-users] Tags shown instead of the page Message-ID: <WorldClient-F200606301113.AA13000040(a)froisland.no> I'v just installed nav on fedora 5, I follow the REHL4 installation guide, and everything work nicely. I'm able to start the server, status show that everything is running fine. the front page is displayed ok, but opening the login page in my browser I get the HTML code instead of the page. FRom the HTLM code it seems that HTML tag is missing. Should this have been parsed though something? Any idea of what is miss configured? This is the HTML tags as they are shown in the browser when I open the login page: <body onLoad="document.getElementById('username').focus();"> <table height=40% border=0 width=100%><tr valign=middle><td valign=middle align=center> <br><br><br> <font face=verdana size=1> <form method="POST" action="/index/login"> <img src="/images/login/navlogo.gif"><br> <br><font color=#FF0000>You are not authorized to access<br>/status/</font> <br><input id="username" type="text" name="login" style="border: 1px solid #99c;"><br><font color=#6699CC>username</font> <br><input type="password" name="password" style="border: 1px solid #99c;"><br><font color=#6699CC>password</font> <input type="hidden" name="origin" value="/status/"> <br><br><input type="submit" value="Log in"> </form> </font> </td></tr></table> </body>

1 0

The web problem
by wj_peng24＠yahoo.com.cn 22 Jun '06

22 Jun '06

hello everyone, This is Patrick here, when I start the nav, and I need to login to the web interface which webroot is :"/usr/local/nav/apache/webroot", but the web shows : Mod_python error: "PythonHeaderParserHandler nav.web" Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line 299, in HandlerDispatch result = object(req) File "/usr/local/nav/lib/python/nav/web/__init__.py", line 48, in headerparserhandler File "/usr/local/nav/lib/python/nav/web/auth.py", line 32, in ? File "/usr/local/nav/lib/python/nav/db/__init__.py", line 29, in ? import psycopg ImportError: /usr/lib/python2.4/site-packages/psycopgmodule.so: failed to map segment from shared object: Permission denied Can anyone who can help me get out of this problem please? --------------------------------- ÇÀ×¢ÑÅ»¢Ãâ·ÑÓÊÏä-3.5GÈÝÁ¿£¬20MžœŒþ£¡ From wj_peng24 at yahoo.com.cn Fri Jun 23 11:20:20 2006 From: wj_peng24 at yahoo.com.cn (wenjun peng) Date: Fri Jun 23 04:20:30 2006 Subject: [Nav-users] quesstion about the web interface Message-ID: <20060623022020.96085.qmail(a)web15905.mail.cnb.yahoo.com> hello, I am using Nav-3.0.1, and I installed both psycopg-1.1.21and psycopg2-2.0b8, when I start nav, it works , everything seems ok, but the web interface dosen't work, it shows the following thing as blew: Mod_python error: "PythonHeaderParserHandler nav.web" Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line 299, in HandlerDispatch result = object(req) File "/usr/local/nav/lib/python/nav/web/__init__.py", line 48, in headerparserhandler File "/usr/local/nav/lib/python/nav/web/auth.py", line 32, in ? File "/usr/local/nav/lib/python/nav/db/__init__.py", line 29, in ? import psycopg ImportError: /usr/lib/python2.4/site-packages/psycopgmodule.so: failed to map segment from shared object: Permission denied Is there any problem with the psycopg? Or there is other problems? This problem puzzled me for already 3 weeks, can anyone who can help me ? from Patrick 23rd Jun 2006 --------------------------------- Mp3·è¿ñËÑ-ÐÂžèÈÈžèžßËÙÏÂ From SLander at hearstsc.com Tue Jun 27 17:06:31 2006 From: SLander at hearstsc.com (SLander(a)hearstsc.com) Date: Tue Jun 27 22:02:31 2006 Subject: [Nav-users] Translate a log file? In-Reply-To: <20060622031019.19020.qmail(a)web15906.mail.cnb.yahoo.com> Message-ID: <OF16D0584B.FB5F02C2-ON8525719A.006D6B7D-8525719A.006E13C6(a)hearstsc.com> Could anyone translate these warnings to English? I am not sure what they are telling me. This is from the networkDiscovery-topology.html file Generated on: Tue Jun 27 14:35:03 EDT 2006 ---->[WARNING]: Boks(8): Floor28-6513-1, mer enn en link til boks(31) floor28-3750-4.home.com, uten at vi vet mp i andre enden. ---->[WARNING]: Boks(8): Floor28-6513-1, mer enn en link til boks(20) floor28-3.home.com, uten at vi vet mp i andre enden. ---->[WARNING]: Boks(8): Floor28-6513-1, mer enn en link til boks(20) floor28-3.home.com, uten at vi vet mp i andre enden. ---->[WARNING]: Boks(8): Floor28-6513-1, mer enn en link til boks(52) sc-bw-gw.home.com, uten at vi vet mp i andre enden. ---->[WARNING]: Boks(9): Floor28-6513-2, mer enn en link til boks(20) floor28-3.home.com, uten at vi vet mp i andre enden. ---->[WARNING]: Boks(9): Floor28-6513-2, mer enn en link til boks(20) floor28-3.home.com, uten at vi vet mp i andre enden. ---->[WARNING]: Boks(28): floor28srv-3.home.com, mer enn en link til boks(59) WDSU-UU-GW, uten at vi vet mp i andre enden. ---->[WARNING]: Boks(95): STAE-CORE-SW1, mer enn en link til boks(93) STAE-NEWS-SW1, uten at vi vet mp i andre enden. ---->[WARNING]: Boks(95): STAE-CORE-SW1, mer enn en link til boks(97) STAE-TRAFFIC-SW1, uten at vi vet mp i andre enden. ---->[WARNING]: Boks(95): STAE-CORE-SW1, mer enn en link til boks(93) STAE-NEWS-SW1, uten at vi vet mp i andre enden. ---->[WARNING]: Boks(95): STAE-CORE-SW1, mer enn en link til boks(97) STAE-TRAFFIC-SW1, uten at vi vet mp i andre enden. [WARNING] Conflicting boksbak in mp vs. mpBoksbak for Boks(9): Floor28-6513-2 Mp: 253 bmp: BoksMpBak [boksbak=8, toIfindex=null], bmpA: BoksMpBak [boksbak=38, toIfindex=51] [WARNING] Conflicting boksbak in mp vs. mpBoksbak for Boks(20): floor28-3.home.com Mp: 50 bmp: BoksMpBak [boksbak=8, toIfindex=84], bmpA: BoksMpBak [boksbak=9, toIfindex=71] [WARNING] Conflicting boksbak in mp vs. mpBoksbak for Boks(33): floor29-2.home.com Mp: 50 bmp: BoksMpBak [boksbak=8, toIfindex=37], bmpA: BoksMpBak [boksbak=9, toIfindex=53] [WARNING] Conflicting boksbak in mp vs. mpBoksbak for Boks(38): hsc30-2.home.com Mp: 50 bmp: BoksMpBak [boksbak=8, toIfindex=null], bmpA: BoksMpBak [boksbak=9, toIfindex=40] [Guess] Boks(8): Floor28-6513-1 Mp: 74 Boksbak(31): floor28-3750-4.home.com [Guess] Boks(8): Floor28-6513-1 Mp: 266 Boksbak(31): floor28-3750-4.home.com Also, still having a problem with viewing rrd files from within report, where the URL is something like: http://navhost/browse/rrd/datasources?id=7099& I get back a blank screen. I have found that a file is created in /tmp - the above created a file /tmp/rrd_764614789.gif. But - it appears NAV is not associating the file rrd_764614789.gif with the id 7099 in the above URL.. Also, in the apache error log there will be an error: [Tue Jun 27 15:53:55 2006] [notice] child pid 14045 exit signal Segmentation fault (11) Can anyone point me in a direction to look? I am wondering if this is something as simple as the graph file being generated in /tmp, and what ever displays it expecting the file to be somewhere else? Thanks Scott This e-mail message is intended only for the personal use of the recipient(s) named above. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify the Hearst Service Center (cadmin(a)hearstsc.com) immediately by email and delete the original message. >From sommerjobb at froisland.no Thu Jun 29 10:05:52 2006 From: sommerjobb at froisland.no (Marius =?iso-8859-1?Q?Fr=F8island?=) Date: Thu Jun 29 09:08:37 2006 Subject: [Nav-users] Could not connect to servlet in network explorer Message-ID: <WorldClient-F200606290905.AA05520037(a)froisland.no> Opening network explorer I get the following error, I just installed the software and am at a loss for what is wrong with my installation. Current path: Home > Network explorer Could not connect to servlet Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/nav/web/pyproxy/proxy.py", line 61, in handler user=user, session=req.session.id) File "/usr/lib/python2.3/site-packages/nav/web/pyproxy/proxy.py", line 124, in doRequest request.request(method, path, query, headers) File "/usr/lib/python2.3/httplib.py", line 721, in request self._send_request(method, url, body, headers) File "/usr/lib/python2.3/httplib.py", line 742, in _send_request self.endheaders() File "/usr/lib/python2.3/httplib.py", line 715, in endheaders self._send_output() File "/usr/lib/python2.3/httplib.py", line 600, in _send_output self.send(msg) File "/usr/lib/python2.3/httplib.py", line 567, in send self.connect() File "/usr/lib/python2.3/httplib.py", line 551, in connect raise socket.error, msg error: (111, 'Connection refused')

1 0

questions about the nav
by wj_peng24＠yahoo.com.cn 08 Jun '06

08 Jun '06

dear Sir/Madam, I am Patrick, from China, I don't know wether I should send this mail to you or not? I just want to ask a question about the nav. I download NAV3.0.1 from the website, and I think I have already installed this software in my OS(Fedora core 4). I configured everything ( include the apache ) And I started the httpd, tomcat5, postgresql, after I run " nav start " , everything seems ok, then ,what should I do in the following. I have checked the introduction on the web, it said I should go to the web ,which served by my apache server,to login, named as "admin", and also use the password as "admin" for the first time. Then I got puzzled, I don't understand, when I checked the root: /usr/local/nav/apache/webroot, ( the introduction told me to set the document root of apache to "/usr/local/nav/apache/webroot",and I did it.) but I can't find any webpage in this dirctory, there is only one file named index, and it's full name is index.py, is it supposed to be the NAV frontpage? Please help me to get out of this trouble, and tell me what to do next? Thanks very much. Patrick 8th JUN 2006 __________________________________________________ žÏ¿ì×¢²áÑÅ»¢³¬ŽóÈÝÁ¿Ãâ·ÑÓÊÏä? http://cn.mail.yahoo.comFrom morten.vold at uninett.no Fri Jun 9 11:08:47 2006 From: morten.vold at uninett.no (Morten Vold) Date: Fri Jun 9 10:08:55 2006 Subject: [Nav-users] Bleeding edge In-Reply-To: <8EEE7738AEDF6947B3E5508A0244D1C290E853(a)stam.himolde.no> References: <8EEE7738AEDF6947B3E5508A0244D1C290E853(a)stam.himolde.no> Message-ID: <44892C8F.8060501(a)uninett.no> Hauge Odd Arne wrote: > Following line in db.conf is missing in the latest svn build: > "script_arnold = nav" That's the way of the trunk ;) Fixed now, thanks for noticing! -- mvh Morten Vold UNINETT

1 0

mailin - a NAV contrib
by vidar.faltinsen＠uninett.no 07 Jun '06

07 Jun '06

Hi, We realize that there is a quite well hidden contrib to NAV out there that is worthy a better advertisement. Mailin is implemented by Andreas Solberg at UNINETT; MailIn is a subsystem of NAV, which receives an e-mail at stdin, find an appropriate parser for the current mail, and post an event to the NAV system. The parsers are created using a plugin architecture. Each parser is a class placed in the plugins/ folder, and inherits from EventSystem. Read more on: http://drift.uninett.no/~andreas/mailin/ We will link to this page from metanav soon... - Vidar

1 0

***SPAM*** Cricket compilation error in debian
by gsri11＠yahoo.co.in 06 Jun '06

06 Jun '06

Hi, Thanks for your reply.I am sending the details as follows $gCricketHome = "/usr/share/nav/cricket"; $gInstallRoot = "$gCricketHome/cricket"; #$gConfigRoot = "$gCricketHome/cricket-config"; Best Regards Morten Vold <morten.vold(a)uninett.no> wrote: rajesh wrote: > Edit the cricket-conf.pl and set these variables: > $gCricketHome = "/usr/share/nav/cricket"; > > $ /usr/lib/nav/makecricketconfig.pl > No path to Cricket specified, searching default paths... > Searching in /home/navcron/cricket. > Searching in /usr/local/cricket. > Found cricket in /usr/local/cricket. > Use of uninitialized value in concatenation (.) or string at /usr/lib/nav/makecricketconfig.pl line 82. > Can't locate ConfigTree/Cache.pm in @INC (@INC contains: /lib /etc/perl /usr/local/lib/perl/5.8.4 /usr/local/share/perl/5.8.4 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/lib/nav/makecricketconfig.pl line 84. > BEGIN failed--compilation aborted at /usr/lib/nav/makecricketconfig.pl line 84. > > I am looking forward where i am doing wrong. Rajesh, what are the next few variables after $gCricketHome in your cricket-conf.pl set to? Makecricketconfig is complaining that it cannot find some Cricket libraries, the specific library it can't find should (in your case) be located at /usr/local/cricket/cricket/lib/ConfigTree/Cache.pm -- mvh Morten Vold UNINETT --------------------------------- Yahoo! India Answers: Share what you know. Learn something new Click here Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now >From SLander at hearstsc.com Tue Jun 6 18:01:46 2006 From: SLander at hearstsc.com (SLander(a)hearstsc.com) Date: Tue Jun 6 22:58:05 2006 Subject: [Nav-users] Trouble with Scope In-Reply-To: <OFA6A1AC20.C23003E0-ON85257184.005E0BEE-85257184.00627BF6@LocalDomain> Message-ID: <OFAA55B1D8.37132614-ON85257185.00730A26-85257185.00732B26(a)hearstsc.com> When I try to view scope (reports -> IP Address scope - Graphical View) I get: Mod_python error: "PythonHandler reporthandler" Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line 299, in HandlerDispatch result = object(req) File "/usr/local/nav/apache/webroot/report/reporthandler.py", line 122, in handler matrix = Matrix(databasescopes[0][0]) File "/usr/lib/python2.4/site-packages/Numeric/Matrix.py", line 69, in __init__ data = _convert_from_string(data) File "/usr/lib/python2.4/site-packages/Numeric/Matrix.py", line 36, in _convert_from_string newrow.extend(map(_eval,temp)) File "/usr/lib/python2.4/site-packages/Numeric/Matrix.py", line 24, in _eval return eval(astr.translate(_table,_todelete)) File "", line 1 10.152.36.024 ^ SyntaxError: invalid syntax I think it is stumbling on readding the cidr address (10.152.36.0/24), but, I can't not add the /xx as that gets added automatically when adding a prefix. What am I doing wrong? Other then that, and that I can't yet display the traffic map (starts java and hangs my browser! - Only way to clear it is to kill the browser via taskman) I now hav NAV running on Suse 10.0. So far, so good. Thanks all This e-mail message is intended only for the personal use of the recipient(s) named above. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify the Hearst Service Center (cadmin(a)hearstsc.com) immediately by email and delete the original message. >From wj_peng24 at yahoo.com.cn Wed Jun 7 11:21:32 2006 From: wj_peng24 at yahoo.com.cn (wj_peng24(a)yahoo.com.cn) Date: Wed Jun 7 10:22:11 2006 Subject: [Nav-users] (Saksnummer:319759) questions about the NAV Message-ID: <20060607060901.24726.qmail(a)web15903.mail.cnb.yahoo.com> Videresendt til nav-users(a)itea.ntnu.no ----------------------------------------------- 2006-06-07 08:10:06: wenjun peng dear Sir/Madam, I am Patrick, from China, I download NAV3.0.1 from the website, and I think I have already installed this software in my OS(Fedora core4). I configured everything( include the apache) And I started the httpd, tomcat5, postgresql, after I run " nav start ", everything seems ok, then ,what should I do in the following. I have checked the introduction on the web, it said I should go to the web ,which served by my apache server,to login, named as "admin", and also use the password of "admin" for the first time. Then I got puzzled, I don't understand, when I checked the root: /usr/local/nav/apache/webroot,( the introduction told me to set the document root of apache to "/usr/local/nav/apache/webroot",and I did it.) but I can't find any webpage in this dirctory, there is only one file named index, and it's full name is index.py, and there is another file named usradmin.py, others are all directories, what wrong with the frontpage? Please help me to get out of this trouble, and tell me what to do next? where should I login in the webpage? Thanks very much. Patrick 7th JUN 2006 __________________________________________________ ????????????????????????????? http://cn.mail.yahoo.com -----------------------------------------------

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users