Discussion Forum

Grakn Core Failed to Start. 1.7 . Increasing Memlock limit not fixed

When trying to start the Grakn server, I get the following message.

Starting Storage…SUCCESS
Starting Grakn Core Server…FAILED!
Unable to start Grakn Core Server.

The grakn.log file shows the following

2020-04-19 16:54:23,495 [main] INFO grakn.core.server.Grakn - Grakn started in 1.110 s
2020-04-19 17:03:27,890 [main] INFO grakn.core.server.Grakn - Grakn started in 1.297 s
2020-04-19 17:09:03,285 [main] INFO grakn.core.server.Grakn - Grakn started in 1.254 s
2020-04-19 17:28:32,243 [main] INFO grakn.core.server.Grakn - Grakn started in 1.473 s
2020-04-19 17:34:35,860 [main] INFO grakn.core.server.Grakn - Grakn started in 1.404 s
2020-04-19 19:22:34,567 [main] INFO grakn.core.server.Grakn - Grakn started in 1.314 s
2020-04-19 19:36:46,984 [main] INFO grakn.core.server.Grakn - Grakn started in 1.163 s
2020-04-19 20:33:01,140 [main] INFO grakn.core.server.Grakn - Grakn started in 1.376 s
2020-04-19 20:50:36,963 [main] INFO grakn.core.server.Grakn - Grakn started in 1.324 s
2020-04-19 21:06:05,400 [main] INFO grakn.core.server.Grakn - Grakn started in 1.260 s
2020-04-19 21:29:29,025 [main] INFO grakn.core.server.Grakn - Grakn started in 1.251 s
2020-04-20 14:34:38,042 [main] INFO grakn.core.server.Grakn - Grakn started in 1.544 s
2020-04-20 15:29:51,830 [main] INFO grakn.core.server.Grakn - Grakn started in 1.387 s

Each time I’ve tried to start the server is shown above.
However, running grakn server status returns the following:
Storage: NOT RUNNING
Grakn Core Server: NOT RUNNING

The cassandra.log shows this after grep UNABLE

WARN [main] 2020-04-19 16:54:15,187 NativeLibrary.java:187 - Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out, especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or run Cassandra as root.
INFO [main] 2020-04-19 16:54:19,066 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
WARN [main] 2020-04-19 17:03:19,541 NativeLibrary.java:187 - Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out, especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or run Cassandra as root.
INFO [main] 2020-04-19 17:03:23,730 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
WARN [main] 2020-04-19 17:08:54,918 NativeLibrary.java:187 - Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out, especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or run Cassandra as root.
INFO [main] 2020-04-19 17:08:59,408 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
WARN [main] 2020-04-19 17:28:23,830 NativeLibrary.java:187 - Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out, especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or run Cassandra as root.
INFO [main] 2020-04-19 17:28:28,060 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
INFO [main] 2020-04-19 17:34:31,698 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
WARN [main] 2020-04-19 19:22:26,175 NativeLibrary.java:187 - Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out, especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or run Cassandra as root.
INFO [main] 2020-04-19 19:22:30,520 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
INFO [main] 2020-04-19 19:36:43,490 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
INFO [main] 2020-04-19 20:32:56,853 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
INFO [main] 2020-04-19 20:50:33,037 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
INFO [main] 2020-04-19 21:06:01,751 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
INFO [main] 2020-04-19 21:29:25,110 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
INFO [main] 2020-04-20 14:34:33,485 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list
INFO [main] 2020-04-20 15:29:47,571 StorageService.java:550 - Unable to gossip with any peers but continuing anyway since node is in its own seed list

After researching these errors online, I increasing my memlock limits to unlimited. I added these to my etc/security/limits.conf file:

    • memlock unlimited
    • nofile 100000
    • nproc 32768
    • as unlimited

ulimit -l returns unlimited as well.

I am running this on a CentOS machine with two cores and 16 GB RAM.

I have yet to get grakn to start working. At first I thought it was possibly because I already had a different java version on my machine, but 1.8 is now my default so that should be ok.

Any advice? Is it because it is starting and I need to stop it?