<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:m = "http://schemas.microsoft.com/office/2004/12/omml"><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META name=GENERATOR content="MSHTML 9.00.8112.16447"> <STYLE>@font-face { font-family: Wingdings; } @font-face { font-family: Wingdings; } @font-face { font-family: Calibri; } @font-face { font-family: Tahoma; } @font-face { font-family: LiberationMono; } @font-face { font-family: LiberationMono-Bold; } @page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.0pt; } P.MsoNormal { MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: black; FONT-SIZE: 11pt; mso-fareast-language: EN-US } LI.MsoNormal { MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: black; FONT-SIZE: 11pt; mso-fareast-language: EN-US } DIV.MsoNormal { MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; COLOR: black; FONT-SIZE: 11pt; mso-fareast-language: EN-US } A:link { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } A:visited { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.EmailStyle17 { FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal } SPAN.EmailStyle18 { FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply } .MsoChpDefault { FONT-SIZE: 10pt; mso-style-type: export-only } DIV.WordSection1 { page: WordSection1 } </STYLE> </HEAD> <BODY lang=EN-SG bgColor=white vLink=purple link=blue> <DIV>I'm not certain of your complete configuration. However looking at the entry that you placed in the volume_list. It looks like you listed the VG that is part of your cluster's resource group. However, the volume_lists should actually list all the volume groups that are not part of the cluster. </DIV> <DIV> </DIV> <DIV>The VG's in the volume_list are actually the ones that the system needs to bring up. The volume group that are part of the cluster will be brought up by rgmanager, so they should not be in volumes_list. The reason for the system panic is because the required volume groups were not listed in volume_list. So the kernel could not varyon the system VG.</DIV> <DIV> </DIV> <DIV>If I have mistakenly interprettted what you've done I'm sorry. </DIV> <BLOCKQUOTE style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"> <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV> <DIV style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black">From: <A title=shanti.pahari@sierra.sg href="mailto:shanti.pahari@sierra.sg">Shanti Pahari</A> </DIV> <DIV style="FONT: 10pt arial">To: <A title=andrewd@sterling.net href="mailto:andrewd@sterling.net">'Andrew Denton'</A> ; <A title=linux-cluster@redhat.com href="mailto:linux-cluster@redhat.com">'linux clustering'</A> </DIV> <DIV style="FONT: 10pt arial">Sent: Wednesday, October 10, 2012 9:54 PM</DIV> <DIV style="FONT: 10pt arial">Subject: Re: [Linux-cluster] cannot run cluster service</DIV> <DIV> </DIV> <DIV class=WordSection1> Hi Andrew,<o:p></o:p> <o:p> </o:p> Now I added following in my lvm.conf<o:p></o:p> volume_list = [ "vg_pdcpicpl02", "@PDC-PIC-PL-CL1", "@PDC-PIC-PL-CL2" ]<o:p></o:p> and<o:p></o:p> # dracut --hostonly --force /boot/initramfs-$(uname -r).img $(uname -r)<o:p></o:p> # shutdown -r now "Activating ramdisk LVM changes"<o:p></o:p> <o:p> </o:p> After that when the system tries to boot up:<o:p></o:p> Kernel panic – not syncing: Attempted to kill init!<o:p></o:p> <o:p> </o:p> So didn’t have luck L<o:p></o:p> <o:p> </o:p> volume_list = [ "vg_pdcpicpl02", "@PDC-PIC-PL-CL1", "@PDC-PIC-PL-CL2" ]<o:p></o:p> The hostname should be cluster connect name or initial hostname ?<o:p></o:p> My /etc/hosts:<o:p></o:p> <o:p> </o:p> 192.168.24.32 PDC-PIC-PL-01 PDC-PIC-PL-01.chcs.sg<o:p></o:p> 192.168.25.132 PDC-PIC-PL-01-PM <o:p></o:p> 192.168.26.13 PDC-PIC-PL-CL1<o:p></o:p> 192.168.24.33 PDC-PIC-PL-02 PDC-PIC-PL-02.chcs.sg<o:p></o:p> 192.168.25.133 PDC-PIC-PL-02-PM<o:p></o:p> 192.168.26.14 PDC-PIC-PL-CL2<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <DIV> <DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"> From: Andrew Denton [mailto:andrewd@sterling.net] Sent: Wednesday, 10 October, 2012 11:27 PM To: linux clustering Cc: Shanti Pahari Subject: Re: [Linux-cluster] cannot run cluster service<o:p></o:p></DIV></DIV> <o:p> </o:p> <DIV> On 10/10/2012 12:06 AM, Shanti Pahari wrote:<o:p></o:p></DIV> <BLOCKQUOTE style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt"> I have cluster setup with 2 node and created web cluster service on it but it cannot run. <o:p></o:p> I have not listed anything in lvm.conf volume_list because once I add anything in volume_list and reboot the system then I cannot mount and even cannot read the lv which I created for my web . It throws error as <o:p></o:p> error message "not activating volume group lv does not pass activation filter"<o:p></o:p> Therefore I didn’t add anything in lvm.conf . Then I try to start my cluster servers for web server but the service failed.<o:p></o:p></BLOCKQUOTE> I've seen this failure too when building my cluster. You either need to add the system's volume groups to volume_list, or tag the system's vgs with the @hostname so it can still activate them. e.g. volume_list = [ "vg_pdcpicpl01", "@PDC-PIC-PL-CL1", "@PDC-PIC-PL-CL2" ] on one node and volume_list = [ "vg_pdcpicpl02", "@PDC-PIC-PL-CL1", "@PDC-PIC-PL-CL2" ] on the other. Next it will complain about initrd being older than lvm.conf, so I've been running # mkinitrd -f /boot/initrd-`uname -r`.img `uname -r` Not sure if that's the right command but it works for me =) One of these days I'm going to tag the system's vgs properly so I can use the same lvm.conf across the nodes. I think it's something like lvchange --addtag PDC-PIC-PL-CL1 vg_pdcpicpl01/lv_root etc... By the way, to display how things are tagged, you have to do lvs -o +tags I wish it displayed them in lvdisplay, but it doesn't. -- Andrew <o:p></o:p></DIV> <HR> -- Linux-cluster mailing list Linux-cluster@redhat.com https://www.redhat.com/mailman/listinfo/linux-cluster</BLOCKQUOTE></BODY></HTML>