Nav-users April 2022

nav-users@lister.sikt.no

2 participants
2 discussions

nav 5.3 - alertengine not sending alert / blacklisted and connection timeout (error 110)
by Andrea Verni 26 Aug '22

26 Aug '22

Hi, I'm running NAV 5.3 and have issue with alertengine and email notifications. Email seems to remain stuck in the queue until I force a reboot of the VM. The error message I see in /var/log/nav/alertengine.log is: 2022-03-08 08:35:10,707 [WARNING] [nav.alertengine.alertaddress.send] Not sending alert 5824 ****** as handler Email is blacklisted: [Errno 110] Connection timed out 2022-03-08 08:35:10,716 [WARNING] [nav.alertengine.alertaddress.send] Not sending alert 5825 to ****** as handler Email is blacklisted: [Errno 110] Connection timed out 2022-03-08 08:35:10,720 [INFO] [nav.alertengine.check_alerts] 0 new alert(s), sent 0 alert(s), 910 queued alert(s), 0 alert(s) deleted, 910 failed send(s), 0 ignored However, by running a tcpdump I do not see any outbound/inbound connection to the configured email server. After the reboot it seems messages are going through (and I do see outbound connections to the configured mail server) 2022-03-08 08:39:38,277 [INFO] [nav.alertengine.alertaddress.send] alert 5367 sent by Email to ****** due to immediately subscription 2 2022-03-08 08:39:38,500 [INFO] [nav.alertengine.alertaddress.send] alert 5320 sent by Email to ****** due to immediately subscription 2 2022-03-08 08:41:34,963 [INFO] [nav.alertengine.check_alerts] 0 new alert(s), sent 910 alert(s), 0 queued alert(s), 0 alert(s) deleted, 0 failed send(s), 0 ignored I'm running Debian 10 and not have iptables/fail2ban on it. Any help? Thanks! Andrea

2 3

Re: wrong Port configuration status for juniper device if port manually disabled
by FOUR Ludovic (EXT) 06 Apr '22

06 Apr '22

Hello, I just forgot to reply to all, my bad sorry I leave all the comments below I took a look into ipdevpoll.log When I'm updating a port, there is new [INFO schedule.netboxjobscheduler] line into ipdevpoll log, means that the scheduler is doing fine. I still have the same issue with portadmin enabled checkbox : if you uncheck enabled box, save, then reload page, the checkbox goes back to checked, and remains in this state. - but it updates the interface - (disabled) I've made some setup to portadmin.conf, and changed link_edit = false (better not cut the tree branch where you are sitting on) but I don't think it's related to. Regards, Ludovic ----- Mail original ----- De: "Morten Brekkevold" <morten.brekkevold(a)sikt.no> À: "FOUR Ludovic / PHA" <ludovic.four(a)unistra.fr> Envoyé: Vendredi 1 Avril 2022 14:39:19 Objet: Re: wrong Port configuration status for juniper device if port manually disabled On Thu, 31 Mar 2022 09:24:46 +0200 (CEST) "FOUR Ludovic (EXT)" <ludovic.four(a)unistra.fr> wrote: > I only disable the physical port in this case. Hi Ludovic, did you intentionally leave the mailing list out of your reply? > I did that, but there's no update even when I close Chrome or firefox > (did some tests on both). I tried by clearing firefox/chrome cache > too. The interface status still remains checked (enable) in portadmin > web page. Then I need to do some testing on our own equipment in an attempt to reproduce this. I'll have to get back to you. > I also have some update problem with aggregated interfaces (aeX) > created with Junos Console. NAV can detect the aeX interface when I > create it. But still remains when I remove it. I can't see the > physical interfaces that were previously members of the aggregated > interface in the physical ports list anymore. What ports NAV knows about is only updated by the inventory job, which runs every 6 hours. However, ipdevpoll does show some restraint from deleting any interface as soon as it appears missing (some devices can be wonky) - it actually marks it internally with a "missing since" timestamp, and removes it only when it remains missing after certain amount of time. I don't recall the exact amount, but I'm guessing 24 hours. > Maybe a SSL cache issue on server side ? > I'm using standard apache mod ssl settings > SSLSessionCache shmcb:${APACHE_RUN_DIR}/ssl_scache(512000) > SSLSessionCacheTimeout 300 No, this is unrelated to content caching. -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users April 2022