sshlog/agent

Error loading Python lib

write2akj opened this issue · 5 comments

Hi matthill

I am getting below error. Could you please help to resolve this:

Error loading Python lib '/tmp/_MEIONNbeW/libpython3.8.so.1.0': dlopen: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/_MEIONNbeW/libpython3.8.so.1.0).

Can you provide more info to help me reproduce?

How did you install? Which operating system? is this x86 or arm? What command are you running to see this error?

@matthill ,

The operating system I am using is CentOS Linux 7 (Core).
uname -r = 3.10.0-327.el7.x86_64

I have installed it by following steps given in readme for "RedHat/Fedora Install (arm64 and x86_64)".

Getting this error when running "sshlog sessions" command and "sshlog watch" command.
[14444] Error loading Python lib '/tmp/_MEI4WBLOV/libpython3.8.so.1.0': dlopen: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/_MEI4WBLOV/libpython3.8.so.1.0)

Also getting below error in log file continuously:
##########################
systemd: sshlog.service holdoff time over, scheduling restart.
systemd: Stopped SSHLog Agent Service.
systemd: Started SSHLog Agent Service.
sshlogd: [14683] Error loading Python lib '/tmp/_MEIYeUCY1/libpython3.8.so.1.0': dlopen: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/_MEIYeUCY1/libpython3.8.so.1.0)
systemd: sshlog.service: main process exited, code=exited, status=255/n/a
systemd: Unit sshlog.service entered failed state.
systemd: sshlog.service failed.
##########################

Ahh, I see. I believe the reason it does not work is because the kernel version is too low.

SSHLog requires Linux Kernel 5.4 or higher (released Nov 2019). Your kernel is 3.10. The daemon uses eBPF to monitor the OpenSSH process in the kernel. That was a feature that was not available back when CentOS 7 was released.

Hello, I faced the same problem, OS Centos 7, but the kernel version is higher
5.4.248-1.el7.elrepo.x86_64

same error in RHEL 8, where the kernel is 4.18.0-477.13.1.el8_8.x86_64

What's odd is that the docker version seems to work fine, even though that is using the same kernel!