Instead of monitoring juju-db.service, nrpe should monitor either juju-db process or snap.juju-db.daemon.service:
ubuntu@juju-controller-1:KDC1:~$ systemctl status snap.juju-db.daemon.service
● snap.juju-db.daemon.service - Service for snap application juju-db.daemon
Loaded: loaded (/etc/systemd/system/snap.juju-db.daemon.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/snap.juju-db.daemon.service.d └─overrides.conf
Active: active (running) since Tue 2022-07-26 09:58:11 UTC; 1 day 2h ago
NRPE check reports "juju-db.service is not running" for juju controller 2.9.32 running on focal.
juju-db in this version runs as a snap:
ubuntu@ juju-controller -1:KDC1: ~$ snap list | grep juju-db
juju-db 4.4.14 127 4.4/stable juju-qa -
ubuntu@ juju-controller -1:KDC1: ~$ ps -ef | grep juju-db db/127/ bin/mongod --config /var/snap/ juju-db/ common/ juju-db. config
root 6219 1 8 Jul26 ? 02:21:28 /snap/juju-
Instead of monitoring juju-db.service, nrpe should monitor either juju-db process or snap.juju- db.daemon. service:
ubuntu@ juju-controller -1:KDC1: ~$ systemctl status snap.juju- db.daemon. service db.daemon. service - Service for snap application juju-db.daemon system/ snap.juju- db.daemon. service; enabled; vendor preset: enabled) system/ snap.juju- db.daemon. service. d
└ ─overrides. conf
● snap.juju-
Loaded: loaded (/etc/systemd/
Drop-In: /etc/systemd/
Active: active (running) since Tue 2022-07-26 09:58:11 UTC; 1 day 2h ago