Arangod

• Check the server log file: If the server has written a log file you should check it because it might contain relevant error context information.

• Check the configuration: The server looks for a configuration file named arangod.conf on startup. The contents of this file will be usedas a base configuration that can optionally be overridden with command-line configuration parameters. You should check the config file for the mostrelevant parameters such as:

  • log parameters: If and where to log
  • database.directory: Path the database files are stored inIf the configuration reveals that something is not configured right the configfile should be adjusted and the server be restarted.

• Check the TCP port: If the server starts up but does not accept any incoming connections this might be due to firewall configuration between the server and any client(s). The server by default will listen on TCP port 8529. Please make sure this port is actually accessible by other clients if you plan to use ArangoDB in a network setup.

When using hostnames in the configuration or when connecting, please makesure the hostname is actually resolvable. Resolving hostnames might invokeDNS, which can be a source of errors on its own.

• Test if *curl can connect*: Once the server is started, you can quicklyverify if it responds to requests at all. This check allows you todetermine whether connection errors are client-specific or not. If at least one client can connect, it is likely that connection problems ofother clients are not due to ArangoDB’s configuration but due to clientor in-between network configurations.

You can test connectivity using a simple command such as:

curl —dump - -X GET && echo