I installed the arangodb-3.1.11 using source code and I am using 
arangodb tool for cluster but I am getting following error when adding the 
3rd - AWS machine -

On master - 

2017/02/28 11:32:48 Starting service...
2017/02/28 11:32:48 Starting agent on port 4001
2017/02/28 11:32:48 Error while starting agent: fork/exec 
/usr/sbin/arangod: no such file or directory
2017/02/28 11:32:49 Starting dbserver on port 4003
2017/02/28 11:32:49 Error while starting dbserver: fork/exec 
/usr/sbin/arangod: no such file or directory
2017/02/28 11:32:50 Starting coordinator on port 4002
2017/02/28 11:32:50 Error while starting coordinator: fork/exec 
/usr/sbin/arangod: no such file or directory

2nd machine - 

 2017/02/28 11:32:47 Starting service as slave with id '94c14751'...
2017/02/28 11:32:47 Starting agent on port 4006
2017/02/28 11:32:47 Error while starting agent: fork/exec 
/usr/sbin/arangod: no such file or directory
2017/02/28 11:32:48 Starting dbserver on port 4008
2017/02/28 11:32:48 Error while starting dbserver: fork/exec 
/usr/sbin/arangod: no such file or directory
2017/02/28 11:32:49 Starting coordinator on port 4007
2017/02/28 11:32:49 Error while starting coordinator: fork/exec 
/usr/sbin/arangod: no such file or directory

on 3rd machine -

2017/02/28 11:32:47 Starting service as slave with id '1d5c34de'...
2017/02/28 11:32:47 Starting agent on port 4011
2017/02/28 11:32:47 Error while starting agent: fork/exec 
/usr/sbin/arangod: no such file or directory
2017/02/28 11:32:47 Listening on 0.0.0.0:4010 (:4010)
2017/02/28 11:32:48 Starting dbserver on port 4013
2017/02/28 11:32:48 Error while starting dbserver: fork/exec 
/usr/sbin/arangod: no such file or directory
2017/02/28 11:32:49 Starting coordinator on port 4012
2017/02/28 11:32:49 Error while starting coordinator: fork/exec 
/usr/sbin/arangod: no such file or directory

-- 
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.

Reply via email to