Grabbing logs: error opening journald follow descriptor: "Too many open files"

Product support
1

Hello,

At some point and without some apparent reason, the containers deployed on my devices stopped showing log after throwing the error in the subject.
How can I get around this?

Thanks in advance,
Federico

2

Hi,
Can you try to run sysctl -w fs.inotify.max_user_instances=512 in the HostOS? If this fixes the problem we know what the problem is. You can validate that the command work by running sysctl fs.inotify.max_user_instances which should yield 512.

5

If this fixes the problem, could you grant us support access to such a device as well. We would like to research how many inotify instances your application uses to find a sane default value for BalenaOS. Thank you.

7

Also if this fixes your problem this (https://github.com/balena-os/meta-balena/issues/1592) would be the issue to track.

1 Like
8

Thanks, that fixed the issue! Unfortunately, I don’t own the device so I cannot grant such access.
Thank you

11

I ran into the same issue, running sysctl -w fs.inotify.max_user_instances=512 fixes the issue once the container restarts the next time.

13

Same issue here, running sysctl -w fs.inotify.max_user_instances=512 does not fix the issue.
Note that I’m running ResinOS-In-Container:

14

for balenaos-in-container, you’ll probably need to run sysctl -w fs.inotify.max_user_instances=1024 in the underlying host running balenaOS