Hi,
Thank you for your kind reply.
Yes, I forgot to mention that I did run in debug mode. It runs fine; no error show up, the expected set of CHART/DIMENSION/BEGIN/SET/END commands are issued. Actually, the resulting charts are OK and perfect in every way; except from the fact that I can’t seem to run more than just my own plugin.
When debugging all modules, it correctly shows the debug info for reading the configuration file, and “built XX job config”. Then when it comes to the custom plugin, just prints the stdout of the module. I paste here a cropped version that shows the idea (to avoid hundreds of lines ;):
I have left two modules for which I have an explicit configuration: postgres and weblog. The log progresses nicely in alphabetical order through the modules, until it reaches mine:
ubuntu@monitor:/usr/libexec/netdata/python.d$ sudo -u netdata ./…/plugins.d/python.d.plugin debug
2021-02-03 23:10:41: python.d INFO: plugin[main] : using python v3
2021-02-03 23:10:41: python.d DEBUG: plugin[main] : looking for ‘python.d.conf’ in [’/etc/netdata’, ‘/usr/lib/netdata/conf.d’]
2021-02-03 23:10:41: python.d DEBUG: plugin[main] : loading ‘/usr/lib/netdata/conf.d/python.d.conf’
2021-02-03 23:10:41: python.d DEBUG: plugin[main] : ‘/usr/lib/netdata/conf.d/python.d.conf’ is loaded
2021-02-03 23:10:41: python.d DEBUG: plugin[main] : looking for ‘pythond-jobs-statuses.json’ in /var/lib/netdata
2021-02-03 23:10:41: python.d DEBUG: plugin[main] : loading ‘/var/lib/netdata/pythond-jobs-statuses.json’
2021-02-03 23:10:41: python.d DEBUG: plugin[main] : ‘/var/lib/netdata/pythond-jobs-statuses.json’ is loaded
[…]
2021-02-03 23:10:41: python.d DEBUG: plugin[main] : [postgres] looking for ‘postgres.conf’ in [’/etc/netdata/python.d’, ‘/usr/lib/netdata/conf.d/python.d’]
2021-02-03 23:10:41: python.d DEBUG: plugin[main] : [postgres] loading ‘/etc/netdata/python.d/postgres.conf’
2021-02-03 23:10:41: python.d DEBUG: plugin[main] : [postgres] ‘/etc/netdata/python.d/postgres.conf’ is loaded
2021-02-03 23:10:41: python.d INFO: plugin[main] : [postgres] built 1 job(s) configs
2021-02-03 23:10:41: python.d DEBUG: plugin[main] : postgres[tcp] was previously active, applying recovering settings
[…]
2021-02-03 23:10:42: python.d DEBUG: plugin[main] : [web_log] looking for ‘web_log.conf’ in [’/etc/netdata/python.d’, ‘/usr/lib/netdata/conf.d/python.d’]
2021-02-03 23:10:42: python.d DEBUG: plugin[main] : [web_log] loading ‘/usr/lib/netdata/conf.d/python.d/web_log.conf’
2021-02-03 23:10:42: python.d DEBUG: plugin[main] : [web_log] ‘/usr/lib/netdata/conf.d/python.d/web_log.conf’ is loaded
2021-02-03 23:10:42: python.d INFO: plugin[main] : [web_log] built 13 job(s) configs
[…]
CHART wmspanel_nimble.incoming_streams_RTMP ‘’ ‘Nimble incoming stream status (RTMP)’ bool RTMP wmspanel_nimble_incoming_stream stacked 10000 60 ‘’ ‘python.d.plugin’ ‘nimble’
DIMENSION ‘hls/23_test-mmc_lqubtp9_vps252383’ ‘hls/23_test-mmc_lqubtp9_vps252383’ absolute 1 1 ’ ’
[…]
BEGIN wmspanel_nimble.incoming_streams_RTMP 0
SET “hls/23_test-mmc_lqubtp9_vps252383” = 1
END
and then waits for the next update (1 minute) to reprint the next set of values.
If I run debug on an official module, e.g. postgres, it behaves similarly, but afterwards there is a
python.d DEBUG: postgres[tcp] : update => [OK] (elapsed time: 28, failed retries in a row: 0)
once the iteration is done, which I don’t understand how to trigger?
Many thanks for your feedback,
Quentin