However, installing nagios-plugins in a fresh Xenial LXC container does not appear sufficient to reproduce the bug:
1. There is no /sys/kernel/debug/tracing present on the system. Installing perf-tools-unstable caused the directory to be created.
2. There is not a nagios user on the system. I created this manually, but wonder if there is some third component that should be installed, that would create this?
3. The directory in question is owned by 'nobody':
root@triage-xenial:~# ls -l /sys/kernel/debug/tracing
ls: cannot access '/sys/kernel/debug/tracing': Permission denied
root@triage-xenial:~# ls -l /sys/kernel
(...)
drwx------ 36 nobody nogroup 0 Jul 10 23:10 debug
(...)
It would be quite helpful to have a step-by-step test case that can be invoked in a Xenial lxc container.
Has anyone checked that this same issue affects bionic or newer, or is Xenial-specific?
This looks similar to https:/ /bugs.launchpad .net/ubuntu/ +source/ monitoring- plugins/ +bug/1827159.
However, installing nagios-plugins in a fresh Xenial LXC container does not appear sufficient to reproduce the bug:
1. There is no /sys/kernel/ debug/tracing present on the system. Installing perf-tools-unstable caused the directory to be created. triage- xenial: ~# ls -l /sys/kernel/ debug/tracing debug/tracing' : Permission denied triage- xenial: ~# ls -l /sys/kernel
2. There is not a nagios user on the system. I created this manually, but wonder if there is some third component that should be installed, that would create this?
3. The directory in question is owned by 'nobody':
root@
ls: cannot access '/sys/kernel/
root@
(...)
drwx------ 36 nobody nogroup 0 Jul 10 23:10 debug
(...)
It would be quite helpful to have a step-by-step test case that can be invoked in a Xenial lxc container.
Has anyone checked that this same issue affects bionic or newer, or is Xenial-specific?