You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After discovering that the aerospike.service would not start -- systemctl status aerospike showed that asd had not started ... I found that
aerospike.conf in /etc/aerospike was corrupted on install. In specific the heartbeat stanza was corrupted -- the ip address was not inserted.
It appears that the cluster IP addresses were not yet known at the moment entries in the heartbeat section were written:
mesh-seed-address-port [ 3002 :: there should be an ip address for a cluster host where the "[" is ... many such corrupted entries were created as can be seen below ...
After manually fixing the entries, I was able to start asd and run asadm and other tools.
Aerospike database configuration file.
service {
user root
group root
pidfile /var/run/aerospike/asd.pid
proto-fd-max 15000
node-id c000000a
cluster-name aerospike_ansible_demo_cluster
}
logging {
# Log file must be an absolute path.
file /var/log/aerospike/aerospike.log {
context any info
}
file /var/log/aerospike/udf.log {
context udf info
context aggr info
}
}
rack-id 100000
# To use file storage backing, comment out the line above and use the
# following lines instead.
storage-engine device {
device /dev/nvme1n1p1
device /dev/nvme1n1p2
device /dev/nvme1n1p3
device /dev/nvme1n1p4
data-in-memory false # Store data in memory in addition to file.
}
}
The text was updated successfully, but these errors were encountered:
I set up the aerospike-ansible project as directed in video presentation and documentation:
Host OS: Ubuntu 22.04
license: corporate
and ran the install command:
$ ansible-playbook aws-setup-plus-aerospike-install.yml --extra-vars="{'enterprise':true,'feature_key':'/home/jheyssel/Desktop/features.conf'}"
After discovering that the aerospike.service would not start -- systemctl status aerospike showed that asd had not started ... I found that
aerospike.conf in /etc/aerospike was corrupted on install. In specific the heartbeat stanza was corrupted -- the ip address was not inserted.
It appears that the cluster IP addresses were not yet known at the moment entries in the heartbeat section were written:
mesh-seed-address-port [ 3002 :: there should be an ip address for a cluster host where the "[" is ... many such corrupted entries were created as can be seen below ...
After manually fixing the entries, I was able to start asd and run asadm and other tools.
Aerospike database configuration file.
service {
user root
group root
pidfile /var/run/aerospike/asd.pid
proto-fd-max 15000
node-id c000000a
cluster-name aerospike_ansible_demo_cluster
}
logging {
# Log file must be an absolute path.
file /var/log/aerospike/aerospike.log {
context any info
}
file /var/log/aerospike/udf.log {
context udf info
context aggr info
}
}
network {
}
namespace test {
replication-factor 2
memory-size 2962M
default-ttl 0d
nsup-period 600
}
The text was updated successfully, but these errors were encountered: