Log Host full of - homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-xxx...xxx.mount: Deactivated successfully

Installation
1

Hi all,
I’m writing about these long list of message present in my Host Log.
I have little knowledge of dockers … I’m not a computer scientist.
Where do I start to analyze this problem.
I have a supervised homeassistant installation on a windows 10 machine with Virtualbox simulating a linux machine
Thank you all

...
Jan 22 14:00:40 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-157365b08ea583ce48086a592ac2e18687b472d055f797b7d157b3a4af2bd98e-runc.q0yLS1.mount: Deactivated successfully.
Jan 22 14:01:10 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-157365b08ea583ce48086a592ac2e18687b472d055f797b7d157b3a4af2bd98e-runc.0C1KRN.mount: Deactivated successfully.
Jan 22 14:01:40 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-157365b08ea583ce48086a592ac2e18687b472d055f797b7d157b3a4af2bd98e-runc.bFDeSj.mount: Deactivated successfully.
Jan 22 14:02:10 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-157365b08ea583ce48086a592ac2e18687b472d055f797b7d157b3a4af2bd98e-runc.qxaK0s.mount: Deactivated successfully.
Jan 22 14:02:41 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-157365b08ea583ce48086a592ac2e18687b472d055f797b7d157b3a4af2bd98e-runc.nw1V9Z.mount: Deactivated successfully.
...
1 Like
2

NEW!!!
with this error in the host log

image
image1502×118 18.6 KB

i found the correspondending docker
image
image880×215 17.4 KB

Now is all to undstend

3

Same issue here, …,.for me it seems to be the Adguard addon also

4

i reinstalled from 0 ADguard…no result

5

Nope, tried that also, even install older version like 4.6 or 4.7 and does it.

I remove the endgame addon and the messages disappeared.

I also notice Adguard not responding a lot…

6
7

I have a same issue with NodeRed integration.

HA api also crashed few times in the last couple days. I’m not sure that was the issue. I have set up more logs and waiting for crash again…

8

I have the same with EMQX, no crashes so far but a whole lot of log messages.

After some search effort I found similar logs which had something to do with the health check within the docker image. I have no clue what to do about it but it’s really annoying.

Update:
I checked the dockerfiles of NodeRed, EMQX and AdGuard and all of those have a HEALTHCHECK command, non of my other addons have it and non of them create this extreme amount of logs.

@frenck is this the expected behaviour? Is there something we can do to stop this?

9

I’m also seeing this with Node-Red and Tasmoadmin addons. Additionally my log is giving every few seconds udiskd error like this:

May 09 04:49:18 homeassistant udisksd[143]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed
May 09 04:49:18 homeassistant udisksd[143]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed
May 09 04:49:42 homeassistant udisksd[143]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed
May 09 04:49:48 homeassistant udisksd[143]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed
May 09 04:49:48 homeassistant udisksd[143]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed
May 09 04:49:48 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cb0794d6e6e9d256aca9442de7e9c8f0e2d30679734beedeea48f1d727c64c52-runc.52vHwQ.mount: Deactivated successfully.
May 09 04:50:12 homeassistant udisksd[143]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed
May 09 04:50:12 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1c020516677b7f21e2228e5b0c50ad6e0b6aa8ccc9e639b9070fe47070f0f55e-runc.rSmLkb.mount: Deactivated successfully.
May 09 04:50:18 homeassistant udisksd[143]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed
May 09 04:50:18 homeassistant udisksd[143]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed
May 09 04:50:18 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-cb0794d6e6e9d256aca9442de7e9c8f0e2d30679734beedeea48f1d727c64c52-runc.wuumwT.mount: Deactivated successfully.
May 09 04:51:12 homeassistant udisksd[143]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed
May 09 04:51:12 homeassistant udisksd[143]: udisks_mount_get_mount_path: assertion 'mount->type == UDISKS_MOUNT_TYPE_FILESYSTEM' failed
May 09 04:51:12 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-1c020516677b7f21e2228e5b0c50ad6e0b6aa8ccc9e639b9070fe47070f0f55e-runc.gD9FcS.mount: Deactivated successfully.

I’m running on Yellow with:

  • Home Assistant 2023.5.2
  • Supervisor 2023.04.1
  • Operating System 10.1
  • Node-Red addon: 14.1.5
  • Tasmoadmin: 0.24.2
10

I have this issue and just found that it is related to vscode.
I wonder if this can explain some performance issues I’m experiencing.
no watchdog or start on boot.

11

Same problem on latest updated system (HAOS)

image
image1920×1272 605 KB

No adguard addon installed

12

This is annoying but completely normal. These log entries are related to docker’s health checks. See here.

1 Like
13

A nice workaround to disable the noise:

# cat /etc/systemd/system/run-docker-.mount.d/10-silence.conf 
[Mount]
LogLevelMax=notice

via

1 Like