Hi I have followed the same process as An Tran and have hit the same issue. Can anybody please help us out. I couldn't trace anything from the logs either.
Also, it might be helpful to mention about --*agency.my-address* in the documentation (https://docs.arangodb.com/3.1/Manual/Deployment/Distributed.html). Thanks On Thursday, 12 January 2017 01:18:13 UTC+5:30, An Tran wrote: > > Hi, > > I just installed ArangoDB 3.1.8 on 3 nodes which I am trying to run in > cluster mode. > > As far as I can tell, I am able to run the agency process successfully on > 3 nodes. Below is the output of one agency process > > [osdi@osdi-04 ~]$ /usr/sbin/arangod --server.endpoint tcp://$HOSTNAME:25001 > --server.authentication false --agency.size 3 --agency.supervision true > --database.directory /data/data/arango/agency > > 2017-01-11T19:42:34Z [16930] INFO ArangoDB 3.1.8 [linux] 64bit, using > VPack 0.1.30, ICU 54.1, V8 5.0.71.39, OpenSSL 1.0.1e-fips 11 Feb 2013 > > 2017-01-11T19:42:34Z [16930] INFO using SSL options: > SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG > > 2017-01-11T19:42:34Z [16930] INFO file-descriptors (nofiles) hard limit is > 999999, soft limit is 999999 > > 2017-01-11T19:42:34Z [16930] INFO JavaScript using startup > '//usr/share/arangodb3/js', application '/var/lib/arangodb3-apps' > > 2017-01-11T19:42:38Z [16930] INFO In database '_system': Database is > up-to-date (30108/standalone/existing) > > 2017-01-11T19:42:38Z [16930] INFO using endpoint > 'http+tcp://osdi-04:25001' for non-encrypted requests > > 2017-01-11T19:42:43Z [16930] INFO ArangoDB (version 3.1.8 [linux]) is > ready for business. Have fun! > > When i try and run the DBServer process it hangs. See below for output. > Do you you guys know > > [osdi@osdi-04 ~]$ arangod --server.authentication=false --server.endpoint > tcp://0.0.0.0:8529 --cluster.my-address tcp://$HOSTNAME:8529 > --cluster.my-local-info $HOSTNAME --cluster.my-role osdi-03 > --cluster.agency-endpoint tcp://osdi-03:25001 --cluster.agency-endpoint > tcp://osdi-04:25001 --cluster.agency-endpoint tcp://osdi-05:25001 > --database.directory /data/data/arango/primary > > 2017-01-11T19:45:36Z [17259] INFO ArangoDB 3.1.8 [linux] 64bit, using > VPack 0.1.30, ICU 54.1, V8 5.0.71.39, OpenSSL 1.0.1e-fips 11 Feb 2013 > > 2017-01-11T19:45:36Z [17259] INFO using SSL options: > SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG > > > When I run arangodb as a standalone server it works fine. See below for > detail > > Enter code here...[osdi@osdi-04 ~]$ arangod > > 2017-01-11T19:46:14Z [17284] INFO ArangoDB 3.1.8 [linux] 64bit, using > VPack 0.1.30, ICU 54.1, V8 5.0.71.39, OpenSSL 1.0.1e-fips 11 Feb 2013 > > 2017-01-11T19:46:14Z [17284] INFO using SSL options: > SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG > > 2017-01-11T19:46:14Z [17284] INFO Authentication is turned on > > 2017-01-11T19:46:14Z [17284] INFO Authentication system only > > 2017-01-11T19:46:14Z [17284] INFO Authentication for unix sockets is > turned on > > 2017-01-11T19:46:14Z [17284] INFO file-descriptors (nofiles) hard limit is > 999999, soft limit is 999999 > > 2017-01-11T19:46:14Z [17284] INFO JavaScript using startup > '//usr/share/arangodb3/js', application '/var/lib/arangodb3-apps' > > 2017-01-11T19:46:18Z [17284] INFO In database '_system': Found 14 defined > task(s), 1 task(s) to run > > 2017-01-11T19:46:18Z [17284] INFO In database '_system': state > standalone/existing, tasks updateUserModels > > 2017-01-11T19:46:18Z [17284] INFO In database '_system': existing cleanup > successfully finished > > 2017-01-11T19:46:18Z [17284] INFO using endpoint 'http+tcp://0.0.0.0:8529' > for non-encrypted requests > > 2017-01-11T19:46:23Z [17284] INFO ArangoDB (version 3.1.8 [linux]) is > ready for business. Have fun! > > > Do you guys know what could be causing this error and how can I fix it? > Also is there a way to turn on more useful logging to debug? > > Thanks, > -- 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.
