Sponsored Content
Operating Systems Solaris Precaution during Quorum Server Reboot Post 303020364 by DukeNuke2 on Tuesday 17th of July 2018 03:05:27 PM
Old 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

Reboot the sco server

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

Server Reboot Alert

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

server reboot

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

IP setting changes after server reboot

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

Reboot the server through console

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

Linux server reboot

We reboot our linux servers daily. Is it needed ? (10 Replies)
Discussion started by: linuxadmin
10 Replies

7. UNIX for Advanced & Expert Users

Precaution to access user mode buffers from kernel

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

Validate mountpoints on solaris server after server reboot

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

Server reboot

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
QUORUM_INITIALIZE(3)				    Corosync Cluster Engine Programmer's Manual 			      QUORUM_INITIALIZE(3)

NAME
quorum_initialize - Create a new connection to the Quorum service SYNOPSIS
#include <corosync/quorum.h> int quorum_initialize(quorum_handle_t *handle, quorum_callbacks_t *callbacks, uint32_t *quorum_type); DESCRIPTION
The quorum_initialize function is used to initialize a connection to the quorum API. Each application may have several connections to the quorum API. Each application uses the handle argument to uniquely identify the con- nection. The handle argument is then used in other function calls to identify the connection to be used for communication with the quorum service. Every time the voting configuraton changes (eg a node joins or leave the cluster) or the quorum status change, the callback is called. The callback function is described by the following type definitions: typedef void (*quorum_notification_fn_t) ( quorum_handle_t handle, uint32_t quorate, uint64_t ring_seq, uint32_t view_list_entries, uint32_t *view_list ); The callbacks argument is of the type: typedef struct { quorum_notification_fn_t quorum_notify_fn; } quorum_callbacks_t; The quorum_type argument is set to: #define QUORUM_FREE 0 #define QUORUM_SET 1 QUORUM_FREE value means that no quorum algorithm is loaded and that no callbacks will take place. QUORUM_SET value means that one quorum algorithm is configured and that callbacks will take place. When a configuration change occurs, the callback is called from the quorum_dispatch() function. 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
quorum_overview(8), quorum_finalize(3), quorum_getquorate(3), quorum_trackstart(3), quorum_trackstop(3), quorum_fd_get(3), quorum_dis- patch(3), quorum_context_set(3), quorum_context_get(3) corosync Man Page 2014-06-10 QUORUM_INITIALIZE(3)
All times are GMT -4. The time now is 08:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy