The issue here, I think, is that the slaves aren’t collecting their config from the master, and thus aren’t polling anything.
I just installed smokeping on a couple of systems here, and I can’t get the stupid thing to talk to the master from the slaves, it’s not even attempting to.
I guess you’ve only replaced the master though, so I’m not sure why it’s behaving like this. Certainly the slaves need to access the URL defined to collect their config, so check that first? Perhaps an HTTPS redirect or something is confusing them.
It’s been a decade since I used smokeping, so I’m not sure why it’s not working. :)
Adam.
From: Joey Stanford nv0n@rmham.org Sent: 19 December 2020 21:46 To: Observium observium@observium.org Cc: Adam Armstrong adama@observium.org Subject: Re: [Observium] Smokeping graphs post migration
It seems this bit of code isn’t being triggered at all, which suggests none of your filenames have a tilde in them?
correct
As a side note, smokeping-generate vs my actual targets appears to differ.
# jstanford @ observium in ~ [14:44:02]
$ diff smokeping-obs-script.txt smokeping-actual-targert.txt
174,179d173
< ++ radio-cedarwood_fremont_rmham
< host = radio-cedarwood.fremont.rmham
<
< ++ radio-cedarwood_pueblo_rmham
< host = radio-cedarwood.pueblo.rmham
<
582,584d575
< ++ router_n5zgt_qth
< host = router.n5zgt.qth
<
737,739d727
<
< ++ wifi_ac0kq_rmham
< host = wifi.ac0kq.rmham