1- Apinizer: The servers are restarted. The systems start automatically. If it does not start, the system is examined with the "apinizer" user.

#The status of the vehicles running in the system can be checked with the following commands.
sudo reboot
sudo systemctl status docker
sudo systemctl status kubelet
sudo systemctl status mongod
sudo systemctl status elasticsearch
POWERSHELL


2- Kubernetes: On the master server, the nodes connected with the command "kubectl get node", that is, other servers are seen. With the command "kubectl describe node X", the node name in the output of the previous command is replaced with "X" and the status of the node is examined. For a specific error, proceed according to the instructions in the document.

kubectl get node
kubectl describe NODENANE
POWERSHELL


  • All running threads are observed by running the following command on the master server. The Apinizer interface is located in the "apinizer" namespace by default. For detailed analysis of any pod, the describe or log commands can be used.
kubectl get pods -A
kubectl describe pod -n NAMESPACE PODNAME
kubectl logs -f -n NAMESPACE PODNAME
POWERSHELL


  • Disk and ram status are examined. Swap is expected to be closed and the disk fullness rate should not exceed 85%.
df -h
free -m
swapoff -a
POWERSHELL


3- MongoDB: Mongodb backup can be made to a desired location at certain intervals via Apinizer. This backup needs to be backed up somewhere other than the server. If mongodb does not start automatically, the logs are examined.

#You can find the location where mongodb logs are kept from the "path" directory in the /etc/mongod.conf file. /var/log/mongodb/mongod.log
POWERSHELL


4- Elasticsearch: Snapshots can be taken to a desired location at certain intervals via Apinizer. During the installation, by default, the place where the data is kept in the file at the address "/opt/elasticsearch/elasticsearch-7.9.2/config/elasticsearch.yml" is specified in the "path.data" statement. Backups can be obtained from the address specified here.

If Elasticsearch does not start automatically, the logs are reviewed.

vi /opt/elasticsearch/elasticsearch-7.9.2/config/elasticsearch.yml
POWERSHELL