Smokeping Cron script outputting "There are no commands defined in the "smokeping" namespace." in NMS confs

SnarkyWomble · 25 September 2020 03:34

Hi all.
I’m in the process of installing smokeping into an already deployed NMS VM Ubuntu image and am having an issue with the population of the /etc/smokeping/config.d/librenms-probes.conf and librenms-targets.conf files.

I am expecting the target and probe files to be populated by the configured targets and probes from NMS but both files contain only “There are no commands defined in the “smokeping” namespace.”

Both confs are created by an hourly cron script as per the setup guide, they are getting created as expected but the contents are not.

/etc/cron.hourly/librenms-smokeping

#! /usr/bin/env bash

sudo -u librenms /opt/librenms/lnms smokeping:generate --targets > /etc/smokeping/config.d/librenms-targets.conf
sudo -u librenms /opt/librenms/lnms smokeping:generate --probes > /etc/smokeping/config.d/librenms-probes.conf

systemctl reload smokeping > /dev/null 2<&1

I seem to have missed something but have followed the setup guide to the letter with no issues except this.

Have I get the cron script correct or is it more likely I have borked something else up?

For Reference:
/etc/smokeping/config.d/librenms-probes.conf

There are no commands defined in the “smokeping” namespace.

/etc/smokeping/config.d/librenms-targets.conf

There are no commands defined in the “smokeping” namespace.

/etc/smokeping/config

@include /etc/smokeping/config.d/General
@include /etc/smokeping/config.d/Alerts
@include /etc/smokeping/config.d/Database
@include /etc/smokeping/config.d/Presentation
@include /etc/smokeping/config.d/Probes
@include /etc/smokeping/config.d/Slaves
@include /etc/smokeping/config.d/Targets

/etc/smokeping/config.d/Probes

*** Probes ***

@include /etc/smokeping/config.d/librenms-probes.conf

/etc/smokeping/config.d/Targets

*** Targets ***

probe = FPing

menu = Top
title = Network Latency Grapher
remark = Welcome to the SmokePing website of Insert Company Name Here.
Here you will learn all about the latency of our network.

@include /etc/smokeping/config.d/librenms-targets.conf

/etc/smokeping/config.d/pathnames

sendmail = /usr/sbin/sendmail
imgcache = /var/cache/smokeping/images
imgurl = …/smokeping/images
datadir = /var/lib/smokeping
piddir = /var/run/smokeping
smokemail = /etc/smokeping/smokemail
tmail = /etc/smokeping/tmail
dyndir = /var/lib/smokeping/__cgi

/var/lib/smokeping

__cgi Local __sortercache

Relevant part of config.php

$config[‘smokeping’][‘dir’] = ‘/var/lib/smokeping’;
$config[‘smokeping’][‘pings’] = 20;
$config[‘smokeping’][‘probes’] = 2;
$config[‘smokeping’][‘integration’] = true;
$config[‘smokeping’][‘url’] = ‘smokeping/’; // If you have a specific URL or path for smokeping

bofh80 · 26 September 2020 01:36

Are you on master / daily? The docs changed for this:

github.com/librenms/librenms

Rewrite smokeping script to be an lnms command

librenms:master ← TheMysteriousX:lookup-smokeping-hosts

opened 02:53AM - 11 May 20 UTC

TheMysteriousX

+1032 -198

I started off trying to make the existing smokeping script not kill smokeping if… it was unable to resolve the device for any reason, and ended up rewriting it. Still to do is a documentation update, and some tests. Smokeping's configuration format is... interesting, so I've taken a line-by-line approach to generating the configuration. It is **not** a drop in replacement for the existing script, as it generates both probe and target blocks to support multi processing and IPv6, but can be invoked as follows to generate a compatible configuration: ``` ./lnms smokeping:generate --targets --no-header --single-process ``` I need to update the docs, but all that should be needed to use it for new deployments is to remove the default smokeping probe and target stanza's. This version will not insert unresolvable devices into the configuration: ``` ... # "junkdevice.example.org" was not resolvable and was omitted from the configuration ... ``` It will also support both IPv4 and IPv6 pollers, with multiple processes: ``` smokeping[4964]: Smokeping version 2.006010 successfully launched. smokeping[4964]: Entering multiprocess mode. smokeping[4964]: Child process 5011 started for probe lnmsFPing60. smokeping[4964]: lnmsFPing60: probing 3 targets with step 60 s and offset 38 s. smokeping[4964]: Child process 5012 started for probe lnmsFPing0. smokeping[4964]: Child process 5013 started for probe lnmsFPing61. smokeping[4964]: lnmsFPing0: probing 41 targets with step 60 s and offset 22 s. smokeping[4964]: Child process 5014 started for probe lnmsFPing63. smokeping[4964]: lnmsFPing61: probing 3 targets with step 60 s and offset 10 s. smokeping[4964]: lnmsFPing63: probing 2 targets with step 60 s and offset 8 s. smokeping[4964]: Child process 5015 started for probe lnmsFPing3. smokeping[4964]: No targets defined for probe FPing6, skipping. smokeping[4964]: No targets defined for probe FPing, skipping. smokeping[4964]: lnmsFPing3: probing 40 targets with step 60 s and offset 4 s. smokeping[4964]: Child process 5016 started for probe lnmsFPing2. smokeping[4964]: lnmsFPing2: probing 40 targets with step 60 s and offset 42 s. smokeping[4964]: Child process 5017 started for probe lnmsFPing62. smokeping[4964]: lnmsFPing62: probing 3 targets with step 60 s and offset 49 s. smokeping[4964]: Child process 5018 started for probe lnmsFPing1. smokeping[4964]: All probe processes started successfully. smokeping[4964]: lnmsFPing1: probing 40 targets with step 60 s and offset 49 s. ``` ``` # ./lnms smokeping:generate --help Description: Generate a configuration suitable for use with smokeping Usage: smokeping:generate [options] Options: --probes Generate probe list - used for splitting the smokeping configuration into multiple files. Conflicts with "--targets" --targets Generate the target list - used for splitting the smokeping configuration into multiple files. Conflicts with "--probes" --no-header Don't add the boilerplate comment to the start of the generated file --single-process Only use a single process for smokeping - useful for integrating LibreNMS with an existing smokeping setup -h, --help Display this help message -q, --quiet Do not output any message -V, --version Display this application version --ansi Force ANSI output --no-ansi Disable ANSI output -n, --no-interaction Do not ask any interactive question --env[=ENV] The environment the command should run under -v|vv|vvv, --verbose Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug ``` #### Please note > Please read this information carefully. You can run `./scripts/pre-commit.php` to check your code before submitting. - [x] Have you followed our [code guidelines?](http://docs.librenms.org/Developing/Code-Guidelines/) - [x] If my Pull Request does some changes/fixes/enhancements in the WebUI, I have inserted a screenshot of it. #### Testers If you would like to test this pull request then please run: `./scripts/github-apply <pr_id>`, i.e `./scripts/github-apply 5926` After you are done testing, you can remove the changes with `./scripts/github-remove`. If there are schema changes, you can ask on discord how to revert.

SnarkyWomble · 26 September 2020 02:10

Yes I believe so. Installed NMS using the VM Image and updating via the daily updates. After reading the change to smokeping generation, I’m starting to think I have done everything right and there is something up with how this change works.
I am unsure what to do about it though.

SnarkyWomble · 26 September 2020 03:26

What was the previous cron script method for populating these confs? If that works I’d like to try it out ASAP.

SnarkyWomble · 29 September 2020 06:01

Sorry to be a pain. Can anyone suggest a way forward?

SnarkyWomble · 30 September 2020 10:43

I worked it out.

What a massive pain in the arse it was tracking that down. It was the system proxy having a typo in the /etc/environment config. Fixed that up and it worked like magic.

Thanks for all the help everyone…