[CentOS] Forget SMB password immediately
Hi, I'm new to CentOS and also on the list, since I usually work with Debian. My problem is as follows: I have a NAS where users connect to do their backups. Each user has a folder shared where only he can enter. Multiple users get connected from a CentOS 5.7 to the NAS, each in its shared folder. I connect to the NAS by entering the login, password and shared folder of user A (here I connect through SMB port 445) and I get disconnected by removing the volume. I re-connect in the same way with the user B and then disconnect. Now if I connect with any user without entering the shared folder (I get a netbios connection to port 139) I can enter to the shared folder of user A and B without entering their credentials. A netstat -an shows me a connection to port 139 and 445 per user. After a while (too I think) connections over ports 445 and 139 are automatically cuted and I have to authenticate again. How I can force always the request of login and password? Thanks in advance. -- Francesc Guitart ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Forget SMB password immediately
Le 23/11/2011 12:11, Guitart Francesc a écrit : > Hi, > > I'm new to CentOS and also on the list, since I usually work with Debian. My > problem is as follows: > > I have a NAS where users connect to do their backups. Each user has a folder > shared where only he can enter. Multiple users get connected from a CentOS > 5.7 to the NAS, each in its shared folder. > > I connect to the NAS by entering the login, password and shared folder of > user A (here I connect through SMB port 445) and I get disconnected by > removing the volume. I re-connect in the same way with the user B and then > disconnect. > > Now if I connect with any user without entering the shared folder (I get a > netbios connection to port 139) I can enter to the shared folder of user A > and B without entering their credentials. > In fact I have explained wrong. This time I log in from any window File >> Go to .. (I don't know the exact translation in english cause I'm in one french computer) and type smb://nas_name. I can access to the NAS and I can enter all the shared folders of all users that I previously had been logged from "Connect to server" Thanks again. -- Francesc Guitart ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 81, Issue 11
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
Today's Topics:
1. CEBA-2011:1477 CentOS 5 i386 system-config-nfsFASTTRACK
Update (Johnny Hughes)
2. CEBA-2011:1477 CentOS 5 x86_64 system-config-nfs FASTTRACK
Update (Johnny Hughes)
--
Message: 1
Date: Wed, 23 Nov 2011 11:42:38 +
From: Johnny Hughes
Subject: [CentOS-announce] CEBA-2011:1477 CentOS 5 i386
system-config-nfs FASTTRACK Update
To: centos-annou...@centos.org
Message-ID: <2023114238.ga24...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Bugfix Advisory 2011:1477
Upstream details at : http://rhn.redhat.com/errata/RHBA-2011-1477.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( md5sum Filename )
i386:
a1d7506340a43ca8c2e65709f90f60b6 system-config-nfs-1.3.23-2.el5.noarch.rpm
Source:
164b0ff793934e60dc2ea6e438d13340 system-config-nfs-1.3.23-2.el5.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
--
Message: 2
Date: Wed, 23 Nov 2011 11:42:39 +
From: Johnny Hughes
Subject: [CentOS-announce] CEBA-2011:1477 CentOS 5 x86_64
system-config-nfs FASTTRACK Update
To: centos-annou...@centos.org
Message-ID: <2023114239.ga24...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Bugfix Advisory 2011:1477
Upstream details at : http://rhn.redhat.com/errata/RHBA-2011-1477.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( md5sum Filename )
x86_64:
a1d7506340a43ca8c2e65709f90f60b6 system-config-nfs-1.3.23-2.el5.noarch.rpm
Source:
164b0ff793934e60dc2ea6e438d13340 system-config-nfs-1.3.23-2.el5.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
--
___
CentOS-announce mailing list
centos-annou...@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
End of CentOS-announce Digest, Vol 81, Issue 11
***
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] Corosync init-script broken on CentOS6
Hello all, I am trying to create a corosync/pacemaker cluster using CentOS 6.0. However, I'm having a great deal of difficulty doing so. Corosync has a valid configuration file and an authkey has been generated. When I run /etc/init.d/corosync I see that only corosync is started. >From experience working with corosync/pacemaker before, I know that this is not enough to have a functioning cluster. For some reason the base install (with or without updates) is not starting corosync dependencies. I've even tried using corosync/pacemaker for the EPEL 6 repo, and still the init-script will not start corosync dependencies. Expected: corosync /usr/lib64/heartbeat/stonithd /usr/lib64/heartbeat/cib /usr/lib64/heartbeat/lrmd /usr/lib64/heartbeat/attrd /usr/lib64/heartbeat/pengine Observed: corosync My install options are: %packages @base @core @ha @nfs-file-server @network-file-system-client @resilient-storage @server-platform @server-policy @storage-client-multipath @system-admin-tools pax oddjob sgpio pacemaker dlm-pcmk screen lsscsi -rgmanager %end The logs from the server aren't terribly helpful either: Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: Forked child 2515 for process stonith-ng Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: Forked child 2516 for process cib Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: Forked child 2517 for process lrmd Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: Forked child 2518 for process attrd Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: Forked child 2519 for process pengine Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: Forked child 2520 for process crmd Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine loaded: Pacemaker Cluster Manager 1.1.2 Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine loaded: corosync extended virtual synchrony service Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine loaded: corosync configuration service Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine loaded: corosync cluster config database access v1.01 Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine loaded: corosync profile loading service Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 Nov 23 12:13:45 cheapo4 corosync[2509]: [MAIN ] Compatibility mode set to whitetank. Using V1 and V2 of the synchronization engine. Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: pcmk_wait_dispatch: Child process lrmd exited (pid=2517, rc=100) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: pcmk_wait_dispatch: Child process lrmd no longer wishes to be respawned Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: update_member: Node cheapo4.jrz.cbn now has process list: 00111302 (1118978) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: pcmk_wait_dispatch: Child process cib exited (pid=2516, rc=100) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: pcmk_wait_dispatch: Child process cib no longer wishes to be respawned Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: update_member: Node cheapo4.jrz.cbn now has process list: 00111202 (1118722) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: pcmk_wait_dispatch: Child process crmd exited (pid=2520, rc=100) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: pcmk_wait_dispatch: Child process crmd no longer wishes to be respawned Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: update_member: Node cheapo4.jrz.cbn now has process list: 00111002 (1118210) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: pcmk_wait_dispatch: Child process attrd exited (pid=2518, rc=100) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: pcmk_wait_dispatch: Child process attrd no longer wishes to be respawned Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: update_member: Node cheapo4.jrz.cbn now has process list: 00110002 (1114114) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: pcmk_wait_dispatch: Child process pengine exited (pid=2519, rc=100) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: pcmk_wait_dispatch: Child process pengine no longer wishes to be respawned Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: update_member: Node cheapo4.jrz.cbn now has process list: 0012 (1048578) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: pcmk_wait_dispatch: Child process stonith-ng exited (pid=2515, rc=100) Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: pcmk_wait_dispatch: Child process stonith-ng no longer
[CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
I tried several ways but still no help. The following are the output (stock Centos 6 2.6.32-71.29.1.el6.x86_64 kernel), grub works fine and it located kernel and initial ramdisk. but kernel booting faied at the very beginning... Any suggestions are more than appreciated. -- 2011-11-23T17:19:21+ Xen Minimal OS! start_info: 0x189(VA) nr_pages: 0x1e shared_inf: 0xb2cea000(MA) pt_base: 0x1893000(VA) nr_pt_frames: 0x11 mfn_list: 0x99(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: root=/dev/sda1 ro 4 stack: 0x94f860-0x96f860 MM: Init _text: 0x0(VA) _etext: 0x6000d(VA) _erodata: 0x78000(VA) _edata: 0x80b00(VA) stack start: 0x94f860(VA) _end: 0x98fe68(VA) start_pfn: 18a7 max_pfn: 1e Mapping memory range 0x1c0 - 0x1e000 setting 0x0-0x78000 readonly skipped 0x1000 MM: Initialise page allocator for 27a(27a)-1e000(1e000) MM: done Demand map pfns at 1e0001000-21e0001000. Heap resides at 21e0002000-41e0002000. Initialising timer interface Initialising console ... done. gnttab_table mapped at 0x1e0001000. Initialising scheduler Thread "Idle": pointer: 0x21e0002010, stack: 0x36f Initialising xenbus Thread "xenstore": pointer: 0x21e00027c0, stack: 0x370 Dummy main: start_info=0x96f960 Thread "main": pointer: 0x21e0002f70, stack: 0x371 "main" "root=/dev/sda1" "ro" "4" vbd 2049 is hd0 *** BLKFRONT for device/vbd/2049 ** backend at /local/domain/0/backend/vbd/162/2049 Failed to read /local/domain/0/backend/vbd/162/2049/feature-barrier. Failed to read /local/domain/0/backend/vbd/162/2049/feature-flush-cache. 20971520 sectors of 512 bytes ** vbd 2064 is hd1 *** BLKFRONT for device/vbd/2064 ** backend at /local/domain/0/backend/vbd/162/2064 Failed to read /local/domain/0/backend/vbd/162/2064/feature-barrier. Failed to read /local/domain/0/backend/vbd/162/2064/feature-flush-cache. 880732160 sectors of 512 bytes ** vbd 2080 is hd2 *** BLKFRONT for device/vbd/2080 ** backend at /local/domain/0/backend/vbd/162/2080 Failed to read /local/domain/0/backend/vbd/162/2080/feature-barrier. Failed to read /local/domain/0/backend/vbd/162/2080/feature-flush-cache. 880732160 sectors of 512 bytes ** [H[J GNU GRUB version 0.97 (7864320K lower / 0K upper memory) [m[4;2H+-+[5;2H|[5;76H|[6;2H|[6;76H|[7;2H|[7;76H|[8;2H|[8;76H|[9;2H|[9;76H|[10;2H|[10;76H|[11;2H|[11;76H|[12;2H|[12;76H|[13;2H|[13;76H|[14;2H|[14;76H|[15;2H|[15;76H|[16;2H|[16;76H|[17;2H+-+[m Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line.[5;78H [m[7m[5;3H CentOS (2.6.32-71.29.1.el6.x86_64) [5;75H[m[m[6;3H [6;75H[m[m[7;3H [7;75H[m[m[8;3H [8;75H[m[m[9;3H [9;75H[m[m[10;3H [10;75H[m[m[11;3H [11;75H[m[m[12;3H [12;75H[m[m[13;3H [13;75H[m[m[14;3H [14;75H[m[m[15;3H [15;75H[m[m[16;3H [16;75H[m[16;78H [5;75H[23;4H The highlighted entry will be booted automatically in 5 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 4 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 3 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 2 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 1 seconds. [5;75H[H[J Booting 'CentOS (2.6.32-71.29.1.el6.x86_64)' root (hd0) Filesystem type is ext2fs, using whole disk kernel /boot/vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=/dev/sda1 rhgb quiet initrd /boot/initramfs-2.6.32-71.29.1.el6.x86_64.img close blk: backend at /local/domain/0/backend/vbd/162/2049 close blk: backend at /local/domain/0/backend/vbd/162/2064 close blk: backend at /local/domain/0/backend/vbd/162/2080 PCI: Warning: Cannot find a gap in th
Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
On 11/23/2011 11:40 AM, Robinson Tiemuqinke wrote: > I tried several ways but still no help. The following are the output (stock > Centos 6 2.6.32-71.29.1.el6.x86_64 kernel), grub works fine and it located > kernel and initial ramdisk. but kernel booting faied at the very beginning... > > Any suggestions are more than appreciated. > > > -- > > 2011-11-23T17:19:21+ > Xen Minimal OS! > start_info: 0x189(VA) > nr_pages: 0x1e > shared_inf: 0xb2cea000(MA) > pt_base: 0x1893000(VA) > nr_pt_frames: 0x11 > mfn_list: 0x99(VA) >mod_start: 0x0(VA) > mod_len: 0 >flags: 0x0 > cmd_line: root=/dev/sda1 ro 4 > stack: 0x94f860-0x96f860 > MM: Init > _text: 0x0(VA) > _etext: 0x6000d(VA) >_erodata: 0x78000(VA) > _edata: 0x80b00(VA) > stack start: 0x94f860(VA) >_end: 0x98fe68(VA) > start_pfn: 18a7 > max_pfn: 1e > Mapping memory range 0x1c0 - 0x1e000 > setting 0x0-0x78000 readonly > skipped 0x1000 > MM: Initialise page allocator for 27a(27a)-1e000(1e000) > MM: done > Demand map pfns at 1e0001000-21e0001000. > Heap resides at 21e0002000-41e0002000. > Initialising timer interface > Initialising console ... done. > gnttab_table mapped at 0x1e0001000. > Initialising scheduler > Thread "Idle": pointer: 0x21e0002010, stack: 0x36f > Initialising xenbus > Thread "xenstore": pointer: 0x21e00027c0, stack: 0x370 > Dummy main: start_info=0x96f960 > Thread "main": pointer: 0x21e0002f70, stack: 0x371 > "main" "root=/dev/sda1" "ro" "4" > vbd 2049 is hd0 > *** BLKFRONT for device/vbd/2049 ** > > > backend at /local/domain/0/backend/vbd/162/2049 > Failed to read /local/domain/0/backend/vbd/162/2049/feature-barrier. > Failed to read /local/domain/0/backend/vbd/162/2049/feature-flush-cache. > 20971520 sectors of 512 bytes > ** > vbd 2064 is hd1 > *** BLKFRONT for device/vbd/2064 ** > > > backend at /local/domain/0/backend/vbd/162/2064 > Failed to read /local/domain/0/backend/vbd/162/2064/feature-barrier. > Failed to read /local/domain/0/backend/vbd/162/2064/feature-flush-cache. > 880732160 sectors of 512 bytes > ** > vbd 2080 is hd2 > *** BLKFRONT for device/vbd/2080 ** > > > backend at /local/domain/0/backend/vbd/162/2080 > Failed to read /local/domain/0/backend/vbd/162/2080/feature-barrier. > Failed to read /local/domain/0/backend/vbd/162/2080/feature-flush-cache. > 880732160 sectors of 512 bytes > ** > [H[J > GNU GRUB version 0.97 (7864320K lower / 0K upper memory) > > [m[4;2H+-+[5;2H|[5;76H|[6;2H|[6;76H|[7;2H|[7;76H|[8;2H|[8;76H|[9;2H|[9;76H|[10;2H|[10;76H|[11;2H|[11;76H|[12;2H|[12;76H|[13;2H|[13;76H|[14;2H|[14;76H|[15;2H|[15;76H|[16;2H|[16;76H|[17;2H+-+[m > Use the ^ and v keys to select which entry is highlighted. > Press enter to boot the selected OS, 'e' to edit the > commands before booting, or 'c' for a command-line.[5;78H [m[7m[5;3H > CentOS (2.6.32-71.29.1.el6.x86_64) > [5;75H[m[m[6;3H > [6;75H[m[m[7;3H > [7;75H[m[m[8;3H > [8;75H[m[m[9;3H > > [9;75H[m[m[10;3H > [10;75H[m[m[11;3H > [11;75H[m[m[12;3H > [12;75H[m[m[13;3H > [13;75H[m[m[14;3H > > [14;75H[m[m[15;3H > [15;75H[m[m[16;3H > [16;75H[m[16;78H [5;75H[23;4H The highlighted entry > will be booted automatically in 5 seconds. [5;75H[23;4H The highlighted > entry will be booted automatically in 4 seconds. [5;75H[23;4H The > highlighted entry will be booted automatically in 3 seconds. [5;75H[23;4H > The highlighted entry will be booted automatically in 2 seconds. > [5;75H[23;4H The highlighted entry will be booted automatically in 1 seconds. > [5;75H[H[J Booting 'CentOS (2.6.32-71.29.1.el6.x86_64)' > > root (hd0) > Filesystem type is ext2fs, using whole disk > > kernel /boot/vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=/dev/sda1 rhgb quiet > initrd
Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
Hi Johnny, Thanks a lot. I'll upgrade kernel to the cr repository, and give it a try now. --Guolin From: Johnny Hughes To: centos@centos.org Sent: Wednesday, November 23, 2011 9:55 AM Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6? On 11/23/2011 11:40 AM, Robinson Tiemuqinke wrote: > I tried several ways but still no help. The following are the output (stock > Centos 6 2.6.32-71.29.1.el6.x86_64 kernel), grub works fine and it located > kernel and initial ramdisk. but kernel booting faied at the very beginning... > > Any suggestions are more than appreciated. > > > -- > > 2011-11-23T17:19:21+ > Xen Minimal OS! > start_info: 0x189(VA) > nr_pages: 0x1e > shared_inf: 0xb2cea000(MA) > pt_base: 0x1893000(VA) > nr_pt_frames: 0x11 > mfn_list: 0x99(VA) > mod_start: 0x0(VA) > mod_len: 0 > flags: 0x0 > cmd_line: root=/dev/sda1 ro 4 > stack: 0x94f860-0x96f860 > MM: Init > _text: 0x0(VA) > _etext: 0x6000d(VA) > _erodata: 0x78000(VA) > _edata: 0x80b00(VA) > stack start: 0x94f860(VA) > _end: 0x98fe68(VA) > start_pfn: 18a7 > max_pfn: 1e > Mapping memory range 0x1c0 - 0x1e000 > setting 0x0-0x78000 readonly > skipped 0x1000 > MM: Initialise page allocator for 27a(27a)-1e000(1e000) > MM: done > Demand map pfns at 1e0001000-21e0001000. > Heap resides at 21e0002000-41e0002000. > Initialising timer interface > Initialising console ... done. > gnttab_table mapped at 0x1e0001000. > Initialising scheduler > Thread "Idle": pointer: 0x21e0002010, stack: 0x36f > Initialising xenbus > Thread "xenstore": pointer: 0x21e00027c0, stack: 0x370 > Dummy main: start_info=0x96f960 > Thread "main": pointer: 0x21e0002f70, stack: 0x371 > "main" "root=/dev/sda1" "ro" "4" > vbd 2049 is hd0 > *** BLKFRONT for device/vbd/2049 ** > > > backend at /local/domain/0/backend/vbd/162/2049 > Failed to read /local/domain/0/backend/vbd/162/2049/feature-barrier. > Failed to read /local/domain/0/backend/vbd/162/2049/feature-flush-cache. > 20971520 sectors of 512 bytes > ** > vbd 2064 is hd1 > *** BLKFRONT for device/vbd/2064 ** > > > backend at /local/domain/0/backend/vbd/162/2064 > Failed to read /local/domain/0/backend/vbd/162/2064/feature-barrier. > Failed to read /local/domain/0/backend/vbd/162/2064/feature-flush-cache. > 880732160 sectors of 512 bytes > ** > vbd 2080 is hd2 > *** BLKFRONT for device/vbd/2080 ** > > > backend at /local/domain/0/backend/vbd/162/2080 > Failed to read /local/domain/0/backend/vbd/162/2080/feature-barrier. > Failed to read /local/domain/0/backend/vbd/162/2080/feature-flush-cache. > 880732160 sectors of 512 bytes > ** > [H[J > GNU GRUB version 0.97 (7864320K lower / 0K upper memory) > > [m[4;2H+-+[5;2H|[5;76H|[6;2H|[6;76H|[7;2H|[7;76H|[8;2H|[8;76H|[9;2H|[9;76H|[10;2H|[10;76H|[11;2H|[11;76H|[12;2H|[12;76H|[13;2H|[13;76H|[14;2H|[14;76H|[15;2H|[15;76H|[16;2H|[16;76H|[17;2H+-+[m > Use the ^ and v keys to select which entry is highlighted. > Press enter to boot the selected OS, 'e' to edit the > commands before booting, or 'c' for a command-line.[5;78H [m[7m[5;3H >CentOS (2.6.32-71.29.1.el6.x86_64) >[5;75H[m[m[6;3H > [6;75H[m[m[7;3H > [7;75H[m[m[8;3H > [8;75H[m[m[9;3H > > [9;75H[m[m[10;3H > [10;75H[m[m[11;3H > [11;75H[m[m[12;3H > [12;75H[m[m[13;3H > [13;75H[m[m[14;3H > > [14;75H[m[m[15;3H > [15;75H[m[m[16;3H > [16;75H[m[16;78H [5;75H[23;4H The highlighted entry >will be booted automatically in 5 seconds. [5;75H[23;4H The highlighted >entry will be booted automatically in 4 seconds. [5;75H[23;4H The >highlighted entry will be booted automatically in 3 seconds. [5;75H[23;4H >The highlighted entry will be booted automatically in 2 seconds. >[5;75H[2
Re: [CentOS] Forget SMB password immediately
On 11/23/11 3:11 AM, Guitart Francesc wrote: > here I connect through SMB port 445 why in dogs name are you using SMB, a Microsoft Windows protocol, for Unix to NAS file sharing? Unix systems should use NFS for file sharing. netbios is a tangled mess of poorly planned protocols with extensions on the extensions, and warts on the warts (ports 137/138/139 were old NetBIOS, using NetBIOS-over-TCP aka NBT as the transport, while port 445 is the newer native CIFS protocol introduced around Windows2000 time). with NFS, you'd mount the backup directory somewhere, like /nfsbackups just once at bootup time and each user would have their own directory in it, /nfsbackusp/fred (or whatever) and only have read/write access to that directory, managed via standard unix style chmod, chown ... -- john r pierceN 37, W 122 santa cruz ca mid-left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] SSD diagnostics / test suite?
Hey folks, I looked back through the list archives and there are surprisingly few threads with "SSD" in the subject. In my new job I've been handed over a number of things that were outstanding with the previous Sys Admin, and one of them was an SSD that was suspect. I just plugged it into a diagnostics laptop to use the Linux Smart software to check it - and it all seems fine even after running the disk test suite from the GUI. In digging for more info I discovered that the errors were actually coming from the RAID controller - and the SSD has obviously been removed from there for the time being. While I have it in my hands I'd like to do some kind of complete test / diagnostics suite on it. Preferably Linux based since that's what we have here. I found a few windows-based tools with my googling. I did stumble upon this page which looks like it has a few useful tips for using SSDs on Linux http://danweinreb.org/blog/using-solid-state-disks-on-linux Now, what about comprehensive suites? Should I just run some IO suites on it like bonnie++ or something like that, and see what SMART says in the process? I'm suspecting the RAID controller at this point ... but want to be as thorough as possible while I have it in my hands. cheers, -Alan -- “Don't eat anything you've ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food" ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
I've tried with cr kernel, not it moves much faster but still fails -- fails at the partition failure, this setup is S3 backed image. root (hd0) Filesystem type is ext2fs, using whole disk kernel /boot/vmlinuz-2.6.32-131.17.1.el6.x86_64 ro root=/dev/sda1 rd_NO_LUKS rd _NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTY PE=pc KEYTABLE=us crashkernel=auto crashkernel=auto initrd /boot/initramfs-2.6.32-131.17.1.el6.x86_64.img close blk: backend at /local/domain/0/backend/vbd/8/2049 close blk: backend at /local/domain/0/backend/vbd/8/2064 close blk: backend at /local/domain/0/backend/vbd/8/2080 close blk: backend at /local/domain/0/backend/vbd/8/2096 close blk: backend at /local/domain/0/backend/vbd/8/2112 Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.32-131.17.1.el6.x86_64 (mockbu...@c6b5.bsys.dev.centos.org) (gcc version 4.4.5 20110214 (Red Hat 4.4.5-6) (GCC) ) #1 SMP Thu Oct 6 19:24:09 BST 2011 Command line: ro root=/dev/sda1 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto crashkernel=auto KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls ACPI in unprivileged domain disabled BIOS-provided physical RAM map: Xen: - 000a (usable) Xen: 000a - 0010 (reserved) Xen: 0010 - 0001c000 (usable) DMI not present or invalid. last_pfn = 0x1c max_arch_pfn = 0x4 last_pfn = 0x10 max_arch_pfn = 0x4 init_memory_mapping: -0001 init_memory_mapping: 0001-0001c000 RAMDISK: 02028000 - 0460c000 No NUMA configuration found Faking a node at -0001c000 Bootmem setup node 0 -0001c000 NODE_DATA [8000 - 0003bfff] bootmap [0003c000 - 00073fff] pages 38 (8 early reservations) ==> bootmem [00 - 01c000] #0 [00 - 001000] BIOS data page ==> [00 - 001000] #1 [000540f000 - 000543e000] XEN PAGETABLES ==> [000540f000 - 000543e000] #2 [006000 - 008000] TRAMPOLINE ==> [006000 - 008000] #3 [000100 - 0002007524] TEXT DATA BSS ==> [000100 - 0002007524] #4 [0002028000 - 000460c000] RAMDISK ==> [0002028000 - 000460c000] #5 [000460c000 - 000540f000] XEN START INFO ==> [000460c000 - 000540f000] #6 [10 - 8d3000] PGTABLE ==> [10 - 8d3000] #7 [000543e000 - 0005a41000] PGTABLE ==> [000543e000 - 0005a41000] Reserving 129MB of memory at 96MB for crashkernel (System RAM: 7168MB) Zone PFN ranges: DMA 0x0001 -> 0x1000 DMA32 0x1000 -> 0x0010 Normal 0x0010 -> 0x001c Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0x0001 -> 0x00a0 0: 0x0100 -> 0x001c SFI: Simple Firmware Interface v0.7 http://simplefirmware.org SMP: Allowing 8 CPUs, 0 hotplug CPUs No local APIC present APIC: disable apic facility PM: Registered nosave memory: 000a - 0010 PCI: Warning: Cannot find a gap in the 32bit address range PCI: Unassigned devices with 32bit resource registers may break! Allocating PCI resources starting at 1c010 (gap: 1c010:40) Booting paravirtualized kernel on Xen Xen version: 3.4.3-2.6.18 (preserve-AD) NR_CPUS:4096 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1 PERCPU: Embedded 30 pages/cpu @88002804f000 s92504 r8192 d22184 u122880 pcpu-alloc: s92504 r8192 d22184 u122880 alloc=30*4096 pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 Xen: using vcpu_info placement Built 1 zonelists in Node order, mobility grouping on. Total pages: 1807817 Policy zone: Normal Kernel command line: ro root=/dev/sda1 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto crashkernel=129M@0M PID hash table entries: 4096 (order: 3, 32768 bytes) Checking aperture... No AGP bridge found AMD-Vi disabled by default: pass amd_iommu=on to enable PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Placing 64MB software IO TLB between 88002000 - 88002400 software IO TLB at phys 0x2000 - 0x2400 Memory: 6955572k/7340032k available (5013k kernel code, 388k absent, 384072k reserved, 7291k data, 1232k init) Hierarchical RCU implementation. NR_IRQS:33024 nr_irqs:336 Console: colour dummy device 80x25 console [tty0] enabled console [hvc0] enabled ... TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 17 registered taskstats version 1 XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2064 XENBUS: Device with no driver: device/vbd/2080 XENBUS: Device with no driver: device/vbd/2096 XENBUS: Device with no driver: device/vbd/2112 XENBUS: Device wit
Re: [CentOS] Corosync init-script broken on CentOS6
Hi, Did you configure corosync ? Normally corosync starts pacemaker, which in turn starts the heartbeat deamons. But you have to configure the latter using for example a pcmk file with configuration in /etc/corosync/conf.d/ (from the top of my head). I normally use : http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ Regards, Michel On Wed, 2011-11-23 at 12:16 -0500, Hal Martin wrote: > Hello all, > > I am trying to create a corosync/pacemaker cluster using CentOS 6.0. > However, I'm having a great deal of difficulty doing so. > > Corosync has a valid configuration file and an authkey has been generated. > > When I run /etc/init.d/corosync I see that only corosync is started. > >From experience working with corosync/pacemaker before, I know that > this is not enough to have a functioning cluster. For some reason the > base install (with or without updates) is not starting corosync > dependencies. > > I've even tried using corosync/pacemaker for the EPEL 6 repo, and > still the init-script will not start corosync dependencies. > > Expected: > corosync > /usr/lib64/heartbeat/stonithd > /usr/lib64/heartbeat/cib > /usr/lib64/heartbeat/lrmd > /usr/lib64/heartbeat/attrd > /usr/lib64/heartbeat/pengine > > Observed: > corosync > > My install options are: > %packages > @base > @core > @ha > @nfs-file-server > @network-file-system-client > @resilient-storage > @server-platform > @server-policy > @storage-client-multipath > @system-admin-tools > pax > oddjob > sgpio > pacemaker > dlm-pcmk > screen > lsscsi > -rgmanager > %end > > The logs from the server aren't terribly helpful either: > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > Forked child 2515 for process stonith-ng > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > Forked child 2516 for process cib > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > Forked child 2517 for process lrmd > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > Forked child 2518 for process attrd > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > Forked child 2519 for process pengine > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > Forked child 2520 for process crmd > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > loaded: Pacemaker Cluster Manager 1.1.2 > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > loaded: corosync extended virtual synchrony service > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > loaded: corosync configuration service > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > loaded: corosync cluster closed process group service v1.01 > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > loaded: corosync cluster config database access v1.01 > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > loaded: corosync profile loading service > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > loaded: corosync cluster quorum service v0.1 > Nov 23 12:13:45 cheapo4 corosync[2509]: [MAIN ] Compatibility mode > set to whitetank. Using V1 and V2 of the synchronization engine. > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: > pcmk_wait_dispatch: Child process lrmd exited (pid=2517, rc=100) > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: > pcmk_wait_dispatch: Child process lrmd no longer wishes to be > respawned > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: > update_member: Node cheapo4.jrz.cbn now has process list: > 00111302 (1118978) > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: > pcmk_wait_dispatch: Child process cib exited (pid=2516, rc=100) > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: > pcmk_wait_dispatch: Child process cib no longer wishes to be respawned > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: > update_member: Node cheapo4.jrz.cbn now has process list: > 00111202 (1118722) > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: > pcmk_wait_dispatch: Child process crmd exited (pid=2520, rc=100) > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: > pcmk_wait_dispatch: Child process crmd no longer wishes to be > respawned > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: > update_member: Node cheapo4.jrz.cbn now has process list: > 00111002 (1118210) > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: > pcmk_wait_dispatch: Child process attrd exited (pid=2518, rc=100) > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: > pcmk_wait_dispatch: Child process attrd no longer wishes to be > respawned > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: > update_member: Node cheapo4.jrz.cbn now has process list: > 00110002 (1114114) > Nov
Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
Robinson Tiemuqinke wrote: > I've tried with cr kernel, not it moves much faster but still fails -- > fails at the partition failure, this setup is S3 backed image. > > root (hd0) > Filesystem type is ext2fs, using whole disk > kernel /boot/vmlinuz-2.6.32-131.17.1.el6.x86_64 ro root=/dev/sda1 > rd_NO_LUKS rd > _NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 > KEYBOARDTY > PE=pc KEYTABLE=us crashkernel=auto crashkernel=auto > initrd /boot/initramfs-2.6.32-131.17.1.el6.x86_64.img > xvdf: > unknown partition table > blkfront: xvdg: barriers disabled > xvdg: unknown partition table > blkfront: xvdh: barriers disabled > xvdh: unknown partition table > blkfront: xvdi: barriers disabled > xvdi: unknown partition table > > Boot has failed, sleeping forever. FUNNY you should mention that... I literally ran into that yesterday, with lots of screaming and yelling. This will sound scary, but isn't: try reinstalling, but when you get to the screen that asks you what you want to do, select the radio button for "upgrade", which says it does *not* format the partition(s). I did that - I had rsync'd / and /boot from another server, identical, with Linux software RAID. Bad mistake - best guess is there are some magic numbers in initrd - so I did this. It only took a couple of minutes, and seemed to not do much more than reinstall grub and some post-install scripts, and everything was wonderful. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
Hi Mark, Would you mind to elaborate your steps of fixing? I'm using 'yum groupinstall --installroot=/ ...' method, then Install(not update) the newest kernel from cr/ repository. Did you rebuild initial ramdisk? If so, what's your command to do that? Thanks a lot. --Rob From: "m.r...@5-cent.us" To: CentOS mailing list Sent: Wednesday, November 23, 2011 11:47 AM Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6? Robinson Tiemuqinke wrote: > I've tried with cr kernel, not it moves much faster but still fails -- > fails at the partition failure, this setup is S3 backed image. > > root (hd0) > Filesystem type is ext2fs, using whole disk > kernel /boot/vmlinuz-2.6.32-131.17.1.el6.x86_64 ro root=/dev/sda1 > rd_NO_LUKS rd > _NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 > KEYBOARDTY > PE=pc KEYTABLE=us crashkernel=auto crashkernel=auto > initrd /boot/initramfs-2.6.32-131.17.1.el6.x86_64.img > xvdf: > unknown partition table > blkfront: xvdg: barriers disabled > xvdg: unknown partition table > blkfront: xvdh: barriers disabled > xvdh: unknown partition table > blkfront: xvdi: barriers disabled > xvdi: unknown partition table > > Boot has failed, sleeping forever. FUNNY you should mention that... I literally ran into that yesterday, with lots of screaming and yelling. This will sound scary, but isn't: try reinstalling, but when you get to the screen that asks you what you want to do, select the radio button for "upgrade", which says it does *not* format the partition(s). I did that - I had rsync'd / and /boot from another server, identical, with Linux software RAID. Bad mistake - best guess is there are some magic numbers in initrd - so I did this. It only took a couple of minutes, and seemed to not do much more than reinstall grub and some post-install scripts, and everything was wonderful. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
Hi, Rob, Robinson Tiemuqinke wrote: > > Would you mind to elaborate your steps of fixing? > > I'm using 'yum groupinstall --installroot=/ ...' method, then > Install(not update) the newest kernel from cr/ repository. > > Did you rebuild initial ramdisk? If so, what's your command to do that? > Thanks a lot. No, I wasn't using a command line, because I couldn't get the sucker to boot, even though when I did what it told me to do on panic - add rdshell to the kernel line before booting - I could manually assemble the RAIDs, but then it wouldn't mount. I *literally* started an install (I had a PXEboot one available) with no ks file. About three or four screens in, it presented me with a set of options to install (wipe everything), or... forget what the second option was, and the third was "upgrade", and it showed a dropdown list (which, for me, only had one entry) of the one I'd installed. I chose that, and then clicked for go, and from that point, it was literally about two minutes, and it installed grub, then did some post-install scripts of its own, and told me it was time to reboot. mark > > --Rob > > > > > From: "m.r...@5-cent.us" > To: CentOS mailing list > Sent: Wednesday, November 23, 2011 11:47 AM > Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos > 6? > > Robinson Tiemuqinke wrote: >> I've tried with cr kernel, not it moves much faster but still fails -- >> fails at the partition failure, this setup is S3 backed image. >> >> root (hd0) >> Filesystem type is ext2fs, using whole disk >> kernel /boot/vmlinuz-2.6.32-131.17.1.el6.x86_64 ro root=/dev/sda1 >> rd_NO_LUKS rd >> _NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 >> KEYBOARDTY >> PE=pc KEYTABLE=us crashkernel=auto crashkernel=auto >> initrd /boot/initramfs-2.6.32-131.17.1.el6.x86_64.img > >> xvdf: >> unknown partition table >> blkfront: xvdg: barriers disabled >> xvdg: unknown partition table >> blkfront: xvdh: barriers disabled >> xvdh: unknown partition table >> blkfront: xvdi: barriers disabled >> xvdi: unknown partition table >> >> Boot has failed, sleeping forever. > > FUNNY you should mention that... I literally ran into that yesterday, with > lots of screaming and yelling. This will sound scary, but isn't: try > reinstalling, but when you get to the screen that asks you what you want > to do, select the radio button for "upgrade", which says it does *not* > format the partition(s). I did that - I had rsync'd / and /boot from > another server, identical, with Linux software RAID. Bad mistake - best > guess is there are some magic numbers in initrd - so I did this. It only > took a couple of minutes, and seemed to not do much more than reinstall > grub and some post-install scripts, and everything was wonderful. > > mark > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
Hi Mark, John and all, Finally got it work! hew.. The last part which makes the difference is change the /dev/sda1 to /dev/xvde1 in files /boot/grub/menu.lst and /etc/fstab. the file system type set to 'ext2' (from ext3) for /dev/xvde1 as well -- this is a S3 backed AMI image. There is no need to re-create initial ramdisk if you use the newest kernel 2.6.32-131.17.1.el6.x86_64 from cr/ depository, all xen block&net modules seems already included -- please someone double check it to comfirm/deny, I'm just too tired now. Thanks again for all your time and efforts and wish your all have a great long holiday weekend. --Rob From: Robinson Tiemuqinke To: CentOS mailing list Sent: Wednesday, November 23, 2011 11:55 AM Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6? Hi Mark, Would you mind to elaborate your steps of fixing? I'm using 'yum groupinstall --installroot=/ ...' method, then Install(not update) the newest kernel from cr/ repository. Did you rebuild initial ramdisk? If so, what's your command to do that? Thanks a lot. --Rob From: "m.r...@5-cent.us" To: CentOS mailing list Sent: Wednesday, November 23, 2011 11:47 AM Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6? Robinson Tiemuqinke wrote: > I've tried with cr kernel, not it moves much faster but still fails -- > fails at the partition failure, this setup is S3 backed image. > > root (hd0) > Filesystem type is ext2fs, using whole disk > kernel /boot/vmlinuz-2.6.32-131.17.1.el6.x86_64 ro root=/dev/sda1 > rd_NO_LUKS rd > _NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 > KEYBOARDTY > PE=pc KEYTABLE=us crashkernel=auto crashkernel=auto > initrd /boot/initramfs-2.6.32-131.17.1.el6.x86_64.img > xvdf: > unknown partition table > blkfront: xvdg: barriers disabled > xvdg: unknown partition table > blkfront: xvdh: barriers disabled > xvdh: unknown partition table > blkfront: xvdi: barriers disabled > xvdi: unknown partition table > > Boot has failed, sleeping forever. FUNNY you should mention that... I literally ran into that yesterday, with lots of screaming and yelling. This will sound scary, but isn't: try reinstalling, but when you get to the screen that asks you what you want to do, select the radio button for "upgrade", which says it does *not* format the partition(s). I did that - I had rsync'd / and /boot from another server, identical, with Linux software RAID. Bad mistake - best guess is there are some magic numbers in initrd - so I did this. It only took a couple of minutes, and seemed to not do much more than reinstall grub and some post-install scripts, and everything was wonderful. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Corosync init-script broken on CentOS6
Am 23.11.2011 14:24 schrieb "Michel van Deventer" : > > Hi, > > Did you configure corosync ? > Normally corosync starts pacemaker, which in turn starts the heartbeat > deamons. > But you have to configure the latter using for example a pcmk file with > configuration in /etc/corosync/conf.d/ (from the top of my head). Yes. /etc/corosync/services.d/pcmk is configured as per that document; still not getting the expected start behaviour. Corosync does start properly, just not via the init-script. Thanks, -Hal > I normally use : > http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ > >Regards, > >Michel > > On Wed, 2011-11-23 at 12:16 -0500, Hal Martin wrote: > > Hello all, > > > > I am trying to create a corosync/pacemaker cluster using CentOS 6.0. > > However, I'm having a great deal of difficulty doing so. > > > > Corosync has a valid configuration file and an authkey has been generated. > > > > When I run /etc/init.d/corosync I see that only corosync is started. > > >From experience working with corosync/pacemaker before, I know that > > this is not enough to have a functioning cluster. For some reason the > > base install (with or without updates) is not starting corosync > > dependencies. > > > > I've even tried using corosync/pacemaker for the EPEL 6 repo, and > > still the init-script will not start corosync dependencies. > > > > Expected: > > corosync > > /usr/lib64/heartbeat/stonithd > > /usr/lib64/heartbeat/cib > > /usr/lib64/heartbeat/lrmd > > /usr/lib64/heartbeat/attrd > > /usr/lib64/heartbeat/pengine > > > > Observed: > > corosync > > > > My install options are: > > %packages > > @base > > @core > > @ha > > @nfs-file-server > > @network-file-system-client > > @resilient-storage > > @server-platform > > @server-policy > > @storage-client-multipath > > @system-admin-tools > > pax > > oddjob > > sgpio > > pacemaker > > dlm-pcmk > > screen > > lsscsi > > -rgmanager > > %end > > > > The logs from the server aren't terribly helpful either: > > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > > Forked child 2515 for process stonith-ng > > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > > Forked child 2516 for process cib > > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > > Forked child 2517 for process lrmd > > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > > Forked child 2518 for process attrd > > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > > Forked child 2519 for process pengine > > Nov 23 12:13:45 cheapo4 corosync[2509]: [pcmk ] info: spawn_child: > > Forked child 2520 for process crmd > > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > > loaded: Pacemaker Cluster Manager 1.1.2 > > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > > loaded: corosync extended virtual synchrony service > > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > > loaded: corosync configuration service > > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > > loaded: corosync cluster closed process group service v1.01 > > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > > loaded: corosync cluster config database access v1.01 > > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > > loaded: corosync profile loading service > > Nov 23 12:13:45 cheapo4 corosync[2509]: [SERV ] Service engine > > loaded: corosync cluster quorum service v0.1 > > Nov 23 12:13:45 cheapo4 corosync[2509]: [MAIN ] Compatibility mode > > set to whitetank. Using V1 and V2 of the synchronization engine. > > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: > > pcmk_wait_dispatch: Child process lrmd exited (pid=2517, rc=100) > > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: > > pcmk_wait_dispatch: Child process lrmd no longer wishes to be > > respawned > > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: > > update_member: Node cheapo4.jrz.cbn now has process list: > > 00111302 (1118978) > > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: > > pcmk_wait_dispatch: Child process cib exited (pid=2516, rc=100) > > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: > > pcmk_wait_dispatch: Child process cib no longer wishes to be respawned > > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: > > update_member: Node cheapo4.jrz.cbn now has process list: > > 00111202 (1118722) > > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] ERROR: > > pcmk_wait_dispatch: Child process crmd exited (pid=2520, rc=100) > > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] notice: > > pcmk_wait_dispatch: Child process crmd no longer wishes to be > > respawned > > Nov 23 12:13:46 cheapo4 corosync[2509]: [pcmk ] info: > > update_member: Node cheapo4.jrz.cbn now has process list: > >
