Hello,
I've check my logs on ipdevpoll and I found this :
2019-01-28 17:37:28,698 [ERROR jobs.jobhandler] [statuscheck
PAL-SW-R1-13.res.iogs] Caught exception during save. Last manager =
DefaultManager(<class 'nav.ipdevpoll.shadows.POEPort'>,
'ContainerRepository'(...)). Last model = <class
'nav.ipdevpoll.shadows.POEPort'>
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nav/ipdevpoll/jobs.py", line
442, in _perform_save
manager.save()
File "/usr/lib/python2.7/dist-packages/nav/ipdevpoll/storage.py",
line 87, in save
obj.save(self.containers)
File "/usr/lib/python2.7/dist-packages/nav/ipdevpoll/storage.py",
line 476, in save
obj.save()
File "/usr/lib/python2.7/dist-packages/django/db/models/base.py",
line 589, in save
force_update=force_update, update_fields=update_fields)
File "/usr/lib/python2.7/dist-packages/django/db/models/base.py",
line 617, in save_base
updated = self._save_table(raw, cls, force_insert, force_update,
using, update_fields)
File "/usr/lib/python2.7/dist-packages/django/db/models/base.py",
line 698, in _save_table
result = self._do_insert(cls._base_manager, using, fields,
update_pk, raw)
File "/usr/lib/python2.7/dist-packages/django/db/models/base.py",
line 731, in _do_insert
using=using, raw=raw)
File "/usr/lib/python2.7/dist-packages/django/db/models/manager.py",
line 92, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/django/db/models/query.py",
line 921, in _insert
return query.get_compiler(using=using).execute_sql(return_id)
File
"/usr/lib/python2.7/dist-packages/django/db/models/sql/compiler.py",
line 921, in execute_sql
cursor.execute(sql, params)
File "/usr/lib/python2.7/dist-packages/django/db/backends/utils.py",
line 65, in execute
return self.cursor.execute(sql, params)
File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 94,
in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/usr/lib/python2.7/dist-packages/django/db/backends/utils.py",
line 65, in execute
return self.cursor.execute(sql, params)
IntegrityError: ERREUR: une valeur NULL viole la contrainte NOT NULL de
la colonne « classification »
DETAIL: La ligne en échec contient (599034, 49, 66, null, 34, t, 2, 4,
null)
2019-01-28 17:37:28,701 [ERROR jobs.jobhandler] [statuscheck
PAL-SW-R1-13.res.iogs] Job 'statuscheck' for PAL-SW-R1-13.res.iogs
aborted: Job aborted due to save failure (cause=IntegrityError('ERREUR:
une valeur NULL viole la contrainte NOT NULL de la colonne \xc2\xab
classification \xc2\xbb\nDETAIL: La ligne en \xc3\xa9chec contient
(599034, 49, 66, null, 34, t, 2, 4, null)\n',))
2019-01-28 17:37:28,703 [INFO schedule.netboxjobscheduler] [statuscheck
PAL-SW-R1-13.res.iogs] statuscheck for PAL-SW-R1-13.res.iogs failed in
0:00:14.603465. next run in 0:04:59.999955.
It seems it doesn't like the PoE on my Dell N2048P because of a NULL
value in "classification" column.
Do you have an idea ?
Regards
--
Cordialement,
IOGS Logo <https://www.institutoptique.fr>
*Ludovic Vinsonnaud * - Ingénieur Réseau
basé à Bordeaux, bureau F108 (IOA, Rue François Mitterrand, 33400 Talence)
*Institut Optique Graduate School*
2 Avenue Augustin Fresnel - 91127 PALAISEAU Cedex
Tel. +33 5 57 01 71 52 - Mob. +33 6 08 08 41 05
Hi,
we have a 3850 Stack with 3x ES-C3850-48T-S and 5x WS-C3850-12X48U. When
we try to PortAdmin and edit a Port we get (see also attached Jpg):
„IP device found but has no type“
Any ideas?
Cheers,
Mischa
--
Mischa Diehm | Network Team (NINS)
UniBasel | IT-Services (ITS)
Klingebergstr. 70 | CH-4056 Basel
Tel. +41 61 267 1574 | https://its.unibas.ch
The first maintenance release of the 5.2 series of NAV is now out!
This release fixes a particularly nasty regression bug in pping, which
would prevent you from being alerted about boxDown events. If you are
already running 5.2.0, we recommend that you upgrade as soon as
possible.
The source code is available for download at GitHub [1].
A new package for Debian 10 (Buster) is available in our APT repository
[2] as usual. Packages for Debian 11 (Bullseye) have not been built yet.
Please 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 has been updated.
Changes
=======
* #2304 (Display alert severity values in the event/alert details
page)
* #2306 ([BUG] pping is unable to report unreachable devices in NAV
5.2.0)
* #2308 ([BUG] Alert Profile severity filters that ship with NAV are
outdated)
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.readthedocs.io/en/latest/release-notes.html#nav-5-2
--
Sincerely,
Morten Brekkevold
Uninett
The initial feature release of the 5.2 series of NAV is now out!
The source code is available for download at GitHub [1].
A new package for Debian 10 (Buster) is available in our APT repository
[2] as usual. Packages for Debian 11 (Bullseye) have not been built yet.
Please 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 has been updated.
Changes
=======
User-visible features and improvements:
* #1928 (Document 802.1X support of PortAdmin for end users)
* #2289 (Add config option to disallow editing of uplinks and
downlinks in PortAdmin)
* #2295 (Redefine alert severity levels and make them configurable)
* #2297 (Document the event and alert type hierarchy)
Fixed GitHub issues in this release:
* #2296 ([BUG] Portadmin save API incorrectly returns 500 error where
400 is appropriate)
* #2298 ([BUG] PortAdmin RpcError on JunOS 20 and newer)
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.readthedocs.io/en/latest/release-notes.html#nav-5-2
--
Sincerely,
Morten Brekkevold
Uninett
Hi,
I deployed NAV 5.14 on a debian 10 VM and configured LDAP authentication as from https://nav.readthedocs.io/en/latest/reference/ldap.html?highlight=ldap - however if using LDAP the login works randomly (need to try 2 to 5/6 time to login) while LDAPS never works. I did a test with ldapsearch on the same VM using both LDAP and LDAPS and both works so no issues with basedn or manager credentials nor with certificates. Is anyone else experiencing the same issue ? Other LDAPS based applications we use internally sucessfully connect to same AD servers.
Anyone can help maybe?
Thanks!
Andrea