# Unable to find active node in AMC "Nodes"

**URL:** <https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213>\
**Category:** AMC\
**Created:** [May 31, 2017, 10:06pm UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213 "2017-05-31T22:06:33Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![ytejas](https://avatars.discourse-cdn.com/v4/letter/y/71e660/32.png) [@ytejas](https://discuss.aerospike.com/u/ytejas)\
**Post date:** [May 31, 2017, 10:06pm UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/1 "2017-05-31T22:06:33Z")

</div>

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.

 ![](https://us1.discourse-cdn.com/flex019/uploads/aerospike/original/1X/1d0fde4d2cb41ee04ed8652c2a8ee4e9684e274b.png)

---

<div class="post-metadata">

**Author:** ![Albot](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/albot/32/2076_2.png) [@Albot](https://discuss.aerospike.com/u/Albot)\
**Post date:** [May 31, 2017, 11:29pm UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/2 "2017-05-31T23:29:45Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![ytejas](https://avatars.discourse-cdn.com/v4/letter/y/71e660/32.png) [@ytejas](https://discuss.aerospike.com/u/ytejas)\
**Post date:** [June 1, 2017, 1:21am UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/3 "2017-06-01T01:21:12Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Albot](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/albot/32/2076_2.png) [@Albot](https://discuss.aerospike.com/u/Albot)\
**Post date:** [June 1, 2017, 1:34am UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/4 "2017-06-01T01:34:23Z")

</div>

Which version of amc? Anything in the and log?

---

<div class="post-metadata">

**Author:** ![Albot](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/albot/32/2076_2.png) [@Albot](https://discuss.aerospike.com/u/Albot)\
**Post date:** [June 1, 2017, 2:00am UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/6 "2017-06-01T02:00:04Z")

</div>

Var log amc

---

<div class="post-metadata">

**Author:** ![ytejas](https://avatars.discourse-cdn.com/v4/letter/y/71e660/32.png) [@ytejas](https://discuss.aerospike.com/u/ytejas)\
**Post date:** [June 1, 2017, 2:11am UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/7 "2017-06-01T02:11:25Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![ptumuluri8](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/ptumuluri8/32/795_2.png) [@ptumuluri8](https://discuss.aerospike.com/u/ptumuluri8)\
**Post date:** [June 1, 2017, 3:07am UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/8 "2017-06-01T03:07:19Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![ytejas](https://avatars.discourse-cdn.com/v4/letter/y/71e660/32.png) [@ytejas](https://discuss.aerospike.com/u/ytejas)\
**Post date:** [June 2, 2017, 4:08pm UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/9 "2017-06-02T16:08:48Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ytejas](https://avatars.discourse-cdn.com/v4/letter/y/71e660/32.png) [@ytejas](https://discuss.aerospike.com/u/ytejas)\
**Post date:** [June 2, 2017, 4:16pm UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/10 "2017-06-02T16:16:38Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Albot](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/albot/32/2076_2.png) [@Albot](https://discuss.aerospike.com/u/Albot)\
**Post date:** [June 2, 2017, 9:28pm UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/11 "2017-06-02T21:28:19Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![ptumuluri8](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/ptumuluri8/32/795_2.png) [@ptumuluri8](https://discuss.aerospike.com/u/ptumuluri8)\
**Post date:** [June 3, 2017, 2:48am UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/12 "2017-06-03T02:48:43Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Albot](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/albot/32/2076_2.png) [@Albot](https://discuss.aerospike.com/u/Albot)\
**Post date:** [June 3, 2017, 3:15am UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/13 "2017-06-03T03:15:00Z")

</div>

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…

---

<div class="post-metadata">

**Author:** ![Abhay](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/abhay/32/1514_2.png) [@Abhay](https://discuss.aerospike.com/u/Abhay)\
**Post date:** [September 14, 2020, 5:01pm UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/14 "2020-09-14T17:01:17Z")

</div>

I have installed aerospike server in kubernates cluster. And accessing it locally through the kube context by port forwarding on port 3000

I want to see AMC, so i am using docker image with following command:

`docker run -tid -p 8081:8081 --name aerospike-console aerospike/amc`

docker container is up but when I try to access it it showing me connection refused.

Getting error when below API:

**Request:**

```
GET 'http://localhost:8081/aerospike/service/clusters/get-cluster-id' 

```

**Response:**

` {"error":"Failed to connect to hosts:dial tcp 127.0.0.1:3000: connect: connection refused","status":"failure"}`

Anybody can help here?

 ![image](https://us1.discourse-cdn.com/flex019/uploads/aerospike/original/2X/7/73bb67373c4e27d5df126c1305833634103f93be.png)

---

<div class="post-metadata">

**Author:** ![Robert\_Glonek](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/robert_glonek/32/1262_2.png) [@Robert\_Glonek](https://discuss.aerospike.com/u/Robert_Glonek)\
**Post date:** [September 18, 2020, 11:57am UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/15 "2020-09-18T11:57:10Z")

</div>

After deploying AMC via docker, AMC will be in it’s own container. Accessing [http://localhost:8081](http://localhost:8081) should bring up a window asking you to enter the IP of a node in a cluster. You must use an IP of the Aerospike node, and AMC must be able to route to it and connect on port 3000 to it. After that you will be redirected to a url that has node IPs in the list.

1. run amc

`docker run -tid -p 8081:8081 --name aerospike-console aerospike/amc`

1. from your browser, access [http://localhost:8081](http://localhost:8081). You will see the following screen.

 ![Screenshot 2020-09-18 at 12.49.47](https://us1.discourse-cdn.com/flex019/uploads/aerospike/original/2X/4/4113ba3f1f2731dcda7f6d2e6ccd1e732f2bd44d.png)

1. enter the IP address of an Aerospike cluster node, like so:

 ![Screenshot 2020-09-18 at 12.49.58](https://us1.discourse-cdn.com/flex019/uploads/aerospike/original/2X/d/d43d9e9aa9583f40d3db39174793ec5a77288b38.png)

1. The URL you will be redirected to will contain a list of IPs of the nodes:

 ![Screenshot 2020-09-18 at 12.50.17](https://us1.discourse-cdn.com/flex019/uploads/aerospike/original/2X/9/9d0044cb5dc86f776a677fff7142a6b47525433d.png)

It looks from the shared screen like the IP entered in the original box was 127.0.0.1, which will not work as AMC is in it’s own container and doesn’t have Aerospike running in the said container.

---

<div class="post-metadata">

**Author:** ![rbotzer](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/rbotzer/32/2114_2.png) [@rbotzer](https://discuss.aerospike.com/u/rbotzer)\
**Post date:** [September 23, 2020, 8:45pm UTC](https://discuss.aerospike.com/t/unable-to-find-active-node-in-amc-nodes/4213/16 "2020-09-23T20:45:35Z")

</div>

By the way, AMC (what was community and enterprise AMC) is open source and lives at [aerospike-community/amc](https://github.com/aerospike-community/amc).

See Hello Aerospike Monitoring Stack, Goodbye AMC.
