On Thu, 31 Jul 2025, 16:05 Michael Biebl, <[email protected]> wrote:
44s Jul 30 20:28:18 autopkgtest-lxd-lryznw rsyslogd[1999]: imklog: cannot > open kernel log (/proc/kmsg): Permission denied. > 44s Jul 30 20:28:18 autopkgtest-lxd-lryznw rsyslogd[1999]: activation of > module imklog failed [v8.2506.0 try https://www.rsyslog.com/e/2145 ] > > It appears, debusine.debian.net uses LXD/LXC but access to /proc/kmsg is > more restricted than on debci. > > > I see 3 possible ways forward > > 1/ Add isolation-machine (agree with you that this would not be best) > > 2/ Add this error message to rsyslog.logcheck.ignore.server, i.e. treat > this as an expected error. Looks wrong to me, but I'm not a logcheck > user. > definitely agree it shouldnt be in the rules shipped by the package - exactly as you suggest, users would want to know if this error was being made - see beloe > 3/ Modify the rsyslog configuration we use for debian/tests/logcheck and > remove the `module(load="imklog")` line from /etc/rsyslog.conf. > I.e. we would run rsylog with a slightly different configuration as > is the default. > could work, but then you'll be less sure that the logcheck rules are right for users > On a cursory glance, I think 3) would be the best option but I would > welcome your opionion on this matter. > How about a variant of 2 --- change the logcheck rules inside the test, only if /proc/kmesg is restricted if [ "/proc/kmesg" is readable (?) ] ; then echo "rules matching the error" > /etc/logcheck/ignore.d.server/foo fi # rest of test as before then the logcheck in the test will ignore those messages in debusine, but be unaffected on salsa (i dont know what the test should be though). and if debusine changes it will then be a no-op. (i havnt looked at the test, but from what i remember this should work, can have a look)
