From be909d3a083e9aa5bf644311c9fd375a192b9a99 Mon Sep 17 00:00:00 2001 From: Peter Bieringer Date: Thu, 6 Jun 2024 06:34:04 +0200 Subject: [PATCH] Updated Server Diagnostics Troubleshooting (markdown) --- Server-Diagnostics---Troubleshooting.md | 23 +++++++++++++++-------- 1 file changed, 15 insertions(+), 8 deletions(-) diff --git a/Server-Diagnostics---Troubleshooting.md b/Server-Diagnostics---Troubleshooting.md index 6981449..8c52108 100644 --- a/Server-Diagnostics---Troubleshooting.md +++ b/Server-Diagnostics---Troubleshooting.md @@ -1,13 +1,16 @@ (work-in-progress, feel free to contribute) +Assumptions +* the system user is named "radicale" +* the system user "radicale" owns the the configured storage location + # Storage verification Since 3.0.0 a special command option exists to verify the storage of the collections: ``` -## as user "radicale" (or the user which "owns" the storage) # add optional for watching the progress: --logging-level debug -/usr/bin/radicale --verify-storage +sudo -u radicale /usr/bin/radicale --verify-storage ``` It should not report any errors, otherwise particular VCF or ICS files have to be fixed manually. @@ -27,15 +30,19 @@ Solution: check for any folder in which itself is a collection and move i # Verification of start -## Started by systemd - -- terminal#1 / watch logs: `journalctl -f -u radicale` -- terminal#2 / start "radicale" service: `systemctl start radicale` ## Manual start -- become "radicale" user: `su - -s /bin/bash radicale` -- start "radicale" (here with log-level debug): `/usr/bin/radicale --logging-level debug` +``` +# including optional for watching the progress: --logging-level debug +# Terminate with CTRL-C to finish test +sudo -u radicale /usr/bin/radicale --logging-level debug +``` + +## Start by systemd + +- terminal#1 / watch logs: `journalctl -f -u radicale` +- terminal#2 / start "radicale" service: `systemctl start radicale` # Listen Status