URI references data outside of the project:/storage/archive/YYY/arc001/XXX/SCANS/1/DICOM/scan_1_catalog.xml

[Torkil Svensgaard]

Hi

We just upgraded an older XNAT installation to 1.6.5 and are now facing this error when trying to archive from the prearchive. Any ideas where to look?

Thanks,

Torkil

[Torkil Svensgaard]

On Monday, February 29, 2016 at 2:40:33 PM UTC+1, Torkil Svensgaard wrote:

We just upgraded an older XNAT installation to 1.6.5 and are now facing this error when trying to archive from the prearchive. Any ideas where to look?

Archive paths in the database are fine, and permissions for the archive folder(s) also look fine (and are unchanged).

Any suggestions on where to look will be much appreciated, as this system is in production and we would very much like to avoid having to roll back.

Thanks,

Torkil

[Herrick, Rick]

Hi Torkil,

Have you changed the location of your prearchive or archive folders as part of the upgrade by any chance? Do you see any other messages that occur in the logs when you try this operation?

I think a good way to start diagnosing this would be to take one of the sessions in the prearchive, get a full listing of all of the files in the session, then zip up all of the non-DICOM files there, so something like:

find . -type f > sessionfiles.txt

zip -r session.zip $(find . ! -name *.dcm)

Let’s start with that and go from there.

-- 

Rick Herrick

Sr. Programmer/Analyst

Neuroinformatics Research Group

Washington University School of Medicine

(314) 740-5961

--
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 post to this group, send email to xnat_di...@googlegroups.com.
Visit this group at https://groups.google.com/group/xnat_discussion.
For more options, visit https://groups.google.com/d/optout.

 

---

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.

[Torkil Svensgaard]

Hi

I think we solved it by changing the Apache proxy configuration, though we are not quite sure why it made a difference for archiving. 

We haven't changed the location for neither archive nor prearchive and there was no other error in the logs but the one in the subject.

Thanks,

Torkil

[Herrick, Rick]

That is really strange. What did you do to the proxy configuration? The only thing I could think of in there is if it did some kind of translation of the application context path (i.e. everything after the server name), but then it seems like that would affect everything, not just one operation.

[Torkil Svensgaard]

We had a double proxypass configured initially, like apache(:80) -->
apache:80 on the xnat box -> tomcat:8009, which we changed to just
apache(:80) --> tomcat:8009.

Mvh.

Torkil

On 03/01/2016 03:33 PM, Herrick, Rick wrote:
> That is really strange. What did you do to the proxy configuration? The
> only thing I could think of in there is if it did some kind of
> translation of the application context path (i.e. everything after the
> server name), but then it seems like that would affect everything, not
> just one operation.
>

> *From:*xnat_di...@googlegroups.com
> [mailto:xnat_di...@googlegroups.com] *On Behalf Of *Torkil Svensgaard
> *Sent:* Tuesday, March 1, 2016 8:26 AM
> *To:* xnat_discussion <xnat_di...@googlegroups.com>
> *Cc:* rub...@drcmr.dk
> *Subject:* Re: [XNAT Discussion] Re: URI references data outside of the

> project:/storage/archive/YYY/arc001/XXX/SCANS/1/DICOM/scan_1_catalog.xml
>
> Hi
>
> I think we solved it by changing the Apache proxy configuration, though
> we are not quite sure why it made a difference for archiving.
>
> We haven't changed the location for neither archive nor prearchive and
> there was no other error in the logs but the one in the subject.
>
> Thanks,
>
> Torkil
>
> On Monday, February 29, 2016 at 4:01:34 PM UTC+1, Rick Herrick wrote:
>
> Hi Torkil,
>
> Have you changed the location of your prearchive or archive folders
> as part of the upgrade by any chance? Do you see any other messages
> that occur in the logs when you try this operation?
>
> I think a good way to start diagnosing this would be to take one of
> the sessions in the prearchive, get a full listing of all of the
> files in the session, then zip up all of the non-DICOM files there,
> so something like:
>
> find . -type f > sessionfiles.txt
>
> zip -r session.zip $(find . ! -name *.dcm)
>
> Let’s start with that and go from there.
>
> --
>

> *Rick Herrick*

>
> Sr. Programmer/Analyst
>
> Neuroinformatics Research Group
>
> Washington University School of Medicine
>

> _(314) 740-5961_
>
> *From: *"xnat_di...@googlegroups.com <javascript:>"
> <xnat_di...@googlegroups.com <javascript:>> on behalf of Torkil
> Svensgaard <tor...@svensgaard.org <javascript:>>
> *Reply-To: *"xnat_di...@googlegroups.com <javascript:>"
> <xnat_di...@googlegroups.com <javascript:>>
> *Date: *Monday, February 29, 2016 at 8:44 AM
> *To: *"xnat_di...@googlegroups.com <javascript:>"
> <xnat_di...@googlegroups.com <javascript:>>
> *Cc: *"rub...@drcmr.dk <javascript:>" <rub...@drcmr.dk <javascript:>>
> *Subject: *[XNAT Discussion] Re: URI references data outside of the

> project:/storage/archive/YYY/arc001/XXX/SCANS/1/DICOM/scan_1_catalog.xml
>
>
>
> On Monday, February 29, 2016 at 2:40:33 PM UTC+1, Torkil Svensgaard
> wrote:
>
> We just upgraded an older XNAT installation to 1.6.5 and are now
> facing this error when trying to archive from the prearchive.
> Any ideas where to look?
>
> Archive paths in the database are fine, and permissions for the
> archive folder(s) also look fine (and are unchanged).
>
> Any suggestions on where to look will be much appreciated, as this
> system is in production and we would very much like to avoid having
> to roll back.
>
> Thanks,
>
> Torkil
>
> --
> 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 <javascript:>.

> To post to this group, send email to xnat_di...@googlegroups.com

> <javascript:>.

> Visit this group at https://groups.google.com/group/xnat_discussion.
> For more options, visit https://groups.google.com/d/optout.
>

> ------------------------------------------------------------------------

>
> 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.
>
> --
> 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

> <mailto:xnat_discussi...@googlegroups.com>.

> To post to this group, send email to xnat_di...@googlegroups.com

> <mailto:xnat_di...@googlegroups.com>.

> Visit this group at https://groups.google.com/group/xnat_discussion.
> For more options, visit https://groups.google.com/d/optout.
>

> ------------------------------------------------------------------------

>
> 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.
>
> --

> You received this message because you are subscribed to a topic in the
> Google Groups "xnat_discussion" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/xnat_discussion/yOxUx1Ba_nw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> xnat_discussi...@googlegroups.com
> <mailto:xnat_discussi...@googlegroups.com>.

> To post to this group, send email to xnat_di...@googlegroups.com

> <mailto:xnat_di...@googlegroups.com>.

[Herrick, Rick]

Just as a note, I’ve switched from using Apache HTTPD to nginx on any of the configurations I set up. The latest full VM images we released and the Vagrant project we created for the 1.6.5 release all use nginx rather than Apache. The configuration is much much simpler, which can help avoid problems like the one you ran into here!


--
Rick Herrick

Sr. Programmer/Analyst
Neuroinformatics Research Group
Washington University School of Medicine

(314) 362-1882

>To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
>To post to this group, send email to xnat_di...@googlegroups.com.

>Visit this group at https://groups.google.com/group/xnat_discussion.
>For more options, visit https://groups.google.com/d/optout.

________________________________