Hi,
Is there a limitation that the conquest service cannot store and send data at the same time? I noticed that for some examinations it keeps retrying to send them if they were interrupted by an incoming exam - see the attached portion of the log (it kept retrying to send the patient received at 09:31:23 - in the log I attach) all day, intermittently forwarding other patients (but not all of them were forwarded)...
Thank you!
OK, so it appears an instance of dgate (or its service) started in the background and then the service manager was trying to start it again (that error appears if you try to start dgate when it's already running - even when I try to start it manually). Now I killed it from the running tasks, it started on its own and it appears to work fine now.
Thank you very much for your assistance!
Hi,
I'm not sure what you mean by service manager - it is run in Ubuntu (we start it with this command: systemctl start app-dgate.service). I tried running dgate from the command line and I get this :
./dgate -v
DGATE (1.5.0c, build Thu May 5 12:07:53 2022, bits 64) is running as threaded server
Database type: built-in SQLite driver
Starting 1 DelayedForwarderThreads
Started 1 export queue thread(s)
***Failed to Listen () - bind error
Hi,
I managed to get some log - I hope it's the good one. The last study arrived and not sent is at 14:22 (time of the log).
Thank you!
Unfortunately I don't find that file in the Conquest-DICOM-Server folder. Is it somewhere else in Linux? (we have Ubuntu Server 20.04.4 LTS).
I attach the entire log file (let me know if there is another log you need), the DICOM.ini file and the acrnema.map file (I only modified the DICOM.ini file and the AETitle through the web service interface). Let me know if you need other files as well.
Thank you for your help!
Hello,
The only log I could find is PacsTrouble.log and I attach the last section of it (the same kind of messages repeat throughout the file). Those "Failed to Listen () - bind error" messages appear all the time, even when it works.
Thank you!
Hi,
I still have issue with the automatic forwarding. It appears that sometimes the studies are not forwarded, especially if they come very close to one another (if we send an exam now and one in 20 seconds or so, none of them get forwarded or only one goes). The destination server is a Caresteam one - does this have a connection?
Below is my configuration of the forwarder:
#Virtual server options
ForwardAssociationLevel = STUDY
ForwardAssociationRefreshDelay = 3600
ExportConverters = 1
ExportConverter0 = forward study to <pacsAEtitle> after 10
VirtualServerFor0 = <pacsAEtitle>,CACHESTUDIES
Later edit: I saw my "not forwarded" studies in the file DelayedFetchForwardFailures6104 . I attach it.
Thank you!
Hello,
I changed the AETitle of the server from CONQUESTSRV1 and everything works except, after I restarted the server (linux), the web patient browser (<hostname>/?mode=top&key=aap:noot) - I don't see any server in the server drop down menu (it used to be CONQUESTSRV1). I cannot access the patient list, if I click on "Go" I get this error: "DICOM ERROR connect failed on socket level (called not running)" I presume I need to configure the new AETitle somewhere but I don't know where. I tried in DICOM.ini from the /webserver/cgi-bin/ folder but with no success (do I need to restart a service after this modification? If yes, which service?)
Thank you!
Emanuel
Hello,
I used "forward study to AE after 60" and "forward study to AE" but in both cases the forward takes places after a lot of time. I have version 1.5.0c
Later edit: I restarted the server and now it works.
