Mod Note: split from https://support.nagios.com/forum/viewto ... 16&t=42456
I've been having issues with my production 5.4.0 instance not scheduling maintenance as well.
I just scheduled a host and ran those two DB queries and came back with '0'
-Andrew
Putting mutiple hosts into downtime
Putting mutiple hosts into downtime
Last edited by ssax on Thu Feb 23, 2017 5:14 pm, edited 3 times in total.
Reason: split as differnent versions
Reason: split as differnent versions
Andrew J. - Do you even grok?
Re: Putting mutiple hosts into downtime
Is it having issues for all downtime or just some?
Are you using recurring downtime OR just scheduled downtime?
Are you using recurring downtime OR just scheduled downtime?
Re: Putting mutiple hosts into downtime
Also, if it's recurring downtime what does your /usr/local/nagiosxi/var/recurringdowntime.log say?
We may want to move this into a ticket, please email [email protected] with a descriptive subject and detailed body and please include a link back to this thread so that we can get a remote session setup.
Thank you
We may want to move this into a ticket, please email [email protected] with a descriptive subject and detailed body and please include a link back to this thread so that we can get a remote session setup.
Thank you
Re: Putting mutiple hosts into downtime
I only have one recurring schedule and it's still there.
One-time attempts from the "Scheduled Downtime" page or the Advanced tab in host or service details.
I'll set a schedule and it will never populate in the scheduled downtime list or show the service/host in maintenance.
One-time attempts from the "Scheduled Downtime" page or the Advanced tab in host or service details.
I'll set a schedule and it will never populate in the scheduled downtime list or show the service/host in maintenance.
Andrew J. - Do you even grok?
Re: Putting mutiple hosts into downtime
Does it give a success message at the top when you do it from Home > Scheduled Downtime after you click the Schedule button? Read the text, there was a bug where it showed green but actually failed and I want to make sure it's not back or something is not interfering with it, it's working properly on my 5.4.2 so I want to figure out what the difference is.
Do you have your DNS short name and the FQDN of the XI server in your /etc/hosts file on the 127.0.0.1 entry?
Do you have your DNS short name and the FQDN of the XI server in your /etc/hosts file on the 127.0.0.1 entry?
Re: Putting mutiple hosts into downtime
Yep. I get the green message reminding me that it could take up to a minute to see it in the schedule.
my loopback IP only had localhost* names. I added both the hostname and the A record name (friendly internal name for user access, also what is configured as Program URL). then , TaDa!, it's working.
Is this the bug or a feature that needs to be worked around?
my loopback IP only had localhost* names. I added both the hostname and the A record name (friendly internal name for user access, also what is configured as Program URL). then , TaDa!, it's working.
Is this the bug or a feature that needs to be worked around?
Andrew J. - Do you even grok?
Re: Putting mutiple hosts into downtime
And I just double-checked my dev instance... 127.0.0.1 has the A name in there already, which is probably why I have no issues there.
I think we can lock this up.
I think we can lock this up.
Andrew J. - Do you even grok?
Re: Putting mutiple hosts into downtime
It's a bug in my opinion:
It's doing it based on the URL that you have in the address bar so it should have an internal DNS record as well if it's doing internal communication, if it doesn't then you'd need to add it to the hosts file (I'd do it anyways since it's faster and will reduce lookup time since it checks the file first). Locking it up and marking as resolved.
Code: Select all
NEW TASK ID 11153 created - Nagios XI Bug Report: Home > Scheduled Downtime - base_url is being pulled from browser address bar and used in backend internal request