Github queries

Robbie, new user here, thought I'd chime in with a note I'm also getting the issue that was reported about the copy collector config failure (I assume everyone is). I know you know about that, but I wanted to ask about another issue...I noticed the Rpi is hitting github a couple times per minute (as reported in Pi-hole). Just wanted to confirm there's a reason for that and if that is right or not.

Is the copy collector config failure the reason NConf fails to apply at least some updates? As a work-around I can manually edit the nagios config file directly which seems to be the only option at the moment. An example of one change I wanted to make but couldn't was increasing a notification interval from one hour to eight hours for a specific host. The file edited directly was: /etc/nems/conf/Default_collector/hosts.cfg, save and restart nagios.

I'm just playing with this to gain some knowledge of linux, hobby-style. So if you're too busy to reply, no worries. Thanks!

-- Greg

PS - I blocked github access with no negative effects to nems running...I unblock to update and then reblock.

Hi Greg,
I issued a patch for the Default_collector bug. Should be fixed for you after a sudo nems-quickfix

Re. Github.
"PS - I blocked github access with no negative effects to nems running...I unblock to update and then reblock."
Please do not do this. Yes, there is good reason why you're seeing Github getting touched... and the Default_collector bug patch is one :)

In order to prevent errors and even data corruption, it was important to have scripts in NEMS determine if the Internet connection was up before running certain tasks. That makes sense for such a server. However, in some geographic areas, it was found that while Internet was up, Github was inaccessible (DNS issue). So those users' NEMS servers could become corrupt when a nightly maintenance task (for example) would say "Yes, Internet is up" and then try to get the files from Github and fail.

The reason you see it periodically and rather often is simply because I check that the Internet is up before running tasks in the background.

Does that help clarify things?

Blocking Github will break some of the best bits of NEMS (see for example, nems-quickfix, which runs as a cron task every day). Plus, blocking Github will cause your NEMS server to think it has no connectivity, which would cause it to skip over maintenance tasks, would break off site backup (if you use that) and so-on.

Robbie

Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:

Thanks Robbie...I removed the firewall rule, let it settle for 15 minutes or so, then ran quickfix, didn't appear fix it. Then ran nems-update followed by nems-quickfix and no change. Still get this message when trying to deploy (under copy collector config):

Quote:sudo nems-quickfix
[sudo] password for "xxxxxxxx":
Performing NEMS QuickFix...
It's really just a fancy name: this may take a while.
Do not stop this script once it is running.
Please wait patiently... Done.

Rebooted, regenerated, ran deploy...but still get the same error "Source file does not exist (/tmp/Default_collector/)". I was on 1.3 for a couple weeks just as you were working on 1.4 and I think what I did was attempted to migrate but that failed or caused some issue, and in the end I just added all the hosts back manually. What I can't recall is if I recreated the image on the memory card or simply ran nems-init and started over.