Skip to content
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.

Recurrent downtimes - error period 1 #7485

Open
jakefoster2018 opened this issue Apr 25, 2019 · 15 comments
Open

Recurrent downtimes - error period 1 #7485

jakefoster2018 opened this issue Apr 25, 2019 · 15 comments
Labels
kind/bug status/in-backlog A dev will begin to work on your modifications soon

Comments

@jakefoster2018
Copy link

BUG REPORT INFORMATION

Prerequisites

Versions
centreon-base-config-centreon-engine-18.10.4-9.el7.centos.noarch
centreon-widget-graph-monitoring-18.10.0-6.el7.centos.noarch
centreon-database-18.10.4-9.el7.centos.noarch
centreon-common-18.10.4-9.el7.centos.noarch
centreon-plugin-Applications-Protocol-Dns-20190412-141630.el7.centos.noarch
centreon-pp-manager-18.10.4-1.el7.centos.noarch
centreon-engine-18.10.0-4.el7.centos.x86_64
centreon-release-18.10-2.el7.centos.noarch
centreon-widget-global-health-18.10.0-8.el7.centos.noarch
centreon-widget-engine-status-18.10.0-9.el7.centos.noarch
centreon-connector-perl-18.10.0-2.el7.centos.x86_64
centreon-plugin-Applications-Monitoring-Centreon-Map4-Jmx-20190412-141630.el7.centos.noarch
centreon-plugin-Operatingsystems-Linux-Snmp-20190412-141630.el7.centos.noarch
centreon-plugin-Applications-Monitoring-Centreon-Database-20190412-141630.el7.centos.noarch
centreon-license-manager-18.10.2-1.el7.centos.noarch
centreon-widget-service-monitoring-18.10.2-1.el7.centos.noarch
centreon-connector-ssh-18.10.0-2.el7.centos.x86_64
centreon-plugin-Operatingsystems-Windows-Snmp-20190412-141630.el7.centos.noarch
centreon-plugin-Hardware-Printers-Generic-Snmp-20190412-141630.el7.centos.noarch
centreon-plugin-Network-Cisco-Standard-Snmp-20190412-141630.el7.centos.noarch
centreon-plugin-Applications-Monitoring-Centreon-Poller-20190412-141630.el7.centos.noarch
centreon-plugin-Applications-Databases-Mysql-20190412-141630.el7.centos.noarch
centreon-widget-live-top10-memory-usage-18.10.0-6.el7.centos.noarch
centreon-widget-tactical-overview-18.10.0-6.el7.centos.noarch
centreon-broker-storage-18.10.1-1.el7.centos.x86_64
centreon-plugin-Applications-Protocol-Ldap-20190412-141630.el7.centos.noarch
centreon-web-18.10.4-9.el7.centos.noarch
centreon-widget-host-monitoring-18.10.1-1.el7.centos.noarch
centreon-engine-daemon-18.10.0-4.el7.centos.x86_64
centreon-plugin-Applications-Monitoring-Centreon-Central-20190412-141630.el7.centos.noarch
centreon-perl-libs-18.10.4-9.el7.centos.noarch
centreon-plugin-Hardware-Ups-Standard-Rfc1628-Snmp-20190412-141630.el7.centos.noarch
centreon-broker-cbmod-18.10.1-1.el7.centos.x86_64
centreon-widget-httploader-18.10.0-6.el7.centos.noarch
centreon-widget-live-top10-cpu-usage-18.10.0-6.el7.centos.noarch
centreon-broker-core-18.10.1-1.el7.centos.x86_64
centreon-poller-centreon-engine-18.10.4-9.el7.centos.noarch
centreon-engine-extcommands-18.10.0-4.el7.centos.x86_64
centreon-broker-cbd-18.10.1-1.el7.centos.x86_64
centreon-widget-grid-map-18.10.0-6.el7.centos.noarch
centreon-widget-servicegroup-monitoring-18.10.0-6.el7.centos.noarch
centreon-connector-18.10.0-2.el7.centos.x86_64
centreon-license-manager-common-18.10.2-1.el7.centos.noarch
centreon-plugin-Applications-Protocol-Http-20190412-141630.el7.centos.noarch
centreon-18.10.4-9.el7.centos.noarch
centreon-clib-18.10.0-2.el7.centos.x86_64
centreon-widget-hostgroup-monitoring-18.10.0-6.el7.centos.noarch
centreon-plugin-Applications-Protocol-Ftp-20190412-141630.el7.centos.noarch
centreon-broker-18.10.1-1.el7.centos.x86_64
centreon-trap-18.10.4-9.el7.centos.noarch

Description

I am unable to set re-occurring downtimes from PM hrs till AM hrs?.
I need to set re-occurring downtime from 21:00 to 07:30 the next day - but i cant do it as the re-occurring downtime errors with 'Error Period 1'
I can set one downtime window from 00:00 -> 07:30, but when i try to set the first downtime window (21:00 -> 00:00) it errors, the only way i can get round it is to set the first downtime window to be 21:00 -> 23:59, which leaves 1 minute of non-downtime and i get notifications in that one minute

@adr-mo
Copy link
Contributor

adr-mo commented Apr 25, 2019

Hi @jakefoster2018,

Thanks for the feedback 💯

We are currently working on this issue 👍

Related issues:

Regards,

@adr-mo adr-mo assigned adr-mo and unassigned adr-mo Apr 25, 2019
@adr-mo adr-mo added kind/bug status/in-backlog A dev will begin to work on your modifications soon labels Apr 25, 2019
@jakefoster2018
Copy link
Author

That's great, when can we expect a fix please?

@adr-mo
Copy link
Contributor

adr-mo commented Apr 29, 2019

Hi @jakefoster2018

This will be available soon hopefuly.

This issue is kind of tricky.

What I can ensure you is that it should be available for the next releases

  • 19.04.1
  • 18.10.5

Regards,

@jakefoster2018
Copy link
Author

Hi there, is this meant to be fixed in 18.10.5 as i've upgrade to that and its still an issue? 'error period 1'

@joschi99
Copy link

Are there some news about this issue? We have the same problem using Centreon 19.10.10. Some workaround or hotfix available?

@JuliusKoenig
Copy link

Issue is still in 20.04.2. Are there some news about this?

@joschi99
Copy link

joschi99 commented Jul 8, 2022

the issue is still open. Is there any solution available?

@ponchoh
Copy link
Member

ponchoh commented Jul 8, 2022

Being that all the versions discussed here have reached their EOL, I will close this case.

https://docs.centreon.com/docs/releases/lifecycle/

😊⛱

@ponchoh ponchoh closed this as completed Jul 8, 2022
@JuliusKoenig
Copy link

Okay then I would like to bring this back to life :)

I have just recreated the above problem in a current version 22.04.0. Unfortunately it is still not possible to schedule a weekly downtime from for example 9 pm. to 2 am.

Here are a few screenshots:

image
here it works

image
and as you can see here, the error "Error period 1" occurs.

@joschi99
Copy link

joschi99 commented Jul 8, 2022

I can confirm that the problem is still there on any supportet version, please reopen the case.

@ponchoh
Copy link
Member

ponchoh commented Jul 8, 2022

Thank you for this @joschi99 and @JuliusKoenig let me look into this and I will get back to you.

@ponchoh ponchoh reopened this Jul 8, 2022
@ponchoh
Copy link
Member

ponchoh commented Jul 8, 2022

Have you tried with a multi period?

image
image

@joschi99
Copy link

Yes, we configured 2 periods, one until 23:59 and the second from 00:00. But as described 1 minute between 23:59 and 0:00 will not covered from the downtime and alarms are send in this time range

@ponchoh
Copy link
Member

ponchoh commented Jul 11, 2022

I see now, we need to use 24 and actually type it.

image

@bambin401
Copy link

Hello, the issue is still existing in version 21.04.20, is there any news on fixing the issue ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug status/in-backlog A dev will begin to work on your modifications soon
Projects
None yet
Development

No branches or pull requests

6 participants