Here is the Sendmail grep:
[1328742000] CURRENT SERVICE STATE: hostname.futureweb.at;Mailserver
Port 25 Check - Sendmail;OK;HARD;1;SMTP OK - 0.024 sec. response time
[1328744759] EXTERNAL COMMAND:
SCHEDULE_SVC_DOWNTIME;hostname.futureweb.at;Mailserver Port 25 Check -
Sendmail;1328744520;1328751720;0;0;1800;futureweb;Downtime set by futureweb
[1328744884] SERVICE ALERT: hostname.futureweb.at;Mailserver Port 25
Check - Sendmail;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10 seconds
[1328744884] SERVICE EVENT HANDLER: hostname.futureweb.at;Mailserver
Port 25 Check - Sendmail;CRITICAL;SOFT;1;restart_by_ssh!sendmail
[1328744941] SERVICE ALERT: hostname.futureweb.at;Mailserver Port 25
Check - Sendmail;CRITICAL;SOFT;2;CRITICAL - Socket timeout after 10 seconds
[1328744941] SERVICE EVENT HANDLER: hostname.futureweb.at;Mailserver
Port 25 Check - Sendmail;CRITICAL;SOFT;2;restart_by_ssh!sendmail
[1328745014] SERVICE ALERT: hostname.futureweb.at;Mailserver Port 25
Check - Sendmail;CRITICAL;HARD;3;CRITICAL - Socket timeout after 10 seconds
[1328745014] SERVICE DOWNTIME ALERT: hostname.futureweb.at;Mailserver
Port 25 Check - Sendmail;STARTED; Service has entered a period of scheduled
downtime
[1328745014] SERVICE EVENT HANDLER: hostname.futureweb.at;Mailserver
Port 25 Check - Sendmail;CRITICAL;HARD;3;restart_by_ssh!sendmail
[1328745291] SERVICE ALERT: hostname.futureweb.at;Mailserver Port 25
Check - Sendmail;OK;HARD;3;SMTP OK - 0.022 sec. response time
[1328745291] SERVICE EVENT HANDLER: hostname.futureweb.at;Mailserver
Port 25 Check - Sendmail;OK;HARD;3;restart_by_ssh!sendmail
[1328775426] EXTERNAL COMMAND:
SCHEDULE_FORCED_SVC_CHECK;hostname.futureweb.at;Mailserver Port 25 Check -
Sendmail;1328775425
[1328775439] SERVICE ALERT: hostname.futureweb.at;Mailserver Port 25
Check - Sendmail;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10 seconds
[1328775439] SERVICE EVENT HANDLER: hostname.futureweb.at;Mailserver
Port 25 Check - Sendmail;CRITICAL;SOFT;1;restart_by_ssh!sendmail
[1328775466] EXTERNAL COMMAND:
SCHEDULE_FORCED_SVC_CHECK;hostname.futureweb.at;Mailserver Port 25 Check -
Sendmail;1328775465
[1328775469] SERVICE ALERT: hostname.futureweb.at;Mailserver Port 25
Check - Sendmail;OK;SOFT;2;SMTP OK - 0.022 sec. response time
[1328775469] SERVICE EVENT HANDLER: hostname.futureweb.at;Mailserver
Port 25 Check - Sendmail;OK;SOFT;2;restart_by_ssh!sendmail
And another Question - why does it send the Event-Handler even when in
scheduled downtime?!?
And Centreon also shown me that the service is in scheduled downtime ... even
if it tells me that the downtime has ended ... (centreon shows me only
information it get's from icinga ...)
Andreas
-----Ursprüngliche Nachricht-----
Von: Wolfgang [mailto:w...@gmx.net]
Gesendet: Donnerstag, 09. Februar 2012 12:30
An: icinga-users@lists.sourceforge.net
Betreff: Re: [icinga-users] scheduled downtime question
Hm. I'd grep for "Sendmail" in icinga.log to check what might have happened.
The service was scheduled for downtime and Centreon shows that the downtime
ended but the classic UI doesn't. I wonder why.
"recurring" stepped into my mind because of the Centreon screenshot.
Am 09.02.2012 11:41, schrieb Andreas Schnederle-Wagner - Futureweb.at:
> 1) service detail shows a downtime but I don't know why ... should not be in
> scheduled downtime? (http://temp.in.futureweb.at/icinga/downtime3.jpg)
> Weird thing is that no scheduled downtime is shown anywhere except on
> the "in scheduled downtime" ... so I can't delete it anywhere?
> 2) in icinga.log (grep on scheduled)
> [1328744837] HOST DOWNTIME ALERT: hostname.futureweb.at;STARTED; Host
> has entered a period of scheduled downtime
> [1328745014] SERVICE DOWNTIME ALERT: hostname.futureweb.at;Mailserver
> Port 25 Check - Sendmail;STARTED; Service has entered a period of
> scheduled downtime
> 3) should be no recurring downtime - was a flexible downtime
> 4) GUIs used: Icinga Classic and Centreon
>
> Andreas
>
> -----Ursprüngliche Nachricht-----
> Von: Michael Friedrich [mailto:michael.friedr...@univie.ac.at]
> Gesendet: Donnerstag, 09. Februar 2012 10:43
> An: icinga-users@lists.sourceforge.net
> Betreff: Re: [icinga-users] scheduled downtime question
>
> Wolfgang wrote:
>> Am 09.02.2012 10:08, schrieb Andreas Schnederle-Wagner - Futureweb.at:
>>> -----Ursprüngliche Nachricht-----
>>> Von: Michael Friedrich [mailto:michael.friedr...@univie.ac.at]
>>> Gesendet: Donnerstag, 09. Februar 2012 09:57
>>> An: icinga-users@lists.sourceforge.net
>>> Betreff: Re: [icinga-users] scheduled downtime question
>>>
>>>>> Andreas Schnederle-Wagner - Futureweb.at wrote:
>>>>> Hi there,
>>>>> got a little Question about scheduled downtimes.
>>>>> Yesterday night we entered a flexible downtime on a few services
>>>>> for maintenance.
>>>>>
>>>>> Today I checked the Icinga Status of those Services - everything
>>>>> looks fine except for one Service - in the "Service View" of
>>>>> Icinga Classic GUI there is a grey downtime sign which tells me
>>>>> "This host is currently in a period of scheduled downtime".
>>>>> The Service with this sign is the only one which actually noticed
>>>>> the scheduled downtime - all other haven't set a "actual end" time
>>>>> - so I guess the downtime was too short for them to notice.
>>>>> But why does this single Service still show me the downtime sign?!?
>>>>> (scheduled downtime start time was 09.02.2012 00:42; endtime:
>>>>> 09.02.2010 02:42)
>>>>> Hope someone can help me on this?
>>>> for gui problems which are not describable in text prosa - screenshots.
>>> Hi,
>>>
>>> Here is the Screenshot:
>>> http://temp.in.futureweb.at/icinga/downtime1.jpg
>>> Here some more information:
>>> http://temp.in.futureweb.at/icinga/downtime2.jpg
>>>
>>> When I look into "System --> Downtime" within Classic it won't show me
>>> anything.
>>>
>>> Andreas
>>>
>> Please check icinga.log for messages related to the start/end of the
>> downtimes.
>> BTW: Which tool are you using for scheduling recurring downtimes as
>> the second screenshot doesn't show a familiar view
> recurring? but yes, the view looks different to any guis i've seen so far.
>
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning Cloud computing makes
use of virtualization - but cloud computing also focuses on allowing computing
to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
