war file: bigdata.jnl not found about database

[beebs-systap]

Hello,

Please see if one of the suggestions described here works for you. You may need to either add the path to the journal file as a startup parameter to Tomcat or edit the RWStore.properties.

The logging is done to the catalina.out for Tomcat in the war / Tomcat deployment model.

[mnscholz]

Hi,

thanks for the help!
Rather late (the holidays...) I want to report that I got blazegraph running on tomcat.

There were two problems:

1. the blazegraph.war release file does not contain blazegraph.jnl. I downloaded the source code, compiled it and got the jnl called blazegraph.jnl.
2. despite the release being called blazegraph.war, in the RWStore.properties (and other .properties files), the library is called bigdata.jnl, not blazegraph.jnl. I changed them to the latter and used an absolute path.

After restarting tomcat a couple of times, blazegraph works fine now.

[thompsonbry]

The .jnl files contain the data for the database. They are initially created if they do not exist. Just FYI. Thanks, Bryan

…

On Thu, Dec 29, 2016 at 11:44 AM, mnscholz ***@***.***> wrote: Hi, thanks for the help! Rather late (the holidays...) I want to report that I got blazegraph running on tomcat. There were two problems: 1. the blazegraph.war release file does not contain blazegraph.jnl. I downloaded the source code, compiled it and got the jnl (called blazegraph.jnl, not bigdata.jnl). 2. despite the release being called blazegraph.war, in the RWStore.properties (and other .properties files), the library is called bigdata.jnl, not blazegraph.jnl. I changed them to the latter and used an absolute path. After restarting tomcat a couple of times, blazegraph works fine now. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#41 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACdv4BsLwINvb4B-EG0CmUG2HzfF7u08ks5rNA2ZgaJpZM4LPLUF> .

[mnscholz]

Good to know! So finally it seems the problem was that blazegraph/tomcat could not create the file due to missing permissions.

Thanks!
Martin

[nvbach91]

Blazegraph by default will create the bigdata.jnl file inside he folder where the servlet container is run. Usually that folder is protected so the jnl file can't be created. You should pick another location by defining an absolute path of in the properties files of Blazegraph.

Solution:

change

./webapps/blazegraph/WEB-INF/web.xml
line:42:<param-value>RWStore.properties</param-value>
./webapps/blazegraph/WEB-INF/GraphStore.properties
line:12:com.bigdata.journal.AbstractJournal.file=bigdata.jnl
./webapps/blazegraph/WEB-INF/classes/RWStore.properties
line:12:com.bigdata.journal.AbstractJournal.file=bigdata.jnl

to

./webapps/blazegraph/WEB-INF/web.xml
line:42:<param-value>/opt/tomcat/webapps/blazegraphpublic/WEB-INF/RWStore.properties</param-value>
./webapps/blazegraph/WEB-INF/GraphStore.properties
line:12:com.bigdata.journal.AbstractJournal.file=/your/existing/desired/path/bigdata.jnl
./webapps/blazegraph/WEB-INF/classes/RWStore.properties
line:12:com.bigdata.journal.AbstractJournal.file=/your/existing/desired/path/bigdata.jnl

also, you might need to

chown tomcat:tomcat /your/existing/desired/path/

link: https://github.com/blazegraph/database/wiki/NanoSparqlServer#common-startup-problems