Nav-users

nav-users@lister.sikt.no

1373 discussions

FW: Version 5.0.5 Widgets missing
by Marzec, Sebastian 19 Aug '20

19 Aug '20

Hello, I have NAV installation installed from packages on Debian system, I have installed Version 5.0.0/5.0.1 (or even older one) and upgraded with every new release to 5.0.5 - Let's call it production Meanwhile downloaded NAV Appliance 5.0.5 and I see that in appliance there are more wigdets, related to UPS and Spanning Tree, The question is how to copy new widgets to this production installation from appliance, where are wigdet files located and how to install them? Best Regards Sebastian

2 1

NAV auth with LDAP and MS AD
by Ingeborg Hellemo 05 Jun '20

05 Jun '20

We have had our own local patch which authenticates via Radius, but the time has come to move in the direction of LDAP and MS AD. [ldap] enabled = yes server = dc10.ad.uit.no port = 636 encryption = ssl uid_attr = sAMAccountName basedn = ou=people,dc=uit,dc=no lookupmethod=direct suffix = @ad.uit.no debug = yes I get authentication to work with an existing account, but can not create a new account. The debug-log shows a strange ldap url during referral: It begins ok: ldap_url_parse_ext(ldaps://dc10.ad.uit.no:636) ... connect success But then: ldap_chase_v3referrals ldap_url_parse_ext(ldaps://uit.no/ou=people,dc=uit,dc=no) Where does the domain uit.no in the URL come from? Is there a config setting I have overlooked? This of course ends in Unable to chase referral "ldaps://uit.no/ou=people,dc=uit,dc=no" (-1: Can't contact LDAP server) (If I use "lookupmethod=search" the webpage throws an error and no account is created. If I use "lookupmethod=direct" the account is created, but without Name, because that was not found in the search - since it was sent to the wrong server) --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 1

Issues with Nav docker container - logs, graph gaps and high postgres utilization
by Steve Kersley 03 Jun '20

03 Jun '20

Morning, TLDR: Gaps in graphs after Nav container running for a day or two. Nav container doesn't create logfiles. Nav postgres container has lots of postgres processes running, consuming ¾ of host CPU. Is this normal or bug (in container, or with my setup?) So, after killing my old Nav system with a series of conflicting upgrades, I decided to embrace the Docker approach, so that Nav (and other services) would be self-contained and not affected by upgrading components. All was initially well, but I'm starting to run into increasing graph gaps that I've not been able to resolve. If I stop and rebuild all of the containers with docker-compose, all seems well to start with, but after a while (few hours to a day or two) I start to get gaps and then it's downhill from there. The next issue I discovered while looking into the graph gaps is that there are no logs. Docker does mount a volume on /var/log/nav (from the dockerfile) but nothing ever gets created in it, meaning it's hard to look for warnings or errors. Is that expected behaviour, or is it something I got wrong when adapting the docker-compose file? The only logs I get from 'docker logs' show smsd being spawned and exiting every second: 2020-05-28 07:29:19,089 INFO spawned: 'smsd' with pid 28112 2020-05-28 07:29:20,092 INFO success: smsd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-05-28 07:29:20,560 INFO exited: smsd (exit status 1; not expected) 2020-05-28 07:29:21,563 INFO spawned: 'smsd' with pid 28116 2020-05-28 07:29:22,565 INFO success: smsd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-05-28 07:29:22,971 INFO exited: smsd (exit status 1; not expected) 2020-05-28 07:29:23,975 INFO spawned: 'smsd' with pid 28118 2020-05-28 07:29:24,977 INFO success: smsd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-05-28 07:29:25,355 INFO exited: smsd (exit status 1; not expected) (looking into this, appears to be exiting because python-gammu is not configured in the container, but is unlikely to be connected to the issue) I did increase UDP receive buffers on the host, which I first thought had solved the issue, but the improvement was a side effect of restarting all of the containers and reverted to gaps later. Nav's seeddb has 65 devices. Almost all just switches, with a handful of vmware hosts. The job durations are peculiar too - the 1minstats job for instance, on some switches takes a couple of seconds to run. On others, nearly a minute (or often several minutes on one in particular), but whether that's the cause or a symptom I don't know. It looks as though the postgres database used by Nav is what's eating resources and presumably causing the graph gaps. The docker host typically has a load average of 9-12. Looking at the processes, there are typically at least 10 postgres processes running in the NavDB container, continually using 20-30% of CPU for each process. This does not seem normal to me? I also gave that container more shared memory, as it was logging occasional errors about not being able to allocate enough. Again no change - worse if anything. The docker host is running as a VM as an in-production 'test' - in the fullness of time (when I'm not remote working), I'll likely move the containers onto a bare metal host. Docker host has 4 cores and 8Gb allocated, and is not hitting swap, but I can increase both. The vmware host it runs on has plenty of CPU and RAM with not a massive amount running on it, and the docker host is running from an array of SSDs. Besides Nav and NavDB containers, it's running containers for Icinga, and the Icinga backend mysql database; a dedicated shared graphite container accessed by both Icinga and Nav; Grafana as a dashboard for both; and nginx as a web proxy for all services. (Previously these services were all running fine alongside each other on a physical host of similar specification, until conflicting dependencies broke things). Does anyone have any thoughts? Entries from my docker-compose.yml: nav: container_name: nav build: context: /docker/build/nav args: NAV_VERSION: 5.0.5 ports: - "8002:80" - "162:162/udp" volumes: - /docker/nav/storage/roomimages:/var/lib/nav/uploads/images/rooms depends_on: - navdb environment: - PGHOST=navdb - PGDATABASE=nav - PGUSER=nav - PGPASSWORD=Password - PGPORT=5432 - CARBONHOST=graphite - CARBONPORT=2003 - GRAPHITEWEB=http://graphite/ - NOINITDB=0 env_file: - /docker/build/nav/nav-variables.env restart: always navdb: image: "postgres:12" container_name: navdb volumes: - /docker/navdb/storage/postgresql:/var/lib/postgresql/data environment: - POSTGRES_PASSWORD=Password - POSTGRES_USER=nav - POSTGRES_DB=nav restart: always shm_size: '256mb' Steve.

2 3

Monitor Paloalto equipment
by Edgar Matias 03 Jun '20

03 Jun '20

Hello NAV community, I recently added a Paloalto firewall to the NAV to be monitored. This is the gateway for some vlan. NAV lists all interfaces, but does not classify them as routing or switching ports. There are other things that are not recognized as power supply sensors, for example. I believe this is because the NAV does not have specific MIBs configured. Is there a way to import MIBs to this specific device, or a workaround ? Thanks in advance. Great tool ;) -- Edgar Matias Application Infrastructures Area Fundação para a Ciência e a Tecnologia Unidade FCCN – Computação Científica Nacional Av. do Brasil, 101, 1700-066 Lisboa, Portugal T: [+351] 218 440 100 | [+351] 900 000 000 www.fccn.pt

2 3

Syslog alert by mail
by Biselx Nicolas 13 Mai '20

13 Mai '20

Hi, I want to use the Syslog Analyzer, so far no problem the messages arrive in the database. Is it possible to send alerts according to the priority level by email? Regards Biselx Nicolas

2 1

Upgrade to NAV 5, navsyncdb barfs
by Ingeborg Hellemo 11 Mai '20

11 Mai '20

I'm in the middle of upgrading NAV from 4.8 to 5.0.5 and running 'navsyncdb' to alter the database schemas. (The database is named nynav because this is a test upgrade) /#navsyncdb Existing namespaces in nynav search path: "$user", public. Adding manage, profiles, logger, arnold, radius. Applying outstanding schema changes sql/changes/sc.04.09.0001.sql: OK sql/changes/sc.04.09.0050.sql: OK sql/changes/sc.04.09.0100.sql: OK sql/changes/sc.04.09.0110.sql: OK sql/changes/sc.04.09.0200.sql: OK sql/changes/sc.05.00.0001.sql: OK sql/changes/sc.05.00.0010.sql: operator is not unique: unknown || integer LINE 29: 'SNMP v' || snmp_version || ' read profile #' || row AS na... ^ HINT: Could not choose a best candidate operator. You might need to add explicit type casts. Server version Postgresql 9.6.17 Since this is a newly created database with imported data it might be missing some environment variables or something. --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 4

LLDP Error / v5.0.5
by scorpion7 21 Apr '20

21 Apr '20

NAV v5.0.5 appears to have a problem in the topology/LLDP portion. The switch referenced below is a Cisco WS-3750X stack, running 15.2(4)E10. Referenced devices are [Ubiquiti] APs. FWIW – the switch does have such things as ARP inspection, DHCP snooping, etc. – enabled. 2020-04-13 06:23:35,227 [INFO plugins.lldp.lldpneighbor] [topo switch0.<obscured>] found multiple interface matches for <LLDPNeighbor identified=True netbox=Netbox(id=27, sysname='wifi-b.<obscured>') interfaces=[Interface(id=607, netbox=Netbox(id=27, sysname='wifi-b.<obscured>'), ifname='br0', ifdescr='br0', iftype=6), Interface(id=609, netbox=Netbox(id=27, sysname='wifi-b.<obscured>'), ifname='br0.20', ifdescr='br0.20', iftype=6), Interface(id=589, netbox=Netbox(id=27, sysname='wifi-b.<obscured>'), ifname='eth0', ifdescr='eth0', iftype=6), Interface(id=605, netbox=Netbox(id=27, sysname='wifi-b.<obscured>'), ifname='eth0.20', ifdescr='eth0.20', iftype=6)]> 2020-04-13 06:23:35,229 [INFO plugins.lldp.lldpneighbor] [topo switch0.<obscured>] found multiple interface matches for <LLDPNeighbor identified=True netbox=Netbox(id=28, sysname='wifi-g.<obscured>') interfaces=[Interface(id=610, netbox=Netbox(id=28, sysname='wifi-g.<obscured>'), ifname='br0', ifdescr='br0', iftype=6), Interface(id=611, netbox=Netbox(id=28, sysname='wifi-g.<obscured>'), ifname='br0.20', ifdescr='br0.20', iftype=6), Interface(id=612, netbox=Netbox(id=28, sysname='wifi-g.<obscured>'), ifname='br-trunk', ifdescr='br-trunk', iftype=6), Interface(id=590, netbox=Netbox(id=28, sysname='wifi-g.<obscured>'), ifname='eth0', ifdescr='eth0', iftype=6), Interface(id=608, netbox=Netbox(id=28, sysname='wifi-g.<obscured>'), ifname='eth0.10', ifdescr='eth0.10', iftype=6), Interface(id=606, netbox=Netbox(id=28, sysname='wifi-g.<obscured>'), ifname='eth0.20', ifdescr='eth0.20', iftype=6)]> 2020-04-13 06:23:35,241 [ERROR jobs.jobhandler] [topo switch0.<obscured>] Plugin nav.ipdevpoll.plugins.lldp.LLDP('switch0.<obscured>') reported an unhandled failure Traceback (most recent call last): File "/opt/venvs/nav/lib/python3.7/site-packages/twisted/internet/defer.py", line 500, in errback self._startRunCallbacks(fail) File "/opt/venvs/nav/lib/python3.7/site-packages/twisted/internet/defer.py", line 567, in _startRunCallbacks self._runCallbacks() File "/opt/venvs/nav/lib/python3.7/site-packages/twisted/internet/defer.py", line 653, in _runCallbacks current.result = callback(current.result, *args, **kw) File "/opt/venvs/nav/lib/python3.7/site-packages/twisted/internet/defer.py", line 1442, in gotResult _inlineCallbacks(r, g, deferred) --- <exception caught here> --- File "/opt/venvs/nav/lib/python3.7/site-packages/twisted/internet/defer.py", line 1384, in _inlineCallbacks result = result.throwExceptionIntoGenerator(g) File "/opt/venvs/nav/lib/python3.7/site-packages/twisted/python/failure.py", line 408, in throwExceptionIntoGenerator return g.throw(self.type, self.value, self.tb) File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/plugins/lldp.py", line 71, in handle yield run_in_thread(self._process_remote) File "/opt/venvs/nav/lib/python3.7/site-packages/twisted/python/threadpool.py", line 250, in inContext result = inContext.theWork() File "/opt/venvs/nav/lib/python3.7/site-packages/twisted/python/threadpool.py", line 266, in <lambda> inContext.theWork = lambda: context.call(ctx, func, *args, **kw) File "/opt/venvs/nav/lib/python3.7/site-packages/twisted/python/context.py", line 122, in callWithContext return self.currentContext().callWithContext(ctx, func, *args, **kw) File "/opt/venvs/nav/lib/python3.7/site-packages/twisted/python/context.py", line 85, in callWithContext return func(*args,**kw) File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/db.py", line 100, in _reset return func(*args, **kwargs) File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/plugins/lldp.py", line 116, in _process_remote neighbors = [LLDPNeighbor(lldp) for lldp in self.remote] File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/plugins/lldp.py", line 116, in <listcomp> neighbors = [LLDPNeighbor(lldp) for lldp in self.remote] File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/neighbor.py", line 117, in __init__ self.identify() File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/neighbor.py", line 121, in identify self.interfaces = self._identify_interfaces() File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/plugins/lldp.py", line 222, in _identify_interfaces result = lookup(str(portid)) File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/plugins/lldp.py", line 248, in _interfaces_from_mac return self._interface_query(Q(ifphysaddress=mac)) File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/neighbor.py", line 234, in _interface_query 'id', 'ifname', 'ifdescr', 'iftype').filter(netbox & query): File "/opt/venvs/nav/lib/python3.7/site-packages/django/db/models/query.py", line 250, in __iter__ self._fetch_all() File "/opt/venvs/nav/lib/python3.7/site-packages/django/db/models/query.py", line 1121, in _fetch_all self._result_cache = list(self._iterable_class(self)) File "/opt/venvs/nav/lib/python3.7/site-packages/django/db/models/query.py", line 106, in __iter__ for row in compiler.results_iter(chunked_fetch=self.chunked_fetch): File "/opt/venvs/nav/lib/python3.7/site-packages/django/db/models/sql/compiler.py", line 841, in results_iter results = self.execute_sql(MULTI, chunked_fetch=chunked_fetch) File "/opt/venvs/nav/lib/python3.7/site-packages/django/db/models/sql/compiler.py", line 899, in execute_sql raise original_exception File "/opt/venvs/nav/lib/python3.7/site-packages/django/db/models/sql/compiler.py", line 889, in execute_sql cursor.execute(sql, params) File "/opt/venvs/nav/lib/python3.7/site-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/opt/venvs/nav/lib/python3.7/site-packages/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/opt/venvs/nav/lib/python3.7/site-packages/django/utils/six.py", line 685, in reraise raise value.with_traceback(tb) File "/opt/venvs/nav/lib/python3.7/site-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) django.db.utils.DataError: invalid input syntax for type macaddr: "None" LINE 1: ..."netboxid" = 26 AND "interface"."ifphysaddress" = 'None') OR... ^ 2020-04-13 06:23:35,242 [ERROR jobs.jobhandler] [topo switch0.<obscured>] Job 'topo' for switch0.<obscured> aborted: Job aborted due to plugin failure (cause=DataError('invalid input syntax for type macaddr: "None"\nLINE 1: ..."netboxid" = 26 AND "interface"."ifphysaddress" = \'None\') OR...\n ^\n')) Related: Was running an older version of NAV which appeared (at least via GUI) to have no issue this equipment combination of Cisco and Ubiquiti. Due to an odd issue, did end up dropping the VM and simply created a new one with latest Debian and latest NAV version, re-populating the equipment and configuration. Which may have been why certain things came to light? The Netmap doesn’t appear to be fully populated – suspect that it’s a cascading result of the above error?

2 1

Experience with NAV in large networks
by carsten＠strotmann.de 01 Apr '20

01 Apr '20

Hi, I'm evaluating NAV for one of my clients. As I have seen similar systems to NAV breaking down in large (> 100.000 devices) networks, I would like to know if anyone has experience with NAV in such large networks and how NAV scales in these networks. Anyone using NAV in such large environments? Greetings Carsten

2 1

website down?
by Steve Kersley 01 Apr '20

01 Apr '20

Morning, I can't imagine that you're not aware, but the NAV website has been down for the last few days. The documentation subsite is up, but the main site not. I'm guessing at the moment there are more pressing issues! Hope all NAV creators and users are well! Steve.

3 3

Announcement: NAV 5.0.5 released
by Morten Brekkevold 14 Mar '20

14 Mar '20

It's Friday the 13th and a pandemic is upon us, so we thought: Why not release the fifth maintenance version of the 5.0 series of NAV! The source code is available for download at GitHub [1]. New packages for Debian 9/10 (Stretch/Buster) are available in our APT repository [2] as usual. Please also be extra aware of config file changes. Look out for `*.dpkg-dist` files in /etc/nav and make sure to update your running config. The virtual appliance will be updated shortly. Deprecation warning =================== Python 2 reaches its end-of-life on **January 1, 2020**. NAV 5.0 therefore moves to Python 3, and as such, you will need at least Python 3.5 to run NAV. Most of NAV will still run on Python 2 as of the 5.0 release, but from this point, Python 2 will be deprecated and we will start removing code that exists solely to keep compatibility with Python 2. Changes ======= Fixed GitHub issues in this release: * #1994 (snmptrapd linkupdown plugin does not handle v2 traps) * #2101 ([BUG] Geomap data API endpoint crashes with a TypeError) * #2109 ([BUG] ipdevinfo sensor details page crashes with AttributeError on unit-less sensors) * #2111 ([BUG] Logging non-ASCII characters crashes NAV programs) * #2113 (Document advice for robust e-mail) * #2114 ([BUG] Unable to save status filter in [Status] page) * #2119 ([BUG] Latitude/Longitude is displayed weirdly in the SeedDB room list) * #2123 (Drop support for legacy status preference pickles) * #2129 (Euthanize unresponsive ipdevpoll workers) * #2130 ([BUG] Cannot import dashboard) Please see the release notes [3] for more details. Happy NAVing everyone! Links ===== [1] https://github.com/UNINETT/nav/releases [2] https://nav.uninett.no/install-instructions/#debian [3] https://nav.uninett.no/doc/latest/release-notes.html#nav-5.0 -- Sincerely, Morten Brekkevold Uninett

2 1

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