Conqest+K-PACS = Connection Timeout

nataraj · Feb 22nd 2010

I've built conquest+mysql on linux, run K-PACS in qemu+windows XP.

I can successfully reqest server for studies, add new studies to the server (at least new records can be seen when I reqest records), I've added correct IP and host name into acrnema.map so it does not refuse make C-Move on unknown host. But I still can not view studies, stored on server. Both server and client reports connection timeout:

dgate -b sais:

Code

UPACS THREAD 2: STARTED AT: Mon Feb 22 13:34:34 2010A-ASSOCIATE-RQ Packet Dump        Calling Application Title : "KPServer"        Called Application Title : "dgate_linux     "        Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16384        Number of Proposed Presentation Contexts: 1        Presentation Context 0 "1.2.840.10008.5.1.4.1.2.2.2" 1Server Command   := 0021Message ID       := 0003        C-Move Destination: "KPServer"(QualifyOn) (mapped) IP:192.168.1.253, PORT:5678MyStudyRootRetrieveGeneric :: SearchOnQuery On ImageIssue Query on Columns: DICOMImages.SOPClassUI, DICOMImages.SOPInstanc, DICOMSeries.SeriesDate, DICOMSeries.SeriesTime, DICOMSeries.Modality, DICOMSeries.SeriesDesc, DICOMSeries.BodyPartEx, DICOMSeries.ProtocolNa, DICOMSeries.PatientPos, DICOMSeries.SeriesInst, DICOMSeries.SeriesNumb, DICOMStudies.StudyInsta,DICOMImages.ObjectFile,DICOMImages.DeviceNameValues: DICOMSeries.SeriesInst = '1.3.46.670589.5.2.10.2156913941.892665339.860724' and DICOMStudies.StudyInsta = '1.3.46.670589.5.2.10.2156913941.892665384.993397' and DICOMSeries.StudyInsta = DICOMStudies.StudyInsta and DICOMImages.SeriesInst = DICOMSeries.SeriesInstTables: DICOMImages, DICOMSeries, DICOMStudiesRecords = 2Number of Images to send: 2Host 'KPServer' did not accept the connectionC-Move (StudyRoot)UPACS THREAD 2: ENDED AT: Mon Feb 22 13:39:35 2010UPACS THREAD 2: TOTAL RUNNING TIME: 301 SECONDS

K-PACS log sais

Code

\par *******************************************************
\par \cf1 22.02.2010 10:34:25 ThreadID[736] : Retrieving images from dgate_linux started
\par \cf2 *******************************************************
\par [736]        >> : c-find request for StudyInstanceUID: 1.3.46.670589.5.2.10.2156913941.892665384.993397 initated
\par \cf3 [DICOM SCU]        >> : Connected to: 192.168.1.253:5678
\par [DICOM SCU]        >> : Item Type: 2
\par [DICOM SCU]        >> : Association Accept::ReadDynamic
\par [DICOM SCU]        >> : Presentation Context Accept, Transfer Syntax: 1.2.840.10008.1.2
\par \cf2 [736]        >> : c-find result: 0 sequences in study with UID 1.3.46.670589.5.2.10.2156913941.892665384.993397
\par [736]        >> : c-move request for sequence 1.3.46.670589.5.2.10.2156913941.892665339.860724 initiated.
\par \cf3 [DICOM SCU]        >> : Connected to: 192.168.1.253:5678
\par [DICOM SCU]        >> : Item Type: 2
\par [DICOM SCU]        >> : Association Accept::ReadDynamic
\par [DICOM SCU]        >> : Presentation Context Accept, Transfer Syntax: 1.2.840.10008.1.2
\par [DICOM SCU]        >> : KPServer >> dgate_linux
\par [DICOM SCU]        >> : (0000,0000),  4,\tab UL, "92" - Group Length
\par [DICOM SCU]        >> : (0000,0002), 28,\tab UI, "1.2.840.10008.5.1.4.1.2.2.2" - Affected SOP Class UID
\par [DICOM SCU]        >> : (0000,0100),  2,\tab US, "33" - Command Field
\par [DICOM SCU]        >> : (0000,0110),  2,\tab US, "3" - Message ID
\par [DICOM SCU]        >> : (0000,0600),  8,\tab AE, "KPServer" - Move Destination
\par [DICOM SCU]        >> : (0000,0700),  2,\tab US, "0" - Priority
\par [DICOM SCU]        >> : (0000,0800),  2,\tab US, "258" - Data Set Type
\par [DICOM SCU]        >> :
\par [DICOM SCU]        >> : KPServer >> dgate_linux
\par [DICOM SCU]        >> : (0008,0021),  0,\tab DA, "" - Series Date
\par [DICOM SCU]        >> : (0008,0031),  0,\tab TM, "" - Series Time
\par [DICOM SCU]        >> : (0008,0052),  6,\tab CS, "SERIES" - Query/Retrieve Level
\par [DICOM SCU]        >> : (0008,0060),  0,\tab CS, "" - Modality
\par [DICOM SCU]        >> : (0008,103E),  0,\tab LO, "" - Series Description
\par [DICOM SCU]        >> : (0018,0015),  0,\tab CS, "" - Body Part Examined
\par [DICOM SCU]        >> : (0018,1030),  0,\tab LO, "" - Protocol Name
\par [DICOM SCU]        >> : (0018,5100),  0,\tab CS, "" - Patient Position
\par [DICOM SCU]        >> : (0020,000D), 48,\tab UI, "1.3.46.670589.5.2.10.2156913941.892665384.993397" - Study Instance UID
\par [DICOM SCU]        >> : (0020,000E), 48,\tab UI, "1.3.46.670589.5.2.10.2156913941.892665339.860724" - Series Instance UID
\par [DICOM SCU]        >> : (0020,0011),  0,\tab IS, "" - Series Number
\par [DICOM SCU]        >> :
par [DICOM SCU]        >> : KPServer << dgate_linux
\par [DICOM SCU]        >> : (0000,0000),  4,\tab UL, "116" - Group Length
\par [DICOM SCU]        >> : (0000,0002), 28,\tab UI, "1.2.840.10008.5.1.4.1.2.2.2" - Affected SOP Class UID
\par [DICOM SCU]        >> : (0000,0100),  2,\tab US, "32801" - Command Field
\par [DICOM SCU]        >> : (0000,0120),  2,\tab US, "3" - Message ID Being Responded To
\par [DICOM SCU]        >> : (0000,0800),  2,\tab US, "257" - Data Set Type
\par [DICOM SCU]        >> : (0000,0900),  2,\tab US, "49157" - Status
\par [DICOM SCU]        >> : (0000,1020),  2,\tab US, "0" - Number of Remaining Sub-Operations
\par [DICOM SCU]        >> : (0000,1021),  2,\tab US, "0" - Number of Completed Sub-Operations
\par [DICOM SCU]        >> : (0000,1022),  2,\tab US, "0" - Number of Failed Sub-Operations
\par [DICOM SCU]        >> : (0000,1023),  2,\tab US, "0" - Number of Warning Sub-Operations
\par [DICOM SCU]        >> :
\par \cf4 [736]        >> : Error: retreive failed for HEAD EXP2 , Study:
\par  , Sequence:  1
\par \cf2 *******************************************************
\par \cf4 22.02.2010 10:38:57 ThreadID[736] : Closed.
\par Task processed with errors
\par \cf2 *******************************************************
\par \cf0
\par }

Display More

Something is wrong, but I am not so familiar with DICOM to understand what exactly is wrong.
Can somebody tell me how to fix this?
Or form what point I should start to debug and torbleshoot?
Or what to read to undestand this more?

nataraj · Feb 23rd 2010

Quote

i think u still need to configure Conquest as a dicom node in KPACS, because it seems KPACS is refusing the connection.

Thanks. As I can guess, the real problem were that K-PACSes ip can be reached directly from Conqest server. (it was a result of running K-PACS in qemu without taking care about making client's IP really visible).
And you are right, KPAKS were not configured correctly. But it was lesser problem.

Conqest+K-PACS = Connection Timeout

Participate now!

Share