Mount options discovery

Troubleshooting
,
1

I run check-mk-raw v2.4.0p32 in a Docker container on an Ubuntu host.

The container uses the following volume mounts:

    volumes:
      - "/data/docker/volumes/check-mk-raw/backup:/backup"
      - "/data/docker/volumes/check-mk-raw/docker-entrypoint.d:/docker-entrypoint.d"
      - "/data/docker/volumes/check-mk-raw/omd/sites:/omd/sites"
      - "/etc/localtime:/etc/localtime:ro"
      - "/etc/timezone:/etc/timezone:ro"

I mount /etc/localtime and /etc/timezone into the container so that the container uses the same timezone as the host.

This works in general. However, whenever I recreate the Checkmk container, Checkmk seems to randomly discover either a Mount options of /usr/share/zoneinfo/Etc/UTC service or a Mount options of /etc/timezone service.

Currently, the Check_MK Discovery service for the Checkmk container host reports changes because earlier it discovered the Mount options of /etc/timezone service, while after the last container recreation using docker compose down and docker compose up -d during the last Checkmk image/container update, it discovered the Mount options of /usr/share/zoneinfo/Etc/UTC service instead.

image
image1211×683 30.6 KB

I could now just remove the vanished service and add the unmonitored one. But next time it’s again the other way around. Does anyone have an idea why this happens, or any hints on how to make this more stable, so that Checkmk always detects the same mount options?

2

I use Setup > Services > Service discovery rules > Disabled services to ignore mount points or other services.

image
image864×724 22.2 KB

Screenshot is from my 2.1.0p5.cre server.

You can do the literal string as it is discovered otherwise, or when applicable you can do regex too. It looks for all services that starts with the string or regex you put in. If you don’t want other strings to be matched that starts the same, close string with $.

1 Like