Open Narendra-Sadhu opened 4 years ago
I don’t see anything terribly informative in the log file. It appears to encounter a stream closed exception while trying to query the length of the file. There might be more information in older logs?
My suspicions would tend towards a possible concurrent open of the blazegraph context. Or a concurrent start and stop of the blazegraph context.
Also, I suggest verifying that the file in that location has your historical data rather than being silently created when blazegraph failed to find a file at that location.
Bryan
On Tue, Oct 13, 2020 at 23:25 Narendra-Sadhu notifications@github.com wrote:
We are using Blazegraph version 2.1.4 hosted in OpenShift server. It was working fine but suddenly it throws java.lang.RuntimeException when we are trying to access blazegraph.
WARN : WebAppContext.java:506: Failed startup of context o.e.j.w.WebAppContext@735f7ae5 {/blazegraph,jar:file:/blazegraph/blazegraph.jar!/war,STARTING}{jar:file:/blazegraph/blazegraph.jar!/war} java.lang.RuntimeException: java.lang.RuntimeException: file=/var/lib/blazegraph/eg1019.jnl
From the error log we could see exception related jnl file but file was there in right path and it was working fine previously and it also worked fine after we restarted blazegraph.
we would like know the root cause of the issue. Attached complete log file. blazegraph error log.txt https://github.com/blazegraph/database/files/5376038/blazegraph.error.log.txt
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/blazegraph/database/issues/181, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATW7YBUMUVOI34TQDGGYTDSKU75RANCNFSM4SQFMSZA .
We are using Blazegraph version 2.1.4 hosted in OpenShift server. It was working fine but suddenly it throws java.lang.RuntimeException when we are trying to access blazegraph.
From the error log we could see exception related jnl file but file was there in right path and it was working fine previously and it also worked fine after we restarted blazegraph.
we would like know the root cause of the issue. Attached complete log file. blazegraph error log.txt