C-FIND request handler has failed

Hi all. I have some problen. After machime with ORTHANC is restart, I have a problem. Cant open list of today researches. On logs I see only “C-FIND request handler has failed: Corrupted file (e.g. inconsistent MD5 hash)”. What I must do to fix it? Thanks.

Someone, help me please!

I am no Orthanc expert but it looks like a database problem (maybe shutdown when it was indexing a file?).

I can’t help, you will have to wait until someone more experienced read the post

Hi all. I have some problen. After machime with ORTHANC is restart, I
have a problem. Cant open list of today researches. On logs I see
only "C-FIND request handler has failed: Corrupted file (e.g.
inconsistent MD5 hash)". What I must do to fix it? Thanks.

Previous discussion:
https://groups.google.com/d/topic/orthanc-users/KASEJ9Gx3vQ/discussion

Here's how you could find the instance ID of the corrupt file (assuming
it is a DICOM instance that is corrupt). The following uses HTTPie but
you could do it with curl directly just as easily.

$ docker image pull docker.io/osimis/orthanc:latest
Trying to pull repository docker.io/osimis/orthanc ...
sha256:a33547e44e10900b3ebbc154867b396e157caeebaca76a9746d98623831d3eb0
: Pulling from docker.io/osimis/orthanc
Digest:
sha256:a33547e44e10900b3ebbc154867b396e157caeebaca76a9746d98623831d3eb0
Status: Image is up to date for docker.io/osimis/orthanc:latest
$ container=$(docker container run --detach --publish=80:8042
docker.io/osimis/orthanc:latest)
$ echo $DOCKER_HOST
sandbox.local:2375
$ orthanc=${DOCKER_HOST%:*}
$ # Upload DICOM instances to $orthanc
$ find "$sample_dicom_files" -name '*.dcm' -exec sh -c "http
$orthanc/instances <'{}' | jq --raw-output .ID" ';'
486de496-5c290fda-8efafb74-266beb66-12f37f1e
f9104f86-018a8eb1-ae4f65f9-ecaa484d-53fed56e
28ea296e-4fc7bb2a-9fd92a7a-52083ddd-d0964137
5f9c4ce3-b481774d-78613093-40d7a776-5ccaf682
f6005125-f3ba4f0c-74a96a01-2c919933-d9b704c7
05be1d54-96701b7c-905af136-35f4f3a2-d250175e
704f739a-8864479d-8427b7df-6adc8d3c-1593bb48
1fb8b9cf-751f354b-e0d34a54-83e46297-940d954c
(...)
$ # Corrupt a random file
$ docker container exec "$container" sh -c "echo foo

/var/lib/orthanc/db/00/7d/007d63d2-3769-4715-81ce-a6f9ace6825f"

$ # Find Orthanc ID of corrupt instance
$ http "$orthanc/instances" | jq --raw-output . | while read
instance; do if http --ignore-stdin --check-status POST
"$orthanc/instances/$instance/attachments/dicom/verify-md5"
&>/dev/null; then echo "$instance: OK"; else echo "$instance: CORRUPT"
&& exit; fi; done
486de496-5c290fda-8efafb74-266beb66-12f37f1e: OK
f9104f86-018a8eb1-ae4f65f9-ecaa484d-53fed56e: OK
28ea296e-4fc7bb2a-9fd92a7a-52083ddd-d0964137: OK
5f9c4ce3-b481774d-78613093-40d7a776-5ccaf682: OK
(...)
647ee9a0-7116b300-b96be851-e9429e9b-cf171387: CORRUPT

Once you have the ID you can find it in Orthanc storage and examine it
with more advanced tools to try and recover some data.