Not able to setup sensu cluster 2.0 and cant access dashboard


#1

Hi Team,

Please find below configuration

I cant setup sensu cluster and cant access dashboard

Please check and let me know the right configration

sensuctl config view

=== Active Configuration

API URL: http://IPA:8080

Sensu Edition: core

Environment: default

Organization: default

Format: tabular

Backend.yml:

state-dir: "/var/lib/sensu"

agent configuration

agent-host: IP1 # listen on all IPv4 and IPv6 addresses

agent-port: 8081

api configuration

#api-host: "[::]" # listen on all IPv4 and IPv6 addresses

#api-port: 8080

api-host: IP1# listen on all IPv4 and IPv6 addresses

api-port: 8080

ssl configuration

#cert-file: "/path/to/ssl/cert.pem"

#key-file: "/path/to/ssl/key.pem"

#trusted-ca-file: "/path/to/trusted-certificate-authorities.pem"

#insecure-skip-tls-verify: false

store configuration

etcd-listen-client-urls: "http://IP1:2379"

etcd-listen-peer-urls: "http:// IP1:2380"

etcd-initial-cluster: "backend-0=http:// IP1:2380"

etcd-initial-advertise-peer-urls: "http:// IP1:2380"

etcd-initial-cluster-state: "new"

etcd-initial-cluster-token: ""

etcd-name: "backend-0"


#2

Hi @balajik515!

How many sensu-backend nodes are you trying to run within your cluster? Based on your configuration, it looks like you are trying to run a single standalone sensu-backend. If it’s the case, then you should simply comment all the store configuration section since you won’t need it. Otherwise, I’d recommend you to look at our clustering guide:

https://docs.sensu.io/sensu-go/5.0/guides/clustering/

Then, make sure to take a look at the backend logs, while restarting the sensu-backend process, with journalctl -u sensu-backend -f or tail -f /var/log/sensu/sensu-backend.log depending on your operating system and let us know if you seed anything relevant.

Thanks


Not able to setup sensu cluster 5.0 and cant access dashboard
#3

@balajik515 it’s also worth noting that putting ``` around your code blocks will help make them a bit more readable, since the # is rendered as markup.