New satellite is not working

Icinga Web Modules Icinga Director
1

Hi guys,
I’ve just add a new satellite on my Icinga environment and this satellite is not working.
When I add some host to be checked by this new satellite the status stays “Pending”.
I can also see that the check source is empty even selecting the zone of this satellite.

2

The check source is filled after its first run means as long as the check is pending this field stays empty.

Regarding the new satellite common issues are wrong zones.conf or certificate errors. If you share your zones.conf from master and new satellite we could check. For certificates you could run

icinga2 ca list

and check for unsigned certificate requests. And you can check the logs on master and new satellite for any hint.

1 Like
3

Hi Roland,
The command “icinga2 ca list” brings empty list
On log files it seems that the nodes are communicating

Zones.conf - master node
object Endpoint “nldeinnmo001” {
}

// this satellite is working
object Endpoint “brapirnmo001” {
host = “12.12.12.12”
port = “5665”
}

//this satellite is not working
object Endpoint “nldboxnmo001” {
host = “14.14.14.14”
port = “5665”
}

object Zone “master” {
endpoints = [ “nldeinnmo001” ]
}

object Zone “brapir.satellite.zone” {
endpoints = [ “brapirnmo001” ]
parent = “master”
}

object Zone “nldbox.satellite.zone” {
endpoints = [ “nldboxnmo001” ]
parent = “master”
}

object Zone “global-templates” {
global = true
}

object Zone “director-global” {
global = true
}

4

zones.conf for master looks ok. What about zones.conf for the new satellite?

Empty list for icinga2 ca list is typical for certificate request which are older than 7 days IIRC or not received requests.

The logs tells about valid or unsigned certificates.

BTW: When posting conf files please use code blocks for better readability.

1 Like
5

See below the zone.conf of the satellite that is not working.
How can I share the log files?

object Endpoint "nldeinnmo001" {
        host = "11.11.11.11"
        port = "5665"
}

object Zone "master" {
        endpoints = [ "nldeinnmo001" ]
}

object Endpoint "nldboxnmo001" {
}

object Zone "nldbox.satellite.zone" {
        endpoints = [ "nldboxnmo001" ]
        parent = "master"
}

object Zone "global-templates" {
        global = true
}

object Zone "director-global" {
        global = true
}
6

I do not see any mistakes. You could also verify both on master and new satellite if the objects are existing:

icinga2 object list -t endpoint
icinga2 object list -t zone

For posting logs you can also use code blocks (and of course not the whole file but only the relevant part).

My last idea is about networking:

  • icinga2 has port 5665/tcp open?
  • no packetfilter aka firewall is blocking?
  • SELinux or similar is not blocking?
  • ip addresses are correct?
7

Forgot to mention that it is best practice to monitor zones using cluster and/or cluster-zone. That would also help in the case.

8

Now my satellite that was working, stopped.
The stranger thing is when I try to add some host linked to this satellite, the ckeck status stay with “pending”. The hosts that I’ve added before is working.