Unable to upload any dicom object after upgrade to 5.24.2 #3638
jason1122g
started this conversation in
General
Replies: 2 comments 4 replies
-
Not reproducible - see attached screenshots in upload-dicom-obj-5.24.pdf Would it be possible to anonymize and share the DICOM object (whose upload fails)? |
Beta Was this translation helpful? Give feedback.
3 replies
-
I could reproduce same error after upgrade to 5.12.0 from 5.11.0, and the unique constraint violation error did not appear before db migration. But after I migrated db from
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
Cannot upload any dicom after upgrade to 5.24.2 from 5.11.0
We have also migrated the db from MariaDB to PostgreSQL via pgloader
Expected behavior
It should be able to upload dicom objects
Additional context
We cannot reproduce the issue stably
This issue might be related to the data size because it usually appears in the env already containing many dicom objects
The upgrade procedure is same as the description in wiki pages (https://github.com/dcm4che/dcm4chee-arc-light/wiki/Upgrade-on-Docker)
Our environment is composed of the following docker images:
Whenever we want to upload any dicom objects, the following wildfly error logs appear:
And we noticed that the duplicated pk number increase in each turn
This index seems to be related to
dicomattrs
tableIt sets pk as auto increament so that we suspected it might be an issue of sequence
But pgloader did reset the sequence and
select nextval('dicomattrs_pk_seq1');
showed a number being much more larger than 227xxWe are wondering if there is any missing step which might cause this issue 🤔
Truly appreciated for any help
Beta Was this translation helpful? Give feedback.
All reactions