All versions of this manual
X
 

Troubleshooting: Checking Linkurious' status

Process monitoring

Linkurious starts 3 separate processes when launched:

  • node (or node.exe): The internal process manager
  • node (or node.exe): The Linkurious Server process
  • java (or java.exe): The embedded Elasticsearch indexation server (if enabled).

Check if these processes are alive by opening the menu from the Linkurious directory (see how on each operating system below).

The menu looks like this: Linkurious manager menu

Linux systems

Run menu.sh (the status is above the menu). Alternately, run menu.sh status.

Windows systems

Run menu.bat (the status is above the menu). Alternately, run menu.bat status.

Mac OS X systems

Run menu.sh.command (the status is above the menu). Alternately, run menu.sh.command status.

API status

The status of the API can be retrieved using a browser or a command line HTTP client like cURL.

To retrieve the API status, send a GET request to http://127.0.0.1:3000/api/status (replace 127.0.0.1 and 3000 with the actual host and port of your server).

// example response 
{"status":{"code":200,"name":"initialized","message":"Linkurious ready to go :)","uptime":8633}}

API version

The version of the API can be retrieved using a browser or a command line HTTP client like cURL.

To retrieve the API status, send a GET request to http://127.0.0.1:3000/api/version (replace 127.0.0.1 and 3000 with the actual host and port of your server).

// example response 
{"tag_name":"1.8.0","name":"Xenodochial Xenoposeidon","prerelease":false,"enterprise":true}