ruby - Couldn't start riemann health -


i'm new riemann , new ruby , clojure well.

when implementation of riemann command:

riemann-health

the error message is

riemann::client::tcpsocket::error not connect 127.0.0.1:5555:errno::econnrefused: connection refused - connect(2) /var/lib/gems/1.9.1/gems/riemann-client-0.2.5/lib/riemann/client/tcp_socket.rb:233:in `connect_nonblock' 

my develop environment is:

ubuntu 14.04.2 lts

riemann version 0.2.10.

java version "1.8.0_45"

ruby 1.9.3p484

i'm assuming running riemann , riemann-dash on same computer , not using docker either of these:

riemann listens

  • port 5555 udp events
  • port 5555 tcp events
  • port 5556 tcp queries

so there several combinations of possible problems:

  • riemann not running @ all
  • riemann started up, , fell on , died.
    happens when has no config file instance.
  • riemann not listening on 5555 tcp
  • riemann not listening on 5555 udp
  • riemann listening incorrect interface (aka "bind address") if riemann configured listen 1.2.3.4:5555 not respond connections localhost (127.0.0.1)
  • the connection being blocked firewall (no, don't turn firewall off)
  • riemann listening on udp , sending tcp (or other way around)

once have convinced riemann process still running run

sudo netstat -nlp | grep 5555  

and sure can see riemann infact listening port 5555 both tcp , udp. install netcat , make sure can connect ports

nc -v localhost:5555 

and

nc -uvv localhost:5555 asdfasfd 

(yes need type gobbeldy second example send packet.

if still havent got connection install etherial or tcpdump , start sniffing.

if running docker, , using riemann in udp there whole other set of things check.


Comments

Popular posts from this blog

how to insert data php javascript mysql with multiple array session 2 -

multithreading - Exception in Application constructor -

windows - CertCreateCertificateContext returns CRYPT_E_ASN1_BADTAG / 8009310b -