Hi Jonathan, the 2nd part of the answer covering problems while using Stanbol
(1) Entityhub On Sun, Nov 18, 2012 at 5:57 AM, Jonathan Hunt <stanbol.apache....@huntdesign.co.nz> wrote: > Because I got no response to the create request, I tried again and got > "Unable to update an Entity http://huntdesign.co.nz/person/DavidBanner > becuase it does already exists and updateing existing is deactivated. You > might want to set the 'does already' parameter to TRUE in your Request" > > There are several spelling errors in that response: it does => it, exists > and => exists and, updateing existing => updating existing. What's the best > way to resolve these? > This is not as easy as it sounds as this message is created dynamically based on various situations and parameters. I have changed how the message is created to (hopefully) create proper English regardless of the setting causing it. > > Creating an entity using > curl -i -X POST -H "Content-Type:application/rdf+xml" -T david_banner.rdf > "http://localhost:8080/entityhub/entity"; > worked but returned no response. > The docs at http://localhost:8080/entityhub/entity indicate a 201 with the id > of the entity will be returned. calling this on my machine returned curl -i -X POST -H "Content-Type:application/rdf+xml" -T davidbanner-foaf.rdf "http://localhost:8080/entityhub/entity"; HTTP/1.1 100 Continue HTTP/1.1 201 Created Location: http://localhost:8080/entityhub/entity?id=http://huntdesign.co.nz/person/DavidBanner Content-Length: 0 Server: Jetty(6.1.x) > Attempting to retrieve the entity caused a 500 error > curl -X GET > "http://localhost:8080/entityhub/entity?id=http://huntdesign.co.nz/person/DavidBanner"; > returned, in part > "Error 500 Unknown prefix foaf (parsed from field foaf:schoolHomepage)!" > > curl -X DELETE > "http://localhost:8080/entityhub/entity?id=http://huntdesign.co.nz/person/DavidBanner"; > returns no response. also curl -X GET "http://localhost:8080/entityhub/entity?id=http://huntdesign.co.nz/person/DavidBanner"; worked as expected. However the Error message you received is interesting as it indicated that the namespace prefix document of the SolrYard is corrupted - a very bad thing that should never happen and needs definitely to be fixed! To validate if this causes your problem please make this request directly on the SolrCore used by the Entityhub http://localhost:8080/solr/default/entityhub/select?q=uri:urn\:eu.iksproject\:rick.yard.solr\:config.namespacePrefixConfig in this document you should find the {prefix} -> {uri} mappings defined as follows <arr name="_config/{prefix}"><str>{uri}</str></arr> and as the entity you uploaded to the Entityhub used the foaf namespace this file should contain the value <arr name="_config/foaf"><str>http://xmlns.com/foaf/0.1/</str></arr> If this is not the case, than it would explain the error message you are experiencing. If you are able to replicate this, than it would be extremely helpful if you could provide DEBUG level logging of those two requests. For that you need to start Stanbol with the "-l DEBUG" parameter (Please also empty the log file after startup). You can find the log file under "{stanbol-working-dir}/stanbol/logs/error.log" - - - (2) dbpedia Referenced Site and dbpediaLinking Engine > Also the dbpediaLinking engine is not available. The only way how that can happen is if the "NamedEntityTaggingEngine" is unsatisfied. You can check for the reason under http://localhost:8090/system/console/components searching for a NamedEntityTaggingEngine with the state "unsatisfied" and than clicking on this component. If the detailed information do not show any unsatisfied dependencies, than the reason was an Exception during activation of the NamedEntityTaggingEngine should be logged in the "{stanbol-working-dir}/stanbol/logs/error.log" file. > dbpediaLinking is enabled in this build, but when I try to submit content to > the enhancer, I get > "org.apache.stanbol.enhancer.servicesapi.ChainException: Enhancement Chain > failed because of required Engine 'dbpediaLinking' failed with Message: > Unable to process ContentItem > '<urn:content-item-sha1-37c8a8244041cf6113d4ee04b3a04d0a014f6e10>' with > Enhancement Engine 'dbpediaLinking' because the engine was unable to process > the content (Engine class: > org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine)(Reason: > Unable to initialize the Cache with Yard dbpediaIndex! This is usually > caused by Errors while reading the Cache Configuration from the Yard.)!" This is caused of the initialization of the dbpedia ReferencedSite is not yet completed or failed. As initialization of the small dbpedia index (included in the launcher) usually only takes some seconds it is more likely that some error occurred. You can force a re-initialisation of the dbpedia sites by stopping/starting the "org.apache.stanbol.data.sites.dbpedia" bundle (e.g. via the Felix Webconsole under http://localhost:8080/system/console/bundles). If this does not solve your issue it makes it at lease easier to find the reason by looking at the loggings during the startup. Additional information are also available in a file called "dbpedia.solrindex.ref" (best use find to search for the file as it is hard to explain the where it is located). the file is a normal text file with the current state of the site. If the State is Error it should also contain the exception that caused the initialization to fail. best Rupert -- | Rupert Westenthaler rupert.westentha...@gmail.com | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
