New answers tagged

1

The results of pcs resource show ase157_res is op start timeout="20s" ? Since it takes 30 seconds to "/etc/init.d/that_script start", timeout= must be more than that.


0

If you are fencing hosts with for example impi and one node gets shot in the head with your backup DB running then it's very possible that you will corrupt the database unless it's on a fault tolerant partition that the other host can pick up- can't you use something like galera across the corosync cluster? ...


0

Have you tried simply adding an, exit 3, in the status function of the script to make it compliant? Something like this should work: # Check Sybase Adaptive Server and Backup Server status status() { dataserver=$(pidof dataserver) backupserver=$(pidof backupserver) if [ -n "$dataserver" ]; then echo "sybase Adaptive Server is running!" ...


1

systemctl status does not provide advanced information on the service running. If you are looking for ways to notify systemd about status changes on your service, sd_notify might be helpful. This depends on your services ability for self-diagnosis, though. If your service uses sd_notify, you can configure the service withWatchdogSec`. To cite from the ...


1

You need to monitor it. At first, you need to say how is defined downtime for your api. Is it defined as client cannot connect, is it defined as no methods is working, is it defined as at least one method is not working? Next step is write custom monitoring script or setup common monitoring solution (depends on step 1) and let this monitor your api. ...


0

I found out that there are actually two ways: A quorum disk (only works for older versions of Proxmox (<4), though): https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster#Quorum_Disk_Configuration Just install 2 big nodes and a small node with no VMs/Containers on it.


0

Each cluster needs to have (at least) a system DS. That scheduler message means that either your cluster 100 does not have a system DS, or the system DS found does not have enough capacity for the pending VM. If there is a system DS in that cluster, it may not be properly monitored, showing a storage capacity of 0.



Top 50 recent answers are included