Page 2 of 2

Re: Possible reoccurring downtime bug

Posted: Tue Oct 08, 2019 6:20 pm
by nickap
Checking recurring config id: aaf233dbdbf7cfa7ef801c40c965c7f0
hostgroup: Server_Group, services: yes
**************************************************************
get_next_scheduled_time('3:00', 'sun', '', '') called
current_timestamp: 1570575662, 2019-10-08 19:01
candidate_timestamp: 1570518000, 2019-10-08 03:00
candidate_timestamp in past, adjusting..
candidate_timestamp: 1570604400, 2019-10-09 03:00
got candidate_day_of_week: wed, checking: sun
candidate_timestamp: 1570690800,2019-10-10 03:00
got candidate_day_of_week: thu, checking: sun
candidate_timestamp: 1570777200,2019-10-11 03:00
got candidate_day_of_week: fri, checking: sun
candidate_timestamp: 1570863600,2019-10-12 03:00
got candidate_day_of_week: sat, checking: sun
candidate_timestamp: 1570950000,2019-10-13 03:00
got candidate_day_of_week: sun, checking: sun
check successful
all parameters match, re-adjusting candidate for proper time
candidate_timestamp: 1570950000000, 2019-10-13 03:00
Downtime exists with start_time: 1570950000, and duration 5400 seconds ..
NOT SCHEDULING
Downtime exists with start_time: 1570950000, and duration 5400 seconds ..
NOT SCHEDULING
Downtime exists with start_time: 1570950000, and duration 5400 seconds ..
NOT SCHEDULING
Downtime exists with start_time: 1570950000, and duration 5400 seconds ..
NOT SCHEDULING
.
.
.
(same message as above over and over)
.
.
Checking recurring config id: bd5c3b7817f8720deacc2873f67ccb70
host: Server, service: Server Check
**************************************************************

get_next_scheduled_time('12:00', 'sat', '', ',jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec') called
current_timestamp: 1570575662, 2019-10-08 19:01
candidate_timestamp: 1570550400, 2019-10-08 12:00
candidate_timestamp in past, adjusting..
candidate_timestamp: 1570636800, 2019-10-09 12:00
got candidate_day_of_week: wed, checking: sat
got candidate_month_of_year: oct, checking: jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec
check successful
candidate_timestamp: 1570723200,2019-10-10 12:00
got candidate_day_of_week: thu, checking: sat
got candidate_month_of_year: oct, checking: jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec
check successful
candidate_timestamp: 1570809600,2019-10-11 12:00
got candidate_day_of_week: fri, checking: sat
got candidate_month_of_year: oct, checking: jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec
check successful
candidate_timestamp: 1570896000,2019-10-12 12:00
got candidate_day_of_week: sat, checking: sat
check successful
got candidate_month_of_year: oct, checking: jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec
check successful
all parameters match, re-adjusting candidate for proper time
candidate_timestamp: 1570896000000, 2019-10-12 12:00
Downtime exists with start_time: 1570896000, and duration 172800 seconds ..
NOT SCHEDULING

Re: Possible reoccurring downtime bug

Posted: Wed Oct 09, 2019 1:32 pm
by mbellerue
I'm not seeing anything for 2019-10-05. Could you PM me a fresh system profile, as well as the time that your email notification was received and the name of the host or service in question? That will give us a starting point to track this down.