redis-rspamd failed install

[DrWizzle]

I've noticed a few times when i've installed DA over the past few weeks, custombuild fails on rspamd. I've then had to manually install it from the options in custombuild. Once i've done that, rspamd as a service turns green in the system control panel (GUI) but I still had errors when I checked the status of the server.

Not sure if any of you guys have experienced this?

Note: This isn't a production server, this is one I use for misc tasks, testing and a sandbox for software.

root@v4 ~ # systemctl --failed
  UNIT                 LOAD   ACTIVE SUB    DESCRIPTION                                 >
● redis-rspamd.service loaded failed failed Multi-user redis persistent key-value databa>
Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

1 loaded units listed.
lines 1-8/8 (END)

root@v4 ~ # systemctl status redis-rspamd.service
× redis-rspamd.service - Multi-user redis persistent key-value database
     Loaded: loaded (/etc/systemd/system/redis-rspamd.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2025-09-30 13:45:22 CEST; 1min 43s ago
       Docs: http://redis.io/documentation,
             man:redis-server(1)
    Process: 760946 ExecStartPre=/bin/mkdir -p ${HOME}/.redis/db/ (code=exited, status=217/USER)
    Process: 760947 ExecStart=/usr/local/bin/redis-server --supervised systemd --dir ${HOME}/.redis/db/ --port 0 --unixsocket ${HOME}/.redis/redis.sock --unixsocketperm 770 --save 900 1 --save 300 10 --save 60 10000 (code=exited, status=217/USER)
   Main PID: 760947 (code=exited, status=217/USER)
        CPU: 5ms

Sep 30 13:45:22 v4 systemd[1]: Starting redis-rspamd.service - Multi-user redis persistent key-value database...
Sep 30 13:45:22 v4 (mkdir)[760946]: redis-rspamd.service: Failed to determine user credentials: No such process
Sep 30 13:45:22 v4 (s-server)[760947]: redis-rspamd.service: Failed to determine user credentials: No such process
Sep 30 13:45:22 v4 systemd[1]: redis-rspamd.service: Main process exited, code=exited, status=217/USER
Sep 30 13:45:22 v4 systemd[1]: redis-rspamd.service: Failed with result 'exit-code'.
Sep 30 13:45:22 v4 systemd[1]: Failed to start redis-rspamd.service - Multi-user redis persistent key-value database.
root@v4 ~ #

From these error messages it looked like the user and group _rspamd hadn't been created by DA so i've had to do these manually.

root@v4 ~ # id _rspamd
id: ‘_rspamd’: no such user
root@v4 ~ # getent passwd _rspamd
root@v4 ~ # useradd -r -m -d /home/_rspamd -s /usr/sbin/nologin _rspamd
root@v4 ~ # mkdir -p /home/_rspamd/.redis/db
root@v4 ~ # chown -R _rspamd:_rspamd /home/_rspamd/.redis
root@v4 ~ # systemctl daemon-reexec

Doing this seems to solve the problem. Not sure if it's the proper fix, but it works. Is this one of the custombuild fixes that I saw was going to be fixed in the next release of DA?

root@v4 ~ # systemctl restart redis-rspamd
systemctl status redis-rspamd
● redis-rspamd.service - Multi-user redis persistent key-value database
     Loaded: loaded (/etc/systemd/system/redis-rspamd.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-09-30 13:57:11 CEST; 6ms ago
       Docs: http://redis.io/documentation,
             man:redis-server(1)
    Process: 762097 ExecStartPre=/bin/mkdir -p ${HOME}/.redis/db/ (code=exited, status=0/SUCCESS)
   Main PID: 762099 (redis-server)
     Status: "Ready to accept connections"
      Tasks: 6 (limit: 76811)
     Memory: 2.5M (peak: 3.2M)
        CPU: 32ms
     CGroup: /system.slice/redis-rspamd.service
             └─762099 "/usr/local/bin/redis-server unixsocket:/home/_rspamd/.redis/redis.sock"

Sep 30 13:57:11 v4 systemd[1]: Starting redis-rspamd.service - Multi-user redis persistent key-value database...
Sep 30 13:57:11 v4 redis-server[762099]: 762099:C 30 Sep 2025 13:57:11.582 * Supervised by systemd. Please make sure you set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
Sep 30 13:57:11 v4 redis-server[762099]: 762099:C 30 Sep 2025 13:57:11.582 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Sep 30 13:57:11 v4 redis-server[762099]: 762099:C 30 Sep 2025 13:57:11.582 * Redis version=8.2.1, bits=64, commit=00000000, modified=1, pid=762099, just started
Sep 30 13:57:11 v4 redis-server[762099]: 762099:C 30 Sep 2025 13:57:11.582 * Configuration loaded
Sep 30 13:57:11 v4 redis-server[762099]: 762099:M 30 Sep 2025 13:57:11.582 * monotonic clock: POSIX clock_gettime
Sep 30 13:57:11 v4 redis-server[762099]: 762099:M 30 Sep 2025 13:57:11.583 * Running mode=standalone, port=0.
Sep 30 13:57:11 v4 redis-server[762099]: 762099:M 30 Sep 2025 13:57:11.583 * Server initialized
Sep 30 13:57:11 v4 redis-server[762099]: 762099:M 30 Sep 2025 13:57:11.583 * Ready to accept connections unix
Sep 30 13:57:11 v4 systemd[1]: Started redis-rspamd.service - Multi-user redis persistent key-value database.
root@v4 ~/.redis #