Dear Mailing list,
I have a problem and I hope you might have some suggestions how to fix it. My group has been using Orthanc successfully for some years now. We have one clinical DICOM server connected to a remote server that hosts Orthanc.
So far so good, but the other day, the clinical DICOM server went down, and ever since the orthanc daemon crashes when we try to access it, i.e. Search Studies or Test Echo, even though the DICOM server is back, responds to ping, and will recieve data from the MR scanner. In fact, Test Echo reports success, but the orthanc daemon dies immediately after.
Our remote server runs Ubuntu 20.04.2 LTS, while http://localhost:8042/system reports:
ApiVersion | 4 |
---|---|
DatabaseBackendPlugin | null |
DatabaseVersion | 6 |
DicomAet | CARONTE |
DicomPort | 4242 |
HttpPort | 8042 |
IsHttpServerSecure | true |
Name | Caronte |
PluginsEnabled | true |
StorageAreaPlugin | null |
Version | 1.5.8 |
As I understand it, v. 1.5.8 is the latest version compatible with our OS. We do not currently have gdb installed so I cannot produce a crash report. I’m hoping that people might have useful suggestions even without it. I attach the log obtained by starting the server, starting firefox and then requesting a test echo, starting from:
sudo -u orthanc /usr/sbin/Orthanc --verbose /etc/orthanc/ > Orthanc.log 2>&1 &
I attach the orthanc configuration files and log file. DICOM server i.p. and name have been modified for privacy reasons!
dicomweb.json (736 Bytes)
orthanc.json (21.1 KB)
Orthanc.log.txt (13.6 KB)
serve-folders.json (551 Bytes)
worklists.json (395 Bytes)