Sponsored Content
Operating Systems Solaris Precaution during Quorum Server Reboot Post 303020359 by sb200 on Tuesday 17th of July 2018 12:04:02 PM
Old 07-17-2018
Thanks Peasant for you reply


Just to confirm that... are you saying that I don't have to disable or enable the quorum devices in five clusters during the reboot activity which I mention in my first post of this thread
 

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
DLM_CONTROLD(8) 							dlm							   DLM_CONTROLD(8)

NAME
dlm_controld - dlm cluster control daemon SYNOPSIS
dlm_controld [OPTIONS] DESCRIPTION
The kernel dlm requires a user daemon to manage lockspace membership. dlm_controld manages lockspace membership using corosync cpg groups, and translates membership changes into dlm kernel recovery events. dlm_controld also manages posix locks for cluster file systems using the dlm. OPTIONS
Command line options override a corresponding setting in dlm.conf(5). For default settings, see dlm_controld -h. --daemon_debug | -D enable debugging to stderr and don't fork --foreground don't fork --log_debug | -K enable kernel dlm debugging messages --protocol | -r str dlm kernel lowcomms protocol: tcp, sctp, detect --debug_logfile | -L write debugging to log file --enable_plock | -p 0|1 enable/disable posix lock support for cluster fs --plock_debug | -P enable plock debugging --plock_rate_limit | -l int limit rate of plock operations (0 for none) --plock_ownership | -o 0|1 enable/disable plock ownership --drop_resources_time | -t int plock ownership drop resources time (milliseconds) --drop_resources_count | -c int plock ownership drop resources count --drop_resources_age | -a int plock ownership drop resources age (milliseconds) --post_join_delay | -j int seconds to delay fencing after cluster join --enable_fencing | -f 0|1 enable/disable fencing --enable_concurrent_fencing 0|1 enable/disable concurrent fencing --enable_startup_fencing | -s 0|1 enable/disable startup fencing --enable_quorum_fencing | -q 0|1 enable/disable quorum requirement for fencing --enable_quorum_lockspace 0|1 enable/disable quorum requirement for lockspace operations --fence_all str fence all nodes with this agent --unfence_all enable unfencing self with fence_all agent --help | -h print this help, then exit --version | -V Print program version information, then exit SEE ALSO
dlm_tool(8), dlm.conf(5) dlm 2012-04-05 DLM_CONTROLD(8)
All times are GMT -4. The time now is 03:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy