xnat desktop client fails after upgrade

104 views
Skip to first unread message

George Kowalski

unread,
Sep 30, 2022, 10:42:07 AM9/30/22
to xnat_discussion
after an upgrade yesterday to version 1.8.5.1, build: 14 our desktop client 3.1.0 fails to upload images to our prod server. Yes we tested this against our dev server and it did and still works with no issue. 

So my question is , what port is the upload communicating on for it's uploading, as our prod server is in a DMZ of sorts from our local machines ? 

I can still upload ZIP files via https into the production server pre-archive , but the upload with the client just hangs and no activity in the pre-archive or logs is shown. 

G

George Kowalski

unread,
Sep 30, 2022, 11:03:04 AM9/30/22
to xnat_discussion
and no,  we've never had the DICOM SCP Receivers enabled 

Screen Shot 2022-09-30 at 10.01.06 AM.png
Interestingly I Just noticed that on our dev server ( running the same 1.8.5.1 ) the archive Behaving is different : 

Screen Shot 2022-09-30 at 10.02.29 AM.png

Rick Herrick

unread,
Sep 30, 2022, 11:25:26 AM9/30/22
to xnat_di...@googlegroups.com
The uploader uses the standard HTTP/HTTPS port, same as any REST API call or the web UI, so I doubt it has to with your network/DMZ configuration if you can access XNAT at all from the workstation where you’re running the desktop client.

When you said it fails, how exactly does it fail?

You can turn on the DevTools in the desktop client by clicking DevTools->Toggle DevTools. That can tell you 1) what API calls might be failing in the Network tab and 2) any errors in the application itself would probably produce warning or error messages in the console.

If you have access to the XNAT backend, you can look at the logs there, mostly likely in the folder ${xnat.home}/logs.

Rick Herrick
Senior Software Developer


------ Original Message ------
From "George Kowalski" <george....@gmail.com>
To "xnat_discussion" <xnat_di...@googlegroups.com>
Date 9/30/2022 9:42:07 AM
Subject [XNAT Discussion] xnat desktop client fails after upgrade

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/ddf911e4-09e8-411d-9d05-dc3f51bd5c50n%40googlegroups.com.

George Kowalski

unread,
Sep 30, 2022, 11:58:10 AM9/30/22
to xnat_discussion
Yea the Desktop starts up a server on port 7714 , and the last I see in the network log is 7 requests that that "server" : 


Screen Shot 2022-09-30 at 10.49.49 AM.png




At this point nothing gets into the prearchive , no errors on the xnat prod tomcat server . 

Yea , start our own server : 


Hmm , writing to the console , lets look there : 

Screen Shot 2022-09-30 at 10.55.07 AM.png

well that's just scrolling and scrolling ...  no useful data I can see.

G

Rick Herrick

unread,
Sep 30, 2022, 2:20:39 PM9/30/22
to xnat_di...@googlegroups.com
The server on port 7714 is used by the desktop client itself for accessing files across the various processes running internally, so all references to that port are qualified by localhost. In other words, none of that network traffic will hit the DMZ.

When you start trying to upload, do you see anything in the XNAT log access.log that looks like this?


Or in the log received.log like this?

2022-09-30 13:13:52,056 - admin:/data/xnat/prearchive/Project/20220930_131352007/Session/SCANS/3/DICOM/xxx.dcm

Rick Herrick
Senior Software Developer


------ Original Message ------
From "George Kowalski" <george....@gmail.com>
To "xnat_discussion" <xnat_di...@googlegroups.com>
Date 9/30/2022 10:58:10 AM
Subject Re: [XNAT Discussion] xnat desktop client fails after upgrade

George Kowalski

unread,
Sep 30, 2022, 2:51:04 PM9/30/22
to xnat_discussion
Yes the Access log ( I've pasted everything that appears after I hit the upload button ) has these lines : https://gist.github.com/gkowalski/79618c93223f2f8a6df00b795fd110ce 

Nothing added to the received.log .. 


George Kowalski

unread,
Sep 30, 2022, 4:08:37 PM9/30/22
to xnat_discussion
And Now I notice in the restlet.log the following errors : 

Rick Herrick

unread,
Sep 30, 2022, 6:10:07 PM9/30/22
to xnat_di...@googlegroups.com
Okay that’s very helpful. This is definitely the issue, but I’m not quite sure what’s going on in that code. We’re looking into it now.

Rick Herrick
Senior Software Developer


------ Original Message ------
From "George Kowalski" <george....@gmail.com>
To "xnat_discussion" <xnat_di...@googlegroups.com>
Date 9/30/2022 3:08:37 PM
Subject Re: Re[2]: [XNAT Discussion] xnat desktop client fails after upgrade

George Kowalski

unread,
Oct 3, 2022, 1:34:20 PM10/3/22
to xnat_discussion
Even worse. Downgrading xnat to  1.8.4.1, build: 7  and it still does not work with XNAT Desktop Client 3.1.0 or 3.0.0 . 

When we try to upload images, or even before that Screen Shot 2022-10-03 at 12.32.07 PM.png : 

George Kowalski

unread,
Oct 3, 2022, 3:11:43 PM10/3/22
to xnat_discussion
ok , finally got our production box  back and working with  the previous 1.8.4.1 install after restoring the app and database . 

I had to completely uninstall all the pieces of xnat  Desktop client that Parallels found in it's uninstall tool : 

Screen Shot 2022-10-03 at 2.01.17 PM.png

A reinstall of v3.1.0 and I'm back to the old version. So something in the upgrade tripped up the Desktop client into an unusable state. 

Even with this working checking the box for View Log : 

Screen Shot 2022-10-03 at 1.58.21 PM.png

give an error : 
Screen Shot 2022-10-03 at 1.52.25 PM.png

G

Rick Herrick

unread,
Oct 4, 2022, 3:14:40 PM10/4/22
to xnat_di...@googlegroups.com
Hey George, we’ve identified the proximate cause of your issue. It’s related to changes in data handling for DICOM SCP receivers. Do you have any receivers configured in your XNAT deployment? I’m pretty certain the answer is no, as we’ve been able to replicate this issue with the same error messages, but just making sure...

For reference, I created XNAT-7186 in our issue tracker. We should have a fix for this issue in a release pretty soon.

In the mean time, you can work around the problem in 1.8.5.x by configuring a new DICOM SCP receiver with any AE title and port then disabling it.

Rick Herrick
Senior Software Developer


------ Original Message ------
From "George Kowalski" <george....@gmail.com>
To "xnat_discussion" <xnat_di...@googlegroups.com>
Date 10/3/2022 2:11:43 PM
Subject Re: Re[4]: [XNAT Discussion] xnat desktop client fails after upgrade

George Kowalski

unread,
Jan 6, 2023, 9:42:34 AM1/6/23
to xnat_discussion

Thanks Ill give it a try
Reply all
Reply to author
Forward
0 new messages