07-17-2018
He said you have to check if your "needed" and "present" count are correct. If they are, you can reboot the quorum server without any danger. In a 2 node cluster you should have 2 on the needed side and 3 on the present. The 3rd would be the quorum server. After the reboot check again for present=3.
This User Gave Thanks to DukeNuke2 For This Post:
9 More Discussions You Might Find Interesting
1. SCO
Dear sir,
I am using sco open server 5.06.How we can reboot the system without using root password? Whar are the permision need to change to do this.
Thanks,
Mostafizur Rahman (3 Replies)
Discussion started by: rahmanm
3 Replies
2. Shell Programming and Scripting
I want to get an email alert from a cronjob when a server got rebooted unexpectedly. Please help. Thanks! :confused: (2 Replies)
Discussion started by: angloi
2 Replies
3. UNIX for Advanced & Expert Users
hi all, :)
for a reboot of sun box for patch installation i would like to know where do the reboot logs apart from /var/adm/messages and patch run messages would be available,
i would like to know the sequence of messages logged in the file like
requesting the users to log out
sending a... (1 Reply)
Discussion started by: matrixmadhan
1 Replies
4. AIX
I've recently changed my gateway setting using SMIT. Everything went fine except that the gateway setting kept reverting back to the old one everytime I reboot the server.
I'm on AIX 5.2 running p-Series. Thanks for any info. (3 Replies)
Discussion started by: dereklow
3 Replies
5. Solaris
Hi All,
I want to know the procedure like if server is down, i want to reboot the server through console ($rsc or $sc prompt).Could you please help me out.
I would really appreciate your cooperation.
thanks for understanding
regards
krishna (5 Replies)
Discussion started by: murthy76
5 Replies
6. Linux
We reboot our linux servers daily. Is it needed ? (10 Replies)
Discussion started by: linuxadmin
10 Replies
7. UNIX for Advanced & Expert Users
When accessing a user mode buffers from kernel space drivers what precautions must we take and how those precautions need to be implemented? (0 Replies)
Discussion started by: rupeshkp728
0 Replies
8. Solaris
Hi,
anyone please let us know how to write shell script to find the missing mountpoints after server reboot.
i want to take the mountpount information before server reboot, and validate the mountpoints after server reboot if any missing.please let us know the shell script from begining to end as... (24 Replies)
Discussion started by: VenkatReddy786
24 Replies
9. Red Hat
Hi,
The server got rebooted and below messages can be seen in /var/log/messages
Sep 7 10:49:12 minersville kernel: Call Trace: <IRQ> <ffffffff80167420>{__alloc_pages+796}
Sep 7 10:49:12 minersville kernel: <ffffffff80182814>{kmem_getpages+106} <ffffffff80183c16>{fallback_alloc+304}... (3 Replies)
Discussion started by: admin_db
3 Replies
LEARN ABOUT CENTOS
votequorum_qdevice_register
VOTEQUORUM_QDEVICE_REGISTER(3) Corosync Cluster Engine Programmer's Manual VOTEQUORUM_QDEVICE_REGISTER(3)
NAME
votequorum_qdevice_register - Registers a new quorum device
SYNOPSIS
#include <corosync/votequorum.h>
int votequorum_qdevice_register(votequorum_handle_t handle, const char * name);
DESCRIPTION
The votequorum_qdevice_register is used to register a new quorum device. A quorum device is an external way of adding votes to a small
cluster. The quorum device is, in effect, a pseudo node in the cluster that provide votes based on some external device, usually a shared
disk partition or perhaps a network router.
This call creates the device but does not mark it active. votequorum_qdevice_poll must be called for the votes to be included in the quo-
rum calculation.
name is string containing an informative name for the quorum device. It is simply stored by votequorum and used in the display of corosync-
quorumtool, it can be a maximum of 254 characters.
The number of votes contributed by the quorum device is already known to votequorum, it is set in cmap quorum.device.votes and not by the
device.
Note that it is the responsibility of the quorum device subsystem (not provided as part of votequorum) to keep all nodes informed of the
quorum device status.
RETURN VALUE
This call returns the CS_OK value if successful, otherwise an error is returned.
ERRORS
CS_ERR_TRY_AGAIN Resource temporarily unavailable
CS_ERR_INVALID_PARAM Invalid argument
CS_ERR_ACCESS Permission denied
CS_ERR_LIBRARY The connection failed
CS_ERR_INTERRUPT System call inturrupted by a signal
CS_ERR_NOT_SUPPORTED The requested protocol/functuality not supported
CS_ERR_MESSAGE_ERROR Incorrect auth message received
CS_ERR_NO_MEMORY Not enough memory to completed the requested task
SEE ALSO
votequorum_overview(8), votequorum_initialize(3), votequorum_finalize(3), votequorum_getinfo(3), votequorum_trackstart(3), votequo-
rum_trackstop(3), votequorum_fd_get(3), votequorum_dispatch(3), votequorum_context_set(3), votequorum_context_get(3), votequorum_setex-
pected(3), votequorum_setvotes(3), votequorum_qdevice_unregister(3), votequorum_qdevice_poll(3), votequorum_qdevice_update(3), votequo-
rum_qdevice_master_wins(3)
corosync Man Page 2014-06-10 VOTEQUORUM_QDEVICE_REGISTER(3)