Bug #844
closedlttng-sessiond error on syscall list when unable to load kernel tracer
100%
Description
We should have a check for the file descriptor being set or not, rather than
hitting a EBADF.
modprobe: FATAL: Module lttng-tracer not found.
Error: Unable to load required module lttng-tracer
Error: Unable to remove module lttng-ring-buffer-metadata-mmap-client
Error: Unable to remove module lttng-ring-buffer-client-mmap-overwrite
Error: Unable to remove module lttng-ring-buffer-client-mmap-discard
Error: Unable to remove module lttng-ring-buffer-metadata-client
Error: Unable to remove module lttng-ring-buffer-client-overwrite
Error: Unable to remove module lttng-ring-buffer-client-discard
Error: Unable to remove module lttng-lib-ring-buffer
Error: Unable to remove module lttng-tracer
Warning: No kernel tracer available
PERROR - 11:17:37.654597 [4836/4836]: kernelctl syscall list: Bad file descriptor (in syscall_init_table() at syscall.c:55)
Error: Unable to populate syscall table. Syscall tracing won't work for this session daemon.
^CError: Unable to remove module lttng-ring-buffer-metadata-mmap-client
Error: Unable to remove module lttng-ring-buffer-client-mmap-overwrite
Error: Unable to remove module lttng-ring-buffer-client-mmap-discard
Error: Unable to remove module lttng-ring-buffer-metadata-client
Error: Unable to remove module lttng-ring-buffer-client-overwrite
Error: Unable to remove module lttng-ring-buffer-client-discard
Error: Unable to remove module lttng-lib-ring-buffer
Error: Unable to remove module lttng-tracer