From users-return-19541-archive-asf-public=cust-asf.ponee.io@jena.apache.org Thu Mar 7 20:47:36 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id A8864180654 for ; Thu, 7 Mar 2019 21:47:35 +0100 (CET) Received: (qmail 9017 invoked by uid 500); 7 Mar 2019 20:47:29 -0000 Mailing-List: contact users-help@jena.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jena.apache.org Delivered-To: mailing list users@jena.apache.org Received: (qmail 8990 invoked by uid 99); 7 Mar 2019 20:47:29 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Mar 2019 20:47:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A7C1F185456 for ; Thu, 7 Mar 2019 20:47:28 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.701 X-Spam-Level: X-Spam-Status: No, score=0.701 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id EflC_uDwy-ch for ; Thu, 7 Mar 2019 20:47:26 +0000 (UTC) Received: from tmailer.gwdg.de (tmailer.gwdg.de [134.76.10.23]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 0620861122 for ; Thu, 7 Mar 2019 20:47:26 +0000 (UTC) Received: from excmbx-02.um.gwdg.de ([134.76.9.217] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.90_1) (envelope-from ) id 1h1zvJ-0004nn-Jy for users@jena.apache.org; Thu, 07 Mar 2019 21:47:25 +0100 Received: from EXCMBX-03.um.gwdg.de (134.76.9.218) by EXCMBX-02.um.gwdg.de (134.76.9.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.1713.5; Thu, 7 Mar 2019 21:47:25 +0100 Received: from EXCMBX-03.um.gwdg.de ([fe80::c022:aee6:d671:12de]) by EXCMBX-03.um.gwdg.de ([fe80::c022:aee6:d671:12de%20]) with mapi id 15.01.1713.004; Thu, 7 Mar 2019 21:47:25 +0100 From: "Walker, Andreas" To: "users@jena.apache.org" Subject: AW: AW: Error 500: No conversion to a Node: Thread-Topic: AW: Error 500: No conversion to a Node: Thread-Index: AQHU0/908PQn1eSTiUej1x7OcopudqX//nCtgACM4gCAABjnDA== Date: Thu, 7 Mar 2019 20:47:25 +0000 Message-ID: <378eee0f25bc46138882034cff7e2f8b@sub.uni-goettingen.de> References: <4793f7d1a7874a28b9af83f6499e3295@sub.uni-goettingen.de> ,<8f0d19e7-00ee-0b57-e03f-640bb6cd748e@apache.org> In-Reply-To: <8f0d19e7-00ee-0b57-e03f-640bb6cd748e@apache.org> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [84.140.104.252] Content-Type: multipart/alternative; boundary="_000_378eee0f25bc46138882034cff7e2f8bsubunigoettingende_" MIME-Version: 1.0 X-Virus-Scanned: (clean) by clamav --_000_378eee0f25bc46138882034cff7e2f8bsubunigoettingende_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Andy, I am running Version 3.10.0. The problem with reloading the database is the= regular (multiple times a day) recurrence of the problem, so if there are = any strategies to avoid it, I'd appreciate any advice. Best, Andreas ________________________________ Von: Andy Seaborne Gesendet: Donnerstag, 7. M=E4rz 2019 21:12 An: users@jena.apache.org Betreff: Re: AW: Error 500: No conversion to a Node: Hi Andreas - which version are you running? It does not look like the corruption problem, which is now fixed. The best thing to do is reload the database again. Whatever terms were messed up are permanently damaged I'm afraid. Andy On 07/03/2019 10:49, Walker, Andreas wrote: > Dear all, > > > as a quick follow-up which might be helpful in identifying the error; I c= an currently run a SPARQL query (just listing any triples) with LIMIT 80, b= ut no higher, before I run into the error, so it seems like there might ind= eed be a particular part of the database that is corrupted. > > > Best, > > Andreas > > ________________________________ > Von: Walker, Andreas > Gesendet: Mittwoch, 6. M=E4rz 2019 10:42:32 > An: users@jena.apache.org > Betreff: Error 500: No conversion to a Node: > > Dear all, > > > from time to time, my Fuseki server starts throwing the following error m= essage on any SPARQL query I pose to one of my graphs: > > > "Error 500: No conversion to a Node: " > > > Unfortunately, I couldn't find any explanation of this error message, bey= ond a discussion of a corrupted TDB2 database. > > > (https://users.jena.apache.narkive.com/LF4XE801/corrupted-tdb2-database)<= https://users.jena.apache.narkive.com/LF4XE801/corrupted-tdb2-database> > > > Once this happens, the only thing I could do so far is to drop the entire= afflicted graph and rebuild it, but of course that isn't going to be a via= ble solution in the long term. > > > The only way I interact with Fuseki is by starting and stopping it, query= ing it via the SPARQL endpoint (and sometimes through the web interface, e.= g. when troubleshooting my application), and uploading new triples (as turt= le files) via the web interface. I haven't been able to find a pattern in w= hen the error appears so far. > > > Any insights into why this error appears, and what to do in order to avoi= d it? I'd appreciate any help. > > > Best, > > Andreas > --_000_378eee0f25bc46138882034cff7e2f8bsubunigoettingende_--