Conquest under Linux - dgate --movepatient problem

    Hi,


    i am sorry if my question had already been supplied.


    I have a problem under linux with the command line dgate -w/etc/conquest --movepatient:AEtitle1,AEtitle2,patientid which doesn't work.
    i haven't any log information. The command just stand with a _ prompt during many minutes and don't do anything.


    I try under windows and the command works fine whatever the direction : aetitle1 to aetitle2(receive) or aetitle2 to aetitle1(send)


    I don't know how to solve my problem.


    Thanks for everyone who could help me.


    I use the latest version of conquest.

    Can you try:


    dgate -w/etc/conquest "--movepatient:AEtitle1,AEtitle2,patientid"


    and if that fails, send a server log around this command? You may also try to actually run dgate from the /etc/conquest folder. There may be a linux issue with -w.


    Marcel

    thank you for you answer.


    So I have tryied to do dgate "--movepatient:AEtitle1,AEtitle2,patientid" directly under the /etc/conquest folder and it failed again.


    here is the only thing i have in PacsTrouble.log:


    Wed Oct 19 11:31:45 2011 ***forward xxxx to: local server not working
    Wed Oct 19 11:31:45 2011 *** connection terminated


    There is nothing in PacsUser.log file.


    any idea?

    Hi,


    This error message means that a connect to 127.0.0.1 does not work. The dgate --move commands just start a dicom move.


    Options:


    the server is not running correctly (unlikely)
    the port the --move command reads in dicom.ini is not the port at which the server is running
    there is an internal firewall issue
    the tcp/ip network is not working


    Try: dgate --display_status: and check the output


    Marcel

    it works!


    as you said, it s a -w/path problem or the fact that I use daemonize to put dgate in service mode.


    I launch dgate directly under the /etc/conquest folder, then on an other shell i launch dgate --move....and it works!


    So my problem is really the fact that i want to launch dgate in service mode...


    But thank you very much, i will try to find a way to launch dgate in service mode.

    Hi


    I have a similar problem. I am trying to start dgate from a script using:


    # /conquestdir/dgate -v -w/conquestdir &


    dgate seems to fail to load dicom.ini. The strange thing is it definitely finds the directory. If I mistype it it reports it as not existing. Starting dgate in its home directory works fine. Could this be the old forward/backslash issue between windows and linux?


    I am trying to set up a systemctl script to start dgate as a service on Fedora 16.


    Cheers
    Alanphys

Participate now!

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

Register Yourself Login