Hi Marcel, we've been having a lot of intermittent "Forward failed to connect" errors for quite some time, with no apparent rhyme or reason, and it only seems to be getting worse. We archive several days worth of logs (serverstatus.log, PacsTrouble, etc). After doing a grep of these files (on 3 of our conquest servers all running CentOS and Conquest 1417e) we're able to get a tally of how often and on which days we're seeing errors in the last several days (see below). Sometimes getting these failed forwards just needs a reboot and it magically works, other times our only option is to manually delete the potentially faulty file... But we often don't know what's faulty about it because the logs don't return detailed enough information.
We're wondering a couple things.
1) is there a way to get better logging for when image-sends fail? We have it on debug, however, we're not actually getting a real reason why the "forward failed to connect..."
2) do you think upgrading to Conquest 1419b will either
a) fix some of these failure instances
b) and/or give us better logging?
3) do you have any other recommendations?
We're also seeing sometimes images will be sucessfully delivered to Conquest and then no other movement or errors or logging will occur on these images... We're not sure what to make of this. I'll post the config below as well.
Errors | forward failed to connect, HERE.
[root@vlconquest01 logs]# grep -ic 'forward failed to connect' */*status.log
[root@vlconquest02 logs]# grep -ic 'forward failed to connect' */*status.log
[root@vlconquest03 logs]# grep -ic 'forward failed to connect' */*status.log
Our dicom.ini file, posted separately.