Hi,
I wrote a Python app to send patients from my Orthanc server to another off-site Orthanc server an it mostly works but I sometimes get a http 500 error, especially on long series. Is there a way to prevent this?
Tanks.
Hi
Not without providing any information.
Hi Alain,
I am very sorry for the very short and ambigous question. I’ll provide more details.
I have 2 Orthanc builds in 2 different Synology NAS devices. One is an old build, still using the Orthanc Beta app, which was present before Synology unsupported it when its OS updated to DSM 7 from DSM 6. I still use it because it just works for its intended purpose, which is to store patient DICOMs sent by ultrasound devices. The other Orthanc is running as a Docker container and is the latest image. This one is intended as a back up of the first Orthanc. The way I normally keep it updated is by taking a back-up of the Postgres database of Orthanc, and also use an external HDD attached to Synology to copy the Orthanc Storage. Then I restore them on the other Orthanc. This method works but is primitive somehow, requiring a database restore every 2-3 months, and manually copying everything (well, not everything, just what has been added, but it still can take time).
A solution that I’ve created, using ChatGPT as the main orchestrator, is a Python app that quieries Orthanc to get the list of patients sent to it since its inception (in 2017), check which patients were archived at a certain date, then send these patients to the other Orthanc offsite. It is working quite well, except in some patients, where it gives a http 500 error. It isn’t a random error, it always happens at the same patients. The instances themselves don’t have any issues, they can be opened and viewed. Also, it is possible to copy them to a temporary folder in Synology and then send them using a curl command to the offsite Orthanc.
ChatGPT’s theory is that the Orthanc Beta app may have limitations in sending files over http, especially if they are large instances (one that failed was a 450 MB ultrasound clip). I wanted to know if this is a limitation of the Orthanc beta app, or if there is something that I am overlooking.
Of course, the right course of action would be to update Orthanc, but this would mean a risk of disruption if things get messy (it will require a DSM update, installing Docker, setting Orthanc again, creating a new config, etc… which is doable of course, I already did it for the othe Orthanc, but would prefer not to if I don’t have to.
Again, apologies for the short original message,
Regards…
What is Orthanc Beta app ? BTW, there are no software limitations but there is always a limited hardware memory on your system.
BTW, for us to investigate, we need a reproducible working example that includes logs, DICOM files, configurations and versions of both systems.