Ns8 merged error

mrmarkuz · April 22, 2024, 8:18am

I got the “invalid argument” error again on my NS8 Rocky dev test machine…

Here are the logs:

gist.github.com

https://gist.github.com/mrmarkuz/364f75dfa0a4be4b94ed3a7478355912

gistfile1.txt

2024-04-22T09:58:27+02:00 [1:zammad3:systemd] Started libcrun container.
2024-04-22T09:58:27+02:00 [1:zammad3:zammad3] 5e16ca948c21561d59e210f84ae8a358c70e33f6c2a90f33ca589dc09305cf1b
2024-04-22T09:58:27+02:00 [1:zammad3:systemd] Started Podman  zammad-redis.service.
2024-04-22T09:58:27+02:00 [1:zammad3:systemd] Starting Podman  zammad-init.service...
2024-04-22T09:58:28+02:00 [1:zammad3:systemd] Starting Podman  zammad-railsserver.service...
2024-04-22T09:58:28+02:00 [1:zammad3:systemd] Starting Podman  zammad-scheduler.service...
2024-04-22T09:58:28+02:00 [1:zammad3:systemd] Starting Podman  zammad-websocket.service...
2024-04-22T09:58:28+02:00 [1:zammad3:zammad-redis] 1:C 22 Apr 2024 07:58:28.036 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
2024-04-22T09:58:28+02:00 [1:zammad3:zammad-redis] 1:C 22 Apr 2024 07:58:28.037 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2024-04-22T09:58:28+02:00 [1:zammad3:zammad-redis] 1:C 22 Apr 2024 07:58:28.037 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started

This file has been truncated. show original

Solvable by removing the merged dirs and restarting the services:

rmdir /home/zammad3/.local/share/containers/storage/overlay/*/merged