Hello !

Mod_python error: "PythonHandler mod_python.publisher"

Traceback (most recent call last):

File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 299, in HandlerDispatch result = object(req)

File "/usr/lib/python2.3/site-packages/mod_python/publisher.py", line 98, in handler path=[path])

File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 454, in import_module f, p, d = imp.find_module(parts[i], path)

ImportError: No module named index

You have to make a file called .htaccess, eg : echo "SetHandler none" > .htaccess This should be in a FAQ, very easy to forget. :-) -- 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@it.uib.no - IT-Avd, UiB - http://www.uib.no

From fredrik.holmberg at luh.hihm.no Fri Mar 11 15:05:40 2005 From: fredrik.holmberg at luh.hihm.no (Fredrik Holmberg) Date: Fri Mar 11 15:05:44 2005 Subject: [Nav-users] error when accessing cricket.. In-Reply-To: <Pine.GSO.4.61.0503111449220.20340@alf.uib.no> References: <42319FE6.2070506@luh.hihm.no> <Pine.GSO.4.61.0503111449220.20340@alf.uib.no> Message-ID: <4231A5B4.8080707@luh.hihm.no>

Creating .htaccess in "public_html" solved the problem. Thanks! - Fredrik Roar Pettersen wrote:

Hello !

...

Mod_python error: "PythonHandler mod_python.publisher"

Traceback (most recent call last):

File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 299, in HandlerDispatch result = object(req)

File "/usr/lib/python2.3/site-packages/mod_python/publisher.py", line 98, in handler path=[path])

File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 454, in import_module f, p, d = imp.find_module(parts[i], path)

ImportError: No module named index

You have to make a file called .htaccess, eg :

echo "SetHandler none" > .htaccess

This should be in a FAQ, very easy to forget. :-)

-- 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@it.uib.no - IT-Avd, UiB - http://www.uib.no

From TristanRhodes at weber.edu Fri Mar 11 09:13:49 2005 From: TristanRhodes at weber.edu (Tristan RHODES) Date: Fri Mar 11 17:12:18 2005 Subject: [Nav-users] Use SNMP::Info to manage device types? Message-ID: <s2316158.051@gwmta2.weber.edu>

The developer list is closed, so I am would like ask a question to this list. I believe there is a way to manually add device types to NAV, and there is a Wiki page listing many device OIDs. This works, but it may be a duplication of effort. There is a perl module named SNMP::Info that provides an object-oriented interface to Network Devices and data stored in SNMP MIBs. http://snmp-info.sourceforge.net/ If this module could be integrated into NAV, many different network management projects can add devices to this module, and all will benefit from it. Any thoughts on this? Tristan Rhodes

From TristanRhodes at weber.edu Fri Mar 11 09:35:19 2005 From: TristanRhodes at weber.edu (Tristan RHODES) Date: Fri Mar 11 17:33:40 2005 Subject: [Nav-users] Suse Linux Enterprise Server (SLES) 9 install documentation? Message-ID: <s231665d.085@gwmta2.weber.edu>

I read in the wiki that SLES is used at NTNU and documentation will be available shortly. Is there any way I can help out with this? I can test the install process and make suggestions. http://metanav.ntnu.no/moin.cgi/NAVInstallation "SuSE Linux Enterprise Server The current NTNU installation of NAV is up and running on SLES 9. Installation instructions will be made available shortly." Tristan Rhodes

From peder.sefland at hivolda.no Mon Mar 14 11:26:35 2005 From: peder.sefland at hivolda.no (Peder Magne Sefland) Date: Mon Mar 14 11:27:07 2005 Subject: [Nav-users] periodic misslink in message-system for nav3 Message-ID: <s2357507.093@HVO-3.hivolda.no>

When I try to add or edit a message, very often I get the Syslog-page. But if I go back and try again, I might get det right message-page. Peder Sefland

From woj at tstd.pl Mon Mar 14 11:37:27 2005 From: woj at tstd.pl (Wojciech Kozicki) Date: Mon Mar 14 11:37:44 2005 Subject: [Nav-users] Use SNMP::Info to manage device types? In-Reply-To: <s2316158.051@gwmta2.weber.edu> References: <s2316158.051@gwmta2.weber.edu> Message-ID: <200503141137.28354.woj@tstd.pl>

On Friday 11 of March 2005 17:13, Tristan RHODES wrote:

The developer list is closed, so I am would like ask a question to this list.

I believe there is a way to manually add device types to NAV, and there is a Wiki page listing many device OIDs. This works, but it may be a duplication of effort.

There is a perl module named SNMP::Info that provides an object-oriented interface to Network Devices and data stored in SNMP MIBs.

http://snmp-info.sourceforge.net/

If this module could be integrated into NAV, many different network management projects can add devices to this module, and all will benefit from it.

Any thoughts on this?

In my opinion main NAV problem is, that it is not flexible, there is no interface for adding custom devices. I was writing about this, but there is no feedback. Tristan's idea is very good. regards. -- Wojciech (Woj) Kozicki

From magnus at ntnu.no Mon Mar 14 13:35:21 2005 From: magnus at ntnu.no (Magnus Nordseth) Date: Mon Mar 14 13:35:24 2005 Subject: [Nav-users] Use SNMP::Info to manage device types? In-Reply-To: <200503141137.28354.woj@tstd.pl> References: <s2316158.051@gwmta2.weber.edu> <200503141137.28354.woj@tstd.pl> Message-ID: <20050314123521.GC12721@stud.ntnu.no>

Wojciech Kozicki:

In my opinion main NAV problem is, that it is not flexible, there is no interface for adding custom devices. I was writing about this, but there is no feedback.

The SNMP::Info module is probably cool, but as the SNMP handling in NAV is written in java, it doesn't help us much. You can add support for device foo in NAV by writing a device handler in getDeviceData subsystem, which shouldn't be too difficult, I suggest using one of the existing handlers as a starting point. Best regards, -- Magnus Nordseth echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc

From Vegard.Vesterheim at uninett.no Mon Mar 14 14:22:48 2005 From: Vegard.Vesterheim at uninett.no (Vegard Vesterheim) Date: Mon Mar 14 14:22:53 2005 Subject: [Nav-users] Use SNMP::Info to manage device types? In-Reply-To: <20050314123521.GC12721@stud.ntnu.no> (Magnus Nordseth's message of "Mon, 14 Mar 2005 13:35:21 +0100") References: <s2316158.051@gwmta2.weber.edu> <200503141137.28354.woj@tstd.pl> <20050314123521.GC12721@stud.ntnu.no> Message-ID: <tkvf7u745z.fsf@voll.uninett.no>

On Mon, 14 Mar 2005 13:35:21 +0100 Magnus Nordseth <magnus@ntnu.no> wrote:

Wojciech Kozicki:

...

In my opinion main NAV problem is, that it is not flexible, there is no interface for adding custom devices. I was writing about this, but there is no feedback.

The SNMP::Info module is probably cool, but as the SNMP handling in NAV is written in java, it doesn't help us much.

I don't know enough details about the NAV database, but I would assume that alternative methods for harvesting SNMP data for insertion into the NAV database would be possible. Wouldn't it? List of devices supported by SNMP::Info: http://snmp-info.sourceforge.net/DeviceMatrix.html BTW, people taking interest in the SNMP::Info package should also be aware of the netdisco application (http://netdisco.org) for which SNMP::Info was created. netdisco is an application similar to NAV in many respects. It is implemented solely in perl, has auto-discovery capabilities, has a full-fledged API for extensions, the main interface is web-based but a command line interface is provided as well. A nifty functionality is layer 2 traceroute which displays switch port details along one possible route between two IP adresses. netdisco also provides a 'Duplex Mismatch Finder'. The web interface in netdisco is more basic, nowhere near as slick as NAV, but I guess some ideas from netdisco could be incorporated into NAV. - Vegard -

From fredrik.holmberg at luh.hihm.no Mon Mar 14 15:40:38 2005 From: fredrik.holmberg at luh.hihm.no (Fredrik Holmberg) Date: Mon Mar 14 15:43:54 2005 Subject: [Nav-users] " ... violates foreign key constraint "$1" Message-ID: <4235A266.7030309@luh.hihm.no>

Keep getting these messages in getDeviceData.log: Mar 14 15:21:37 2005 xxx-gw.uninett.no_01 GwportHandler-6-NEW GWPORTPREFIX Gwportprefix: gwip=128.39.xxx.xxx hsrp=false prefix=128.39.xxx.xxx/32 (0) (e1ca74) Mar 14 15:21:37 2005 xxx-gw.uninett.no_01 GwportHandler-3-HANDLE SQLException: ERROR: insert or update on table "gwportprefix" violates foreign key constraint "$1" Does anyone know of a way to fix this, or doesn't it have any particular effect on NAV3 (beta 10)? - Fredrik Holmberg

From kreide at online.no Mon Mar 14 16:02:01 2005 From: kreide at online.no (Kristian Eide) Date: Mon Mar 14 16:02:09 2005 Subject: [Nav-users] Use SNMP::Info to manage device types? Message-ID: <42367F67@epostleser.online.no>

In my opinion main NAV problem is, that it is not flexible, there is no interface for adding custom devices. I was writing about this, but there is no feedback.

In fact, NAV is meant to be very flexible! New OIDs can be added via the web interface, and NAV will automatically detect which devices support the new OIDs. Data collection is done by the 'getDeviceData' daemon, which uses a plugin-based architecture. The API for this is resonably well documented in Javadoc, however, it is a fact that familiarity with Java programming is required in order to create new collection plugins. Unfortunately it also seems many system administrators are much more familiar with script languages and the barrier to entry is thus high. Creating a perl binding which focused on easy of development would solve this problem, but it is of now uncertain if resources are available to implement something like this. We will discuss it internally and announce any decision this list. -- Kristian