Page 2 of 2
Re: Scheduled Downtime - Unable to remove action
Posted: Tue Apr 23, 2019 3:59 pm
by scottwilkerson
Can you run the following while trying to remove a downtime and report the results
Code: Select all
tail -f /usr/local/nagiosxi/var/cmdsubsys.log
Re: Scheduled Downtime - Unable to remove action
Posted: Wed Apr 24, 2019 4:43 am
by hoegh
Hi scottwilkerson,
This is the output of the command while trying to remove downtime
[root@OSLMSnagios ~]# tail -f /usr/local/nagiosxi/var/cmdsubsys.log
PROCESSED 0 COMMANDS
PROCESSED 0 COMMANDS
PROCESSED 0 COMMANDS
PROCESSED 0 COMMANDS
PROCESSED 0 COMMANDS
PROCESSED 0 COMMANDS
PROCESSED 0 COMMANDS
PROCESSED 0 COMMANDS
PROCESSED 0 COMMANDS
PROCESSED 0 COMMANDS
PROCESSED 0 COMMANDS
Regards
Hoegh
Re: Scheduled Downtime - Unable to remove action
Posted: Wed Apr 24, 2019 7:15 am
by scottwilkerson
If you go to the Event Log Report and search for DOWNTIME do you see the canceled downtimes?
Re: Scheduled Downtime - Unable to remove action
Posted: Wed Apr 24, 2019 1:13 pm
by hoegh
Hi scottwilkerson,
In Event Log Report, when searched for DOWNTIME the canceled downtimes cannot be seen.
Regards,
Hoegh
Re: Scheduled Downtime - Unable to remove action
Posted: Wed Apr 24, 2019 1:23 pm
by scottwilkerson
Can you PM me your system profile? Admin -> System Profile -> Download Profile
Re: Scheduled Downtime - Unable to remove action
Posted: Thu Apr 25, 2019 1:17 am
by hoegh
Hi scottwilkerson,
I have PM you the profile, let us know what further need to done.
Regards,
Hoegh
Re: Scheduled Downtime - Unable to remove action
Posted: Thu Apr 25, 2019 11:50 am
by scottwilkerson
The attachment was missing in the PM
Re: Scheduled Downtime - Unable to remove action
Posted: Thu Apr 25, 2019 9:36 pm
by hoegh
I've sent again with Profile Attachment.
Please check.
Re: Scheduled Downtime - Unable to remove action
Posted: Fri Apr 26, 2019 8:58 am
by scottwilkerson
Response sent via PM
Re: Scheduled Downtime - Unable to remove action
Posted: Fri Apr 26, 2019 12:46 pm
by scottwilkerson
Solved.
cgi.cfg was blank so the command execution was denied because they were not allowed.
Locking thread