Acknowledgements are not working without an expiry time #2911

pgress · 2017-08-04T08:52:09Z

We try to acknowledge an Service which is in Warning-State. We write an Comment and set Sticky Acknowledgement and press the button "Acknowledge Problem".
After this we get the following errror:

icinga2: Can't send external Icinga command: 409 Acknowledgement 'expiry' timestamp must be in the future for object localhost!Disk.

#0 /usr/share/icingaweb2/modules/monitoring/application/forms/Command/Object/AcknowledgeProblemCommandForm.php(159): Icinga\Module\Monitoring\Command\Transport\CommandTransport->send(Object(Icinga\Module\Monitoring\Command\Object\AcknowledgeProblemCommand))
#1 /usr/share/php/Icinga/Web/Form.php(1152): Icinga\Module\Monitoring\Forms\Command\Object\AcknowledgeProblemCommandForm->onSuccess()
#2 /usr/share/icingaweb2/modules/monitoring/library/Monitoring/Web/Controller/MonitoredObjectController.php(129): Icinga\Web\Form->handleRequest()
#3 /usr/share/icingaweb2/modules/monitoring/application/controllers/ServiceController.php(77): Icinga\Module\Monitoring\Web\Controller\MonitoredObjectController->handleCommandForm(Object(Icinga\Module\Monitoring\Forms\Command\Object\AcknowledgeProblemCommandForm))
#4 /usr/share/icingaweb2/library/vendor/Zend/Controller/Action.php(507): Icinga\Module\Monitoring\Controllers\ServiceController->acknowledgeProblemAction()
#5 /usr/share/php/Icinga/Web/Controller/Dispatcher.php(76): Zend_Controller_Action->dispatch('acknowledgeProb...')
#6 /usr/share/icingaweb2/library/vendor/Zend/Controller/Front.php(937): Icinga\Web\Controller\Dispatcher->dispatch(Object(Icinga\Web\Request), Object(Icinga\Web\Response))
#7 /usr/share/php/Icinga/Application/Web.php(389): Zend_Controller_Front->dispatch(Object(Icinga\Web\Request), Object(Icinga\Web\Response))
#8 /usr/share/php/Icinga/Application/webrouter.php(109): Icinga\Application\Web->dispatch()
#9 /usr/share/icingaweb2/public/index.php(4): require_once('/usr/share/php/...')
#10 {main}

The Command-Transport is send within the Icinga2-API.

Your Environment

Icinga Web 2 version and modules (System - About):
cube | 1.0.0
graphite | 0.0.0.5
monitoring | 2.4.1
Version used (icinga2 --version): version: r2.7.0-1
Operating System and version: Debian GNU/Linux 8.9 (jessie)
Enabled features (icinga2 feature list): Enabled features: api checker command graphite ido-mysql mainlog notification
Config validation (icinga2 daemon -C): no error
If you run multiple Icinga 2 instances, the zones.conf file (or icinga2 object list --type Endpoint and icinga2 object list --type Zone) from all affected nodes.

host001:/root # icinga2 object list --type Endpoint
Object 'host001.localdomain' of type 'Endpoint':
  % declared in '/etc/icinga2/zones.conf', lines 1:0-1:47
  * __name = "host001.localdomain"
  * host = "10.0.0.133"
    % = modified in '/etc/icinga2/zones.conf', lines 2:3-2:22
  * log_duration = 86400
  * name = "host001.localdomain"
  * package = "_etc"
  * port = "5665"
  * source_location
    * first_column = 0
    * first_line = 1
    * last_column = 47
    * last_line = 1
    * path = "/etc/icinga2/zones.conf"
  * templates = [ "host001.localdomain" ]
    % = modified in '/etc/icinga2/zones.conf', lines 1:0-1:47
  * type = "Endpoint"
  * zone = ""

Object 'host002.localdomain' of type 'Endpoint':
  % declared in '/etc/icinga2/zones.conf', lines 5:1-5:48
  * __name = "host002.localdomain"
  * host = "10.0.0.134"
    % = modified in '/etc/icinga2/zones.conf', lines 6:3-6:22
  * log_duration = 86400
  * name = "host002.localdomain"
  * package = "_etc"
  * port = "5665"
  * source_location
    * first_column = 1
    * first_line = 5
    * last_column = 48
    * last_line = 5
    * path = "/etc/icinga2/zones.conf"
  * templates = [ "host002.localdomain" ]
    % = modified in '/etc/icinga2/zones.conf', lines 5:1-5:48
  * type = "Endpoint"
  * zone = ""
host001:/root # icinga2 object list --type Zone
Object 'global_zone' of type 'Zone':
  % declared in '/etc/icinga2/zones.conf', lines 13:1-13:25
  * __name = "global_zone"
  * endpoints = null
  * global = true
    % = modified in '/etc/icinga2/zones.conf', lines 14:3-14:15
  * name = "global_zone"
  * package = "_etc"
  * parent = ""
  * source_location
    * first_column = 1
    * first_line = 13
    * last_column = 25
    * last_line = 13
    * path = "/etc/icinga2/zones.conf"
  * templates = [ "global_zone" ]
    % = modified in '/etc/icinga2/zones.conf', lines 13:1-13:25
  * type = "Zone"
  * zone = ""

Object 'master' of type 'Zone':
  % declared in '/etc/icinga2/zones.conf', lines 9:1-9:20
  * __name = "master"
  * endpoints = [ "host001.localdomain", "host002.localdomain" ]
    % = modified in '/etc/icinga2/zones.conf', lines 10:3-10:84
  * global = false
  * name = "master"
  * package = "_etc"
  * parent = ""
  * source_location
    * first_column = 1
    * first_line = 9
    * last_column = 20
    * last_line = 9
    * path = "/etc/icinga2/zones.conf"
  * templates = [ "master" ]
    % = modified in '/etc/icinga2/zones.conf', lines 9:1-9:20
  * type = "Zone"
  * zone = ""

The text was updated successfully, but these errors were encountered:

sahnd · 2017-08-07T07:08:30Z

I am facing the same issue.
Seems as if icingaweb2 implicitly sets a (faulty) expire time for acknowledgements, if "Use Expire Time" is not checked.

localhorst-org · 2017-08-07T08:58:40Z

same for me after update from http://packages.icinga.org/ubuntu icinga-xenial main to version 2.7.0-1.xenial

icinga2: Can't send external Icinga command: 409 Acknowledgement 'expiry' timestamp must be in the future for object xxx-xxxx-xxx-xxx!xxxxxxx_xxx_xxx_xxxxxxxx.

#0 /usr/share/icingaweb2/modules/monitoring/application/forms/Command/Object/AcknowledgeProblemCommandForm.php(159): Icinga\Module\Monitoring\Command\Transport\CommandTransport->send(Object(Icinga\Module\Monitoring\Command\Object\AcknowledgeProblemCommand))
#1 /usr/share/php/Icinga/Web/Form.php(1152): Icinga\Module\Monitoring\Forms\Command\Object\AcknowledgeProblemCommandForm->onSuccess()
#2 /usr/share/icingaweb2/modules/monitoring/library/Monitoring/Web/Controller/MonitoredObjectController.php(129): Icinga\Web\Form->handleRequest()
#3 /usr/share/icingaweb2/modules/monitoring/application/controllers/ServiceController.php(77): Icinga\Module\Monitoring\Web\Controller\MonitoredObjectController->handleCommandForm(Object(Icinga\Module\Monitoring\Forms\Command\Object\AcknowledgeProblemCommandForm))
#4 /usr/share/icingaweb2/library/vendor/Zend/Controller/Action.php(507): Icinga\Module\Monitoring\Controllers\ServiceController->acknowledgeProblemAction()
#5 /usr/share/php/Icinga/Web/Controller/Dispatcher.php(76): Zend_Controller_Action->dispatch('acknowledgeProb...')
#6 /usr/share/icingaweb2/library/vendor/Zend/Controller/Front.php(937): Icinga\Web\Controller\Dispatcher->dispatch(Object(Icinga\Web\Request), Object(Icinga\Web\Response))
#7 /usr/share/php/Icinga/Application/Web.php(389): Zend_Controller_Front->dispatch(Object(Icinga\Web\Request), Object(Icinga\Web\Response))
#8 /usr/share/php/Icinga/Application/webrouter.php(109): Icinga\Application\Web->dispatch()
#9 /usr/share/icingaweb2/public/index.php(4): require_once('/usr/share/php/...')
#10 {main}

bcogel · 2017-08-08T07:55:06Z

Same here.

RHEL 6.9 , icinga2-2.7.0-1.el6, icingacli-2.4.1-1.el6, icingaweb2-2.4.1-1.el6

We're using transport via API to get the ACKs and comments on our two servers in the master zone in sync. For redundancy and failover they are on different locations and both have icingaweb2 with separate databases installed.

dnsmichi · 2017-08-08T10:40:35Z

Can be reproduced using the Vagrant boxes & snapshot packages / git master, 72dfa6d

@lippserd

Icinga 2 v2.7.0 is more strict with the `expiry` attribute if sent (cannot be null, or in the past). While acknowledgments with expire time worked well (and do so with this patch), the command renderer did not check whether the value is actually not null before setting it into the data form. The boolean value from the checkbox is not available in the command renderer unfortunately. @lippserd: Verified working with and without expire time inside the Vagrant boxes. fixes #2911

dnsmichi · 2017-08-08T11:00:32Z

Please test the referenced PR.

pgress · 2017-08-08T12:18:01Z

Looks and works excellent

localhorst-org · 2017-08-08T13:29:08Z

worked also for me thx!

bcogel · 2017-08-08T13:32:23Z

Works for me too...

snooops · 2017-08-09T06:11:44Z

works on debian jessie 64bit package

dnsmichi mentioned this issue Aug 8, 2017

API Commands: Only send acknowledgement expire time if not null #2914

Merged

dnsmichi mentioned this issue Aug 9, 2017

409 Acknowledgement 'expiry' timestamp must be in the future for object after upgrade to 2.7.0 Icinga/icinga2#5481

Closed

lippserd closed this as completed in #2914 Aug 9, 2017

dnsmichi mentioned this issue Aug 10, 2017

Acknowledgements from Icingaweb2 2.4.1 do not work with Icinga2 2.7.0 Icinga/icinga2#5493

Closed

dnsmichi mentioned this issue Sep 4, 2017

Error when acknowledging in icingaweb2 after updating icinga2 to v2.7 #2937

Closed

lippserd changed the title ~~Acknowledgements arent working without an expiry time~~ Acknowledgements are not working without an expiry time Sep 8, 2017

lippserd added bug Something isn't working area/monitoring Affects the monitoring module labels Sep 8, 2017

lippserd added this to the 2.4.2 milestone Sep 8, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Acknowledgements are not working without an expiry time #2911

Acknowledgements are not working without an expiry time #2911

pgress commented Aug 4, 2017 •

edited

Loading

sahnd commented Aug 7, 2017

localhorst-org commented Aug 7, 2017 •

edited by lazyfrosch

Loading

bcogel commented Aug 8, 2017

dnsmichi commented Aug 8, 2017

dnsmichi commented Aug 8, 2017

pgress commented Aug 8, 2017 •

edited

Loading

localhorst-org commented Aug 8, 2017

bcogel commented Aug 8, 2017

snooops commented Aug 9, 2017

Acknowledgements are not working without an expiry time #2911

Acknowledgements are not working without an expiry time #2911

Comments

pgress commented Aug 4, 2017 • edited Loading

Your Environment

sahnd commented Aug 7, 2017

localhorst-org commented Aug 7, 2017 • edited by lazyfrosch Loading

bcogel commented Aug 8, 2017

dnsmichi commented Aug 8, 2017

dnsmichi commented Aug 8, 2017

pgress commented Aug 8, 2017 • edited Loading

localhorst-org commented Aug 8, 2017

bcogel commented Aug 8, 2017

snooops commented Aug 9, 2017

pgress commented Aug 4, 2017 •

edited

Loading

localhorst-org commented Aug 7, 2017 •

edited by lazyfrosch

Loading

pgress commented Aug 8, 2017 •

edited

Loading