Unable to start sensu-client service (0.13.1-1 msi) on Windows R2 Standard

David_Clark · August 12, 2014, 10:50am

Hi,

I’ve been trying to set up a sensu client on a Windows R2 machine by following the instructions at http://sensuapp.org/docs/latest/windows after installing from the 0.13.1-1.msi file.

However, the service fails to start and the sensu-client.log is showing the following:

C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `set_tls_parms’: wrong number of arguments (6 for 4) (ArgumentError)

Any ideas where I should look to resolve this. The full stack is shown below:

{“timestamp”:“2014-08-12T11:36:53.198799+0200”,“level”:“warn”,“message”:“config file applied changes”,“file”:“C:/opt/sensu/conf.d/config.json”,“changes”:{}}

C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `set_tls_parms’: wrong number of arguments (6 for 4) (ArgumentError)

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `start_tls'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:1154:in `upgrade_to_tls_if_necessary'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:571:in `post_init'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:58:in `block in new'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:49:in `instance_eval'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:49:in `new'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:679:in `bind_connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:649:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:445:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp.rb:242:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-1.0.0/lib/sensu/transport/rabbitmq.rb:17:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-1.0.0/lib/sensu/transport.rb:22:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/daemon.rb:133:in `setup_transport'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:244:in `start'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:13:in `block in run'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `call'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `run_machine'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `run'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:12:in `run'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/bin/sensu-client:10:in `<top (required)>'

from C:/opt/sensu/embedded/bin/sensu-client:23:in `load'

My config.json file looks similar to this (apart from the host and password

{

“rabbitmq”: {

“host”: “myrabbithost.net”,

“port”: 5671,

“vhost”: “/sensu”,

“user”: “sensu”,

“password”: “mypassword”,

“ssl”: {

“cert_chain_file”: “/opt/sensu/ssl/cert.pem”,

“private_key_file”: “/opt/sensu/ssl/key.pem”

}

Thanks

David

David_Clark · August 12, 2014, 10:53am

Some additional information: the installed gems are as follows:

activesupport (4.1.4)

amq-protocol (1.9.2)

amqp (1.3.0)

async_sinatra (1.0.0)

bigdecimal (1.2.0)

childprocess (0.5.3)

daemons (1.1.9)

em-redis-unified (0.5.0)

em-worker (0.0.2)

eventmachine (1.0.3 x86-mingw32)

ffi (1.9.3 x86-mingw32)

i18n (0.6.11)

io-console (0.4.2)

json (1.7.7)

minitest (5.4.0, 4.3.2)

mixlib-cli (1.5.0)

multi_json (1.10.1)

psych (2.0.0)

rack (1.5.2)

rack-protection (1.5.3)

rake (0.9.6)

rdoc (4.0.0)

sensu (0.13.1)

sensu-em (2.4.0)

sensu-extension (1.0.0)

sensu-extensions (1.0.0)

sensu-logger (1.0.0)

sensu-plugin (0.3.0)

sensu-settings (1.0.0)

sensu-spawn (1.0.0)

sensu-transport (1.0.0)

sinatra (1.3.5)

test-unit (2.0.0.0)

thin (1.5.0)

thread_safe (0.3.4)

tilt (1.4.1)

tzinfo (1.2.2)

uuidtools (2.1.4)

Alexander_York · September 3, 2014, 9:53pm

David,

I have the same problem. I've noticed the question hit the irc around three times worth no answer. Have you discovered anything new since you posted?

Kyle_Anderson · September 3, 2014, 10:29pm

This is kinda a crazy shot in the dark, but this sounds like the way
sensu-em is calling set_tls_parms per your stack trace:

github.com

sensu/sensu-em/blob/d751f66bf74b1655c230abed048712408d399afd/lib/em/connection.rb#L419


      
          # @see #ssl_verify_peer
          def start_tls args={}
            priv_key, cert_chain, verify_peer, use_tls, cipher_list = args.values_at(:private_key_file, :cert_chain_file, :verify_peer, :use_tls, :cipher_list)
          
            [priv_key, cert_chain].each do |file|
              next if file.nil? or file.empty?
              raise FileNotFoundException,
              "Could not find #{file} for start_tls" unless File.exists? file
            end
          
            EventMachine::set_tls_parms(@signature, priv_key || '', cert_chain || '', verify_peer, (use_tls ? true : false), cipher_list || '')
            EventMachine::start_tls @signature
          end
          
          # If [TLS](http://en.wikipedia.org/wiki/Transport_Layer_Security) is active on the connection, returns the remote [X509 certificate](http://en.wikipedia.org/wiki/X.509)
          # as a string, in the popular [PEM format](http://en.wikipedia.org/wiki/Privacy_Enhanced_Mail). This can then be used for arbitrary validation
          # of a peer's certificate in your code.
          #
          # This should be called in/after the {#ssl_handshake_completed} callback, which indicates
          # that SSL/TLS is active. Using this callback is important, because the certificate may not
          # be available until the time it is executed. Using #post_init or #connection_completed is

Is using 6 args, like normal, but that error hints that it is using
the *wrong* rubyeventmachine.so. (dll?)

Compare

Stock, 4 args:

github.com

eventmachine/eventmachine/blob/b7f2b34d6b8d04aa8fdb017059833b64c602d819/ext/rubymain.cpp#L1227


      
          	EM_eUnsupported = rb_define_class_under (EmModule, "Unsupported", rb_eRuntimeError);
          
          	rb_define_module_function (EmModule, "initialize_event_machine", (VALUE(*)(...))t_initialize_event_machine, 0);
          	rb_define_module_function (EmModule, "run_machine", (VALUE(*)(...))t_run_machine_without_threads, 0);
          	rb_define_module_function (EmModule, "run_machine_without_threads", (VALUE(*)(...))t_run_machine_without_threads, 0);
          	rb_define_module_function (EmModule, "add_oneshot_timer", (VALUE(*)(...))t_add_oneshot_timer, 1);
          	rb_define_module_function (EmModule, "start_tcp_server", (VALUE(*)(...))t_start_server, 2);
          	rb_define_module_function (EmModule, "stop_tcp_server", (VALUE(*)(...))t_stop_server, 1);
          	rb_define_module_function (EmModule, "start_unix_server", (VALUE(*)(...))t_start_unix_server, 1);
          	rb_define_module_function (EmModule, "attach_sd", (VALUE(*)(...))t_attach_sd, 1);
          	rb_define_module_function (EmModule, "set_tls_parms", (VALUE(*)(...))t_set_tls_parms, 4);
          	rb_define_module_function (EmModule, "start_tls", (VALUE(*)(...))t_start_tls, 1);
          	rb_define_module_function (EmModule, "get_peer_cert", (VALUE(*)(...))t_get_peer_cert, 1);
          	rb_define_module_function (EmModule, "send_data", (VALUE(*)(...))t_send_data, 3);
          	rb_define_module_function (EmModule, "send_datagram", (VALUE(*)(...))t_send_datagram, 5);
          	rb_define_module_function (EmModule, "close_connection", (VALUE(*)(...))t_close_connection, 2);
          	rb_define_module_function (EmModule, "report_connection_error_status", (VALUE(*)(...))t_report_connection_error_status, 1);
          	rb_define_module_function (EmModule, "connect_server", (VALUE(*)(...))t_connect_server, 2);
          	rb_define_module_function (EmModule, "bind_connect_server", (VALUE(*)(...))t_bind_connect_server, 4);
          	rb_define_module_function (EmModule, "connect_unix_server", (VALUE(*)(...))t_connect_unix_server, 1);

To sensu-em, 6 args:

github.com

sensu/sensu-em/blob/d751f66bf74b1655c230abed048712408d399afd/ext/rubymain.cpp#L1227


      
          	EM_eUnsupported = rb_define_class_under (EmModule, "Unsupported", rb_eRuntimeError);
          
          	rb_define_module_function (EmModule, "initialize_event_machine", (VALUE(*)(...))t_initialize_event_machine, 0);
          	rb_define_module_function (EmModule, "run_machine", (VALUE(*)(...))t_run_machine_without_threads, 0);
          	rb_define_module_function (EmModule, "run_machine_without_threads", (VALUE(*)(...))t_run_machine_without_threads, 0);
          	rb_define_module_function (EmModule, "add_oneshot_timer", (VALUE(*)(...))t_add_oneshot_timer, 1);
          	rb_define_module_function (EmModule, "start_tcp_server", (VALUE(*)(...))t_start_server, 2);
          	rb_define_module_function (EmModule, "stop_tcp_server", (VALUE(*)(...))t_stop_server, 1);
          	rb_define_module_function (EmModule, "start_unix_server", (VALUE(*)(...))t_start_unix_server, 1);
          	rb_define_module_function (EmModule, "attach_sd", (VALUE(*)(...))t_attach_sd, 1);
          	rb_define_module_function (EmModule, "set_tls_parms", (VALUE(*)(...))t_set_tls_parms, 6);
          	rb_define_module_function (EmModule, "start_tls", (VALUE(*)(...))t_start_tls, 1);
          	rb_define_module_function (EmModule, "get_peer_cert", (VALUE(*)(...))t_get_peer_cert, 1);
          	rb_define_module_function (EmModule, "send_data", (VALUE(*)(...))t_send_data, 3);
          	rb_define_module_function (EmModule, "send_datagram", (VALUE(*)(...))t_send_datagram, 5);
          	rb_define_module_function (EmModule, "close_connection", (VALUE(*)(...))t_close_connection, 2);
          	rb_define_module_function (EmModule, "report_connection_error_status", (VALUE(*)(...))t_report_connection_error_status, 1);
          	rb_define_module_function (EmModule, "connect_server", (VALUE(*)(...))t_connect_server, 2);
          	rb_define_module_function (EmModule, "bind_connect_server", (VALUE(*)(...))t_bind_connect_server, 4);
          	rb_define_module_function (EmModule, "connect_unix_server", (VALUE(*)(...))t_connect_unix_server, 1);

So... why is the sensu client loading the stock EvenMachine instead of
Sensu EM? (best guess at the real issue)

···

On Wed, Sep 3, 2014 at 2:53 PM, Alexander York <a.van.york@gmail.com> wrote:

David,

I have the same problem. I've noticed the question hit the irc around three times worth no answer. Have you discovered anything new since you posted?

Sean_Porter · September 3, 2014, 10:41pm

We need to build sensu-em, on Windows, natively. I have been unsuccessful in doing so. I require help, from someone with more platform experience.

···

On Sep 3, 2014 3:29 PM, “Kyle Anderson” kyle@xkyle.com wrote:

This is kinda a crazy shot in the dark, but this sounds like the way

sensu-em is calling set_tls_parms per your stack trace:

https://github.com/sensu/sensu-em/blob/d751f66bf74b1655c230abed048712408d399afd/lib/em/connection.rb#L419

Is using 6 args, like normal, but that error hints that it is using

the wrong rubyeventmachine.so. (dll?)

Compare

Stock, 4 args:

https://github.com/eventmachine/eventmachine/blob/b7f2b34d6b8d04aa8fdb017059833b64c602d819/ext/rubymain.cpp#L1227

To sensu-em, 6 args:

https://github.com/sensu/sensu-em/blob/d751f66bf74b1655c230abed048712408d399afd/ext/rubymain.cpp#L1227

So… why is the sensu client loading the stock EvenMachine instead of

Sensu EM? (best guess at the real issue)

On Wed, Sep 3, 2014 at 2:53 PM, Alexander York a.van.york@gmail.com wrote:

David,

I have the same problem. I’ve noticed the question hit the irc around three times worth no answer. Have you discovered anything new since you posted?

Alexander_York · September 4, 2014, 1:41am

That’s a fantastic observation …

···

On Wed, Sep 3, 2014 at 6:29 PM, Kyle Anderson kyle@xkyle.com wrote:

This is kinda a crazy shot in the dark, but this sounds like the way

sensu-em is calling set_tls_parms per your stack trace:

https://github.com/sensu/sensu-em/blob/d751f66bf74b1655c230abed048712408d399afd/lib/em/connection.rb#L419

Is using 6 args, like normal, but that error hints that it is using

the wrong rubyeventmachine.so. (dll?)

Compare

Stock, 4 args:

https://github.com/eventmachine/eventmachine/blob/b7f2b34d6b8d04aa8fdb017059833b64c602d819/ext/rubymain.cpp#L1227

To sensu-em, 6 args:

https://github.com/sensu/sensu-em/blob/d751f66bf74b1655c230abed048712408d399afd/ext/rubymain.cpp#L1227

So… why is the sensu client loading the stock EvenMachine instead of

Sensu EM? (best guess at the real issue)

On Wed, Sep 3, 2014 at 2:53 PM, Alexander York a.van.york@gmail.com wrote:

David,

I have the same problem. I’ve noticed the question hit the irc around three times worth no answer. Have you discovered anything new since you posted?

Alexander_York · September 4, 2014, 1:43am

I’m not a developer, but I do work with windows daily at my job and tinker in c# apps … I’d love to contribute if I can be of any help … I’d really love to bring Sensu to my edu and dump nagios/scom.

···

On Wed, Sep 3, 2014 at 6:41 PM, Sean Porter portertech@gmail.com wrote:

We need to build sensu-em, on Windows, natively. I have been unsuccessful in doing so. I require help, from someone with more platform experience.

On Sep 3, 2014 3:29 PM, “Kyle Anderson” kyle@xkyle.com wrote:

This is kinda a crazy shot in the dark, but this sounds like the way

sensu-em is calling set_tls_parms per your stack trace:

https://github.com/sensu/sensu-em/blob/d751f66bf74b1655c230abed048712408d399afd/lib/em/connection.rb#L419

Is using 6 args, like normal, but that error hints that it is using

the wrong rubyeventmachine.so. (dll?)

Compare

Stock, 4 args:

https://github.com/eventmachine/eventmachine/blob/b7f2b34d6b8d04aa8fdb017059833b64c602d819/ext/rubymain.cpp#L1227

To sensu-em, 6 args:

https://github.com/sensu/sensu-em/blob/d751f66bf74b1655c230abed048712408d399afd/ext/rubymain.cpp#L1227

So… why is the sensu client loading the stock EvenMachine instead of

Sensu EM? (best guess at the real issue)

On Wed, Sep 3, 2014 at 2:53 PM, Alexander York a.van.york@gmail.com wrote:

David,

I have the same problem. I’ve noticed the question hit the irc around three times worth no answer. Have you discovered anything new since you posted?

Alexander_York · September 4, 2014, 12:50pm

FYI,

found this …

i solved the problem changing line 419 of embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb from:
8:54 AM
EventMachine::set_tls_parms(@signature, priv_key || ‘’, cert_chain || ‘’, verify_peer, (use_tls ? true : false), cipher_list || ‘’)
8:54 AM
8:54 AM

Didn’t work for me, but it’s something …

···

to: EventMachine::set_tls_parms(@signature, priv_key || ‘’, cert_chain || ‘’, false)

On Tuesday, August 12, 2014 6:50:01 AM UTC-4, David Clark wrote:

Hi,

I’ve been trying to set up a sensu client on a Windows R2 machine by following the instructions at http://sensuapp.org/docs/latest/windows after installing from the 0.13.1-1.msi file.

However, the service fails to start and the sensu-client.log is showing the following:

C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `set_tls_parms’: wrong number of arguments (6 for 4) (ArgumentError)

Any ideas where I should look to resolve this. The full stack is shown below:

{“timestamp”:“2014-08-12T11:36:53.198799+0200”,“level”:“warn”,“message”:“config file applied changes”,“file”:“C:/opt/sensu/conf.d/config.json”,“changes”:{}}

C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `set_tls_parms’: wrong number of arguments (6 for 4) (ArgumentError)

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `start_tls’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:1154:in `upgrade_to_tls_if_necessary’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:571:in `post_init’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:58:in `block in new’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:49:in `instance_eval’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:49:in `new’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:679:in `bind_connect’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:649:in `connect’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:445:in `connect’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp.rb:242:in `connect’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-1.0.0/lib/sensu/transport/rabbitmq.rb:17:in `connect’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-1.0.0/lib/sensu/transport.rb:22:in `connect’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/daemon.rb:133:in `setup_transport’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:244:in `start’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:13:in `block in run’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `call’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `run_machine’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `run’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:12:in `run’

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/bin/sensu-client:10:in `<top (required)>’

from C:/opt/sensu/embedded/bin/sensu-client:23:in `load’

My config.json file looks similar to this (apart from the host and password

{

“rabbitmq”: {

“host”: “myrabbithost.net”,

“port”: 5671,

“vhost”: “/sensu”,

“user”: “sensu”,

“password”: “mypassword”,

“ssl”: {

“cert_chain_file”: “/opt/sensu/ssl/cert.pem”,

“private_key_file”: “/opt/sensu/ssl/key.pem”

}

Thanks

David

Wayne_Paden · September 19, 2014, 5:40pm

I was having the same issue and modifying the connections.rb file (as mentioned above) and the client is once again able to connect. Has this been reported as a bug? I know there was a post on the ‘sensu’ twitter account indicating that the 13.1.2 msi should fix the issue but this does not appear to be the case. Am I doing the installation wrong?

···

On Thursday, September 4, 2014 5:50:30 AM UTC-7, Alexander York wrote:

FYI,

found this …

i solved the problem changing line 419 of embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb from:

8:54 AM
EventMachine::set_tls_parms(@signature, priv_key || ‘’, cert_chain || ‘’, verify_peer, (use_tls ? true : false), cipher_list || ‘’)

8:54 AM

8:54 AM
to: EventMachine::set_tls_parms(@signature, priv_key || ‘’, cert_chain || ‘’, false)

Didn’t work for me, but it’s something …

On Tuesday, August 12, 2014 6:50:01 AM UTC-4, David Clark wrote:

Hi,

I’ve been trying to set up a sensu client on a Windows R2 machine by following the instructions at http://sensuapp.org/docs/latest/windows after installing from the 0.13.1-1.msi file.

However, the service fails to start and the sensu-client.log is showing the following:

C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `set_tls_parms’: wrong number of arguments (6 for 4) (ArgumentError)

Any ideas where I should look to resolve this. The full stack is shown below:

{“timestamp”:“2014-08-12T11:36:53.198799+0200”,“level”:“warn”,“message”:“config file applied changes”,“file”:“C:/opt/sensu/conf.d/config.json”,“changes”:{}}

C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `set_tls_parms’: wrong number of arguments (6 for 4) (ArgumentError)

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `start_tls'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:1154:in `upgrade_to_tls_if_necessary'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:571:in `post_init'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:58:in `block in new'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:49:in `instance_eval'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:49:in `new'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:679:in `bind_connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:649:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:445:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp.rb:242:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-1.0.0/lib/sensu/transport/rabbitmq.rb:17:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-1.0.0/lib/sensu/transport.rb:22:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/daemon.rb:133:in `setup_transport'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:244:in `start'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:13:in `block in run'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `call'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `run_machine'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `run'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:12:in `run'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/bin/sensu-client:10:in `<top (required)>'

from C:/opt/sensu/embedded/bin/sensu-client:23:in `load'

My config.json file looks similar to this (apart from the host and password

{

“rabbitmq”: {

“host”: “myrabbithost.net”,

“port”: 5671,

“vhost”: “/sensu”,

“user”: “sensu”,

“password”: “mypassword”,

“ssl”: {

“cert_chain_file”: “/opt/sensu/ssl/cert.pem”,

“private_key_file”: “/opt/sensu/ssl/key.pem”

}

Thanks

David

Stella_Tyler · September 28, 2014, 7:44am

When you say that you use the built-in mutator extension “only_check_output”, how can I use the built-in mutator instead of the graphite one? and what am I need to add in order to send the data to Graphite?

···

Wifi Security Camera | Wireless Security Camera System

On Thursday, September 4, 2014 3:29:45 AM UTC+5, Kyle Anderson wrote:

This is kinda a crazy shot in the dark, but this sounds like the way

sensu-em is calling set_tls_parms per your stack trace:

https://github.com/sensu/sensu-em/blob/d751f66bf74b1655c230abed048712408d399afd/lib/em/connection.rb#L419

Is using 6 args, like normal, but that error hints that it is using

the wrong rubyeventmachine.so. (dll?)

Compare

Stock, 4 args:

https://github.com/eventmachine/eventmachine/blob/b7f2b34d6b8d04aa8fdb017059833b64c602d819/ext/rubymain.cpp#L1227

To sensu-em, 6 args:

https://github.com/sensu/sensu-em/blob/d751f66bf74b1655c230abed048712408d399afd/ext/rubymain.cpp#L1227

So… why is the sensu client loading the stock EvenMachine instead of

Sensu EM? (best guess at the real issue)

On Wed, Sep 3, 2014 at 2:53 PM, Alexander York a.van...@gmail.com wrote:

David,

I have the same problem. I’ve noticed the question hit the irc around three times worth no answer. Have you discovered anything new since you posted?

Alik_Kurdyukov · September 30, 2014, 6:35pm

I created a bug Sensu client fails to start on Windows · Issue #791 · sensu/sensu · GitHub but I see no activity on this. I solved the problem by editing .rb file with Salt I use to deploy client. But this is bad workaround.

Does anyone here knows how to build MSI distribution?

···

On Friday, September 19, 2014 9:40:16 PM UTC+4, Wayne Paden wrote:

I was having the same issue and modifying the connections.rb file (as mentioned above) and the client is once again able to connect. Has this been reported as a bug? I know there was a post on the ‘sensu’ twitter account indicating that the 13.1.2 msi should fix the issue but this does not appear to be the case. Am I doing the installation wrong?

On Thursday, September 4, 2014 5:50:30 AM UTC-7, Alexander York wrote:

FYI,

found this …

i solved the problem changing line 419 of embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb from:

8:54 AM
EventMachine::set_tls_parms(@signature, priv_key || ‘’, cert_chain || ‘’, verify_peer, (use_tls ? true : false), cipher_list || ‘’)

8:54 AM

8:54 AM
to: EventMachine::set_tls_parms(@signature, priv_key || ‘’, cert_chain || ‘’, false)

Didn’t work for me, but it’s something …

On Tuesday, August 12, 2014 6:50:01 AM UTC-4, David Clark wrote:

Hi,

I’ve been trying to set up a sensu client on a Windows R2 machine by following the instructions at http://sensuapp.org/docs/latest/windows after installing from the 0.13.1-1.msi file.

However, the service fails to start and the sensu-client.log is showing the following:

C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `set_tls_parms’: wrong number of arguments (6 for 4) (ArgumentError)

Any ideas where I should look to resolve this. The full stack is shown below:

{“timestamp”:“2014-08-12T11:36:53.198799+0200”,“level”:“warn”,“message”:“config file applied changes”,“file”:“C:/opt/sensu/conf.d/config.json”,“changes”:{}}

C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `set_tls_parms’: wrong number of arguments (6 for 4) (ArgumentError)

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:419:in `start_tls'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:1154:in `upgrade_to_tls_if_necessary'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:571:in `post_init'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:58:in `block in new'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:49:in `instance_eval'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/em/connection.rb:49:in `new'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:679:in `bind_connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:649:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp/session.rb:445:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/amqp-1.3.0/lib/amqp.rb:242:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-1.0.0/lib/sensu/transport/rabbitmq.rb:17:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-transport-1.0.0/lib/sensu/transport.rb:22:in `connect'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/daemon.rb:133:in `setup_transport'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:244:in `start'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:13:in `block in run'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `call'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `run_machine'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `run'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/lib/sensu/client.rb:12:in `run'

from C:/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.13.1/bin/sensu-client:10:in `<top (required)>'

from C:/opt/sensu/embedded/bin/sensu-client:23:in `load'

My config.json file looks similar to this (apart from the host and password

{

“rabbitmq”: {

“host”: “myrabbithost.net”,

“port”: 5671,

“vhost”: “/sensu”,

“user”: “sensu”,

“password”: “mypassword”,

“ssl”: {

“cert_chain_file”: “/opt/sensu/ssl/cert.pem”,

“private_key_file”: “/opt/sensu/ssl/key.pem”

}

Thanks

David

Topic		Replies	Views
Start Sensu Client Error Sensu Classic (EOL)	13	680	November 22, 2018
Exception when running sensu client on Windows server 2012 R2 Sensu Classic (EOL)	4	494	February 26, 2015
Windows 2008 R2 client failing to start Sensu Classic (EOL)	4	834	October 4, 2016
Sensu-Client won't start on Windows Server 2012 R2 Sensu Classic (EOL)	0	504	May 22, 2016
Sensu service start on windows fails Sensu Classic (EOL)	1	688	December 1, 2014

Unable to start sensu-client service (0.13.1-1 msi) on Windows R2 Standard

Related topics