Darren Weber

I used `dpkg -L blazegraph` to find more installation details, including the `/usr/bin/loadRestAPI.sh` script. I read about that on the wiki and was able to get it working on a...

I may now understand these values from the `/etc/default/blazegraph` configs: ``` NAME=blazegraph BLZG_DATA=/var/lib/${NAME} JOURNAL_FILE=blazegraph.jnl JOURNAL="${BLZG_DATA}"/"${JOURNAL_FILE}" ``` They seem to result in this file: ``` $ ls -l /var/lib/blazegraph/ total 212M...

WOW, so many options in https://blazegraph.github.io/database/apidocs/com/bigdata/journal/Options.html -- a bit over my head when it comes to my knowledge of file system optimizations. Are there any experiences or recommendations for these...

BTW, and this comment is specific to this initial startup problem, the `service blazegraph status` was entirely ignorant of the checksum failure - despite the failure to start, that service...

FYI, the following got the service back up: ```sh sudo -i ls -lh /var/lib/blazegraph/ service blazegraph status # check it is stopped or use `stop` mv /var/lib/blazegraph/blazegraph.jnl /var/lib/blazegraph/blazegraph.bak ls -lh...

Tried to change the disk location for the KB store by setting ``` # /etc/default/blazegraph NAME=blazegraph # default BLZG_DATA=/data/${NAME} # changed only this JOURNAL_FILE=blazegraph.jnl # default JOURNAL="${BLZG_DATA}"/"${JOURNAL_FILE}" # default ```...

Going to try using `touch /forcefsck` and reboot the system to find/fix corruption on this virtualbox vm - related commentary - http://askubuntu.com/questions/476313/force-fsck-safe

Got the system running again, so we can close this issue. If you want, you might create a separate issue to fix the `service blazegraph status` when the checksum fails...

A possible fix for this (sorry it's not a PR): ``` $ git diff diff --git a/blazegraph-deb/src/deb/bin/loadRestAPI.sh b/blazegraph-deb/src/deb/bin/loadRestAPI.sh index 2ee49ed..995103e 100755 --- a/blazegraph-deb/src/deb/bin/loadRestAPI.sh +++ b/blazegraph-deb/src/deb/bin/loadRestAPI.sh @@ -7,9 +7,7 @@ FILE_OR_DIR=$1...

Looks like this is already fixed and a dup of #25.