Database issues after installing cnda-freesurfer-common-1.0.5 plugin

[Alex Bartnik]

Hello,

I recently installed the cnda-freesurfer-common-1.0.5.jar plugin to automatically generate assessors for my freesurfer data, which worked perfectly. However, I've been encountering several strange issues ever since, some minor and some severe. I've removed the plugin but the issues still remain.

The biggest issue I've noticed is that xnat_mrsessiondata_history in the postgres DB is no longer updated when I archive sessions. I use xnatpy a lot for automating my XNAT workflow, which does a lot of calls to grab the mrSessionData as json and needs the xnat_mrsessiondata_history row present for the session or it crashes. Strangely, the History tab on the web interface for a session does get updated, I just can't see anything in the postgres database.

On a project level, I am now getting a pop up stating "Search Validation: sxmlM:init:item.setProperty is not a function" whenever I navigate to a project's main page. Also, I can no longer access the project settings to enable/disable container commands, instead I get an error badge that says "Data for "<project name>" project not found."

I have a couple external users hosting their data in my XNAT so I'd strongly prefer not to have to start over with a new database. Is there any way I can clean up my database and restore the previous functionality?

Versions:

XNAT 1.8.2.2, build 4

PostgreSQL 12.2

[Charlie Moore]

Hello there,

As a high level comment: XNAT does not support removing data type plugins when you have instances of the data. If you remove the plugin, I could see things behaving strangely. I have a vague recollection of that "Search Validation: sxmlM:init:item.setProperty is not a function" message being traceable back to a frustrating intermittent issue where something goes wrong when starting tomcat. So, have you tried this?

1. Backup everything in case things somehow get worse.

2. Reinstall the freesurfer-common plugin.

3. Restart tomcat.

If that still doesn't work, you could give tomcat another restart just to make sure. There might be something interesting logged by XNAT while tomcat is starting as well. YMMV

Thanks,

Charlie

[Alex Bartnik]

Thanks Charlie, restarting without and again with the plugin solved the issue for about a week. I encountered the same thing again yesterday, so I restarted again and it's back to normal again. I'll keep monitoring it, maybe it's just indicative of something strange going on with my tomcat. Unfortunately I don't see much in the tomcat logs when rebooting to go off of, but I'll keep an eye out for anything.