Owncloud: Lots of weird entries in log: "systemd run-docker-runtime/...mount: succeeded"

Oehrly · 28. Juli 2020

Hi, so I have set up OMV5 with some docker containers. I'm running Owncloud, Onlyoffice, Nginx/Letsencrypt and Heimdall. Now my Owncloud setup is making some "problems".

If I check /var/log/daemon.log the whole log is spammed with the following entries:

Code

Jul 28 22:04:04 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-0cc6595466f3fdab8e936d35a8d33a92f92e36f2204064a4aacd1cec1d19755c-runc.db6jRx.mount: Succeeded.
Jul 28 22:04:04 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.uCgJLC.mount: Succeeded.
Jul 28 22:04:04 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.uCgJLC.mount: Succeeded.
Jul 28 22:04:34 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-0cc6595466f3fdab8e936d35a8d33a92f92e36f2204064a4aacd1cec1d19755c-runc.PJEFrb.mount: Succeeded.
Jul 28 22:04:34 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-0cc6595466f3fdab8e936d35a8d33a92f92e36f2204064a4aacd1cec1d19755c-runc.PJEFrb.mount: Succeeded.
Jul 28 22:04:34 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.0v3aTh.mount: Succeeded.
Jul 28 22:04:34 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.0v3aTh.mount: Succeeded.
Jul 28 22:05:04 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-8fe2d192aca9b26d04a30d0509ff9574caef3a713caa8fb0f99dfffe4b26dae9-runc.HkXn79.mount: Succeeded.
Jul 28 22:05:04 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-8fe2d192aca9b26d04a30d0509ff9574caef3a713caa8fb0f99dfffe4b26dae9-runc.HkXn79.mount: Succeeded.
Jul 28 22:05:04 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.1eGV9U.mount: Succeeded.
Jul 28 22:05:04 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.1eGV9U.mount: Succeeded.
Jul 28 22:05:34 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.8eTkyz.mount: Succeeded.
Jul 28 22:05:34 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.8eTkyz.mount: Succeeded.
Jul 28 22:06:04 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-8fe2d192aca9b26d04a30d0509ff9574caef3a713caa8fb0f99dfffe4b26dae9-runc.DM6lzu.mount: Succeeded.
Jul 28 22:06:04 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-8fe2d192aca9b26d04a30d0509ff9574caef3a713caa8fb0f99dfffe4b26dae9-runc.DM6lzu.mount: Succeeded.
Jul 28 22:06:05 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.vbiLD4.mount: Succeeded.
Jul 28 22:06:05 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.vbiLD4.mount: Succeeded.
Jul 28 22:06:35 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-0cc6595466f3fdab8e936d35a8d33a92f92e36f2204064a4aacd1cec1d19755c-runc.vmAMzC.mount: Succeeded.
Jul 28 22:06:35 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-0cc6595466f3fdab8e936d35a8d33a92f92e36f2204064a4aacd1cec1d19755c-runc.vmAMzC.mount: Succeeded.
Jul 28 22:06:35 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.X7wuPH.mount: Succeeded.
Jul 28 22:06:35 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.X7wuPH.mount: Succeeded.
Jul 28 22:07:05 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-0cc6595466f3fdab8e936d35a8d33a92f92e36f2204064a4aacd1cec1d19755c-runc.L6K30h.mount: Succeeded.
Jul 28 22:07:05 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-0cc6595466f3fdab8e936d35a8d33a92f92e36f2204064a4aacd1cec1d19755c-runc.L6K30h.mount: Succeeded.
Jul 28 22:07:05 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.NS06el.mount: Succeeded.
Jul 28 22:07:05 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.NS06el.mount: Succeeded.
Jul 28 22:07:34 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-8fe2d192aca9b26d04a30d0509ff9574caef3a713caa8fb0f99dfffe4b26dae9-runc.QLcajs.mount: Succeeded.
Jul 28 22:07:34 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-8fe2d192aca9b26d04a30d0509ff9574caef3a713caa8fb0f99dfffe4b26dae9-runc.QLcajs.mount: Succeeded.
Jul 28 22:07:35 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-0cc6595466f3fdab8e936d35a8d33a92f92e36f2204064a4aacd1cec1d19755c-runc.4pOgxW.mount: Succeeded.
Jul 28 22:07:35 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-0cc6595466f3fdab8e936d35a8d33a92f92e36f2204064a4aacd1cec1d19755c-runc.4pOgxW.mount: Succeeded.
Jul 28 22:07:35 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.4bTTX1.mount: Succeeded.
Jul 28 22:07:35 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.4bTTX1.mount: Succeeded.
Jul 28 22:08:05 oehrly systemd[8055]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.M02ZjE.mount: Succeeded.
Jul 28 22:08:05 oehrly systemd[1]: run-docker-runtime\x2drunc-moby-e770b2c92136456f03c78a1e0125fab421cfd484ffabe5ef68038893a740172b-runc.M02ZjE.mount: Succeeded.

Alles anzeigen

Basically the same entries once every minute.

Now, based on the ids, the offending containers are owncloud, mariadb and redis (both belong to owncloud).

I have no problems, performance is great and so on but I wonder, do I need to be concerned? I cannot find any errors elsewhere, no matter which log I've checked so far.

What is this? Is it a problem?

davidh2k · 29. Juli 2020

According to this link, its caused by the healthcheck feature. Maybe take a deeper look at the thread for workarounds, there are one or two suggestions.

Besides filling up your log heavily, it doesn't seem to do any harm.

Greetings

David

Oehrly · 29. Juli 2020

Thank you for the info and the link!

So it's not a real problem that I need to be concerned about. That's great. I might look into the workarounds for cleaning the log when I have some time for that though.

MarcS · 16. Januar 2021

Zitat von davidh2k

According to this link, its caused by the healthcheck feature. Maybe take a deeper look at the thread for workarounds, there are one or two suggestions.

Besides filling up your log heavily, it doesn't seem to do any harm.

Greetings
David

Alles anzeigen

Hi - I have exactly the same problem on a rpi4. The link above is now closed and no real solution was found.

I do have performance issues especially with my Nextcloud container.

Have you seen any new developments that would resolve the issue?

cubemin · 13. April 2021

There is indeed no solution yet, but there IS a workaround. I tested it and it stops syslog from being flooded.

prahal · 6. Dezember 2022

There is a proper workaround and I believe docker should autoinstall this systemd conf file: https://github.com/docker/for-…9#issuecomment-1004955357

TLDR:

Create /etc/systemd/system/run-docker-.mount.d/10-silence.conf or for cri-io and containerd /etc/systemd/system/run-containerd-.mount.d/10-silence.conf (or whatever prefix you need to silence) with:

Code

[Mount]
LogLevelMax=notice

Then do sudo systemctl daemon-reload.

Note that this requires Systemd >= 249.

Owncloud: Lots of weird entries in log: "systemd run-docker-runtime/...mount: succeeded"

Jetzt mitmachen!

Tags