Copyright © 2015-2017 TigerGraph. All Rights Reserved.
For technical support on this topic, contact email@example.com with a subject line beginning with "FAQ"
TigerGraph System Administrator FAQs
In this document, all commands should be executed as TigerGraph user, unless specified.
How to apply or update my license key?
During install, you can either specify your license key as an argument, for example:
Or you may input it when prompted.
To apply a new license key, use the following command:
When my license key expire?
The following command will tell you your key's expiration date:
What are the components of the TigerGraph platform?
A description of each component is given in the Glossary section of the
TigerGraph Platform Overview
How can I find out current status of the system?
The following command tells you the basic summary of each component:
If you want to know more, including process information, memory/cpu usage information of each component, use the -v option for verbose output.
How can I find out the port of a service?
The default RESTful API port is 9000. It can be changed by configuration. To find out the current RESTful API port, use following command:
The default port for the GraphStudio UI is 44240. Use the following to check its configuration:
If you are using a remote GSQL client, it communicates with the GSQL server via port 8123.
To see a list of all ports:
How do I backup my data?
GBAR is the utility to do backup and restore of TigerGraph system. Before a backup, GBAR needs to be configured. Please see GBAR - Graph Backup and Restore v1.0 for details.
To backup the current system:
Please be advised that GBAR only backs up data and configuration. No logs or binaries will be backed up.
How do I restore a backup?
To restore an existing backup:
Please be advised that running restore will STOP the service and ERASE existing data.
How can I find out statistics of my graph data?
will tell you the size of graph data on disk, number of vertices and edges.
How can I find out statistics of requests?
TigerGraph provides a RESTful API to tell request statistics. Assuming REST port is 9000, use command below:
How do I restart a service?
If you need to restart everything, use the following:
If you know which component(s) you want to restart,you can list them:
Multiple component names are separated by spaces.
How to I stop some or all services?
Normally it is not necessary to manually turn off any services. However if you wish to, use the stop command.
Note: runnng "gadmin stop" still does not stop every single TigerGraph service. Glive will still run because it is monitoring other services, and the Admin server will still run because it manages the other services. If you need to perform a full shutdown, for example, before a software upgrade or before a hardware change, perform the following sequence of commands:
Why the service is down?
There are a few typical causes for a service being down:
Expired license key.
Double check your license key expiration date, and contact firstname.lastname@example.org if it is expired. After applying a new license key, your service will come back online.
Usually, TigerGraph will reach out before your license key expires. Please act accordingly when that happens.
Not enough memory.
TigerGraph is a memory intensive system. When there is not much free memory, Linux may kill a process based on memory usage. Please check your memory usage after TigerGraph starts. We suggest at least 30% free memory after TigerGraph starts up.
To confirm if one of TigerGraph's processes is a victim, use <span>dmesg</span> to check.
Not enough free disk space.
TigerGraph writes data, logs, as well as some temporary files onto disk(s). It requires enough free space to function properly. If TigerGraph service or one of its components is down, please check whether there is enough free space on the disk using <span>df</span> .
Where are the logs?
Use following command to figure out where are log files for each component:
To log at the log file for a particular component:
If you want to look at only the last N lines of the log:
Why has my request timed out?
Timeout is applied to any request coming into TigerGraph system. If a request runs longer than the Timeout value, it will be killed. The default timeout value is 16 second.
If you knows that your query will run longer than the value, configure all related timeouts to a bigger value. To do this:
Input a value you expected, the unit is in second. Then apply the config to the system and restart the service.