Error Message Reference

This section includes the possible causes and solutions for AnzoGraph error messages. Click a message in the list below to view details about that error:

7070: Connection refused

This message indicates that you ran a query against the SPARQL HTTP port (7070) and the port is unavailable. This issue might occur if you run queries using the AnzoGraph command line and is likely caused by one of the following issues:

  • The AnzoGraph database is not running. See Checking the Status of AnzoGraph below.
  • AnzoGraph is running but HTTP protocol is disabled because you specified no for the Do you want insecured (HTTP) access to cluster prompt during the AnzoGraph deployment. See Enabling HTTP Protocol below.

Checking the Status of AnzoGraph

To check if AnzoGraph is running, you can view the status in the AnzoGraph Admin Console. For example:

If the server is not started, click the Start () button. When AnzoGraph is running, the Admin Console shows the status as online. For example:

If you have secure shell access, you can view the status by running the following command on the leader node: 

/opt/anzograph/bin/azgctl -status

The output shows the status of each node. For example:

Node 0 (IP:10.0.0.54): GQE is on-line
Node 1 (IP:10.0.0.109): GQE is on-line
Node 2 (IP:10.0.0.199): GQE is on-line
Node 3 (IP:10.0.0.237): GQE is on-line

If the results report that "GQE is off-line," run the following command to start the database:

/opt/anzograph/bin/azgctl -start

Enabling HTTP Protocol

If HTTP protocol is disabled for your deployment and you want to enable it so that you can use the AnzoGraph CLI or post queries to the SPARQL HTTP port (7070), follow the instructions below.

Note: Enabling HTTP protocol requires SSH access. How do I enable SSH access to AnzoGraph instances?

  1. On the AnzoGraph leader server, run the following command to stop the database:
    /opt/anzograph/bin/azgctl -stop
  2. Open the AnzoGraph settings file /opt/anzograph/config/settings.conf in an editor. For example:
    vi /opt/anzograph/config/settings.conf
  3. Add a new line to the end of the file and enter the following value:
    enable_sparql_protocol=true
  4. Save and close the file, and then run the following command to start the database and submit the configuration change:
    /opt/anzograph/bin/azgctl -start

Once AnzoGraph starts, the HTTP protocol is enabled on port 7070 and you can use the AZGI CLI or post queries to 7070.

Cluster command failed: aws s3 ls bucket_name/directory_name --recursive >/tmp/zzs3dir

This message indicates that you tried to load files from S3 and AnzoGraph does not have permission to read the files in the bucket and directory listed in the message. If you SSH to the EC2 instance, you can verify whether the instance has access by running the AWS CLI command aws s3 ls bucket_name/directory_name --recursive. How do I enable SSH access to AnzoGraph instances?

To resolve the issue, log in to the AWS S3 Management Console and change the bucket permissions to Public for your account, or choose another option that gives the AnzoGraph servers read access to the files in the bucket.

Unsupported functionality: loading files with this extension - URL

This message indicates that the load file directory listed in the error message does not include the load file type extension in its name.

For example, running a query that loads files from the URL s3://csi-sdl-data-tickit/tickit results in this error. Since the tickit directory includes .ttl.gz files, renaming tickit to tickit.ttl.gz resolves the error.

For more information about load requirements, see Load Requirements and Recommendations.

Exiting: Error - Cannot execute as user 'root'. To override this security protection, set 'enable_root_user=true': Invalid user id

This message indicates that you tried to start AnzoGraph as the root user and root access is disabled. You can try the command again as a non-root user, or you can enable root access by adding enable_root_user=true to the AnzoGraph settings file. For instructions, see Changing System Settings.

Invalid Certificate

This message indicates that you replaced the default AnzoGraph certificates with your own trusted certificates and the certificates are invalid. Certificates can be invalid because they expired or they were generated or signed incorrectly.

Related Topics