Unable to find active node in AMC "Nodes"


#1

I have started a cluster with three nodes and have written the appropriate VagrantFile and the aerospace.config files for the three nodes. However, the AMC is not showing the third node.

Three nodes are running as per the arrows on the right; but they dont display in the Nodes section.


#2

Try adding them to the url. Or restast AMC. AMC is kinda shoddy…


#3

I tried adding them with the GUI option but AMC crashes immediately. I also tried implementing in the URL likewise http://localhost:8081/#dashboard/localhost:3000/30/33.33.33.91:3000,33.33.33.95:3000,33.33.33.92:3000 but no help.

Configurations: MacOS, Vagrant 1.9.5, Aerospike Community Edition build 3.12.1


#4

Which version of amc? Anything in the and log?


#6

Var log amc


#7

the log files do not have any errors. ssh-ing the vagrant boxes individually helped me.


#8
  • Restarting the AMC service worked for me.

  • Check /var/log/amc/amc.log grep for “refresh failed” and check whether the communication between your nodes is taking place or not. You can figure out error by looking into the log files.

  • Check this link http://www.aerospike.com/docs/amc/install/linux/el6 it may help you in resolving it.

You can check your error logs of AMC at /var/log/amc/error.log if any generated.


#9

The amc error log states failed to establish with error: dial tcp: too many colons in address ::1:3000; 33:33:33:95:3000 failed to establish with error: dial tcp 33:33:33:95:3000: i/o timeout; 127.0.0.1:3000 failed to establish with error: dial tcp 127.0.0.1:3000: getsockopt: connection refused;

I have also upgraded the amc to 4.0.12.


#10

AMC errors are being displayed in the /var/log/amc/amc.log instead of the /var/log/amc/error.log


#11

Ah, so this may be an IPV6 issue. I had similar issues. Instead of opening AMC and targeting “localhost”, try targeting the full IP address of the server which AMC is installed on. You could also try 127.0.0.1


#12

@Albot I got the same issue it worked for me when I gave full IP address of the server.


#13

nice! I have submitted a request to have Aerospike prefer ipv4 when possible. Not sure if it’ll be done, but the workaround is fairly easy. Alternatively you could change your hosts file…