I have made a bad server endpoint in ArangoDB -

i have bad server endpoint in arangodb. stopping system starting. start --no-server can't connect arangosh.

how can 1 limit endpoint @ start if give endpoint command arangod --server.endpoint tcp://127.0.0.1:8529 still tries load endpoint has in database , fails.

when starting arangod, try bind endpoint specified in command-line option --server.endpoint. if option not specified in startup command, option may present configuration file used on startup.

additionally, server try bind endpoints specified in file named endpoints in server's database directory. file optional.

if endpoint (regardless if specified via command-line, configuration file or in endpoints file) specified multiple times, server refuse start. because try bind endpoint has bound to.

when binding endpoint fails whatever reason, there should line in server's error log:

2015-06-03t11:37:23z [4165] fatal failed bind endpoint 'tcp://127.0.0.1:8529'. please check whether instance running or review endpoints configuration. 

i can guess actual error reason in case, there may endpoints file present containing endpoint specified on command-line or in config file. in case should see above error message. removing endpoints file in case.

by way, --no-server intentionally disables http server in arangod, won't able connect arangoshell or else.