Ooh, I see, 5.5! Sorry. not had my morning coffee yet. Yeah I tried 5.5 a
while back out of curiosity rather than a use case and it certainly didn't
work OOTB.

Tom

On Thu, Mar 24, 2016 at 7:32 AM, Tom Barber <tom.bar...@meteorite.bi> wrote:

> I appreciate its cheating, but when you build OODT with Radix did you use
> the Solr maven profile? We fixed it up in 0.12 and it seemed to be working
> fine, although I wasn't the one who tested it fully.
>
> Tom
>
> On Thu, Mar 24, 2016 at 7:15 AM, Konstantinos Mavrommatis <
> kmavromma...@celgene.com> wrote:
>
>> Hi,
>> I am using oodt v 0.12
>> Interestingly the file etc/logging.properties was not in its place
>> although this was a clean installation on a clean, newly started Ubuntu
>> 14.04 server on AWS (!!) I copied the file from the
>> oodt-src/filemgr/target/classes/etc/logging.properties and set the logging
>> level.
>> Running the same command:
>> At the end of the file there are following error lines
>>
>> INFO: Posting message:<add><doc><field
>> name="id">93addb3e-4d02-41ca-bee6-fbb321d6c890</field><field
>> name="CAS.ProductId">93addb3e-4d02-41ca-bee6-fbb321d6c890</field><field
>> name="CAS.ProductName">test.txt</field><field
>> name="CAS.ProductTypeName">GenericFile</field><field
>> name="CAS.ProductReceivedTime">2016-03-24T07:12:01Z</field><field
>> name="CAS.ProductTypeId">urn:oodt:GenericFile</field><field
>> name="CAS.ProductStructure">Flat</field><field
>> name="CAS.ProductTransferStatus">TRANSFERING</field></doc></add> to URL:
>> http://localhost:8983/solr/update
>> Mar 24, 2016 7:12:01 AM
>> org.apache.oodt.cas.filemgr.catalog.solr.SolrClient index
>> SEVERE: HTTP method failed: HTTP/1.1 404 Not Found
>> Mar 24, 2016 7:12:01 AM
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager catalogProduct
>> SEVERE: ingestProduct: CatalogException when adding Product: test.txt to
>> Catalog: Message: HTTP method failed: HTTP/1.1 404 Not Found
>> Mar 24, 2016 7:12:01 AM
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager ingestProductCore
>> SEVERE: HTTP method failed: HTTP/1.1 404 Not Found
>> Mar 24, 2016 7:12:01 AM
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient ingestProduct
>> SEVERE: Failed to ingest product [ name:test.txt] :java.lang.Exception:
>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Error
>> ingesting product [org.apache.oodt.cas.filemgr.structs.Product@60a79fbb]
>> : HTTP method failed: HTTP/1.1 404 Not Found -- rolling back ingest
>> Mar 24, 2016 7:12:01 AM
>> org.apache.oodt.cas.filemgr.catalog.solr.SolrClient delete
>> INFO: Posting message:<delete><query>id:null</query></delete> to URL:
>> http://localhost:8983/solr/update?commit=true
>> Mar 24, 2016 7:12:01 AM
>> org.apache.oodt.cas.filemgr.catalog.solr.SolrClient delete
>> SEVERE: HTTP method failed: HTTP/1.1 404 Not Found
>> Mar 24, 2016 7:12:01 AM
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager removeProduct
>> WARNING: Exception modifying product: [null]: Message: HTTP method
>> failed: HTTP/1.1 404 Not Found
>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: HTTP
>> method failed: HTTP/1.1 404 Not Found
>>         at
>> org.apache.oodt.cas.filemgr.catalog.solr.SolrClient.delete(SolrClient.java:130)
>>         at
>> org.apache.oodt.cas.filemgr.catalog.solr.SolrCatalog.removeProduct(SolrCatalog.java:165)
>>         at
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.removeProduct(XmlRpcFileManager.java:1113)
>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>         at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>         at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>         at java.lang.reflect.Method.invoke(Method.java:606)
>>         at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
>>         at
>> org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
>>         at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
>>         at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
>>         at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
>>         at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
>>         at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
>>         at java.lang.Thread.run(Thread.java:745)
>>
>> Mar 24, 2016 7:12:01 AM
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient ingestProduct
>> SEVERE: Failed to rollback ingest of product
>> [org.apache.oodt.cas.filemgr.structs.Product@2782f72b] :
>> java.lang.Exception:
>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Error
>> ingesting product [org.apache.oodt.cas.filemgr.structs.Product@60a79fbb]
>> : HTTP method failed: HTTP/1.1 404 Not Found
>> Mar 24, 2016 7:12:01 AM
>> org.apache.oodt.cas.filemgr.cli.action.IngestProductCliAction execute
>> SEVERE: java.lang.Exception:
>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Error
>> ingesting product [org.apache.oodt.cas.filemgr.structs.Product@60a79fbb]
>> : HTTP method failed: HTTP/1.1 404 Not Found
>> 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@60a79fbb]
>> : HTTP method failed: HTTP/1.1 404 Not Found-----Original Message-----
>>
>>
>>
>> From: Lewis John Mcgibbney [mailto:lewis.mcgibb...@gmail.com]
>> Sent: Wednesday, March 23, 2016 7:25 PM
>> To: dev@oodt.apache.org
>> Subject: Re: Setting up filemanager with SOLR 5.5
>>
>> 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
>> > https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A9000&d
>> > =CwIBaQ&c=CZZujK3G2KuXGEKnzq-Hrg&r=wndYZ4MLMT9l3Zb2WZv2hq2O6yvZ1Cs-T2g
>> > HY95y7ZA&m=yypXYFp0GDrsimQXj-42kCPwJnfRFvCIjjJKzPQVqSw&s=we1KbELso6G5c
>> > QKnuCw6lUZ-uHRh9J4QgzUSy_xWj1A&e=  --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:
>> > https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8983_s
>> > olr&d=CwIBaQ&c=CZZujK3G2KuXGEKnzq-Hrg&r=wndYZ4MLMT9l3Zb2WZv2hq2O6yvZ1C
>> > s-T2gHY95y7ZA&m=yypXYFp0GDrsimQXj-42kCPwJnfRFvCIjjJKzPQVqSw&s=cuARMuJC
>> > 3xzy3KYRi1OQeZ7vboagVHfSOb7cYjedhfo&e=
>> > I also modified the filemgr.properties file with the following lines:
>> >
>> > filemgr.catalog.factory=org.apache.oodt.cas.filemgr.catalog.solr.SolrC
>> > atalogFactory
>> > org.apache.oodt.cas.filemgr.catalog.solr.url=https://urldefense.proofp
>> > oint.com/v2/url?u=http-3A__localhost-3A8983_solr&d=CwIBaQ&c=CZZujK3G2K
>> > uXGEKnzq-Hrg&r=wndYZ4MLMT9l3Zb2WZv2hq2O6yvZ1Cs-T2gHY95y7ZA&m=yypXYFp0G
>> > DrsimQXj-42kCPwJnfRFvCIjjJKzPQVqSw&s=cuARMuJC3xzy3KYRi1OQeZ7vboagVHfSO
>> > b7cYjedhfo&e=
>> >
>> > 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
>> > https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A9000&d
>> > =CwIBaQ&c=CZZujK3G2KuXGEKnzq-Hrg&r=wndYZ4MLMT9l3Zb2WZv2hq2O6yvZ1Cs-T2g
>> > HY95y7ZA&m=yypXYFp0GDrsimQXj-42kCPwJnfRFvCIjjJKzPQVqSw&s=we1KbELso6G5c
>> > QKnuCw6lUZ-uHRh9J4QgzUSy_xWj1A&e=  --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*
>>
>> *********************************************************
>> 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.
>>
>
>

Reply via email to