Re: NodeTableTRDF/Read exception

Before that there are few occasions of quite heavy way to handle missing graph in CLEAR GRAPH. Maybe something going on there? Jun 19 11:35:22 xxx.fi java[1047205]: [2023-06-19 11:35:22] Fuseki INFO  [34] POST http://xxx.fi/ds Jun 19 11:35:22 xxx.fi java[1047205]: [2023-06-19 11:35:22]

Re: NodeTableTRDF/Read exception

I deleted jena data folder, restarted db and started reinputting data. Still after a while I get NodeTableTRDF/Read. Any idea? On 21/03/2022 20.43, Andy Seaborne wrote: The only time I have seen anything similar to this is on Android where something other process is messing about the files.

Re: NodeTableTRDF/Read exception

Normal updates work but this comes with clear graph. On 12/05/2023 14.58, Mikael Pesonen wrote: Got this NodeTableTRDF/Read again in our production environment. I got message from admin that Jena had unusually high memory consumption and it suddenly normalized yesterday. Maybe it could be

Re: NodeTableTRDF/Read exception

Got this NodeTableTRDF/Read again in our production environment. I got message from admin that Jena had unusually high memory consumption and it suddenly normalized yesterday. Maybe it could be related to this. On 21/03/2022 20.43, Andy Seaborne wrote: The only time I have seen anything

Re: NodeTableTRDF/Read exception

We don't have that going on atleast. On 21/03/2022 20.43, Andy Seaborne wrote: The only time I have seen anything similar to this is on Android where something other process is messing about the files. TDB is not proof again other processes accessing the same files, including with shared

Re: NodeTableTRDF/Read exception

The only time I have seen anything similar to this is on Android where something other process is messing about the files. TDB is not proof again other processes accessing the same files, including with shared network drives where different computers access the same filesystem. Andy On

Re: NodeTableTRDF/Read exception

Got this again after few days of little usage after TDB2 was rebuilt from empty. Would you suggest this is hw error? No possibility that its Jena error? On 28/05/2021 17.25, Andy Seaborne wrote: On 28/05/2021 14:59, Mikael Pesonen wrote: I should try some older Jena/Fuseki version?

Re: NodeTableTRDF/Read exception

On 28/05/2021 14:59, Mikael Pesonen wrote: I should try some older Jena/Fuseki version? Yes. Also - run on different hardware. - run multiple times - look at the data and see if anything unusual is in it. etc etc On 28/05/2021 16.49, Andy Seaborne wrote: On 28/05/2021 14:03,

Re: NodeTableTRDF/Read exception

I should try some older Jena/Fuseki version? On 28/05/2021 16.49, Andy Seaborne wrote: On 28/05/2021 14:03, Mikael Pesonen wrote: No this is the fresh db, started from empty today. And plenty of disk space. So it's repeatble. With no Minimal, Verifiable, Complete Example, it'll have

Re: NodeTableTRDF/Read exception

On 28/05/2021 14:03, Mikael Pesonen wrote: No this is the fresh db, started from empty today. And plenty of disk space. So it's repeatble. With no Minimal, Verifiable, Complete Example, it'll have to be an on-site investigation. Try different versions. Andy On 28/05/2021 15.58,

Re: NodeTableTRDF/Read exception

No this is the fresh db, started from empty today. And plenty of disk space. On 28/05/2021 15.58, Andy Seaborne wrote: Why are you adding data to a broken database? On 28/05/2021 12:02, Mikael Pesonen wrote: Actually now it happened again. Same size, about 80MB of turtle, imported without

Re: NodeTableTRDF/Read exception

Why are you adding data to a broken database? On 28/05/2021 12:02, Mikael Pesonen wrote: Actually now it happened again. Same size, about 80MB of turtle, imported without warnings this time, but reading the graph fails with this exception. 13:59:39 WARN  Fuseki  :: [44] RC = 500 :

Re: NodeTableTRDF/Read exception

Actually now it happened again. Same size, about 80MB of turtle, imported without warnings this time, but reading the graph fails with this exception. 13:59:39 WARN  Fuseki  :: [44] RC = 500 : NodeTableTRDF/Read org.apache.jena.tdb2.TDBException: NodeTableTRDF/Read     at

Re: NodeTableTRDF/Read exception

See the thread following from Harri's message "TDBException: NodeTableTRDF/Read (vol. 2)" Andy On 27/05/2021 15:56, Mikael Pesonen wrote: Tried with the invalid data on fresh db and it didn't cause this exception. So root cause happened probably way earlier and is unknown. On

Re: NodeTableTRDF/Read exception

Tried with the invalid data on fresh db and it didn't cause this exception. So root cause happened probably way earlier and is unknown. On 20/05/2021 14.10, Andy Seaborne wrote: Please can we have a complete, minimal example. On 19/05/2021 11:12, Mikael Pesonen wrote: More info on this.

Re: NodeTableTRDF/Read exception

Unfortunately the data is confidential. I can try to generate the same errors on reseted db if same thing happens. On 20/05/2021 14.10, Andy Seaborne wrote: Please can we have a complete, minimal example. On 19/05/2021 11:12, Mikael Pesonen wrote: More info on this. When the causes of

Re: NodeTableTRDF/Read exception

Please can we have a complete, minimal example. On 19/05/2021 11:12, Mikael Pesonen wrote: More info on this. When the causes of the two warnings are fixed, same data is imported correctly and everything works. So, when there are "too many" WARN level errors in importing data, the graph

Re: NodeTableTRDF/Read exception

More info on this. When the causes of the two warnings are fixed, same data is imported correctly and everything works. So, when there are "too many" WARN level errors in importing data, the graph becomes corrupted. On 18/05/2021 18.02, Andy Seaborne wrote: On 18/05/2021 13:03, Mikael

Re: NodeTableTRDF/Read exception

This error occurs with all actions related to same graph. So I can't for example drop or clear the graph anymore. Actions on other graphs work as usual. On 18/05/2021 18.02, Andy Seaborne wrote: On 18/05/2021 13:03, Mikael Pesonen wrote: This occurred again on another server. There were

Re: NodeTableTRDF/Read exception

On 18/05/2021 13:03, Mikael Pesonen wrote: This occurred again on another server. There were no errors before this, but many warnings on invalid data, if that is related. Now we get this error on all operations. 12:57:42 WARN  Fuseki  :: [line: 149803, col: 81] Bad IRI:

Re: NodeTableTRDF/Read exception

This occurred again on another server. There were no errors before this, but many warnings on invalid data, if that is related. Now we get this error on all operations. 12:57:42 WARN  Fuseki  :: [line: 149803, col: 81] Bad IRI: Code: 4/UNWISE_CHARACTER in PATH:

Re: NodeTableTRDF/Read exception

Server just ran out of disk space, but it's since been on low usage so could have happened few months ago. And logs are only for 1 month... On 27/04/2021 13.22, Andy Seaborne wrote: On 27/04/2021 09:59, Mikael Pesonen wrote: That's our guess too, but would be nice to have some idea

Re: NodeTableTRDF/Read exception

On 27/04/2021 09:59, Mikael Pesonen wrote: That's our guess too, but would be nice to have some idea where to look for the cause. Does Jena/Fuseki handle disk full situations without corruption? It should do (the transaction aborts) which is why I was asking. Bulk loading, other than

Re: NodeTableTRDF/Read exception

That's our guess too, but would be nice to have some idea where to look for the cause. Does Jena/Fuseki handle disk full situations without corruption? On 27/04/2021 11.56, Andy Seaborne wrote: In the original message, There was shortage of disk space, hope the db is not corrupted.

Re: NodeTableTRDF/Read exception

In the original message, > There was shortage of disk space, hope the db is not corrupted. What happened? This is the only thing you've mentioned that relates to update. Everything else is "read" and the fault occurred at an earlier time or its an environmental factor (one mentioned file

Re: NodeTableTRDF/Read exception

After that comes NodeTableTRDF/Read exception. On 23/04/2021 21.11, Andy Seaborne wrote: On 23/04/2021 14:57, Mikael Pesonen wrote: Sorry here is the entire log It's a different log. [2] is now [5] Apr 23 16:23:49 solid java[1153]: [2021-04-23 16:23:49] Fuseki INFO [5] POST http

Re: NodeTableTRDF/Read exception

; PWD=/home/**; USER=root ; COMMAND=/bin/cat /lib/systemd/system/apache-jena-fuseki.service Apr 23 15:31:44 solid sudo[22157]:   **: TTY=pts/1 ; PWD=/home/**; USER=root ; COMMAND=/bin/cat /lib/systemd/system/apache-jena-fuseki.service After that comes NodeTableTRDF/Read exception. On 23/04

Re: NodeTableTRDF/Read exception

/systemd/system/apache-jena-fuseki.service After that comes NodeTableTRDF/Read exception. On 23/04/2021 21.11, Andy Seaborne wrote: On 23/04/2021 14:57, Mikael Pesonen wrote: Sorry here is the entire log It's a different log. [2] is now [5] Apr 23 16:23:49 solid java[1153]: [2021-04-23 16

Re: NodeTableTRDF/Read exception

=/home/**; USER=root ; COMMAND=/bin/cat /lib/systemd/system/apache-jena-fuseki.service Apr 23 15:31:44 solid sudo[22157]:   **: TTY=pts/1 ; PWD=/home/**; USER=root ; COMMAND=/bin/cat /lib/systemd/system/apache-jena-fuseki.service After that comes NodeTableTRDF/Read exception. On 23/04/2021 21.11

Re: NodeTableTRDF/Read exception

On 23/04/2021 14:57, Mikael Pesonen wrote: Sorry here is the entire log It's a different log. [2] is now [5] Apr 23 16:23:49 solid java[1153]: [2021-04-23 16:23:49] Fuseki INFO  [5] POST http://nimisampo.lingsoft.fi:3030/ds Apr 23 16:23:49 solid java[1153]: [2021-04-23 16:23:49] Fuseki

Re: NodeTableTRDF/Read exception

Sorry here is the entire log Apr 23 16:23:49 solid java[1153]: [2021-04-23 16:23:49] Fuseki INFO  [5] POST http://nimisampo.lingsoft.fi:3030/ds Apr 23 16:23:49 solid java[1153]: [2021-04-23 16:23:49] Fuseki INFO  [6] POST http://nimisampo.lingsoft.fi:3030/ds Apr 23 16:23:49 solid java[1153]:

Re: NodeTableTRDF/Read exception

On 23/04/2021 13:33, Mikael Pesonen wrote: Hi, we get this exception now when starting Jena and it's not loading any data. I have no idea what is changed on the server. Apr 23 13:51:09 solid java[6846]: [2021-04-23 13:51:09] Fuseki WARN  [2] RC = 500 : NodeTableTRDF/Read Apr 23 13:51:09

NodeTableTRDF/Read exception

Hi, we get this exception now when starting Jena and it's not loading any data. I have no idea what is changed on the server. Apr 23 13:51:09 solid java[6846]: [2021-04-23 13:51:09] Fuseki WARN  [2] RC = 500 : NodeTableTRDF/Read Apr 23 13:51:09 solid java[6846]: