Hi K, Which version of OODT are you using? Can you set logging to debug, restart your filemanager instance and tail the log for any more clues. If you get any more clues then post them here. Also, if you are running off of master branch then this is an excellent opportunity for us to improve the error message, printing the product ID as oppose the opaque object... the later is relatively useless.
On Wed, Mar 23, 2016 at 6:48 PM, Konstantinos Mavrommatis < kmavromma...@celgene.com> wrote: > Hi, > I have setup oodt using RADiX. > > When I use the default Lucene catalog factory I manage to ingest a file > with no problem: > # ./filemgr-client --url http://localhost:9000 --operation > --ingestProduct --productName test.txt --productStructure Flat > --productTypeName GenericFile --metadataFile file:///tmp/test.txt.met > --refs file:///tmp/test.txt > ingestProduct: Result: afda62a1-f15f-11e5-a7d4-7d8cde2ab6dd > > > Then I install solr 5.5/jetty and created a new core named oodt > #solr create_core -c oodt > I run the example command in solr documentation and verified that this > instance is able to index documents. I can also access solr dashboard at > the following URL: http://localhost:8983/solr > I also modified the filemgr.properties file with the following lines: > > filemgr.catalog.factory=org.apache.oodt.cas.filemgr.catalog.solr.SolrCatalogFactory > org.apache.oodt.cas.filemgr.catalog.solr.url=http://localhost:8983/solr > > I have tried to run this command with and without the schema.xml in the > core directory. In both cases I get the error: > > But now when I try to ingest a file I get: > # ./filemgr-client --url http://localhost:9000 --operation > --ingestProduct --productName test.txt --productStructure Flat > --productTypeName GenericFile --metadataFile file:///tmp/test.txt.met > --refs file:///tmp/test.txt > ERROR: Failed to ingest product 'test.txt' : java.lang.Exception: > org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Error > ingesting product [org.apache.oodt.cas.filemgr.structs.Product@5eebbe] : > HTTP method failed: HTTP/1.1 404 Not Found > > Any ideas what is going on? > > Thanks > K > > ********************************************************* > THIS ELECTRONIC MAIL MESSAGE AND ANY ATTACHMENT IS > CONFIDENTIAL AND MAY CONTAIN LEGALLY PRIVILEGED > INFORMATION INTENDED ONLY FOR THE USE OF THE INDIVIDUAL > OR INDIVIDUALS NAMED ABOVE. > If the reader is not the intended recipient, or the > employee or agent responsible to deliver it to the > intended recipient, you are hereby notified that any > dissemination, distribution or copying of this > communication is strictly prohibited. If you have > received this communication in error, please reply to the > sender to notify us of the error and delete the original > message. Thank You. > -- *Lewis*
