Mercurial > hg > orthanc-book

changeset 541:d70347eecb91

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
cont
author Sebastien Jodogne <s.jodogne@gmail.com>
date Thu, 05 Nov 2020 15:17:15 +0100
parents d18496f166b8
children cdda6258a7ba
files Sphinx/source/faq/debugging.rst Sphinx/source/faq/dicom.rst Sphinx/source/users/configuration.rst
diffstat 3 files changed, 10 insertions(+), 5 deletions(-) [+]
line wrap: on
line diff
--- a/Sphinx/source/faq/debugging.rst	Thu Nov 05 15:06:41 2020 +0100
+++ b/Sphinx/source/faq/debugging.rst	Thu Nov 05 15:17:15 2020 +0100
@@ -19,8 +19,8 @@
 files in verbose mode <log>` do not provide meaningful information.
 
 **Important reminder:** Most issues with Orthanc can be solved by
-carefully looking at the :ref:`Orthanc logs <log>` in ``--verbose``
-mode!
+carefully looking at the :ref:`Orthanc logs <log>` after starting
+Orthanc with the ``--verbose --trace-dicom`` command-line options!
 
 
 Any system
--- a/Sphinx/source/faq/dicom.rst	Thu Nov 05 15:06:41 2020 +0100
+++ b/Sphinx/source/faq/dicom.rst	Thu Nov 05 15:17:15 2020 +0100
@@ -7,7 +7,8 @@
 computer network are related to the configuration of these
 modalities. As preliminary debugging actions, you should:
 
-* Make sure you use the `most recent version <https://www.orthanc-server.com/download.php>`_ of Orthanc.
+* Make sure you use the `most recent version
+  <https://www.orthanc-server.com/download.php>`_ of Orthanc.
 * Make sure the two computers can "ping" each other.
 * Turn off all the firewalls on the two computers (especially on Microsoft Windows).
 * Make sure the remote computer has `DICOM TLS encryption
@@ -36,8 +37,10 @@
     options ``LuaScripts`` and ``Plugins`` both to the empty list.
   * ``DicomAssociationCloseDelay`` should be set to ``0``.
 
-* Restart Orthanc with the ``--verbose`` option at command line, and
-  carefully inspect the log. This might provide immediate debugging
+* Restart Orthanc with the ``--verbose --trace-dicom`` options at
+  command line, and carefully inspect the log (the ``trace-dicom``
+  option is new in Orthanc 1.8.1 and provides low-level information
+  from DCMTK). This might provide immediate debugging
   information. Make sure to read :ref:`how to generate an exploitable
   log <log>`.
 * Issue a :ref:`DICOM C-Echo <dicom-echo>` from each modality to make
--- a/Sphinx/source/users/configuration.rst	Thu Nov 05 15:06:41 2020 +0100
+++ b/Sphinx/source/users/configuration.rst	Thu Nov 05 15:17:15 2020 +0100
@@ -61,3 +61,5 @@
     $ Orthanc ./Configuration.json --verbose
     $ Orthanc ./Configuration.json --trace
 
+To learn more about the Orthanc logs, :ref:`check out the dedicated
+page <log>`.