Current status

[mrx8]

Is your project ongoing?
There are no updates since last year.
I would be truly sad if it will not be ongoing...
Additionally the current docker image segfaults for me:

docker run \
  --ulimit memlock=-1:-1 \
  --ulimit nofile=262144:262144 \
  -p 6379:6379 \
  -p 6380:6380 \
  -p 9090:9090 \
  -it \
  --rm \
  cachegrand/cachegrand-server:latest
> Generating SSL certificate
--> Certificate Authority
====> Generating new CA key /etc/cachegrand/ca.key
====> Generating new CA Certificate /etc/cachegrand/ca.pem
====> Generating new config file openssl.cnf
--> Certificate
====> Generating new SSL KEY /etc/cachegrand/certificate.key
====> Generating new SSL CSR /etc/cachegrand/certificate.csr
====> Generating new SSL CERT /etc/cachegrand/certificate.pem
[2024-05-07T08:00:00Z][INFO       ][program_startup_report] cachegrand-server version v0.4.0 (built on 2023-05-28T18:17:00Z)
[2024-05-07T08:00:00Z][INFO       ][program_startup_report] > Release build, compiled using gcc v11.3.0
[2024-05-07T08:00:00Z][INFO       ][program_startup_report] > Hashing algorithm in use t1ha2
[2024-05-07T08:00:00Z][INFO       ][program_startup_report] > Running on Linux 08a7c3b776d4 6.1.92-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon May 27 03:37:00 UTC 2024 x86_64
[2024-05-07T08:00:00Z][INFO       ][program_startup_report] > Memory: 31447 MB total, 0 MB swap total
[2024-05-07T08:00:00Z][INFO       ][program_startup_report] > TLS: mbed TLS 2.28.0 (kernel offloading disabled)
[2024-05-07T08:00:00Z][INFO       ][program_startup_report]        Try to load the tls kernel module with "modprobe tls", no need to restart cachegrand-server
[2024-05-07T08:00:00Z][INFO       ][program_startup_report] > Realtime clock source <POSIX>, resolution <3 ms>
[2024-05-07T08:00:00Z][INFO       ][program_startup_report] > Monotonic clock source <Hardware (TSC)> (estimated cpu cycles per second <3.90 GHz>), resolution <1 ms>
[2024-05-07T08:00:00Z][INFO       ][config] Loading the configuration from /etc/cachegrand/cachegrand.yaml
[2024-05-07T08:00:00Z][WARNING    ][program_ulimit] Unable to set max opened file ulimit
[2024-05-07T08:00:00Z][INFO       ][program] Starting <12> workers
[2024-05-07T08:00:00Z][ERROR      ][worker][id: 00][cpu: 00][io_uring_support] Unable to allocate io_uring using the given params
[2024-05-07T08:00:00Z][ERROR      ][worker][id: 00][cpu: 00][io_uring_support] Unable to allocate io_uring using the given params
[2024-05-07T08:00:00Z][WARNING    ][worker][id: 00][cpu: 00][worker_iouring] io_uring linking not supported, accepting new connections will incur in a performance penalty
[2024-05-07T08:00:00Z][ERROR      ][worker][id: 00][cpu: 00][io_uring_support] Unable to allocate io_uring using the given params
[2024-05-07T08:00:00Z][ERROR      ][worker][id: 00][cpu: 00][worker] io_uring worker initialization failed, terminating
/startup.sh: line 7:    14 Segmentation fault      (core dumped) /usr/bin/cachegrand-server -c /etc/cachegrand/cachegrand.yaml

[danielealbano]

Sorry to read about your issue @mrx8, I haven't had room to work on it in the last few months but it's definitely not dead and the 0.5 release is almost ready including a number of fixes and internal improvements!
I will probably moving very slowly till October :)

I will try to investigate your issue over the weekend but from the logs it seems there might be an issue with the permission / capabilities of accessing io_uring