Discuss

discuss@lists.centos.org

34753 discussions

Start a nNew thread

CentOS-announce Digest, Vol 112, Issue 10
by centos-announce-request＠centos.org 21 Jun '14

21 Jun '14

1 0

ATI Rage XL Driver for Centos 6.5
by H 20 Jun '14

20 Jun '14

I have just installed Centos 6.5 on a Asus motherboard with an embedded ATI Rage XL controller (and with no room to install a more capable graphics card) and it is infuriatingly slow, running in VESA mode. Unfortunately this card is not supported "out-of-the-box" by centos 6.5 and after Googling I have not found that the kmod-fglrx-legacy driver from elrepo would work either according to its info page. Does anyone have experience with this (dated) card? Thank you. Hakan

1 1

Re: [CentOS] iptables question
by James B. Byrne 20 Jun '14

20 Jun '14

On Mon, June 16, 2014 23:34, Chuck Campbell wrote: > I appreciate you restating this. I'll try to go make sense of iptables, given > the insight, > Keep in mind that there are three default chains, INPUT, OUTPUT and FORWARD that are used to initiate the packet path through IPTABLES and that they are mutually exclusive. INPUT deals ONLY with packets that arrive from off of AND are destined for the host running IPTABLES. OUTPUT deals only with packets that originate from the host running IPTABLES regardless of where they are destined. And FORWARD deals only with packets that arrive from and are destined off of the host running IPTABLES. A packet starts in only one of these based solely on its origin/destination pairing and it does not cross over automatically into either of the others. For example, if a forwarded packet is detected then the INPUT and OUTPUT chains are not used at all. I have seen chain misconfiguration where IPTABLES rules evidently assume that a packet is to pass from the INPUT chain or the OUTPUT chain to the FORWARD chain automatically. In some cases it seems that the rules writer has implicitly assumed that INPUT -> FORWARD -> OUTPUT is the default routing of all packet paths. This is not the case and it does not happen unless the other chain is specifically called from within the originating chain. My practice is to place general rules that I wish to apply to all packets, regardless of source or destination, into a chain called GENERAL and simply call that chain as the last instruction in each of the default chains. Actually I put very little else in the default chains and route from the GENERAL chain to other chains dedicated to specific rule sets, like for port knocking (FWKNOP_ALLOW); or for assured access (ALWAYS_ALLOW); or for blacklists: ALWAYS_DENY and FAIL2BAN_DENY for example. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 2

CentOS-announce Digest, Vol 112, Issue 9
by centos-announce-request＠centos.org 20 Jun '14

20 Jun '14

Send CentOS-announce mailing list submissions to centos-announce(a)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-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)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-2014:0767 CentOS 6 hplip FASTTRACK Update (Johnny Hughes) 2. CEBA-2014:0769 CentOS 6 xz FASTTRACK Update (Johnny Hughes) 3. CEBA-2014:0768 CentOS 6 edac-utils FASTTRACK Update (Johnny Hughes) 4. CEBA-2014:0766 CentOS 6 libxml2 Update (Johnny Hughes) 5. CESA-2014:0771 Important CentOS 6 kernel Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 19 Jun 2014 11:20:34 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0767 CentOS 6 hplip FASTTRACK Update To: centos-announce(a)centos.org Message-ID: <20140619112034.GA14769(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0767 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0767.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 73b2506d8b4362e5cc7f777e9ff33d6d4e736acd0d437465087eddfa6e083af6 hpijs-3.12.4-6.el6.i686.rpm e2cc8cb9b3d406a8527253e5624ca839038f774bd621b5605d2f9a459ebc8057 hplip-3.12.4-6.el6.i686.rpm 46b88ac8b485ba062f9450ea2244730fb1e6f5349fc45dfedb091c7e3e08a38d hplip-common-3.12.4-6.el6.i686.rpm 0e3bf22971a75e75813b4b36d280b590050b98e7e417df4a4b2d644fc6dc23be hplip-gui-3.12.4-6.el6.i686.rpm ffe6923f51128ea06f09bc6640991d3fab31f0e9a9772a083e45e9f43b5efa4a hplip-libs-3.12.4-6.el6.i686.rpm b2a3fdd4a625588370090db15c8e33e862c2348017e6ca1181fe5a94d7fe07b8 libsane-hpaio-3.12.4-6.el6.i686.rpm x86_64: 837f8abc422d0120a9ee37713188e65232e721ee8b843a7d0d127ec25cd477fc hpijs-3.12.4-6.el6.x86_64.rpm bdb661fd6fdbba277ab139149849eb1f187b0c1eff066049aa2eb98a8e0b470b hplip-3.12.4-6.el6.x86_64.rpm a9de4de10f414c210991f4555ed31f305edf42b639c9a5a44d7aa7ae3561332d hplip-common-3.12.4-6.el6.x86_64.rpm 924ecb76346318f4f191417814c36c6c7b5af62f1e538484c88dcc676861a5f7 hplip-gui-3.12.4-6.el6.x86_64.rpm ffe6923f51128ea06f09bc6640991d3fab31f0e9a9772a083e45e9f43b5efa4a hplip-libs-3.12.4-6.el6.i686.rpm 84315da2a03b061c2b8ef9d9eb9e7cae56e1133fc6213a4de17c03e236cc3293 hplip-libs-3.12.4-6.el6.x86_64.rpm 2096ce09942b6a87ae3ddc52e2f8b4b6b219622ccacde8725fb92d1f1c5a0825 libsane-hpaio-3.12.4-6.el6.x86_64.rpm Source: 357126746ffff08db4a9341780535b8e709d7ec853925d51485aca0543a15d4a hplip-3.12.4-6.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Thu, 19 Jun 2014 11:21:13 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0769 CentOS 6 xz FASTTRACK Update To: centos-announce(a)centos.org Message-ID: <20140619112113.GA15047(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0769 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0769.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 63d334c65874542d42df4740d86822cc7fa91364a972042ed773a9b4d84113ae xz-4.999.9-0.5.beta.20091007git.el6.i686.rpm 26afe9f8a375ee8a3bf5cc52de769361e9c4526d7430220be2a92cf5a33f4195 xz-devel-4.999.9-0.5.beta.20091007git.el6.i686.rpm 0b1bb46a0c35feac61006c98aba19b021886d18e343266556db49bbd8f79ded6 xz-libs-4.999.9-0.5.beta.20091007git.el6.i686.rpm 40f3e000a98c7769ddbe81d87021e91fec21a25d737d5c65774d07da674b1956 xz-lzma-compat-4.999.9-0.5.beta.20091007git.el6.i686.rpm x86_64: 289d9739bf5d9e6af58ef852055433e98d0c21df3fe6f48a707782795c31b1ad xz-4.999.9-0.5.beta.20091007git.el6.x86_64.rpm 26afe9f8a375ee8a3bf5cc52de769361e9c4526d7430220be2a92cf5a33f4195 xz-devel-4.999.9-0.5.beta.20091007git.el6.i686.rpm 375ad29ef7036eaf0e17887615c40debd013a76fae10a01ebf6310a733edc883 xz-devel-4.999.9-0.5.beta.20091007git.el6.x86_64.rpm 0b1bb46a0c35feac61006c98aba19b021886d18e343266556db49bbd8f79ded6 xz-libs-4.999.9-0.5.beta.20091007git.el6.i686.rpm 84f86a3d561bb3a2691d5422d656e2c03a81b79c23ccc38a2410c19e3c129b75 xz-libs-4.999.9-0.5.beta.20091007git.el6.x86_64.rpm 77eb536eba351b866338a97038221a885317ffe28cfaa4e596e530a587bc3a45 xz-lzma-compat-4.999.9-0.5.beta.20091007git.el6.x86_64.rpm Source: 4ddfc94a5481099c36e475b83e9839c393ed90a5c86898b1601397915a834abd xz-4.999.9-0.5.beta.20091007git.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Thu, 19 Jun 2014 11:21:51 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0768 CentOS 6 edac-utils FASTTRACK Update To: centos-announce(a)centos.org Message-ID: <20140619112151.GA15281(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0768 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0768.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f9238919a8e55753462b1690cc36a16b0a0c29260663dd5fe3e9ee0ae7a187c9 edac-utils-0.9-15.el6.i686.rpm 91b52fdaf78f24484edef2e78096ba684ed88bd392f81f93d869c502a572d90d edac-utils-devel-0.9-15.el6.i686.rpm x86_64: f9238919a8e55753462b1690cc36a16b0a0c29260663dd5fe3e9ee0ae7a187c9 edac-utils-0.9-15.el6.i686.rpm 52d7bb5b647fba78ada71901b02330ba8257b622655fbe462c624ca2e639960c edac-utils-0.9-15.el6.x86_64.rpm 91b52fdaf78f24484edef2e78096ba684ed88bd392f81f93d869c502a572d90d edac-utils-devel-0.9-15.el6.i686.rpm 6063758a7dcb69cd8e8a7bf0fc690ec5dbe8029c14be8b109e8f6fd1b1c5ecb2 edac-utils-devel-0.9-15.el6.x86_64.rpm Source: cb39863dd169453d8936482a1d68c279d3db20d0eac7945a368ed1e6668e78fb edac-utils-0.9-15.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Thu, 19 Jun 2014 11:22:32 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0766 CentOS 6 libxml2 Update To: centos-announce(a)centos.org Message-ID: <20140619112232.GA15545(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0766 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0766.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: bd16112cd246ff7ab7ffa5fedb8fcfd07b0700f1401e9516798cdd7180b7a73b libxml2-2.7.6-14.el6_5.2.i686.rpm 4d974dba18cc895bd5c12be855dcc7b73384bf5cbaeaa0f6d8409933cea68c2b libxml2-devel-2.7.6-14.el6_5.2.i686.rpm 0a5cd5f0c78b066e911a198488ce1ca8467b9d2e5703c85f58a0462e5a27a645 libxml2-python-2.7.6-14.el6_5.2.i686.rpm d25e465b78e18ce27e812a12d5498daa793f7be6b792a487041df2c4bacf2844 libxml2-static-2.7.6-14.el6_5.2.i686.rpm x86_64: bd16112cd246ff7ab7ffa5fedb8fcfd07b0700f1401e9516798cdd7180b7a73b libxml2-2.7.6-14.el6_5.2.i686.rpm 97706202cc7651c744e17d692ecc681631f034bb72fa0470851c481ca700e775 libxml2-2.7.6-14.el6_5.2.x86_64.rpm 4d974dba18cc895bd5c12be855dcc7b73384bf5cbaeaa0f6d8409933cea68c2b libxml2-devel-2.7.6-14.el6_5.2.i686.rpm bf8305860d78eb9fb23c11b827b0e602684833cb93370f4fcb77c2c3ced1170c libxml2-devel-2.7.6-14.el6_5.2.x86_64.rpm ad3c67b36deb04c2da00695aaedf05f74382b938775c3aa05cb11d43715b6b9a libxml2-python-2.7.6-14.el6_5.2.x86_64.rpm d0788e39b9c287c69cb5e3359ccb3c6181d60524a525923e6f1727b9674f97ad libxml2-static-2.7.6-14.el6_5.2.x86_64.rpm Source: 316dd3cd987bddf05dcbd8cfc6d0d14128d3b07e536bd3e97877d117d5375283 libxml2-2.7.6-14.el6_5.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 5 Date: Fri, 20 Jun 2014 10:10:41 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0771 Important CentOS 6 kernel Update To: centos-announce(a)centos.org Message-ID: <20140620101041.GA64315(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0771 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0771.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f3587df00882294a1f51e3a268f3092c8fefd73033df1be2ff68b2e178243a6c kernel-2.6.32-431.20.3.el6.i686.rpm ad2d4627c720409ca7aadcc3554481a28363c790cab49c4c25c5a7ef52977e7d kernel-abi-whitelists-2.6.32-431.20.3.el6.noarch.rpm 5e24aa3c00fe03125bb99ae5d338c05a9c85f777088d84eed96d57169b4d888e kernel-debug-2.6.32-431.20.3.el6.i686.rpm e72fbd7585e3bd6380833e2fe31aed46960f156dd1424b731f7ed8b28ecaba7e kernel-debug-devel-2.6.32-431.20.3.el6.i686.rpm 126e79095d80f4c2ff6e84d9740079734469c8b6ebfbd5e5c81446fec2442898 kernel-devel-2.6.32-431.20.3.el6.i686.rpm 0175e76317a53b76f56dd4fc82df9e578a26d54fe793aa5242440faac4b9d940 kernel-doc-2.6.32-431.20.3.el6.noarch.rpm 767726f39007768932493bdf17acc2b5e405420222c71e0e106beed86efca60c kernel-firmware-2.6.32-431.20.3.el6.noarch.rpm fbe7af9b46dce8a1a24451da3f510b0fbe5c84a18de678b58a132f2bd2e0b294 kernel-headers-2.6.32-431.20.3.el6.i686.rpm 23cced3b317b8c97618deade126b7f48e9b26b939bc0de39cc18d25dafb41733 perf-2.6.32-431.20.3.el6.i686.rpm 36e9cb5d02de0b329a599c111db97b9ceaebcf1546fa7d304dbc5140b573d7f7 python-perf-2.6.32-431.20.3.el6.i686.rpm x86_64: c60e176749bcac0eb7393a03422d1b8f842f4fd4edee8c128fa0f21f62e83e2d kernel-2.6.32-431.20.3.el6.x86_64.rpm ad2d4627c720409ca7aadcc3554481a28363c790cab49c4c25c5a7ef52977e7d kernel-abi-whitelists-2.6.32-431.20.3.el6.noarch.rpm 785c5e1b6d7da3a65013e6d58f2d75e464754e578c990e32f2fe60aa8db2065d kernel-debug-2.6.32-431.20.3.el6.x86_64.rpm e273baedf4a0e73d876fc84f4efacffedf445225ced974822a3618dd988bf138 kernel-debug-devel-2.6.32-431.20.3.el6.x86_64.rpm 06f62baeb7a82f18f936ffb1d257e51dc338d18c94ccf254cb6a3cd6a4dbddfb kernel-devel-2.6.32-431.20.3.el6.x86_64.rpm 0175e76317a53b76f56dd4fc82df9e578a26d54fe793aa5242440faac4b9d940 kernel-doc-2.6.32-431.20.3.el6.noarch.rpm 767726f39007768932493bdf17acc2b5e405420222c71e0e106beed86efca60c kernel-firmware-2.6.32-431.20.3.el6.noarch.rpm 5470ff283b4b5c94b74c5031172066f685bd167af538fae436050b78af0094a0 kernel-headers-2.6.32-431.20.3.el6.x86_64.rpm 0ed20d751273ffe0988e920af796e80d558ec9c2cc325d6cfa9f839e0b2d34d2 perf-2.6.32-431.20.3.el6.x86_64.rpm c94621c2d430b78017f22f1abcaecd5b42e94784b1e8202ce4930b3dc91636dc python-perf-2.6.32-431.20.3.el6.x86_64.rpm Source: ceb3c48340be0f13764003ce3c3e9c46350c58f3ad117910fffc954b4311eb5b kernel-2.6.32-431.20.3.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 112, Issue 9 ***********************************************

1 0

good thin client PDF reader for centos 6.4
by Dan Hyatt 19 Jun '14

19 Jun '14

Any suggestions for a good lightweight pdf reader for my centos servers? Thanks, -- Dan Hyatt

6 6

Thunderbird bug, anyone else have seen it?
by Eliezer Croitoru 19 Jun '14

19 Jun '14

https://bugzilla.mozilla.org/show_bug.cgi?id=541130 The bug I see is using thunderbird 24.6 which is the latest update on centos 6.5. The issue is that every time I open an email with some "+" somewhere in the source (which I didn't traced yet) I get annoying message: An error occurred while loading or saving configuration information for thunderbird. Some of your configuration settings may not work properly. =In the details section I get: Bad key or directory name: "/desktop/gnome/url-handlers/EDH+CAMELLIA/command": `+' is an invalid character in key/directory names Bad key or directory name: "/desktop/gnome/url-handlers/EDH+CAMELLIA/command": `+' is an invalid character in key/directory names Bad key or directory name: "/desktop/gnome/url-handlers/EDH+aRSA/command": `+' is an invalid character in key/directory names Bad key or directory name: "/desktop/gnome/url-handlers/EDH+aRSA/command": `+' is an invalid character in key/directory names Bad key or directory name: "/desktop/gnome/url-handlers/EECDH+aRSA+AESGCM/command": `+' is an invalid character in key/directory names Bad key or directory name: "/desktop/gnome/url-handlers/EECDH+aRSA+AESGCM/command": `+' is an invalid character in key/directory names Bad key or directory name: "/desktop/gnome/url-handlers/EECDH+aRSA+SHA384/command": `+' is an invalid character in key/directory names Bad key or directory name: "/desktop/gnome/url-handlers/EECDH+aRSA+SHA384/command": `+' is an invalid character in key/directory names Bad key or directory name: "/desktop/gnome/url-handlers/EECDH+aRSA+SHA256/command": `+' is an invalid character in key/directory names Bad key or directory name: "/desktop/gnome/url-handlers/EECDH+aRSA+SHA256/command": `+' is an invalid character in key/directory names ##end By the last message of the bug-report I understand that RH released a bug-fix\patch that should help with the issue. Before I file a bug, anyone else is having the same issue? anyone has the patch from the bug-report? Thanks, Eliezer

4 5

problem with centos.org whois
by Devin Reade 19 Jun '14

19 Jun '14

It looks like someone pooched a domain transfer, and the whois entry for centos.org is missing its NS records. I've sent an email to the whois tech contact @redhat, but I'm sending this to the list to hopefully bring it to someone else's attention, as well. Hopefully it gets gets out before my mailserver expires its DNS cache for centos.org. Expect centos.org to be offline for a bit ... Devin -- I wish there was a knob on the TV to turn up the intelligence. There's a knob called `brightness', but it doesn't work. - Gallagher

4 4

compiling centos 6.5 linux-2.6.32-431.el6-kernel
by Dilip Basavaraju 19 Jun '14

19 Jun '14

Dear all, I have compiled the linux-2.6.32-431.el6-kernel with the following steps 1. Make mproper 2. Make menuconfig 3. Make 4. Make modules 5. Make modules_install The compilation is successful but there is a huge change in the size of the .ko generated compared to original .ko from the rpm. Please suggest the steps to compile the centos linux-2.6.32-431.el6-kernel and use the modules and to build the kernel.rpm Thanks and regards Dilip Kumar B L&T Technology Services Ltd www.LntTechservices.com<http://www.lnttechservices.com/> This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

3 2

Question about clustering
by Alessandro Baggi 18 Jun '14

18 Jun '14

Hi list, I'm new to clustering, and I'm running a little cluster@home. The cluster is running on a workstation hardware and running on Centos 6.5. Component: corosync, pacemaker, drbd and pcs. All works good. This cluster has different resources: 1) drbd0 2) drbd1 3) drbd0_fs 4) drbd1_fs 5) pgsql 6) smb + nmb 7) libvirt (lbs) 8) libvirt_guests (lsb) I've this constraint colocation and ordering constraint (sorry for format): Ordering Constraints: promote drbd_ms then start drbd0_fs (Mandatory) (id:order-drbd_ms-drbd0_fs-mandatory) promote drbd1_ms then start drbd1_fs (Mandatory) (id:order-drbd1_ms-drbd1_fs-mandatory) start drbd1_fs then start pgsql_res (Mandatory) (id:order-drbd1_fs-pgsql_res-mandatory) start drbd0_fs then start samba_res (Mandatory) (id:order-drbd0_fs-samba_res-mandatory) start samba_res then start nmbd_res (Mandatory) (id:order-samba_res-nmbd_res-mandatory) start drbd1_fs then start libvirt_res (Mandatory) (id:order-drbd1_fs-libvirt_res-mandatory) start libvirt_res then start libvirt_guest_res (Mandatory) (id:order-libvirt_res-libvirt_guest_res-mandatory) Colocation Constraints: drbd0_fs with drbd_ms (INFINITY) (with-rsc-role:Master) (id:colocation-drbd0_fs-drbd_ms-INFINITY) drbd1_fs with drbd1_ms (INFINITY) (with-rsc-role:Master) (id:colocation-drbd1_fs-drbd1_ms-INFINITY) drbd1_fs with pgsql_res (INFINITY) (id:colocation-drbd1_fs-pgsql_res-INFINITY) drbd0_fs with samba_res (INFINITY) (id:colocation-drbd0_fs-samba_res-INFINITY) samba_res with nmbd_res (INFINITY) (id:colocation-samba_res-nmbd_res-INFINITY) drbd1_fs with libvirt_res (INFINITY) (id:colocation-drbd1_fs-libvirt_res-INFINITY) libvirt_res with libvirt_guest_res (INFINITY) (id:colocation-libvirt_res-libvirt_guest_res-INFINITY) Today, starting my "cluster", I've encontered a (obscure-not identified) problem during libvirt_guest_res start, and I've noticed that drbd1_fs was stopped because libvirt_guest_res has failed, and consequently all other resource that depend from drbd1_fs was stopped. I suppose that this behaviour is colocation constraint related (correct me if I'm wrong). In my case I've: drbd1_fs with libvirt_res libvirt_res with libvirt_guest_res drbd1_fs with pgsql There is a way to avoid that if libvirt_guest_res fails, drbd1_fs will not be stopped and then all other resources depending from drbd1_fs? Another question is about fencing. I've ridden that a cluster must have fencing to be considered as such. On CentOS 6.5 there is stonith that concerns node level fencing. For this type of fencing I must have ilo, ilom, drac, and other. It's possible to have fencing without Light-out devices, blade power control device and other? There are other device that can be used for fencing? Supposing a 2 node cluster with two server assembled (no hp, dell, sun, ibm..) how I can implement fencing with stonith? I can run a cluster without fencing and what implies do not use fencing? Thanks in advance. Alessandro.

6 16

CentOS-announce Digest, Vol 112, Issue 8
by centos-announce-request＠centos.org 18 Jun '14

18 Jun '14

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss