Verify the executable you are running ​

Start from the documented Coordinator DB installation procedure when establishing a reproducible environment. Record where the executable came from, which checkout or artifact you selected and which configuration files accompany it. Do not assume an independently packaged executable has the same defaults as the supplied example.

After startup, test a small public operation through the interface the application will use:

./coordinator client --database data --query "SELECT 1 AS connected FORMAT csv"

A successful result verifies that particular connection and query. It does not establish compatibility for every data type, file format or application workload. Run a representative import and query before replacing an existing executable.

Keep config.xml and users.xml explicit. The server requires them and does not create missing credentials. A different configuration directory can change listener addresses, user paths and log destinations independently of the database path.

For a packaging issue, report the executable source, exact startup command, selected configuration and full error. Remove credentials from the report. The public installation guide is the reference workflow; unsupported distribution channels should not be treated as a separately promised product or service.

See installation, configuration paths and connection options.