Syslog is spammed
... with lines like this:
systemd[1]: run-docker-runtime\x2drunc-moby-b5a33fd628d7f785d1fb027c2592ada23c9c197ee57718863090b82c589ca6cf-runc.ZqDmtM.mount: Succeeded.
The lines are created like every 15 seconds. Does anybody have a clue as to what's going on?
9 Replies
:wave: Hey @Carl,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.That doesn't sound like an Immich issue
I use docker only for Immich though.
That doesn't mean it's an Immich issue
Could be an issue with docker, for example
After digging it seems to be a docker health check which is apparently enabled on all containers. No idea if the interval can be configured or maybe make it less chatty so it doesn't spam the log files but I'll see if I can find out.
Follow-up: the redis container has health check enabled without interval. I have set it to 5m in the docker-compose.yml file. Let's see what happens.
All the containers have a health check. You can disable or alter as you see fit
If you get more into self hosting you might want to pay less attention to logs of this level lol
I have altered the interval on the redis container to 5m but it still happens.
don't know about not checking the syslogs though. There's an awful lot of lines there and it makes finding other issues more cumbersome. I'll see if I can change the log level.
You can ignore these with syslog filters instead of changing the healthcheck interval
Yes, that's what I am going to do. First find out how 🙂