DICOM server 1.4.19b bug fixes and updates

  • So if I run ./linux.sh and go to http://localhost:5912/ I don't get any response.

    If I look in $ netstat -lptu I can see tcp 0 0 *:5912 *:* LISTEN 6324/dgatesmall


    1. $ ./linux.sh
    2. nohup: appending output to 'nohup.out'
    3. ###!!! [Parent][MessageChannel] Error: (msgtype=0x15007F,name=PBrowser::Msg_Destroy) Closed channel: cannot send/recv
    4. ###!!! [Child][MessageChannel] Error: (msgtype=0x2C0105,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost

    And nohup.out:

    The process doesn't get killed - I have to do that myself.

    Is this just something to do with the system I am trying this on? Does this work for others?

  • Hi,

    So the install control server runs OK. Then there is a webserver which uses the same dgatesmall as well as CGI application (service.lua is actually the script that creates the web page). Maybe the files are not copied correctly into cgi-bin on apache?



    Marcel van Herk is developer of the Conquest DICOM server together with Lambert Zijp.

  • Hi! I am a old urologist in Japan. I can not understand "c++" at all. So I am not sure that bugs are already corrected and my changes are correct, and afraid that you can understand my English.

    std::auto_ptr (is deprecated) -> std::unique_ptr

















    STRATEGY::_processLine = processLine; ->

    STRATEGY::_processLine = move(processLine);



  • Hi Marcel - do you have a preference for how requests come to you? I can name a few right now, but I don't want to dump in the wrong location. One (seemingly) small enhancement that would be nice for us would be if timestamps in logfiles would include milliseconds.