NAV 5.9.1
Suddenly, since yesterday, a lot (but not all) of the navtopology cron jobs sends an email with "navtopology is already running"
An example:
/var/log/cron Apr 30 09:35:00 <hostname> /usr/sbin/cron[69867]: (navcron) CMD (navtopology --l2 --vlan)
10 minutes later an email arrives
Date: Tue, 30 Apr 2024 09:43:35 +0200 (CEST) Subject: Cron navcron@bjarne navtopology --l2 --vlan
navtopology is already running (69867)
What can trigger this error? var/log/navtopology shows that the job runs as usual. (Last lines in the run is "deleting unused prefixes/vlans")
The one thing that changed before this error turned up is that the server running NAV was moved behind Cisco ACI and a (application centric) firewall.
--Ingeborg
On Tue 30 Apr 2024 at 13:48, Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
navtopology is already running (69867)
What can trigger this error? var/log/navtopology shows that the job runs as usual. (Last lines in the run is "deleting unused prefixes/vlans")
How long does `navtopology --l2 --vlan` take to run on your server? By default, the cronjob is run 35 minutes past every hour. I'm guessing eitherq navtopology is running for more than an hour (which is bad), or you have set it up to run much more often than the default (or accidentally made double cron job entries).
On Tue 30 Apr 2024 at 13:48, Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
navtopology is already running (69867)
What can trigger this error? var/log/navtopology shows that the job runs as usual. (Last lines in the run is "deleting unused prefixes/vlans")
How long does `navtopology --l2 --vlan` take to run on your server? By default, the cronjob is run 35 minutes past every hour. I'm guessing eitherq navtopology is running for more than an hour (which is bad), or you have set it up to run much more often than the default (or accidentally made double cron job entries).
The navtopology job takes less than 10 minutes. The email with the error message arrives at 43 minutes past every hour (And belongs to _this_ hours job).
Only one cronjob is running
/# grep navtopology /var/cron/tabs/* /var/cron/tabs/navcron:35 * * * * navtopology --l2 --vlan
--Ingeborg
On Wed 15 May 2024 at 10:50, Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
The navtopology job takes less than 10 minutes. The email with the error message arrives at 43 minutes past every hour (And belongs to _this_ hours job).
Only one cronjob is running
Wait, actually this is a side-effect of a bug that's been fixed, but not released yet. `navtopology` is on of the programs affected by https://github.com/Uninett/nav/issues/2877
New release is imminent, but I know you know how to patch if you get too annoyed :)
-
Ingeborg Hellemo -
Morten Brekkevold