From 860bb31eb492d624b9a9fda5f075b3bf4ecd0401 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bob=20Dr=C3=B6ge?= Date: Sun, 3 Dec 2023 20:56:30 +0100 Subject: [PATCH 1/2] &endash; -> – --- docs/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 73e3ce2..976eff9 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -402,7 +402,7 @@ for example: * Lack of sufficient disk space, for the CernVM-FS client cache, for the proxy server, or for the private Stratum 1 replica server; * Network latency issues, either within the local network (to the proxy server or Stratum 1 replica server), - or to the outside world (public Stratum 1 replica servers) &endash; see also the [Connectivity](#connectivity) + or to the outside world (public Stratum 1 replica servers) – see also the [Connectivity](#connectivity) section; From c28d9bcdaa9158b8dc9d6cca0f65494157e3dafa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bob=20Dr=C3=B6ge?= Date: Sun, 3 Dec 2023 21:03:53 +0100 Subject: [PATCH 2/2] add warning about write permission to CVMFS_DEBUGLOG path --- docs/troubleshooting.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 976eff9..4006fa1 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -442,6 +442,10 @@ has been run. See [CernVM-FS documentation / debug-logs](https://cvmfs.readthedocs.io/en/stable/cpt-configure.html#debug-logs) for more information. Note that the debug log will log every operation in CVMFS and generates large files - it should be turned back off after capturing an issue. +!!! warning + Make sure that the `cvmfs` user actually has write permission to the location specified with `CVMFS_DEBUGLOG`. + Otherwise you will not only get no log file, but it will also lead to client failures. + An interesting command for mounted repositories is ``` { .bash .copy } attr -g logbuffer /cvmfs/software.eessi.io