I just tested the setup script, and didn't encounter a problem here. It seems like this may be a problem which is on your local system.
Please confirm that there is not a firewall blocking access to the internet from the installation machine. These seems like a possible firewall issue.
The commons jar should have been available at the first link that Maven tried:
http://repo1.maven.org/maven/commons-jelly/jars/commons-jelly-tags-xml-20030211.142705.jar
Your output says the connection timed out. However, the URL works fine for me. Try visiting the link from an internet browser on the installation machine. If it works through that, but not from the install script then this is probably a firewall issue.
Tim
Glad to hear you've made some progress. The jars you are missing are actually already included in the release. So, you don't need to go find them.
I can directly give you the rest of the files you need. I'll send them directly to your virend...@gmail.com account.
Tim Olsen
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra
The message:
Directory /home/xnat/$ /home/xnat/plugin-resources/repository does not exist. Attempting to create.
Doesn't make since. The jars XNAT is looking for are distributed with xnat. They are located in xnat/plugin-resources/repository. For example, the xdat-1.jar file is in xnat/plugin-resources/repository/xdat/xdat-1.jar.
Please confirm that the repository is there (i.e. /home/xnat/plugin-resources/repository).
After some consultation here, we think the problem may be related to the '/home/xnat$ ' which is prepended to the '/home/xnat/plugin-resources/repository' path in the message above. It seems like this path is getting confused somehow.
Unfortunately, we have never seen this behavior before, so we may not be able to give a quick answer.
Did you try adding the additional jars I sent to a fresh XNAT install? Or did you use the installation which had previously had problems? I would try deleting the old install and downloading a fresh copy... if you haven't already tried that. But, this is more of a guess.
What operating system are you running?
Anyone else have any ideas?
Tim
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra
Sent: Sunday, January 27, 2008 2:31 AM
To: xnat_discussion
Subject: Re: Installation trouble due to commons-jelly-tags-interaction-20030211.143817.jar
Did you try a fresh XNAT install? Perhaps, you could try installing it in a different location. That might expose what is going wrong.
Tim
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra
Sent: Tuesday, January 29, 2008 9:14 AM
To: xnat_discussion
Subject: Re: Installation trouble due to commons-jelly-tags-interaction-20030211.143817.jar
Your build.properties looks fine. You shouldn't need to have modified the project.properties file (we never touch it in our installs). However, the modifications you made seem fine.
Unfortunately, I'm running out of ideas.
Maven is unable to find the jars which are included in the xnat/plugin-resources/repository folder. This has never happened on any of our other installations.
Maven only tries to download jars from the internet, if it can't find the jars on its local file system. So the problem isn't that it is trying to access the internet. The problem is that it can't find the jars which are sitting a few directories away.
One last thing to try would be to copy the contents of xnat/plugin-resources/repository into ~/.maven/repository. Maybe Maven would be able to find them there. However, that would not identify the problem here (which may cause problems elsewhere).
Otherwise, perhaps you can try installing on a different machine. I just tested the current released version on one of our machines, and everything appeared fine.
Downloaded http://www.xnat.org/xnat_1_3_3.zip
Unzip xnat_1_3_3.zip
Cd xnat
Modify build.properties
./bin/setup.sh
Make sure that all of the steps are done by the same OS user.
Tim
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra Maloo
Sent: Wednesday, January 30, 2008 6:07 AM
To: xnat_discussion
Subject: Re: Installation trouble due to commons-jelly-tags-interaction-20030211.143817.jar
Mohana, when you get a chance can you post the solution, to give the thread some resolution.
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra Maloo
Sent: Friday, February 01, 2008 4:19 PM
To: xnat_discussion
Subject: Re: Installation trouble due to commons-jelly-tags-interaction-20030211.143817.jar
- Kevin
________________________________________
From: xnat_di...@googlegroups.com [xnat_di...@googlegroups.com] On Behalf Of Virendra Maloo [virendr...@wipro.com]
Sent: Monday, March 10, 2008 7:17 AM
To: xnat_discussion
Subject: Re: Installation trouble due to commons-jelly-tags-interaction-20030211.143817.jar
Is it like we can run the following command only once while installing
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra Maloo
Sent: Monday, March 10, 2008 7:18 AM
To: xnat_discussion
Subject: Re: Installation trouble due to commons-jelly-tags-interaction-20030211.143817.jar
This is the expected behavior. The ID field in the subject xml is the unique identifier for the subject. When you restore a document with the same ID value, this is assumed to be a modification of the previously stored subject. So, any changes would be stored to the same subject record. This is also the case with experimentData/ID.
Each of your subjects should have a different (unique) subject id. If you are storing data through the web interface (which is the most common way), this will be handled for you. If you are building xml docs yourself, then you will need to make sure the ID value is different for each one (otherwise you will overwrite the previous one, as you discovered).
I hope this helps.
Tim
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra Maloo
Sent: Tuesday, March 11, 2008 6:28 AM
To: xnat_discussion
Subject: Re: Installation trouble due to commons-jelly-tags-interaction-20030211.143817.jar
This is actually a problem with the format of the xml you modified. If you add the xml namespace declarations in your root element, then this problem should go away.
xmlns:xnat="http://nrg.wustl.edu/xnat" xmlns:prov="http://www.nbirn.net/prov" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
It would look something like this...
<xnat:MRSession xmlns:xnat="http://nrg.wustl.edu/xnat" xmlns:prov="http://www.nbirn.net/prov" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ID="XNAT002_MR1">
....
</xnat:MRSession>
Tim
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra Maloo
>But I remember it took less time when ran during installation, and now
>it takes almost 6-7 seconds to store(insert) a record.
>Why is this happening?
Are you re-storing the same document (possible with a few changes)? If so, the second store will be slower than the first. This is because it will need to query each table to see what has changed.
Also, a large amount of the execution time here is the initialization of XNAT. This can be prevented by using web services. Normally, if you use the StoreXML with the -project attribute (and the xdat.url in build.properties is set properly), the tool will automatically use the web services. Otherwise, a set of scripts for using the web services is available at http://www.xnat.org/tools.html#client.
>Imagine a situation, where we have to insert 100's of records, In that
>case, the system will fail..
We do this, and the system doesn't fail. Generally, the slower stores are caused by large documents. Small documents store relatively quickly. Large documents are usually the result of image analysis. Speed generally isn't an issue during image analysis because most steps in the analysis take much longer then 6-7 seconds.
If you are able to use the web services, this should save on your cpu time.
> StoreXML -project xnat -dir sample_data/ xml-base -r true -u admin -p admin -allowDataDeletion true
This command looks proper, except there is a space between sample_data/ and xml-base. If that is there in your command, then it could cause the error you are seeing.
Hope this helps,
Tim Olsen
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra Maloo
Sent: Wednesday, March 12, 2008 9:51 AM
To: xnat_discussion
Subject: Re: Installation trouble due to commons-jelly-tags-interaction-20030211.143817.jar
I tried storing data from 'storexml', (calling it from script).
Try reorganizing your options, so that the -allowDataDeletion tag comes before the -dir tag. In practice the tag order shouldn't matter. But, this will test to see if something else in your command syntax is causing the issue.
Tim
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra Maloo
Sent: Thursday, March 13, 2008 1:30 AM
To: xnat_discussion
Subject: Re: Installation trouble due to commons-jelly-tags-interaction-20030211.143817.jar
Virendra,
The StoreXML script stores XML documents into the database. After storing the documents, the MR records should show up in the MR browse and have subsequent MR Reports.
The 'bin/update.sh' script is used for updating the XNAT installation. It has nothing to do with uploading data.
Is your problem that the MR records aren't showing up in the MR listings/reports? Or is your problem that the data files associated with those sessions aren't showing up in the MR report?
If you want to be able to view the image data through the website, you'll need to follow the directions within the documentation:
Tim Olsen
-----Original Message-----
From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Virendra Maloo
Sent: Friday, March 14, 2008 1:39 AM
To: xnat_discussion
Subject: Re: Installation trouble due to commons-jelly-tags-interaction-20030211.143817.jar
This might be one useful change in the XNAT website.