Hello There, Guest!  
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

4.1: notify-service-by-pushover and notify-host-by-pushover not showing in NConf

#1
Hey Robbie,

I had the chance to update my nems-linux box to 4.1. It was pretty straight forward on installing and then restoring the backup. However, there is an issue with the pushover components that I am seeing.  For some reason, I am not seeing notify-by-pushover or notify-host-by-pushover in my contacts within Nconf. If I do a search on the box via ssh, I am seeing the PHP file. 

Code:
sudo find / -name "notify-*"
/usr/local/nagios/libexec/notify-by-pushover.php
/root/nems/nems-migrator/data/1.4/submodules/barryo/nagios-plugins/notify-by-pushover.php
/root/nems/nems-migrator/data/1.5/nagios/plugins/notify-by-pushover.php
/root/nems/nems-migrator/data/1.5/nagios/plugins/notify-by-telegram.lua



I restored from my 1.3 backup and wondering if this caused an issue with it not showing in nConf. nConf shows 4.1


Attached Files Thumbnail(s)
   
 Reply
#2
Because you've migrated from 1.3, the default check_commands and notification commands will all be from 1.3.

How big is your config? I can patch it for you to also include 1.4's commands, if you like.

This will be improved in NEMS 1.5, but unfortunately there's no quickfix yet for 1.4.x. I will roll one out, but am too busy with NEMS 1.5 development at the moment.

If you would like me to patch your backup file, login to your NEMS 1.3 system and create a support.nems file for me.

Robbie
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#3
Hi Robbie,

Thanks for the reply. I decided to just start from fresh as I really only had one host configured.  Thanks for offering to patch it though. I was just bringing this up in case it was a bug.
 Reply
#4
Thanks. Yes, that's why I'd asked how large your setup was... since you only have one, it's best to just create a new config under 1.4.1.

It's not a "bug" per se: you imported your configuration from 1.3, so as expected, you then end up with the configuration from 1.3.

I will indeed make it more intuitive though, as a feature improvement (not bug fix) to try to better reconcile between old configs so you are still able to tap into the new check_commands, and so-on.

I added it to the to-do list. Doubt it'll get into 1.5 at release, but perhaps sometime during the 1.5 support cycle.

Thanks,
Robbie
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#5
Same issue over here -- and I'm guessing it's the same cause. @Robbie -- what's easiest? I can send you the support.nems bundle or I can just wait for v1.5. Let me know. Thank you!
 Reply
#6
This is already done in NEMS 1.5 - see https://www.patreon.com/posts/nems-linux-1-5-24488499

Indeed, I'd love to have your support.nems file just so I can test yours against the updated importer before it is released (the more real-world tests I have, the more stable it will be).

Cheers,
Robbie
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#7
Thanks for the file. Confirmed when imported into NEMS 1.5, your configuration works + has the missing check commands.
Robbie Ferguson // The Bald Nerd

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

Users browsing this thread: 1 Guest(s)