Grakn server startup issue after update to 1.2.0


#1

I had a similar problem to this beforehand and managed to fix it by killing the queue process running on the Redis port, and then re-installing. I did the same but this time when I re-installed I updated to 1.2.0 and now the Engine is failing to boot but the storage is not running, I also checked if anything was listening on port 4567 and seems to be nothing.

    Harrys-MacBook-Pro-2:~ hcbh96$ grakn server start
=============================================================================
      ________  _____     _______  __    __  __    __      _______  ___
     |   __   ||   _  \  |   _   ||  |  /  /|  \  |  |    |   _   ||   |
     |  |  |__||  | |  | |  | |  ||  | /  / |   \ |  |    |  | |  ||   |
     |  | ____ |  |_| /  |  |_|  ||  |/  /  |    \|  |    |  |_|  ||   |
     |  ||_   ||   _  \  |   _   ||   _  \  |   _    |    |   _   ||   |
     |  |__|  ||  | \  \ |  | |  ||  | \  \ |  | \   | __ |  | |  ||   |
     |________||__|  \__\|__| |__||__|  \__\|__|  \__||__||__| |__||___|

                          Grakn: The Database For AI
=============================================================================

Starting Storage....SUCCESS
Starting Queue.....SUCCESS
Starting Engine........................................................................................................................................................FAILED!
Unable to start Engine
Harrys-MacBook-Pro-2:1.2.0 hcbh96$ grakn server status
=============================================================================
      ________  _____     _______  __    __  __    __      _______  ___
     |   __   ||   _  \  |   _   ||  |  /  /|  \  |  |    |   _   ||   |
     |  |  |__||  | |  | |  | |  ||  | /  / |   \ |  |    |  | |  ||   |
     |  | ____ |  |_| /  |  |_|  ||  |/  /  |    \|  |    |  |_|  ||   |
     |  ||_   ||   _  \  |   _   ||   _  \  |   _    |    |   _   ||   |
     |  |__|  ||  | \  \ |  | |  ||  | \  \ |  | \   | __ |  | |  ||   |
     |________||__|  \__\|__| |__||__|  \__\|__|  \__||__||__| |__||___|

                          Grakn: The Database For AI
=============================================================================

Storage: NOT RUNNING
Queue: RUNNING
Engine: RUNNING
Harrys-MacBook-Pro-2:1.2.0 hcbh96$ jps
30353 CassandraDaemon
56984 Grakn
57918 Jps
Harrys-MacBook-Pro-2:1.2.0 hcbh96$ ps -ef | grep redis-server
  501 56974     1   0  5:44PM ??         0:00.61 /usr/local/Cellar/grakn/1.2.0/libexec/services/redis/redis-server-osx 127.0.0.1:6379 
  501 57921 54813   0  5:58PM ttys000    0:00.01 grep redis-server
Harrys-MacBook-Pro-2:1.2.0 hcbh96$ ls -l
total 96
-rw-r--r--  1 hcbh96  admin    574 Apr  4 17:42 INSTALL_RECEIPT.json
-rw-r--r--  1 hcbh96  admin  34522 Mar 29 20:23 LICENSE.txt
-rw-r--r--  1 hcbh96  admin   6865 Mar 29 20:23 README.md
drwxr-xr-x  4 hcbh96  admin    128 Apr  4 17:42 bin
drwxr-xr-x  9 hcbh96  admin    288 Apr  4 17:42 libexec
Harrys-MacBook-Pro-2:1.2.0 hcbh96$ 


***********************last lines lines of output from it is about 100
long and didnt want to document dump you ****************************

52259:M 04 Apr 17:12:57.972 # Server started, Redis version 3.2.9
52259:M 04 Apr 17:13:01.878 * DB loaded from append only file: 3.905 seconds
52259:M 04 Apr 17:13:01.878 * The server is now ready to accept connections on port 6379
52259:M 04 Apr 17:13:58.013 * 10000 changes in 60 seconds. Saving...
52259:M 04 Apr 17:13:58.016 * Background saving started by pid 52273
52273:C 04 Apr 17:13:58.022 * DB saved on disk
52259:M 04 Apr 17:13:58.117 * Background saving terminated with success

#2

Solved, I again killed the process running on
501 56974 1 0 5:44PM ?? 0:00.61 /usr/local/Cellar/grakn/1.2.0/libexec/services/redis/redis-server-osx 127.0.0.1:6379

Then shut down the terminal and reset laptop and it now seems to be working. So no rush with this one but the output may still be useful to you guys.


#3

It seems the problem is due to Grakn not stopped properly last time. If you are experiencing the same issue in the future, please report it by making a new thread , following this guide