Ontotext GraphDB process terminates

Question

I have graphDB 8.0.2 running on an Ubuntu server. I run it with /var/lib/graphdb/bin/graphdb -Xmx1224M -Xms712M & . The graphdb process stops with no reason. I don't see any errors in the logs (see below). What could be the reason for this ? How can I debug this ? I already increased the memory given to the process, but still experiments this behavior. Would even more memory solve anything ?

Thank you for your help

[INFO ] 2017-09-06 13:38:58,092 [repositories/sem-bo | oerhsrTupleQueryResultView] Request for query -1311463370 is finished [INFO ] 2017-09-06 13:38:58,097 [repositories/sem-bo | cofsRepositoryController] POST query -2012703728 [INFO ] 2017-09-06 13:38:58,114 [repositories/sem-bo | oerhsrTupleQueryResultView] Request for query -2012703728 is finished [INFO ] 2017-09-06 13:43:43,796 [Thread-4 | cogsGraphDB] Stopping GraphDB. [INFO ] 2017-09-06 13:43:43,964 [localhost-startStop-2 | cofcsSemanticDataManagement] Shutting down current semantic location [INFO ] 2017-09-06 13:43:44,381 [Thread-5 | cotsiPluginManager] Shutting down plugins (DEFAULT)... [INFO ] 2017-09-06 13:43:44,415 [Thread-5 | cotbAVLRepository] NumberOfStatements = 45247 [INFO ] 2017-09-06 13:43:44,415 [Thread-5 | cotbAVLRepository] NumberOfExplicitStatements = 45089 [INFO ] 2017-09-06 13:43:44,415 [Thread-5 | cotfGraphDBFreeSchemaRepository] Shutting down entity pool [INFO ] 2017-09-06 13:43:49,444 [Thread-5 | cotfGraphDBFreeSchemaRepository] Entity pool was shut down

Answer 1

Based on the logs the only thing that comes to mind is something sends the interrupt signal to GraphDB and it's quitting gracefully.

The recommended way to run GraphDB in the background is by adding the -d (daemonize) option, eg in your case /var/lib/graphdb/bin/graphdb -Xmx1224M -Xms712M -d .