refresh ignored in sensu 0.13


#1

Hi there,

After updating to 0.13 it seems like the refresh property is completely ignored. Worked perfectly in 0.12 before. Here’s a example check definition:

{

“checks”: {

“check_ntp”: {

“command”: “/etc/sensu/plugins/check-ntp.rb”,

“interval”: 300,

“handlers”: [

“default”

  ],

“subscribers”: [

“base”

],

“standalone”: false,

“occurrences”: 1,

“refresh”: 86400,

“subdue”: {

“begin”: “00:00:00 CEST”,

“end”: “00:00:00 CEST”

},

“playbook”: “https://example.com/xxxxxxxx

}

}

}

``

Events are handled every 5 minutes and my chatroom is kinda full by now :wink:

The changelog doesn’t seem to indicate issues related to the refresh property.

Cheers!

Daniel


#2

“refresh” is from the sensu-plugin lib, doesn’t have anything to do with Sensu core. Is the handler in question using the lib?

Sean.

···

On Jul 28, 2014 4:51 AM, “Daniel Kerwin” d.kerwin@gini.net wrote:

Hi there,

After updating to 0.13 it seems like the refresh property is completely ignored. Worked perfectly in 0.12 before. Here’s a example check definition:

{

“checks”: {

“check_ntp”: {

“command”: “/etc/sensu/plugins/check-ntp.rb”,

“interval”: 300,

“handlers”: [

“default”

  ],

“subscribers”: [

“base”

],

“standalone”: false,

“occurrences”: 1,

“refresh”: 86400,

“subdue”: {

“begin”: “00:00:00 CEST”,

“end”: “00:00:00 CEST”

},

“playbook”: “https://example.com/xxxxxxxx

}

}

}

``

Events are handled every 5 minutes and my chatroom is kinda full by now :wink:

The changelog doesn’t seem to indicate issues related to the refresh property.

Cheers!

Daniel


#3

Actually, this is indeed a bug in 0.13, https://github.com/sensu/sensu/pull/760

···

On Mon, Jul 28, 2014 at 7:48 AM, Sean Porter portertech@gmail.com wrote:

“refresh” is from the sensu-plugin lib, doesn’t have anything to do with Sensu core. Is the handler in question using the lib?

Sean.

On Jul 28, 2014 4:51 AM, “Daniel Kerwin” d.kerwin@gini.net wrote:

Hi there,

After updating to 0.13 it seems like the refresh property is completely ignored. Worked perfectly in 0.12 before. Here’s a example check definition:

{

“checks”: {

“check_ntp”: {

“command”: “/etc/sensu/plugins/check-ntp.rb”,

“interval”: 300,

“handlers”: [

“default”

  ],

“subscribers”: [

“base”

],

“standalone”: false,

“occurrences”: 1,

“refresh”: 86400,

“subdue”: {

“begin”: “00:00:00 CEST”,

“end”: “00:00:00 CEST”

},

“playbook”: “https://example.com/xxxxxxxx

}

}

}

``

Events are handled every 5 minutes and my chatroom is kinda full by now :wink:

The changelog doesn’t seem to indicate issues related to the refresh property.

Cheers!

Daniel


#4

Hi Sean,

Thanks for pointing to the solution (somehow i missed the pull request). Any plans on releasing this soon as a new version? As a user i think it makes a switch to 0.13 very hard.

Thanks and cheers!

Daniel

···

Am Montag, 28. Juli 2014 17:23:30 UTC+2 schrieb portertech:

Actually, this is indeed a bug in 0.13, https://github.com/sensu/sensu/pull/760

On Mon, Jul 28, 2014 at 7:48 AM, Sean Porter porte...@gmail.com wrote:

“refresh” is from the sensu-plugin lib, doesn’t have anything to do with Sensu core. Is the handler in question using the lib?

Sean.

On Jul 28, 2014 4:51 AM, “Daniel Kerwin” d.ke...@gini.net wrote:

Hi there,

After updating to 0.13 it seems like the refresh property is completely ignored. Worked perfectly in 0.12 before. Here’s a example check definition:

{

“checks”: {

“check_ntp”: {

“command”: “/etc/sensu/plugins/check-ntp.rb”,

“interval”: 300,

“handlers”: [

“default”

  ],

“subscribers”: [

“base”

],

“standalone”: false,

“occurrences”: 1,

“refresh”: 86400,

“subdue”: {

“begin”: “00:00:00 CEST”,

“end”: “00:00:00 CEST”

},

“playbook”: “https://example.com/xxxxxxxx

}

}

}

``

Events are handled every 5 minutes and my chatroom is kinda full by now :wink:

The changelog doesn’t seem to indicate issues related to the refresh property.

Cheers!

Daniel


#5

Just merged that fix, and have a PR open that adds a test (just waiting on TravisCI). Will have 0.13.1-1 packages this afternoon.

Sean.

···

On Jul 28, 2014 8:50 AM, “Daniel Kerwin” d.kerwin@gini.net wrote:

Hi Sean,

Thanks for pointing to the solution (somehow i missed the pull request). Any plans on releasing this soon as a new version? As a user i think it makes a switch to 0.13 very hard.

Thanks and cheers!

Daniel

Am Montag, 28. Juli 2014 17:23:30 UTC+2 schrieb portertech:

Actually, this is indeed a bug in 0.13, https://github.com/sensu/sensu/pull/760

On Mon, Jul 28, 2014 at 7:48 AM, Sean Porter porte...@gmail.com wrote:

“refresh” is from the sensu-plugin lib, doesn’t have anything to do with Sensu core. Is the handler in question using the lib?

Sean.

On Jul 28, 2014 4:51 AM, “Daniel Kerwin” d.ke...@gini.net wrote:

Hi there,

After updating to 0.13 it seems like the refresh property is completely ignored. Worked perfectly in 0.12 before. Here’s a example check definition:

{

“checks”: {

“check_ntp”: {

“command”: “/etc/sensu/plugins/check-ntp.rb”,

“interval”: 300,

“handlers”: [

“default”

  ],

“subscribers”: [

“base”

],

“standalone”: false,

“occurrences”: 1,

“refresh”: 86400,

“subdue”: {

“begin”: “00:00:00 CEST”,

“end”: “00:00:00 CEST”

},

“playbook”: “https://example.com/xxxxxxxx

}

}

}

``

Events are handled every 5 minutes and my chatroom is kinda full by now :wink:

The changelog doesn’t seem to indicate issues related to the refresh property.

Cheers!

Daniel


#6

Awesome. I’m looking forward to the new version and will be happy to deploy and test it immediately.

···

Am Montag, 28. Juli 2014 17:52:40 UTC+2 schrieb portertech:

Just merged that fix, and have a PR open that adds a test (just waiting on TravisCI). Will have 0.13.1-1 packages this afternoon.

Sean.

On Jul 28, 2014 8:50 AM, “Daniel Kerwin” d.ke...@gini.net wrote:

Hi Sean,

Thanks for pointing to the solution (somehow i missed the pull request). Any plans on releasing this soon as a new version? As a user i think it makes a switch to 0.13 very hard.

Thanks and cheers!

Daniel

Am Montag, 28. Juli 2014 17:23:30 UTC+2 schrieb portertech:

Actually, this is indeed a bug in 0.13, https://github.com/sensu/sensu/pull/760

On Mon, Jul 28, 2014 at 7:48 AM, Sean Porter porte...@gmail.com wrote:

“refresh” is from the sensu-plugin lib, doesn’t have anything to do with Sensu core. Is the handler in question using the lib?

Sean.

On Jul 28, 2014 4:51 AM, “Daniel Kerwin” d.ke...@gini.net wrote:

Hi there,

After updating to 0.13 it seems like the refresh property is completely ignored. Worked perfectly in 0.12 before. Here’s a example check definition:

{

“checks”: {

“check_ntp”: {

“command”: “/etc/sensu/plugins/check-ntp.rb”,

“interval”: 300,

“handlers”: [

“default”

  ],

“subscribers”: [

“base”

],

“standalone”: false,

“occurrences”: 1,

“refresh”: 86400,

“subdue”: {

“begin”: “00:00:00 CEST”,

“end”: “00:00:00 CEST”

},

“playbook”: “https://example.com/xxxxxxxx

}

}

}

``

Events are handled every 5 minutes and my chatroom is kinda full by now :wink:

The changelog doesn’t seem to indicate issues related to the refresh property.

Cheers!

Daniel


#7

Fantastic! I’ll let you know when it’s ready.

Sean.

···

On Mon, Jul 28, 2014 at 8:54 AM, Daniel Kerwin d.kerwin@gini.net wrote:

Awesome. I’m looking forward to the new version and will be happy to deploy and test it immediately.

Am Montag, 28. Juli 2014 17:52:40 UTC+2 schrieb portertech:

Just merged that fix, and have a PR open that adds a test (just waiting on TravisCI). Will have 0.13.1-1 packages this afternoon.

Sean.

On Jul 28, 2014 8:50 AM, “Daniel Kerwin” d.ke...@gini.net wrote:

Hi Sean,

Thanks for pointing to the solution (somehow i missed the pull request). Any plans on releasing this soon as a new version? As a user i think it makes a switch to 0.13 very hard.

Thanks and cheers!

Daniel

Am Montag, 28. Juli 2014 17:23:30 UTC+2 schrieb portertech:

Actually, this is indeed a bug in 0.13, https://github.com/sensu/sensu/pull/760

On Mon, Jul 28, 2014 at 7:48 AM, Sean Porter porte...@gmail.com wrote:

“refresh” is from the sensu-plugin lib, doesn’t have anything to do with Sensu core. Is the handler in question using the lib?

Sean.

On Jul 28, 2014 4:51 AM, “Daniel Kerwin” d.ke...@gini.net wrote:

Hi there,

After updating to 0.13 it seems like the refresh property is completely ignored. Worked perfectly in 0.12 before. Here’s a example check definition:

{

“checks”: {

“check_ntp”: {

“command”: “/etc/sensu/plugins/check-ntp.rb”,

“interval”: 300,

“handlers”: [

“default”

  ],

“subscribers”: [

“base”

],

“standalone”: false,

“occurrences”: 1,

“refresh”: 86400,

“subdue”: {

“begin”: “00:00:00 CEST”,

“end”: “00:00:00 CEST”

},

“playbook”: “https://example.com/xxxxxxxx

}

}

}

``

Events are handled every 5 minutes and my chatroom is kinda full by now :wink:

The changelog doesn’t seem to indicate issues related to the refresh property.

Cheers!

Daniel


#8

Updated all machines to 0.13.1 and it works again as expected. Thanks!

···

Am Montag, 28. Juli 2014 17:59:52 UTC+2 schrieb portertech:

Fantastic! I’ll let you know when it’s ready.

Sean.

On Mon, Jul 28, 2014 at 8:54 AM, Daniel Kerwin d.ke...@gini.net wrote:

Awesome. I’m looking forward to the new version and will be happy to deploy and test it immediately.

Am Montag, 28. Juli 2014 17:52:40 UTC+2 schrieb portertech:

Just merged that fix, and have a PR open that adds a test (just waiting on TravisCI). Will have 0.13.1-1 packages this afternoon.

Sean.

On Jul 28, 2014 8:50 AM, “Daniel Kerwin” d.ke...@gini.net wrote:

Hi Sean,

Thanks for pointing to the solution (somehow i missed the pull request). Any plans on releasing this soon as a new version? As a user i think it makes a switch to 0.13 very hard.

Thanks and cheers!

Daniel

Am Montag, 28. Juli 2014 17:23:30 UTC+2 schrieb portertech:

Actually, this is indeed a bug in 0.13, https://github.com/sensu/sensu/pull/760

On Mon, Jul 28, 2014 at 7:48 AM, Sean Porter porte...@gmail.com wrote:

“refresh” is from the sensu-plugin lib, doesn’t have anything to do with Sensu core. Is the handler in question using the lib?

Sean.

On Jul 28, 2014 4:51 AM, “Daniel Kerwin” d.ke...@gini.net wrote:

Hi there,

After updating to 0.13 it seems like the refresh property is completely ignored. Worked perfectly in 0.12 before. Here’s a example check definition:

{

“checks”: {

“check_ntp”: {

“command”: “/etc/sensu/plugins/check-ntp.rb”,

“interval”: 300,

“handlers”: [

“default”

  ],

“subscribers”: [

“base”

],

“standalone”: false,

“occurrences”: 1,

“refresh”: 86400,

“subdue”: {

“begin”: “00:00:00 CEST”,

“end”: “00:00:00 CEST”

},

“playbook”: “https://example.com/xxxxxxxx

}

}

}

``

Events are handled every 5 minutes and my chatroom is kinda full by now :wink:

The changelog doesn’t seem to indicate issues related to the refresh property.

Cheers!

Daniel


#9

Hi guys,

i’m running 0.13.1-1 and works well after some hours, stop and show this:

{“timestamp”:“2014-07-29T15:19:41.529468+0000”,“level”:“fatal”,“message”:“transport connection error”,“error”:“rabbitmq channel closed”}

{“timestamp”:“2014-07-29T15:19:41.529605+0000”,“level”:“warn”,“message”:“stopping”}

{“timestamp”:“2014-07-29T15:19:41.529693+0000”,“level”:“warn”,“message”:“unsubscribing from keepalive and result queues”}

{“timestamp”:“2014-07-29T15:19:41.529821+0000”,“level”:“warn”,“message”:“resigning as master”}

{“timestamp”:“2014-07-29T15:19:41.529956+0000”,“level”:“info”,“message”:“completing handlers in progress”,“handlers_in_progress_count”:0}

{“timestamp”:“2014-07-29T15:19:42.030648+0000”,“level”:“warn”,“message”:“stopping reactor”}

Thanks!

Ale

···

El martes, 29 de julio de 2014 05:48:04 UTC-3, Daniel Kerwin escribió:

Updated all machines to 0.13.1 and it works again as expected. Thanks!

Am Montag, 28. Juli 2014 17:59:52 UTC+2 schrieb portertech:

Fantastic! I’ll let you know when it’s ready.

Sean.

On Mon, Jul 28, 2014 at 8:54 AM, Daniel Kerwin d.ke...@gini.net wrote:

Awesome. I’m looking forward to the new version and will be happy to deploy and test it immediately.

Am Montag, 28. Juli 2014 17:52:40 UTC+2 schrieb portertech:

Just merged that fix, and have a PR open that adds a test (just waiting on TravisCI). Will have 0.13.1-1 packages this afternoon.

Sean.

On Jul 28, 2014 8:50 AM, “Daniel Kerwin” d.ke...@gini.net wrote:

Hi Sean,

Thanks for pointing to the solution (somehow i missed the pull request). Any plans on releasing this soon as a new version? As a user i think it makes a switch to 0.13 very hard.

Thanks and cheers!

Daniel

Am Montag, 28. Juli 2014 17:23:30 UTC+2 schrieb portertech:

Actually, this is indeed a bug in 0.13, https://github.com/sensu/sensu/pull/760

On Mon, Jul 28, 2014 at 7:48 AM, Sean Porter porte...@gmail.com wrote:

“refresh” is from the sensu-plugin lib, doesn’t have anything to do with Sensu core. Is the handler in question using the lib?

Sean.

On Jul 28, 2014 4:51 AM, “Daniel Kerwin” d.ke...@gini.net wrote:

Hi there,

After updating to 0.13 it seems like the refresh property is completely ignored. Worked perfectly in 0.12 before. Here’s a example check definition:

{

“checks”: {

“check_ntp”: {

“command”: “/etc/sensu/plugins/check-ntp.rb”,

“interval”: 300,

“handlers”: [

“default”

  ],

“subscribers”: [

“base”

],

“standalone”: false,

“occurrences”: 1,

“refresh”: 86400,

“subdue”: {

“begin”: “00:00:00 CEST”,

“end”: “00:00:00 CEST”

},

“playbook”: “https://example.com/xxxxxxxx

}

}

}

``

Events are handled every 5 minutes and my chatroom is kinda full by now :wink:

The changelog doesn’t seem to indicate issues related to the refresh property.

Cheers!

Daniel