OriginTrail / ot-node

OriginTrail Decentralized Knowledge Graph network node
https://origintrail.io
Apache License 2.0
208 stars 75 forks source link

java.lang.RuntimeException: De-serialization problem: #3354

Closed botnumberseven closed 1 month ago

botnumberseven commented 1 month ago

I see a significant amount of java.lang.RuntimeException: De-serialization problem: errors, looks like this

[2024-10-25 00:48:12] TRACE: {Operation ID: 9bb6118b-c431-4485-96b1-51f79076d002} [v1_0_0GetInitCommand] (Command ID: affed89e-51ec-4276-a8cd-57f011014da4) Error message for operation id: 498ee479-7839-4550-8905-27900d13880a, keyword: 0xb8b904c73d2fb4d8c173298a51c27fab70222c320e8bc719d555136ada4201a5f954c021257ca069939dbb5695157dc796f69678 : Received NACK response from node during v1_0_0GetInitCommand. Error message: Invalid SPARQL endpoint response from http://localhost:9999/blazegraph/namespace/public-current/sparql (HTTP status 500): SPARQL-QUERY: queryStr=ASK WHERE { GRAPH { ?s ?p ?o } } java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.RuntimeException: De-serialization problem: addr={off=1711616,len=8274} from store=blazegraph.jnl : cause=java.lang.IllegalArgumentException: Illegal ratio (0) at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122) ...

I have no idea what it is and how it affects node operation. Node is still running. Here is some logs - log_1.txt Please let me know how I can help with it.

Mihajlo-Pavlovic commented 1 month ago

Duplicate of #3344

Larsk97 commented 1 month ago

Also seeing lots of these on my nodes.

botnumberseven commented 1 month ago

@Mihajlo-Pavlovic Just to double check here. #3344 is also blazegraph related issue. But the exception is different NoSuchFileException: /root/ot-node/blazegraph.jnl vs De-serialization problem. So despite that the actual failure mechanism is the same, is that correct?

Mihajlo-Pavlovic commented 1 month ago

In both cases cause is blazegraph issue on remote node.

@u-hubar we should add check that node can't start if node has issue with blazegraph.jnl file