The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.
Synopsis:
Check that Aerospike is listening and responding on the necessary ports
If you have a problem forming your cluster or a node that is acting up running through a basic test to make sure Aerospike is listening and responding will be very benefical in order to narrow down the problem.
-
Check that Aerospike is running
[vagrant@localhost ~]$ ps aux | grep asd root 1311 1.4 5.4 2712340 104612 ? Ssl 07:02 0:52 /usr/bin/asd --config-file /etc/aerospike/aerospike.conf
-
Check that Aerospike is listening
[vagrant@localhost ~]$ netstat -nl | grep "300[0-4]" tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:3001 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:3003 0.0.0.0:* LISTEN
NOTE: If you are running XDR port 3004 will also be open.
-
Can we connect using asinfo inside our node (Only showing partial output for demo purposes)
[vagrant@localhost ~]$ asinfo -h 127.0.0.1 1 : node BB98FB4A9290C00 2 : statistics
-
Can we connect using asinfo from outside the network card (Only showing partial output for demo purposes)
[vagrant@localhost ~]$ asinfo -h [IP-ADDRESS] 1 : node BB98FB4A9290C00 2 : statistics
-
Can we connect using asinfo from another node to this one (Only showing partial output for demo purposes)
[vagrant2@localhost ~]$ asinfo -h [IP-ADDRESS] 1 : node BB98FB4A9290C00 2 : statistics