Forwarding to .... debug

    Hi!


    I have one conquest srv AE:PACS and remote AE:PACS2


    in dicom.ini:

    ...

    ImportConverters = 2

    ImportConverter0 = forward to PACS2; nop %u %m %i %o


    [lua]

    association = package.path=package.path..';'..Global.basedir..'lua/?.lua'

    ImportConverter1 = dofile('/conquest/lua/ImportConverter.lua');

    QueryResultConverter0 = dofile('/conquest/lua/QueryResultConverter.lua');

    ...


    i have enable debug to file (run in conquest folder):

    ./dgate --debuglevel:6

    ./dgate --debuglog_on:debug.txt


    and some time in log this:

    Thu Sep 21 13:47:58 2023 ImportConverter0.0: forwarded object to PACS2

    Thu Sep 21 13:48:33 2023 Importconverter0.1: nop IRIS1 MG 123456789 1.3.51.0.7.11740735244.64250.44111.45637.36524.33411.2401

    Thu Sep 21 13:48:33 2023 ImportConverter0.0: Forward association closed by STUDY

    Thu Sep 21 13:48:33 2023 ****** ImportConverter.lua BEGIN ******

    Thu Sep 21 13:48:33 2023 ...

    Thu Sep 21 13:48:33 2023 ****** ImportConverter.lua END ******


    but some time this:

    Sun Sep 17 13:27:47 2023 ImportConverter0.0: forwarded object to PACS2

    Sun Sep 17 13:27:47 2023 PDU:Connect failed due to corrupt transmission 46

    Sun Sep 17 13:27:47 2023 *** ImportConverter0.0: Forward failed to connect to host PACS2

    Sun Sep 17 13:27:47 2023 Importconverter0.1: nop DS DX 123456788990 1.2.826.1694942589.958750.346

    Sun Sep 17 13:27:47 2023 ****** ImportConverter.lua BEGIN ******

    Sun Sep 17 13:27:47 2023 ...

    Sun Sep 17 13:27:47 2023 ****** ImportConverter.lua END ******



    How i can additional debug forward?

    and what better/faster/correct forward in ImportConverter (before modification and SQL query) or in ExportConverter?

    and how i can make guaranteed forward?

    Hi,


    ExportConverters "forward to" have a retry mechanism, Importconverters not.


    What OS are you on? Some Linux variants are known to give network errors on Conquest.


    Is regular transmission to PACS2 reliable?


    Marcel

    Hi!

    Quote from marcelvanherk

    ExportConverters "forward to" have a retry mechanism, Importconverters not.

    This is an important clarification!

    Quote from marcelvanherk

    What OS are you on? Some Linux variants are known to give network errors on Conquest.

    root@pacs:/data/conquest# uname -a
    Linux pacs 6.2.16-12-pve #1 SMP PREEMPT_DYNAMIC PMX 6.2.16-12 (2023-09-04T13:21Z) x86_64 x86_64 x86_64 GNU/Linux
    root@pacs:/data/conquest# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 23.04
    Release: 23.04
    Codename: lunar

    Quote from marcelvanherk

    Is regular transmission to PACS2 reliable?

    yes! errors sometimes appear...

    Hi!

    for additional debug setup one more conquest between.... and so this:

    on intermediary:

    Code
    ExportConverter0.0: forward /data/conquest/data/22062125738/1.2.826.1695649623.12689047.130_0001_000001_16958809360000.dcm to PACS-BRP

    dgate: ./src/dgate/dicomlib/array.tcc:114: DATATYPE& Array<DATATYPE>::Get(unsigned int) [with DATATYPE = BufferSpace*]: Assertion `Index<ArraySize' failed.

    Aborted

    after this dgate crashed :-(


    dicom.ini on intermediary:

    Code
    ExportConverters = 1

    ExportConverter0 = forward to PACS org PACS2

    log on PACS:

    Code
    Thu Sep 28 10:00:27 2023 ***No valid presentation contexts/transfer syntax found in 0 candidates

    Thu Sep 28 10:00:27 2023 ***In 0 presentation contexts

    Thu Sep 28 10:00:27 2023 ***#Possible transfer syntaxes: 13

    Thu Sep 28 10:00:27 2023 *** multiplex: connection terminated

    via ImportConverter0 = forward to PACS3 org PACS;nop %u %m %i %o this .dcm go ok, but ImportConverter does not have retry-send...

    via ExportConverter0 = forward to PACS3 org PACS;nop %u %m %i %o dgate crashed :-(

    Hi!


    root@pacs3:/data/conquest# ./dgate -v

    Monitoring for files in: /data/conquest/MAG0/incoming/

    DGATE (1.5.0d, build Mon Sep 11 06:59:33 2023, bits 64) is running as threaded server

    Database type: built-in SQLite driver

    dicom.ini:


    root@pacs2:/data/conquest# /data/conquest/dgate -w/data/conquest -v

    Monitoring for files in: /data/conquest/data/incoming/

    DGATE (1.5.0d, build Sun Sep 10 22:05:15 2023, bits 64) is running as threaded server

    Database type: built-in SQLite driver

    Starting 5 DelayedForwarderThreads

    Started 1 export queue thread(s)


    dicom.ini:

    Hi!


    Help please - revised all, configuration,server's config and can't understand what i do wrong:

    dicom files contain utf8 - I can send them wherever you say (to a non-public place) unchanged...

    or i can get you access (ssh) to my server's for experiment...

    Hi,


    FileNameSyntax = %studydate[2,7]/%callingae/%id/%seriesid/%sopuid.dcm


    results in filename:


    /zsdb/MAG0/230912//124335760/1/1.2.826.1694524056.20532531.346.dcm


    I.e. %callingae does not seem to work. Is this related to the issue?


    Marcel

    Hi!


    i was remove %callingae

    (FileNameSyntax = %studydate[2,7]/%id/%seriesid/%sopuid.dcm) result:

    Hi,


    I am forwarding between two Ubuntu conquest instances but the issue does not reproduce:

    Code
    Monitoring for files in: /home/marcel/Conquest-DICOM-Server/data/incoming/

    DGATE (1.5.0d, build Wed Oct 18 23:11:50 2023, bits 64) is running as threaded server

    Database type: built-in SQLite driver

    Starting 1 DelayedForwarderThreads

    Started 1 export queue thread(s)

    ***Truncated StationNam from 20 to 16 chars in file: 231015//18330-4/1/1.2.826.1697347993.72120313.346.dcm

    ***Truncated StudyID from 26 to 16 chars in file: 231015//18330-4/1/1.2.826.1697347993.72120313.346.dcm

    Added file: /home/marcel/Conquest-DICOM-Server/data/231015//18330-4/1/1.2.826.1697347993.72120313.346.dcm

    ExportConverter0.0: forward /home/marcel/Conquest-DICOM-Server/data/231015//18330-4/1/1.2.826.1697347993.72120313.346.dcm to TEST



    I think the truncation is a potential issue, but I see no crash

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login