Hi,
you can't connect 0.0.0.0 - you can only bind it.
So for some reason your application picks up the wrong connection IP, you
need to put in either 127.0.0.1 (if its on the same machine) or the public
IP address of the machine.
In general you can use the output of
netstat -alpnt
to see the connections current in use; The number is limited.
Its a common failure if you don't use connection keepalive that closed
connections linger around to pick up eventually stray tcp packets.
In the Linux kernel you can either configure to re-use ports that are in
this state, but the better way is to use connection keepalive since
establishing new connections needs time and consumes resources on client
and server side.
Cheers,
Willi
On Friday, April 7, 2017 at 9:14:21 AM UTC+2, Georgios Kafataridis wrote:
>
> I am getting "Connect Exception 111 cannot connect to endpoint 'tcp://
> 0.0.0.0:8529': Connection refused" errors once or twice per week. For the
> duration of aranagodb's unavailability I can't even visit the webUI.
>
> What would be the best approach to find what's causing this ? Are there
> any conditions that trigger it apart from hardware limits? Too many
> requests maybe ?
>
> Server is running:
> Debian 8
> Arangodb 3.1.16
>
--
You received this message because you are subscribed to the Google Groups
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
