23 Jun 2026, 05:05 by [email protected]: > This is the particular part of your setup that makes you use DynamicUser=no. > You can also use ReadWritePaths=${HOMEDIR}/${radicale folder} > That change isn't working for me. I added ReadWritePaths, changed DynamicUser=yes, and removed User and Group. After rebooting (because I can't seem to commit the changes when systemctl restart doesn't) radicale broke again. journald output (with duplicate lines removed):
systemd[1]: Starting [email protected] - Socket for uWSGI app radicale... systemd[1]: Listening on [email protected] - Socket for uWSGI app radicale. systemd[1]: Starting [email protected] - radicale uWSGI app... (uwsgi)[9999]: [email protected]: Failed to set up special execution directory in /var/lib: File exists (uwsgi)[9999]: [email protected]: Failed at step STATE_DIRECTORY spawning /usr/bin/uwsgi: File exists systemd[1]: [email protected]: Main process exited, code=exited, status=238/STATE_DIRECTORY systemd[1]: [email protected]: Failed with result 'exit-code'. systemd[1]: Failed to start [email protected] - radicale uWSGI app. systemd[1]: [email protected]: Start request repeated too quickly. systemd[1]: [email protected]: Failed with result 'start-limit-hit'. systemd[1]: [email protected]: Failed with result 'service-start-limit-hit'. uwsgi[9999]: [uWSGI] getting INI configuration from /etc/uwsgi/apps-available/radicale.ini uwsgi[9999]: *** Starting uWSGI 2.0.31-debian (64bit) on [Wed Jun 24 06:00:00 2026] *** uwsgi[9999]: compiled with version: 15.2.0 on 16 January 2026 20:51:30 uwsgi[9999]: os: Linux-7.0.12+deb14.1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 7.0.12-2 (2026-06-12) uwsgi[9999]: nodename: me uwsgi[9999]: machine: x86_64 uwsgi[9999]: clock source: unix uwsgi[9999]: pcre jit disabled uwsgi[9999]: detected number of CPU cores: 4 uwsgi[9999]: current working directory: / uwsgi[9999]: detected binary path: /usr/bin/uwsgi-core uwsgi[9999]: your processes number limit is 63205 uwsgi[9999]: your memory page size is 4096 bytes uwsgi[9999]: detected max file descriptor number: 1024 uwsgi[9999]: lock engine: pthread robust mutexes uwsgi[9999]: thunder lock: disabled (you can enable it with --thunder-lock) uwsgi[9999]: Python version: 3.13.14 (main, Jun 10 2026, 18:10:12) [GCC 15.2.0] uwsgi[9999]: Python main interpreter initialized at 0x7fa593b357c8 uwsgi[9999]: python threads support enabled uwsgi[9999]: The -s/--socket option is missing and stdin is not a socket. systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE I found in my troubleshooting is that someone (probably uwsgi) was messing around with the folder and file permissions. It took some effort to revert to my previous uwsgi-app@radicale configuration. A few more reboots and it seems to be co-operating again. Clearly not something you can expect me to get right without a lot of handholding. I hope something is useful there.
