Skip to content

Commit 2986f50

Browse files
committed
Mention debug logs in the troubleshooting section
Also add bullet points for readability.
1 parent 2219198 commit 2986f50

File tree

2 files changed

+11
-9
lines changed

2 files changed

+11
-9
lines changed

cpt-configure.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1218,6 +1218,8 @@ For the `Nagios monitoring system <http://www.nagios.org>`_ [Schubert08]_, a
12181218
checker plugin is available `on our website
12191219
<http://cernvm.cern.ch/portal/filesystem/downloads>`_.
12201220

1221+
.. _sct_debug_logs:
1222+
12211223
Debug Logs
12221224
----------
12231225

cpt-quickstart.rst

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -220,43 +220,43 @@ Example code for building CernVM-FS with locally built Fuse3 and including the C
220220
Troubleshooting
221221
---------------
222222

223-
In order to check for common misconfigurations in the base setup, run
223+
- In order to check for common misconfigurations in the base setup, run
224224

225225
::
226226

227227
cvmfs_config chksetup
228228

229-
CernVM-FS gathers its configuration parameter from various configuration files that can overwrite each others settings (default configuration, domain specific configuration, local setup, ...).
230-
To show the effective configuration for *repository*.cern.ch, run
229+
- CernVM-FS gathers its configuration parameter from various configuration files that can overwrite each others settings (default configuration, domain specific configuration, local setup, ...). To show the effective configuration for *repository*.cern.ch, run
231230

232231
::
233232

234233
cvmfs_config showconfig repository.cern.ch
235234

236-
In order to exclude autofs/automounter as a source of problems, you can try to mount *repository*.cern.ch manually with the following
235+
- In order to exclude autofs/automounter as a source of problems, you can try to mount *repository*.cern.ch manually with the following
237236

238237
::
239238

240239
mkdir -p /mnt/cvmfs
241240
mount -t cvmfs repository.cern.ch /mnt/cvmfs
242241

243-
In order to exclude SELinux as a source of problems, you can try mounting after SELinux has been disabled by
242+
- In order to exclude SELinux as a source of problems, you can try mounting after SELinux has been disabled by
244243

245244
::
246245

247246
/usr/sbin/setenforce 0
248247

249-
Once the issue has been identified, ensure that the changes are taken by restarting autofs
248+
- Once the issue has been identified, ensure that the changes are taken by restarting autofs
250249

251250
::
252251

253252
systemctl restart autofs
254253

255-
If the problem is that a repository can be mounted and unmounted but
256-
later cannot be remounted, see :ref:`sct_remounting_namespaces_containers`.
254+
- If the problem is that a repository can be mounted and unmounted but later cannot be remounted, see :ref:`sct_remounting_namespaces_containers`.
257255

258-
In order to exclude a corrupted local cache as a source of problems, run
256+
- In order to exclude a corrupted local cache as a source of problems, run
259257

260258
::
261259

262260
cvmfs_config wipecache
261+
262+
- Finally running with debug logs enabled can provide additional information for bug reports. This can be done by specifying a log file path in the client settings, e.g: ``CVMFS_DEBUGLOG=/tmp/cvmfs.log``. See :ref:`sct_debug_logs` for more details.

0 commit comments

Comments
 (0)