You are not logged in.

#1 2022-08-16 13:41:50

clayman
Member
Registered: 2013-05-26
Posts: 19

memcached: seccomp policy failure on syscall 096

Hi all,

I have been trying to get memcached to run locally using stock configuration, but I am constantly hitting an issue where even just attempting to connect to the server using telnet ends with these messages in the journal

Aug 16 15:23:41 clayman-work memcached[645198]: Seccomp policy failure. Caught syscall 096. This is either an exploit attempt, or your system is not supported yet.
Aug 16 15:23:41 clayman-work systemd[1]: memcached.service: Main process exited, code=dumped, status=31/SYS
Aug 16 15:23:41 clayman-work systemd[1]: memcached.service: Failed with result 'core-dump'.
Aug 16 15:23:41 clayman-work systemd[1]: memcached.service: Scheduled restart job, restart counter is at 3.
Aug 16 15:23:41 clayman-work systemd[1]: Stopped memcached daemon.
Aug 16 15:23:41 clayman-work systemd[1]: Started memcached daemon.

I have been googling around trying to diagnose what's going on, read up on seccomp a little bit, but haven't been able to find any decent explanation. I did find out that syscall 096 is the gettimeofday call, which does appear to be correctly added to the seccomp BPF initialized in the source code of memcached.

Has anybody else run into this issue? What am I missing?

Thanks in advance.

EDIT: Forgot to add that I am running the latest kernel (5.19.1-arch2-1) and memcached (1.6.15-1)

Last edited by clayman (2022-08-16 15:21:57)

Offline

Board footer

Powered by FluxBB