Client Error: command 0001 failed

    Hi I'm using Conquest 1.4.14 on Ubuntu (32 bit)


    In PacsTrouble.log seeing the following error:
    I tried putting debug level to 4, but didn't see any more details in server status log.


    ***Client Error: command 0001 failed **
    Tue Nov 10 23:15:35 2009 ***Connection Terminated
    Tue Nov 10 23:32:03 2009 ***Error saving to SQL: 69021{####1LyyA]PLLDL_}/1.2.392.200046.100.2.1.50593.231.20091105022855.1_0001_000001_1257913923003c.v2


    Qtns:
    1. Any guidance on what's causing this?
    2. How can I see the details of the failing mysql query? Raising the debug level to 4 didn't help to get more details in serverstatus.log.


    Appreciate your response,
    -Vin

    Hi Marcel,


    I tried this command dgate --debuglog_on, but I didn't see any debug statements in the server_status.log. I'm running linux 1.4.14 version. Is there any other command I use to log the detailed debug statements in the log. I also setup debug_level to 4 in the dicom.ini and restarted the server, but still no debug statements in the log.


    Thanks for the help


    -V

    Hi Marcel,


    As you suggested I do see the storage error, but doesn't provide details on the error. What kind of storage error or what's causing it, I'm using Mysql, so is it mysql error with particular client, as it's working fine with other clients. Is it insert sql error? Could you please provide some insight into it. I've added the snippet of log below. Thanks for your response.


    Mon Nov 16 09:48:56 2009 UPACS THREAD 19: STARTED AT: Mon Nov 16 09:48:55 2009
    Mon Nov 16 09:48:56 2009 A-ASSOCIATE-RQ Packet Dump
    Mon Nov 16 09:48:56 2009 Calling Application Title : "RAPIDSTORE99996 "
    Mon Nov 16 09:48:56 2009 Called Application Title : "DEDTAE "
    Mon Nov 16 09:48:56 2009 Application Context : "1.2.840.10008.3.1.1.1", PDU length: 65536
    Mon Nov 16 09:48:56 2009 Number of Proposed Presentation Contexts: 27
    Mon Nov 16 09:48:56 2009 Presentation Context 0 "1.2.840.10008.5.1.4.1.1.4" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 1 "1.2.840.10008.5.1.4.1.1.1" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 2 "1.2.840.10008.5.1.4.1.1.2" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 3 "1.2.840.10008.5.1.4.1.1.7" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 4 "1.2.840.10008.5.1.4.1.1.6.1" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 5 "1.2.840.10008.5.1.4.1.1.3.1" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 6 "1.2.840.10008.5.1.4.1.1.6" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 7 "1.2.840.10008.5.1.4.1.1.3" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 8 "1.2.840.10008.5.1.4.1.1.1.1" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 9 "1.2.840.10008.5.1.4.1.1.1.1.1" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 10 "1.2.840.10008.5.1.4.1.1.1.3" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 11 "1.2.840.10008.5.1.4.1.1.1.3.1" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 12 "1.2.840.10008.5.1.4.1.1.1.2" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 13 "1.2.840.10008.5.1.4.1.1.1.2.1" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 14 "1.2.840.10008.5.1.4.1.1.20" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 15 "1.2.840.10008.5.1.4.1.1.128" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 16 "1.2.840.10008.5.1.4.1.1.77.1.1" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 17 "1.2.840.10008.5.1.4.1.1.77.1.2" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 18 "1.2.840.10008.5.1.4.1.1.77.1.4" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 19 "1.2.840.10008.5.1.4.1.1.77.1.3" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 20 "1.2.840.10008.5.1.4.1.1.12.1" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 21 "1.2.840.10008.5.1.4.1.1.12.3" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 22 "1.2.840.10008.5.1.4.1.1.12.2" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 23 "1.2.840.10008.5.1.1.30" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 24 "1.2.840.10008.5.1.1.29" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 25 "1.2.840.10008.5.1.4.1.1.481.1" 1
    Mon Nov 16 09:48:56 2009 Presentation Context 26 "7.5.63.970725.1" 0
    Mon Nov 16 09:48:56 2009 Server Command := 0001
    Mon Nov 16 09:48:56 2009 Message ID := 1fd6
    Mon Nov 16 09:48:56 2009 0000,0002 26 UI AffectedSOPClassUID "1.2.840.10008.5.1.4.1.1.1"
    Mon Nov 16 09:48:56 2009 0000,0100 2 US CommandField 1
    Mon Nov 16 09:48:56 2009 0000,0110 2 US MessageID 8150
    Mon Nov 16 09:48:56 2009 0000,0700 2 US Priority 0
    Mon Nov 16 09:48:56 2009 0000,0800 2 US DataSetType 0
    Mon Nov 16 09:48:56 2009 0000,1000 52 UI AffectedSOPInstanceU "1.2.392.200046.100.2.1.1.12119.20091115202634.6.1.1"
    Mon Nov 16 09:50:27 2009 Failed STORAGE
    Mon Nov 16 09:50:27 2009
    ***Client Error: command 0001 failed **
    Mon Nov 16 09:50:27 2009 ***Connection Terminated
    on Nov 16 09:50:27 2009 ***Connection Terminated
    Mon Nov 16 09:50:27 2009 0000,0002 26 UI AffectedSOPClassUID "1.2.840.10008.5.1.4.1.1.1"
    Mon Nov 16 09:50:27 2009 0000,0100 2 US CommandField 1
    Mon Nov 16 09:50:27 2009 0000,0110 2 US MessageID 8144
    Mon Nov 16 09:50:27 2009 0000,0700 2 US Priority 0
    Mon Nov 16 09:50:27 2009 0000,0800 2 US DataSetType 0
    Mon Nov 16 09:50:27 2009 0000,1000 52 UI AffectedSOPInstanceU "1.2.392.200046.100.2.1.1.12119.20091115202634.3.1.1"
    Mon Nov 16 09:51:03 2009

    Hi Marcel,


    I gave the last option as well and now I do see sql queries in the debug, but for the following error not much is showing up in the logs. Here's the debug log for one of the threads. I still can't figure out what's happening :cry:


    I can send you the log if that would help.


    Mon Nov 16 13:36:37 2009 UPACS THREAD 86: STARTED AT: Mon Nov 16 13:36:37 2009
    Mon Nov 16 13:36:37 2009 A-ASSOCIATE-RQ Packet Dump
    Mon Nov 16 13:36:37 2009 Calling Application Title : "RAPIDSTORE99996 "
    Mon Nov 16 13:36:37 2009 Called Application Title : "DESTAE "
    Mon Nov 16 13:36:37 2009 Application Context : "1.2.840.10008.3.1.1.1", PDU length: 65536
    Mon Nov 16 13:36:37 2009 Number of Proposed Presentation Contexts: 27
    Mon Nov 16 13:36:37 2009 Presentation Context 0 "1.2.840.10008.5.1.4.1.1.4" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 1 "1.2.840.10008.5.1.4.1.1.1" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 2 "1.2.840.10008.5.1.4.1.1.2" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 3 "1.2.840.10008.5.1.4.1.1.7" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 4 "1.2.840.10008.5.1.4.1.1.6.1" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 5 "1.2.840.10008.5.1.4.1.1.3.1" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 6 "1.2.840.10008.5.1.4.1.1.6" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 7 "1.2.840.10008.5.1.4.1.1.3" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 8 "1.2.840.10008.5.1.4.1.1.1.1" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 9 "1.2.840.10008.5.1.4.1.1.1.1.1" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 10 "1.2.840.10008.5.1.4.1.1.1.3" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 11 "1.2.840.10008.5.1.4.1.1.1.3.1" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 12 "1.2.840.10008.5.1.4.1.1.1.2" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 13 "1.2.840.10008.5.1.4.1.1.1.2.1" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 14 "1.2.840.10008.5.1.4.1.1.20" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 15 "1.2.840.10008.5.1.4.1.1.128" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 16 "1.2.840.10008.5.1.4.1.1.77.1.1" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 17 "1.2.840.10008.5.1.4.1.1.77.1.2" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 18 "1.2.840.10008.5.1.4.1.1.77.1.4" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 19 "1.2.840.10008.5.1.4.1.1.77.1.3" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 20 "1.2.840.10008.5.1.4.1.1.12.1" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 21 "1.2.840.10008.5.1.4.1.1.12.3" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 22 "1.2.840.10008.5.1.4.1.1.12.2" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 23 "1.2.840.10008.5.1.1.30" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 24 "1.2.840.10008.5.1.1.29" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 25 "1.2.840.10008.5.1.4.1.1.481.1" 1
    Mon Nov 16 13:36:37 2009 Presentation Context 26 "7.5.63.970725.1" 0
    Mon Nov 16 13:36:37 2009 Server Command := 0001
    Mon Nov 16 13:36:37 2009 Message ID := 205d
    Mon Nov 16 13:36:37 2009 0000,0002 26 UI AffectedSOPClassUID "1.2.840.10008.5.1.4.1.1.1"
    Mon Nov 16 13:36:37 2009 0000,0100 2 US CommandField 1
    Mon Nov 16 13:36:37 2009 0000,0110 2 US MessageID 8285
    Mon Nov 16 13:36:37 2009 0000,0700 2 US Priority 0
    Mon Nov 16 13:36:37 2009 0000,0800 2 US DataSetType 0
    Mon Nov 16 13:36:37 2009 0000,1000 52 UI AffectedSOPInstanceU "1.2.392.200046.100.2.1.1.12119.20091115202634.7.1.1"
    Mon Nov 16 13:39:22 2009 Failed STORAGE
    Mon Nov 16 13:39:22 2009
    ***Client Error: command 0001 failed **
    Mon Nov 16 13:39:22 2009 ***Connection Terminated
    Mon Nov 16 13:39:22 2009 0000,0002 26 UI AffectedSOPClassUID "1.2.840.10008.5.1.4.1.1.1"
    Mon Nov 16 13:39:22 2009 0000,0100 2 US CommandField 1
    Mon Nov 16 13:39:22 2009 0000,0110 2 US MessageID 8285
    Mon Nov 16 13:39:22 2009 0000,0700 2 US Priority 0
    Mon Nov 16 13:39:22 2009 0000,0800 2 US DataSetType 0
    Mon Nov 16 13:39:22 2009 0000,1000 52 UI AffectedSOPInstanceU "1.2.392.200046.100.2.1.1.12119.20091115202634.7.1.1"
    Mon Nov 16 13:39:24 2009
    Mon Nov 16 13:39:24 2009 UPACS THREAD 87: STARTED AT: Mon Nov 16 13:39:23 2009

    Hi,


    the last two message logs differ from the first one you gave (error saving to SQL is missing). It almost looks as if the sending server is making connection but not sending any data. According to the source code, there should have been a log of the associated data. All messages below "***Client Error: command 0001 failed **", are due to a bug in the error reporting (fixed in 1.4.15).


    I have seen a similar error once when sending data with the DCMTK, where it hangs up due to an internal error before actually transmitting the data. Who is sending this stuff?


    And what is {####1LyyA]PLLDL_} in your first post?


    Marcel

    Hi Marcel,


    I didn't see the error in the first post again. Now I'm just seeing the repeated error "connection terminated .." in my later post.


    As you mention "I have seen a similar error once when sending data with the DCMTK, where it hangs up due to an internal error before actually transmitting the data.", do you have any guess what's this internal error is or what is causing it. I'm little bit lost and can't figure out how to debug it.


    The image is being forwarded from two external remote pacs and error is being seen only from one pacs. The error is also not consistent as sometime images do come through but sometime see connection terminated error from this single pacs. It won't be easy to upgrade to 1.4.15 so quickly.


    Appreciate you help.

    Hi,


    the error was related to trying to send with a different compression as the image had, and the DCMTK client has no way to change the compression on the fly and hang up as result.


    To debug, you can try to use a windows machine as forwarder using a forwarder application that logs all transactions. Test.exe from DICOMLIB.ZIP can do that:


    Code
    test -fe PORT host port loglevel						forward PORT to host:port

    	note: loglevel 	0(default)=log nothing, 

    			1=log request commands

    			2=+log request data and response command

    			3=+log all except image data 

    			4=+log all including image data


    Marcel

Participate now!

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

Register Yourself Login