From nineoften at hotmail.com Fri May 24 16:17:09 2019 From: nineoften at hotmail.com (Ni Ne) Date: Fri, 24 May 2019 16:17:09 +0000 Subject: [rancid] Rancid running numerous times for each group? Getting ~40 config fetcher email alerts for same group in a night Message-ID: Running ranicd 3.8 on CentOS 6.10, using git as the repo type. It appears rancid is running numerous times against the same group in a given night - at least if config fetches fail. For instance, I have one group with some problematic devices, and I got 39 "config fetcher" emails for that same group. Looking at logs, it appears rancid is parsing every group approximately the same number of times. There is only one cronjob that kicks off rancid on the entire system: * 0 * * * /usr/local/rancid/bin/rancid-run Groups are only defined once in the rancid.conf system. These are major settings in rancid.conf: MAX_ROUNDS=1; export MAX_ROUNDS OLDTIME=48; export OLDTIME PAR_COUNT=20; export PAR_COUNT #LOCKTIME=4; export LOCKTIME I have noticed this issue since I first built a new rancid 3.8 system - just never got around to trying to fix it until now. I have never seen this issue on the other rancid servers 2.x we have. Aside from version difference, the only notable difference I can think of is that our LIST_OF_GROUPS is fairly long at 332 entries and counting. Anyone have any ideas on how to troubleshoot further? -------------- next part -------------- An HTML attachment was scrubbed... URL: From heas at shrubbery.net Fri May 24 16:23:13 2019 From: heas at shrubbery.net (john heasley) Date: Fri, 24 May 2019 16:23:13 +0000 Subject: [rancid] Rancid running numerous times for each group? Getting ~40 config fetcher email alerts for same group in a night In-Reply-To: References: Message-ID: <20190524162313.GG67795@shrubbery.net> Fri, May 24, 2019 at 04:17:09PM +0000, Ni Ne: > Running ranicd 3.8 on CentOS 6.10, using git as the repo type. > > It appears rancid is running numerous times against the same group in a given night - at least if config fetches fail. > > For instance, I have one group with some problematic devices, and I got 39 "config fetcher" emails for that same group. Looking at logs, it appears rancid is parsing every group approximately the same number of times. > > There is only one cronjob that kicks off rancid on the entire system: > > * 0 * * * /usr/local/rancid/bin/rancid-run man 5 crontab min hr dom mon dow cmd From nineoften at hotmail.com Fri May 24 16:44:23 2019 From: nineoften at hotmail.com (Ni Ne) Date: Fri, 24 May 2019 16:44:23 +0000 Subject: [rancid] Rancid running numerous times for each group? Getting ~40 config fetcher email alerts for same group in a night In-Reply-To: <20190524162313.GG67795@shrubbery.net> References: , <20190524162313.GG67795@shrubbery.net> Message-ID: >> Running ranicd 3.8 on CentOS 6.10, using git as the repo type. >> >> It appears rancid is running numerous times against the same group in a given night - at least if config fetches fail. >> >> For instance, I have one group with some problematic devices, and I got 39 "config fetcher" emails for that same group. Looking at logs, it appears rancid is parsing every group approximately the same number of times. >> >> There is only one cronjob that kicks off rancid on the entire system: >> >> * 0 * * * /usr/local/rancid/bin/rancid-run > man 5 crontab > min hr dom mon dow cmd That looks right to me. Should kick off every night at midnight. Which it's doing. An entire run takes about 4 hours or so. All logs/emails from a nightly run arrive within that time-frame - 12am - 4am. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cra at wpi.edu Fri May 24 16:50:20 2019 From: cra at wpi.edu (Anderson, Charles R) Date: Fri, 24 May 2019 16:50:20 +0000 Subject: [rancid] Rancid running numerous times for each group? Getting ~40 config fetcher email alerts for same group in a night In-Reply-To: References: <20190524162313.GG67795@shrubbery.net> Message-ID: <20190524165017.vg26defsjtzjycht@angus.ind.wpi.edu> On Fri, May 24, 2019 at 04:44:23PM +0000, Ni Ne wrote: > >> Running ranicd 3.8 on CentOS 6.10, using git as the repo type. > >> > >> It appears rancid is running numerous times against the same group in a given night - at least if config fetches fail. > >> > >> For instance, I have one group with some problematic devices, and I got 39 "config fetcher" emails for that same group. Looking at logs, it appears rancid is parsing every group approximately the same number of times. > >> > >> There is only one cronjob that kicks off rancid on the entire system: > >> > >> * 0 * * * /usr/local/rancid/bin/rancid-run > > > man 5 crontab > > > min hr dom mon dow cmd > > That looks right to me. Should kick off every night at midnight. Which it's doing. An entire run takes about 4 hours or so. All logs/emails from a nightly run arrive within that time-frame - 12am - 4am. No, it says to run: * - every minute 0 - of the 0 hour * - of every day of month * - of every month * - of every day of week So I'd expect 60 copies to be run at midnight every night. From nineoften at hotmail.com Fri May 24 16:50:47 2019 From: nineoften at hotmail.com (Ni Ne) Date: Fri, 24 May 2019 16:50:47 +0000 Subject: [rancid] Fw: Rancid running numerous times for each group? Getting ~40 config fetcher email alerts for same group in a night In-Reply-To: References: <20190524162313.GG67795@shrubbery.net> , <20190524164525.GB47818@shrubbery.net>, Message-ID: >> >> Running ranicd 3.8 on CentOS 6.10, using git as the repo type. >> >> >> >> It appears rancid is running numerous times against the same group in a given night - at least if config fetches fail. >> >> >> >> For instance, I have one group with some problematic devices, and I got 39 "config fetcher" emails for that same group. Looking at logs, it appears rancid is parsing every group approximately the same number of times. >> >> >> >> There is only one cronjob that kicks off rancid on the entire system: >> >> >> >> * 0 * * * /usr/local/rancid/bin/rancid-run >> >> > man 5 crontab >> >> > min hr dom mon dow cmd >> >> That looks right to me. Should kick off every night at midnight. Which it's doing. An entire run takes about 4 hours or so. All logs/emails from a nightly run arrive within that time-frame - 12am - 4am. > no, its running every minute (60 times) at midnight. Oh brother, can't believe I missed that. Thank you!!! -------------- next part -------------- An HTML attachment was scrubbed... URL: