All commands and changes for faster implementation were done under root permissions. For the discovery of the nodes I use EC2 discovery plugin
Continue reading Set up Elasticsearch cluster on AWS on Debian for 10 steps
All commands and changes for faster implementation were done under root permissions. For the discovery of the nodes I use EC2 discovery plugin
Continue reading Set up Elasticsearch cluster on AWS on Debian for 10 steps
1st option
# ls -l /dev/disk/by-uuid/
lrwxrwxrwx 1 root root 15 Nov 7 13:00 9c18302c-9aa2-4f55-b2c8-03a9ae68b2a2 -> ../../nvme1n1p1 lrwxrwxrwx 1 root root 15 Nov 7 13:00 b524f8c0-90e7-4fc7-a842-6cb2380086c8 -> ../../nvme0n1p1
2nd option
# blkid /dev/nvme1n1p1
/dev/nvme1n1p1: UUID="9c18302c-9aa2-4f55-b2c8-03a9ae68b2a2" TYPE="ext4" PARTUUID="1e534c5e-e4c8-424c-822b-117e47d72263"
This adds the route immediately to the Kernel IP routing table (after reboot it will be erased).
# route add -net 172.31.0.0 netmask 255.255.0.0 gw 192.168.1.1
to print the Kernel IP Routing table:
# netstat -rn
To keep the Static Route persistent you need to edit the file: /etc/network/interfaces
and the static routes in the following format:
up route add [-net/-host] <host/net>/<mask> gw <host/ip> dev <interface>
up route add -net 172.31.0.0/16 gw 192.168.1.1 dev eno1
# apt-get install ntpdate
# dpkg-reconfigure tzdata
Synchronise with time server:
# ntpdate pool.ntp.org
If all done good, then you will see the correct current time corresponding to your time zone in the screen.
To live with out manual correction of the time, the last command can be put in the /etc/crontab to update rate, for example once a week.
42 4 * * 0 root /usr/sbin/ntpdate pool.ntp.org
Will run every Sunday at 4:42 am