We are getting duplicate reports after updating the email address associated to an existing report.
This resulted in us getting 2 of the same reports for 9am each day.
The time was then edited from 9am to 9.15am, However this then resulted in getting a report at both 9am and 9.15am.
Therefore searched through Nagios Core to /var/spool/cron/apache. Where we could see these duplicate reports using cat command.
0 9 * * * /usr/bin/php /usr/local/nagiosxi/html/includes/components/scheduledreporting/sendreport.php --report=ABCDE --username="USERNAME" > /dev/null 2>&1
15 9 * * * /usr/bin/php /usr/local/nagiosxi/html/includes/components/scheduledreporting/sendreport.php --report=ABCDE --username='USERNAME' > /dev/null 2>&1
The update 9.15am report was then deleted using Nagios xi, however this only removed one.
The one remaining is the file in which Nagios xi seems to have no control over. This is the one we need removed.
We are reluctant to remove this manually in case it causes further issues or corrupts anything.
We also noticed that there is 2 entries for reports in this same location for a user that has long been removed from the system.
0 9 1 * * /usr/bin/php /usr/local/nagiosxi/html/includes/components/scheduledreporting/sendreport.php --report=FlHECO --username="USER" > /dev/null 2>&1
0 9 1 * * /usr/bin/php /usr/local/nagiosxi/html/includes/components/scheduledreporting/sendreport.php --report=2ZuuKN --username="USER" > /dev/null 2>&1
What we are hoping Nagios Support could clarify.
1. The best method to remove this duplication
2. What could have caused this to occur
3. Is there a maintenance method to clear duplications or files that don't match up between core and xi
Duplicate Reports - Nagios xi
-
- Cool Title Here
- Posts: 2188
- Joined: Thu Sep 27, 2012 9:14 am
- Location: Rochester, NY
Re: Duplicate Reports - Nagios xi
Copy/paste the entry into an email to yourself and manually delete it. It's just a cron job so it can be recreated from the Nagios database if it really thinks it needs to be there.
I'm guessing it just got confused somewhere along the way, maybe with a permissions thing with someone poking at it manually.
You can't really hurt anything, since you can always put back.
Don't be afraid to poke.
I'm guessing it just got confused somewhere along the way, maybe with a permissions thing with someone poking at it manually.
You can't really hurt anything, since you can always put back.
Don't be afraid to poke.

Eric Loyd • http://everwatch.global • 844.240.EVER • @EricLoyd
I'm a Nagios Fanatic! • Join our public Nagios Discord Server!