This dashboard gets filled as soon as you add Checkmk servers as host objects to the monitoring, and install a quite recent version of the Checkmk agent there.
After that, you will see one line per Checkmk server in the upper half, and one line per Checkmk site in the bottom half.
Indeed. Was missing that. Thanks
Hmm. Still not good:
- Installed agent plugin on the CMK server
- Added it as host.
Pretty much ok, but this error is persistent:
Any idea, what could go wrong? (Trusted connection not yet established)
These are failed systemd units. To see what was going wrong you could use
systemctl status cloud-init-local.service networkd-dispatcher.service
on the monitored host.
Hmm. Ok.
ubuntu@health:~$ sudo systemctl status cloud-init-local.service networkd-dispatcher.service
● cloud-init-local.service - Initial cloud-init job (pre-networking)
Loaded: loaded (/lib/systemd/system/cloud-init-local.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/cloud-init-local.service.d
└─50-azure-clear-persistent-obj-pkl.conf
Active: failed (Result: exit-code) since Sun 2023-02-12 18:40:37 UTC; 1 day 14h ago
Main PID: 928 (code=exited, status=1/FAILURE)
Feb 12 18:40:37 health cloud-init[928]: from netplan.cli.core import Netplan
Feb 12 18:40:37 health cloud-init[928]: File "/usr/share/netplan/netplan/cli/core.py", line 24, in <module>
Feb 12 18:40:37 health cloud-init[928]: import netplan.cli.utils as utils
Feb 12 18:40:37 health cloud-init[928]: File "/usr/share/netplan/netplan/cli/utils.py", line 25, in <module>
Feb 12 18:40:37 health cloud-init[928]: import netifaces
Feb 12 18:40:37 health cloud-init[928]: ModuleNotFoundError: No module named 'netifaces'
Feb 12 18:40:37 health systemd[1]: cloud-init-local.service: Main process exited, code=exited, status=1/FAILURE
Feb 12 18:40:37 health cloud-init[928]: ------------------------------------------------------------
Feb 12 18:40:37 health systemd[1]: cloud-init-local.service: Failed with result 'exit-code'.
Feb 12 18:40:37 health systemd[1]: Failed to start Initial cloud-init job (pre-networking).
● networkd-dispatcher.service - Dispatcher daemon for systemd-networkd
Loaded: loaded (/lib/systemd/system/networkd-dispatcher.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2023-02-12 18:40:40 UTC; 1 day 14h ago
Main PID: 1205 (code=exited, status=1/FAILURE)
Feb 12 18:40:40 health systemd[1]: Starting Dispatcher daemon for systemd-networkd...
Feb 12 18:40:40 health networkd-dispatcher[1205]: Traceback (most recent call last):
Feb 12 18:40:40 health networkd-dispatcher[1205]: File "/usr/bin/networkd-dispatcher", line 23, in <module>
Feb 12 18:40:40 health networkd-dispatcher[1205]: from gi.repository import GLib as glib
Feb 12 18:40:40 health networkd-dispatcher[1205]: File "/usr/lib/python3/dist-packages/gi/__init__.py", line 42, in <module>
Feb 12 18:40:40 health networkd-dispatcher[1205]: from . import _gi
Feb 12 18:40:40 health networkd-dispatcher[1205]: ImportError: cannot import name '_gi' from partially initialized module 'gi' (most likely due to a circular import) (/usr/lib/python3/dist-packages/gi/__init__.py)
Feb 12 18:40:40 health systemd[1]: networkd-dispatcher.service: Main process exited, code=exited, status=1/FAILURE
Feb 12 18:40:40 health systemd[1]: networkd-dispatcher.service: Failed with result 'exit-code'.
Feb 12 18:40:40 health systemd[1]: Failed to start Dispatcher daemon for systemd-networkd.
ubuntu@health:~$
I recall that I had to update to Python 3.9 because of a problem with Python 3.6 and certbot on this 18.04 machine. Maybe some missing thing in the python environment.
OT: Maybe you have seen my “bug” report here How to setup REDIS check - #5 by neilyoung
Is there any github issue tracker for checkmk you are aware of? I couldn’t find one.
Indeed, reverting back to python3.6 solved the problem. Thanks
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.