Nav-users

nav-users@lister.sikt.no

3 participants
1372 discussions

mod_python error and InterfaceError: connection already closed
by Ted 08 Mai '13

08 Mai '13

I've been running NAV (3.14.15 on Debian appliance) for a few weeks without any issues but recently I started getting errors when running the Layer 2 trace tool. I tried upgrading but I guess the package for Debian hasn't been released yet... Any suggestions would be appreciated. Thank you. The error message is below: MOD_PYTHON ERROR ProcessId: 1023 Interpreter: 'nav-appliance.uninett.no' ServerName: 'nav-appliance.uninett.no' DocumentRoot: '/usr/share/nav/htdocs' URI: '/l2trace/' Location: '/' Directory: None Filename: '/usr/share/nav/htdocs/l2trace' PathInfo: '/' Phase: 'PythonHandler' Handler: 'django.core.handlers.modpython' Traceback (most recent call last): File "/usr/lib/python2.6/dist-packages/mod_python/importer.py", line 1537, in HandlerDispatch default=default_handler, arg=req, silent=hlist.silent) File "/usr/lib/python2.6/dist-packages/mod_python/importer.py", line 1229, in _process_target result = _execute_target(config, req, object, arg) File "/usr/lib/python2.6/dist-packages/mod_python/importer.py", line 1128, in _execute_target result = object(arg) File "/usr/lib/pymodules/python2.6/django/core/handlers/modpython.py", line 228, in handler return ModPythonHandler()(req) File "/usr/lib/pymodules/python2.6/django/core/handlers/modpython.py", line 208, in __call__ signals.request_finished.send(sender=self.__class__) File "/usr/lib/pymodules/python2.6/django/dispatch/dispatcher.py", line 162, in send response = receiver(signal=self, sender=sender, **named) File "/usr/lib/pymodules/python2.6/django/db/__init__.py", line 84, in close_connection conn.close() File "/usr/lib/pymodules/python2.6/django/db/backends/__init__.py", line 70, in close self.connection.close() InterfaceError: connection already closed

2 1

Bruk av NAV og uheldige konsekvenser for Cisco-utstyr
by Inge Bjørnvall Arnesen 07 Mai '13

07 Mai '13

Hei, Takk for et glitrende program! Jeg har testkjørt dette hos oss i et halvårs tid, men sliter med et alvorlig og et mindre alvorlig problem: 1: Cisco ASA. Vi bruker denne serien ganske mye og i de fleste tilfeller fungerer NAV bra. Mot bokser som har 10-30 VLAN ser det ut til å gå som det skal. På bokser med mange VLAN (128+) får vi derimot en feil på SNMP-tasken hvert kvarter: 2013-05-02T11:27:18.100301+02:00 XXX <164>May 02 2013 11:27:18: %ASA-4-711004: Task ran for 150 msec, Process = snmp, PC = 8c4b7c8, Call stack = 2013-05-02T11:27:18.100301+02:00 XXX <164>May 02 2013 11:27:18: %ASA-4-711004: Task ran for 150 msec, Process = snmp, PC = 8c4b7c8, Call stack = 0x08B70783 0x08B50B1D 0x08B4F87C 0x08063B63 2013-05-02T11:27:18.100311+02:00 XXX <164>May 02 2013 11:27:18: %ASA-4-711004: Task ran for 152 msec, Process = snmp, PC = 8b77990, Call stack = 2013-05-02T11:27:18.100311+02:00 XXX <164>May 02 2013 11:27:18: %ASA-4-711004: Task ran for 152 msec, Process = snmp, PC = 8b77990, Call stack = 0x08B77990 0x08B76699 0x08B734A9 0x08B75F48 0x08B50E0E 0x08B4F87C 0x08063B63 2013-05-02T11:27:23.113341+02:00 XXX <164>May 02 2013 11:27:23: %ASA-4-711004: Task ran for 150 msec, Process = snmp, PC = 8b7772e, Call stack = 2013-05-02T11:27:23.113417+02:00 XXX <164>May 02 2013 11:27:23: %ASA-4-711004: Task ran for 150 msec, Process = snmp, PC = 8b7772e, Call stack = 0x08B7772E 0x08B7645B 0x08B734A9 0x08B75F48 0x08B50E0E 0x08B4F87C 0x08063B63 Melding ASA-4-711004 gir beskjed om at en task er et "CPU Hog", noe som kan få alvorlige konsekvenser tradisjonelle ASA-bokser (pre-SMP). Når dette skjer, vil nodene i ASA-klyngen oppleve pakketap og vil nodene vil kunne miste kontakten med hverandre både på inn og utsiden. Det siste ser ut til å være avhengig av den øvrige CPU-belastningen i øyeblikket. 2013-05-02T11:27:28.147580+02:00 XXX <161>May 02 2013 11:27:28: %ASA-1-105005: (Secondary) Lost Failover communications with mate on interface YYY 2013-05-02T11:27:28.147628+02:00 XXX <161>May 02 2013 11:27:28: %ASA-1-105008: (Secondary) Testing Interface YYY 2013-05-02T11:27:28.349692+02:00 XXX <161>May 02 2013 11:27:28: %ASA-1-105009: (Secondary) Testing on interface YYY Passed 2013-05-02T11:27:33.263707+02:00 XXX <161>May 02 2013 11:27:33: %ASA-1-105005: (Secondary) Lost Failover communications with mate on interface outside 2013-05-02T11:27:33.416249+02:00 XXX <161>May 02 2013 11:27:33: %ASA-1-105008: (Secondary) Testing Interface outside 2013-05-02T11:27:33.726430+02:00 XXX <161>May 02 2013 11:27:33: %ASA-1-105009: (Secondary) Testing on interface outside Passed Er dette et kjent problem? Mulig det er tilfeldig, men jeg fikk samme problem når jeg forsøkte noen SNMP bulk-transfers. 2: Cisco switcher. Her får vi en feilmelding fra samtlige switcher hvert kvarter. Meldingen er noe obskur: "2013-05-01T00:04:36.711253+02:00 ZZZ <132>266532: 147851: May 1 00:04:36.638 MEST: %BIT-4-OUTOFRANGE: bit 0 is not in the expected range of 1 to 4094" med hilsen, -- Inge Arnesen

2 1

Announcement: NAV 3.14.1592 released
by Morten Brekkevold 25 Apr '13

25 Apr '13

NAV 3.14.159, another release of the endless NAV 3.14 series is now available for download at Launchpad: https://launchpad.net/nav/3.14/3.14.159 The release fixes the following reported issues: * LP#1155128 (IndexError crash in Machine Tracker) * LP#1158214 (mcc.py does debug logging even when configured not to) * LP#1160921 (Geomap won't load map data over HTTPS in Chrome) * LP#1161108 (Room bulk import format doesn't include geo position) * LP#1163256 (snmptrapd crashes with "interrupted system call" error) * LP#1164582 (netmap bails on fetching network graph if interface.speed missing) * LP#1165017 (Adding 0.0.0.0/0 as excepted range causes netbiostracker to hang) Please report bugs at https://launchpad.net/nav/+filebug Binary packages for Debian will be made available as soon as possible. The Debian package is maintained by Morten Werner Forsbring, on commission from UNINETT. Some people have experienced that the Debian package upgrade seems to freeze. While the NAV backend services are shut down during an upgrade, parts of NAV are still running inside Apache, and may hold on to database locks. This may prevent the package upgrade from updating the database schema - in such a case, restarting Apache from another terminal should unfreeze the upgrade. Happy NAVing everyone! -- John-Magne Bredal UNINETT AS

1 1

Single device configurations
by Bruno Galindro da Costa 15 Apr '13

15 Apr '13

Guys, is it possible to configure NAV to: 1 - ignore a single or a range of devices to be ignored from the polling process? I think this will be possible when we put it in maintenance mode. I'm right? 2 - apply per device ipdevpool's plugins intervals? According to docs, its is possible to set intervals for all devices but I hope that exists some other "hide" config to do that :) -- Att. Bruno Galindro da Costa

2 6

Announcement: NAV 3.14.159 released
by John-Magne Bredal 11 Apr '13

11 Apr '13

1 0

rsyslog, logger.conf and cisco devices
by Ted 10 Apr '13

10 Apr '13

I am running NAV ver. 3.14.15 (downloaded the virtual appliance and did an upgrade) but I am unable to get the syslog part to work (as well as cricket but that I am still researching) The original logger.conf points to /var/lib/nav/log/cisco.log - shouldn't that point to /var/log/nav? Anyway I changed that to point to /var/log/messages I also had to enable in rsyslog.conf to receive UDP messages by uncommenting the lines $ModLoad imudp and $UDPServerRun 514. When I do tail -f /var/log/messages I can see that the Cisco switches are sending messages. If I try to pull up the syslog messages through NAV however it tells me that there are no messages. Any pointers would be greatly appreciated.

2 1

Netmap - link colors
by Bruno Galindro da Costa 02 Apr '13

02 Apr '13

Hi! Which is the premisse for netmap colorize the link between two devices? What is the meaning of grey's link color? I'm wondering this because from yesterday to today, the links between my devices changed from green to grey... -- Att. Bruno Galindro da Costa

2 3

Unmanaged devices
by Bruno Galindro da Costa 02 Apr '13

02 Apr '13

Hi! Question 1: Is it possible to change the device type? I know this information is gathered from device, but when the device has no snmp support, but only an ip address (like a printer), I need to specify it's type in the system to built more detailed and consistent reports. Question 2: How can I insert an unmanaged switch or hub in NAV? I need this because I want to know where this kind of devices are inserted in our network to planning a future replacement of it. Question 3: Where I can change the netmap device icons? The device icon is related to type or category? Would be great if it where possible to change the device's icon to reflect it's model. Hi! -- Att. Bruno Galindro da Costa

2 1

Announcement: NAV 3.14.15 released
by Morten Brekkevold 24 Mar '13

24 Mar '13

NAV 3.14.15, the first maintenance release of the NAV 3.14 series is now available for download at Launchpad: https://launchpad.net/nav/3.14/3.14.15 The 3.14.15 fixes the following reported issues: * LP#1152173 (Deleting rrdviewer.conf causes crash when attempting to view graphs from ipdevinfo) * LP#1152599 (VLANs periodically lose one or more prefixes) * LP#1154626 (Threshold bulk config UI unresponsive, with javascript console error) * LP#1155096 (Filtering by category in syslog analyzer doesn't work) * LP#1156647 (Topology is not cleared when ports are shut down) * LP#1157154 (Netmap stopped working in NAV 3.14.1) * LP#1157594 (netbiostracker crashes when a netbios host reports an empty mac address) * LP#1157658 (Failing ipdevpoll plugin should be identified in log messages at the ERROR level) Please report bugs at https://launchpad.net/nav/+filebug :-) Binary packages for Debian will be made available as soon as possible. The Debian package is maintained by Morten Werner Forsbring, on commission from UNINETT. Some people have experienced that the Debian package upgrade seems to freeze. While the NAV backend services are shut down during an upgrade, parts of NAV are still running inside Apache, and may hold on to database locks. This may prevent the package upgrade from updating the database schema - in such a case, restarting Apache from another terminal should unfreeze the upgrade. Happy NAVing everyone! -- Morten Brekkevold UNINETT

2 1

Netmap broken in 3.14.1
by Corey Thompson 21 Mar '13

21 Mar '13

Just updated the Debian package to from 3.13.1 to 3.14.1 and netmap appears to no longer work, just the spinning wheel. Anyone else experiencing this? Haven't looked much further into it yet, but save myself some time if others have noticed the problem and have a solution. Also, (again, I haven't had time to look closely at it yet) is there a way to configure the geomap to plot only physical layer-2 connections? It is plotting vl1 connections to root hub along with the physical connections. Thanks for any assistance in advance, and I'll report if I find anything. -- Corey Thompson Technology Manager East Grand Forks Water and Light 1010 5th Ave NE East Grand Forks, MN 56721 218-399-3310 cthompson(a)egf.mn

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users