XNAT Desktop Client file size error

[Dave Cash]

Hi XNAT-

I tried using the NAT Desktop Client to download a chunk of data (about 7GB) from one of our servers running 1.8.2. It worked for a while downloading about a GB or so and then timed out. Since then, every time I have tried to re-start it or start a new download through the client, I get the following  error in a dialog box.

Uncaught Exception:

RangeError [ERR_FS_FILE_TOO_LARGE]: File size (2699075397) is greater than possible Buffer: 2147483647 bytes

    at FSReqWrap.readFileAfterStat [as oncomplete] (fs.js:383:11)

I am running the client from a Mac laptop (OSX 10.15.7), and this message appears after I have selected a new smaller catalog to download, quit the Client and opened it up again, and even after restart. Is there a temporary directory or file that this message is referring to that needs to be removed?

Many thanks,
Dave

[Herrick, Rick]

You’re running into an issue with node itself, where the largest possible buffer size is 2GB (2,147,483,647). I’ve definitely downloaded data that ran well over that limit before, but the desktop client actually downloads by resource catalog. That means each resource–for example, the DICOM or NIFTI for a scan or each different resource for a subject, etc.–is downloaded as a zip. I can see this happening if one of those resources zipped up exceeds the buffer size on its own.

 

Can you try turning on the client dev tools (Cmd-I or DevTools->Toggle DevTools) then switching to the Console view and see if you get more of a stacktrace than the truncated message below? That will tell us where in our code the error is occurring and we may be able to get the code to handle the larger size or at least fail more gracefully in the short term.

 

As far as getting rid of the apparent cached reference to the stuff that failed, there are a couple of things you can try (make sure you quit the desktop client first!).

 

First, move or delete the folder ~/Library/Saved Application State/com.xnatapp.app.savedState. When I did this, nothing changed in the state of the app when I restarted it, e.g. all of my configured servers were still available, previous upload and download operations were still visible in the Progress Monitor, etc., so it’s quite possible this also won’t affect the problem you’re seeing.

 

The next thing to try is moving the folder ~/Library/Application Support/xnat-desktop-client. This will lose all configured servers, records of previous operations, etc., but should definitely resolve the cached reference issue you’re having. Presuming that it does fix that problem, you could then shut down the desktop client, move the folder back into place (you’ll need to delete the new instance of that folder that the client will create when you restart it though), and try to find the particular file where the catalog reference is cached. The most likely location(s) seem to be a set of files named db.xxx.json, where xxx is one of downloads.hash, uploads.hash, or nedb-logger, but it’s also possible those are just logs. You can also try deleting the Cache, GPUCache, and Local Storage subfolders to see if those will clear up the issue without nuking your saved configuration.

 

Let me know what you try and what works. I can guarantee with almost 100% certainty that deleting the whole ~/Library/Application Support/xnat-desktop-client folder will fix the cached reference issue, but at the cost of your saved data!

 

-- 

Rick Herrick

XNAT Architect/Developer

Computational Imaging Laboratory

Washington University School of Medicine

 

 

From: xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of Dave Cash <david....@gmail.com>
Date: Sunday, August 15, 2021 at 2:47 PM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] XNAT Desktop Client file size error

* External Email - Caution *

--
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/e1951912-2cc9-4ba7-876a-a0f6ae31e751n%40googlegroups.com.

 

---

The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

[Dave Cash]

Hi Rick-

Apologies, I never got back to you about this. Thanks for your help. I tried a compromise where I deleted  JSON files from ~/Library/Application Support/xnat-desktop-client and all the files within ~/Library/Application Support/xnat-desktop-client/Cache, and the problem went away and I was able to download again. I didn't have any records that I needed keeping at the moment, but ta least that kept my server list in place. 

I will try nd re-create the original error by downloading a chunk of data but with the Console on and see if I get more detailed information.

Thanks for your help!

Dave

[Filipe Henriques]

Good evening, I have the same issues but i can not find the directory on my mac to empty the cache, can you help. I thank you in advance

[Herrick, Rick]

Hi Felipe, can you try opening a terminal window and typing:

 

ls ~/Library/Application\ Support/XNAT-Desktop-Client

 

Let me know what you get back from that.

 

-- 

Rick Herrick

Sr. Programmer/Analyst

Neuroinformatics Research Group

Washington University School of Medicine

Phone: +1 (314) 273-1645

To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/94ee3dd8-75fe-4e58-b620-1372f844a92bn%40googlegroups.com.