Nav-users Juli 2006

nav-users@lister.sikt.no

9 participants
15 discussions

Editdb error
by Jan.Susegg＠hint.no 03 Jul '06

03 Jul '06

I have upgraded to NAV 3.1.0 and I got a problem with accessing EDITDB Mod_python error: "PythonHandler editdb" Traceback (most recent call last): File "/usr/lib/python2.2/site-packages/mod_python/apache.py", line 287, in HandlerDispatch log=debug) File "/usr/lib/python2.2/site-packages/mod_python/apache.py", line 457, in import_module module = imp.load_module(mname, f, p, d) File "/usr/local/nav/apache/webroot/editdb/editdb.py", line 29, in ? import editTables,nav.Snmp,sys,re,copy,initBox,forgetSQL,nav.web File "/usr/local/nav/lib/python/nav/Snmp.py", line 33, in ? from pysnmp import role, v1, v2c, asn1 ImportError: cannot import name role Can anyone tell me how to solve this problem? best regards Jan Susegg North-Trondelag University College >From kreide at gmail.com Mon Jul 3 15:26:46 2006 From: kreide at gmail.com (Kristian Eide) Date: Mon Jul 3 14:26:51 2006 Subject: [Nav-users] Announcement: NAV 3.1.0 is out In-Reply-To: <44A8D9E2.6070700(a)uninett.no> References: <8EEE7738AEDF6947B3E5508A0244D1C2A36A31(a)stam.himolde.no> <44A8D9E2.6070700(a)uninett.no> Message-ID: <b4c110fd0607030526s6ad2e098pacb80842a69cbed0(a)mail.gmail.com> > So the tricky part now is to figure out which changes you've already > included in your database, and which ones you may have overlooked NAV really needs to get a proper version system for its schema changes or it will be very hard to manage such changes in any reasonable way (manually creating sql patch scripts is not the way to go). -- Kristian >From roar.pettersen at uib.no Mon Jul 3 15:45:17 2006 From: roar.pettersen at uib.no (Roar Pettersen) Date: Mon Jul 3 14:45:22 2006 Subject: [Nav-users] Editdb error In-Reply-To: <8A65B72C71E7484FBE1862045AAC5A8FB73D20(a)embla.ansatt.hint.no> References: <8A65B72C71E7484FBE1862045AAC5A8FB73D20(a)embla.ansatt.hint.no> Message-ID: <Pine.SOC.4.64.0607031442450.1934(a)alf.uib.no> Hello ! > Can anyone tell me how to solve this problem? I had exacly the same problem. :-) You have a missmatch in the pysnmp library when you downgraded from pysnmp-3.3.5 to 2.0.8. My solution was to delete /usr/local/lib/python2.4/site-packages/pysnmp/ and install the pysnmp-2.0.8 again. -- 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 15:51:23 2006 From: morten.vold at uninett.no (Morten Vold) Date: Mon Jul 3 14:51:33 2006 Subject: [Nav-users] Announcement: NAV 3.1.0 is out In-Reply-To: <b4c110fd0607030526s6ad2e098pacb80842a69cbed0(a)mail.gmail.com> References: <8EEE7738AEDF6947B3E5508A0244D1C2A36A31(a)stam.himolde.no> <44A8D9E2.6070700(a)uninett.no> <b4c110fd0607030526s6ad2e098pacb80842a69cbed0(a)mail.gmail.com> Message-ID: <44A912CB.1050904(a)uninett.no> Kristian Eide wrote: > NAV really needs to get a proper version system for its schema > changes or it will be very hard to manage such changes in any > reasonable way (manually creating sql patch scripts is not the way to > go). Interesting observation, Kristian, but your advice isn't very helpful without any examples or concrete ideas. What, in your opinion, is a "proper version system for schema changes"? My take on this is that schema changes are relatively few and far apart in NAV today. Therefore I don't see the need to invest a lot of time into devising some elaborate system to avoid having to manually write sql patch scripts. My suggestions is rather to implement a project policy to commit patch scripts along with any schema alterations. That way, a poor release coordinator (me) won't have to piece together every schema change that took place since the last release, and produce a whopping mishmash of hopefully consistent SQL upgrade statements on each release. Also, this should solve the problem for the few who might be using bleeding edge code from trunk at all times. They might not all be SQL wizards, able to analyze the changes and whip up their own SQL statements to change the schema, but each revision that updates the schema will come with an up-to-date upgrade script. We've never claimed that tracking the development trunk should be a piece-of-cake, though. -- mvh Morten Vold UNINETT

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users Juli 2006