As can be seen in my previous post I am trying to load some data. However I ran out of diskspace before realising it and blazegraph of course didnt like this.
I cleaned up some disk space, restarted blazegraph but now I encounter:
INFO: com.bigdata.util.config.LogUtil: Configure: jar:file:/stardog/blazegraph/bigdata-bundled.jar!/log4j.properties
WARN : NanoSparqlServer.java:484: Starting NSS
WARN : WebAppContext.java:506: Failed startup of context o.e.j.w.WebAppContext@2d3fcdbd{/bigdata,null,null}{jar:file:/stardog/blazegraph/bigdata-bundled.jar!/bigdata-war/src/}
java.lang.IllegalStateException: Parent for temp dir not configured correctly: writeable=false
at org.eclipse.jetty.webapp.WebInfConfiguration.makeTempDirectory(WebInfConfiguration.java:336)
at org.eclipse.jetty.webapp.WebInfConfiguration.resolveTempDirectory(WebInfConfiguration.java:304)
at org.eclipse.jetty.webapp.WebInfConfiguration.preConfigure(WebInfConfiguration.java:69)
at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:460)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:496)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:163)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.server.Server.start(Server.java:387)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:354)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at com.bigdata.rdf.sail.webapp.NanoSparqlServer.awaitServerStart(NanoSparqlServer.java:485)
at com.bigdata.rdf.sail.webapp.StandaloneNanoSparqlServer.main(StandaloneNanoSparqlServer.java:150)
serviceURL: http://192.168.122.1:9999
Welcome to Blazegraph(tm) by SYSTAP.
and the website shows:
HTTP ERROR: 503
Problem accessing /bigdata/. Reason:
Service Unavailable
Powered by Jetty://
Any ideas what I can do to restore the database / blazegraph?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you encounter this issue, it means that in the root of the disk there is no tmp folder. This also couldnt be created in my case as I needed sudo rights for that.
A simple sudo mkdir /mountpoint/tmp and a chown fixed this issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Blazegraph only uses temporary files when incremental truth maintenance is
enabled. If you are trying to bulk load a number of files using the
DataLoader, then this situation probably indicates that you have not
correctly configured the DataLoader. Please see the wiki for guidance on
this topic. You want to:
Commit after each file loaded (optional, but this would seem to make
sense for the use case you described with a number of large files).
Compute the database-at-once closure only after all files are loaded
(this disables incremental truth maintenance during the bulk load).
Blazegraph™ http://www.blazegraph.com/ is our ultra high-performance
graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
APIs. Blazegraph is now available with GPU acceleration using our disruptive
technology to accelerate data-parallel graph analytics and graph query.
CONFIDENTIALITY NOTICE: This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.
If you encounter this issue, it means that in the root of the disk there
is no tmp folder. This also couldnt be created in my case as I needed sudo
rights for that.
A simple sudo mkdir /mountpoint/tmp and a chown fixed this issue.
As can be seen in my previous post I am trying to load some data. However I ran out of diskspace before realising it and blazegraph of course didnt like this.
I cleaned up some disk space, restarted blazegraph but now I encounter:
INFO: com.bigdata.util.config.LogUtil: Configure: jar:file:/stardog/blazegraph/bigdata-bundled.jar!/log4j.properties
WARN : NanoSparqlServer.java:484: Starting NSS
WARN : WebAppContext.java:506: Failed startup of context o.e.j.w.WebAppContext@2d3fcdbd{/bigdata,null,null}{jar:file:/stardog/blazegraph/bigdata-bundled.jar!/bigdata-war/src/}
java.lang.IllegalStateException: Parent for temp dir not configured correctly: writeable=false
at org.eclipse.jetty.webapp.WebInfConfiguration.makeTempDirectory(WebInfConfiguration.java:336)
at org.eclipse.jetty.webapp.WebInfConfiguration.resolveTempDirectory(WebInfConfiguration.java:304)
at org.eclipse.jetty.webapp.WebInfConfiguration.preConfigure(WebInfConfiguration.java:69)
at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:460)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:496)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:163)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.server.Server.start(Server.java:387)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:354)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at com.bigdata.rdf.sail.webapp.NanoSparqlServer.awaitServerStart(NanoSparqlServer.java:485)
at com.bigdata.rdf.sail.webapp.StandaloneNanoSparqlServer.main(StandaloneNanoSparqlServer.java:150)
serviceURL: http://192.168.122.1:9999
Welcome to Blazegraph(tm) by SYSTAP.
and the website shows:
HTTP ERROR: 503
Problem accessing /bigdata/. Reason:
Powered by Jetty://
Any ideas what I can do to restore the database / blazegraph?
If you encounter this issue, it means that in the root of the disk there is no tmp folder. This also couldnt be created in my case as I needed sudo rights for that.
A simple sudo mkdir /mountpoint/tmp and a chown fixed this issue.
Blazegraph only uses temporary files when incremental truth maintenance is
enabled. If you are trying to bulk load a number of files using the
DataLoader, then this situation probably indicates that you have not
correctly configured the DataLoader. Please see the wiki for guidance on
this topic. You want to:
sense for the use case you described with a number of large files).
(this disables incremental truth maintenance during the bulk load).
Thanks,
Bryan
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
bryan@systap.com
http://blazegraph.com
http://blog.bigdata.com http://bigdata.com
http://mapgraph.io
Blazegraph™ http://www.blazegraph.com/ is our ultra high-performance
graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
APIs. Blazegraph is now available with GPU acceleration using our disruptive
technology to accelerate data-parallel graph analytics and graph query.
CONFIDENTIALITY NOTICE: This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.
On Thu, Aug 27, 2015 at 2:35 AM, Jasper Koehorst jjkoehorst@users.sf.net
wrote: