Nav-users

nav-users@lister.sikt.no

2 participants
1380 discussions

Announcement: NAV 5.0.7 released
by Morten Brekkevold 15 Okt '20

15 Okt '20

The seventh maintenance release of the 5.0 series of NAV is now out! 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 reached 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: * #2106 ([BUG] Cached LLDP/CDP records are never re-evaluated) * #2182 ([BUG] Delayed delivery alert subscriptions crash Alert Engine with a NameError) * #2184 ([BUG] Unrecognized Neighbors are never removed when all neighbors have been identified) * #2187 ([BUG] Locked accounts with a NULL value for a password cannot be edited) * #2188 ([BUG] Useradmin user listing becomes excruciatingly slow when many users have password issues) * #2189 ([BUG] Regression - ftp service check in 5.X does not work) 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

1 0

RE: Extra info in alertmails
by René Romijn 15 Sep '20

15 Sep '20

Oeps.. you are right 😊 Question still stands though. Is it possible to add more information in the alertsmails. -----Oorspronkelijk bericht----- Van: Morten Brekkevold <morten.brekkevold(a)uninett.no> Verzonden: dinsdag 15 september 2020 15:15 Aan: René Romijn <Rene.Romijn(a)tabsholland.nl> Onderwerp: Re: Extra info in alertmails On Mon, 14 Sep 2020 07:32:05 +0000 René Romijn <Rene.Romijn(a)tabsholland.nl> wrote: > Is it possible to add some more information in the alertmails? For example add Room? Hi René, I suspect you meant to send this to nav-users(a)uninett.no, not nav-users-request(a)uninett.no? -- sincerely, Morten Brekkevold Uninett

2 2

PoE graphs aren't display
by Biselx Nicolas 15 Sep '20

15 Sep '20

Hello, I can't understand why the gauges stay at 0 on the PoE page of a device: For example, If I click on PoE Group 2, I see port with the message delivering power in class4 But nothing appears in the graph either. Do the graphs have to be activated somewhere? Thank you in advance for your help Nicolas Biselx

2 7

Re: Seed Database IP having issues detect device
by Morten Brekkevold 28 Aug '20

28 Aug '20

On Sat, 22 Aug 2020 13:49:22 +0300 Tal Bar-Or <tbaror(a)gmail.com> wrote: > we added devices one by one manually , using a complete new installation. > Thanks > [image: 2020-08-22_13-40-06.jpg] > [image: 2020-08-22_13-48-00.jpg] Ok. I would prefer it if you kept the discussion on-list (unless you wish to post sensitive information in private), so I'm copying the list again in my reply. So, you background processes appear to be running. 1. Has NAV registered any alerts on your affected devices? 2. What are the job statuses of the affected devices (see their ipdevinfo pages)? 3. What does ipdevpoll.log have to say about the affected devices? -- sincerely, Morten Brekkevold Uninett

1 0

Announcement: NAV 5.0.6 released
by Morten Brekkevold 27 Aug '20

27 Aug '20

The sixth maintenance release of the 5.0 series of NAV is now out! 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 reached 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: * #2144 (Prevent ipdevinfo from crashing on weird device names) * #2149 (Inventory failing on DLink DGS-1100 : 'TypeError: argument of type 'int' is not iterable') * #2150 ([BUG] Interface down is causing widget 'status' to display 'Could not load widget' due to HTTP 500) * #2165 ([BUG] Delayed delivery alert subscriptions in single time period alert profiles are never sent) * #2167 (Fix potential typecast issue with SQL migration to NAV 5.0) * #2169 ([BUG] macwatch.py crashes when logging notifications about found MAC addresses) * #2170 ([BUG] Alertengine stops dispatching Slack notifications indefinitely if Slack complains of too many requests) * #2171 (Warn about user accounts that have issues with their passwords) * #2172 (Prevent login/password changes to default account) * #2177 ([BUG] Attempting to move IP devices to another room crashes SeedDB) * #2178 ([BUG] PDU widget stops displaying properly if room is deleted) * #2179 ([BUG] UPS widget does not display properly if UPS is deleted from NAV) * #2180 ([BUG] Entering invalid dates in Device History search form causes crash) 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

1 0

Routerports?
by Jan Astrup 19 Aug '20

19 Aug '20

Hello, I'm new to the nav-system, but i must say i like it alot. However, I'm having issues with a few devices, primarily ubiquiti and cambium wireless access points and CPE's. None of their ports come up as router ports, which in my case i think would be needed in order to get all my links visible on the geomap(?). Also, none of the ports are "patchable", so I can't create patches and assign them to those devices. Any pointers in where i should start looking in order to get this issue fixed? Best regards, Jan Astrup

2 1

Seed Database IP having issues detect device
by Tal Bar-Or 19 Aug '20

19 Aug '20

Hello , Recently we moved to a new nav server. We started to seed the database with a switch we had in the former version nav server. After seeding most of our switches to database we discover that there is an issue and most of switch under *Collected info* section , doesn't have the Type filled , result all switch doesn't have post/interface inventory although snmp check is successful any idea what is wrong? Please advise Thanks [image: 2020-08-09_12-27-04.png] -- Tal Bar-or

2 1

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

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