Re: [CentOS-docs] Mail / Web server guides
On Mon, Mar 25, 2013 at 10:41:31AM -, Christian Salway wrote: Firstly, If such issues could possibly be resolved I feel these scripts would be very beneficial to many users., who better to help out with that than you by the sounds of it. I've already worked this space and have had solutions in place for such provisioning for many, many years; I was not including myself in that many users category :) Anyway, although I would love a perfect system the way CentOS org intended it, there are many reasons why I have done the scripts the way I have. Mainly because there is not always the documentation out there to be able to achieve the centos perfect result, or the packages available in the 'preferred' repos are out-of-date, so people like me find the 'best' solution they can. But the point is... your solution leaves one wide-open for security problems down the road from 1) lack of policy enforcement and 2) unpackaged solutions that will, more than likely, end up missing some updates down the line. Especially when you are talking about such poor codebases as phpmyadmin with sarcasmit's absolutely stellar record of no security issues/sarcasm. selinux I'm all about security but there just isn't any good documentation for managing selinux! That's patently untrue. If there was, SELINUX would still be enabled. For instance, how to allow selinux to let pureftp and apache share the same files, show me a simple guide on that! You mean like the one on the centos wiki or any of the documentation provided by Redhat and Fedora? Here's a list of links to get you started: http://wiki.centos.org/HowTos/SELinux http://wiki.centos.org/TipsAndTricks/SelinuxBooleans http://docs.fedoraproject.org/en-US/Fedora/13/html/Security-Enhanced_Linux/ http://fedorasolved.org/security-solutions/selinux-module-building http://centoshelp.org/security/selinux-common-commands-troubleshooting There are, of course, many, many additional resources. Really... this endless loop I hear about lack of documentation might have been true a number of years ago but it is not the case, nor has it been the case for quite some time. perl-File-Scan-ClamAV I used http://wiki.apache.org/spamassassin/ClamAVPlugin to interact ClamAV and spamassassin which mentions File::Scan::ClamAV but which wasn't available in the repositories I had chosen, so clicking on the link took me to cpan, which I then found a way to automate the install off. I see no reason why it wasn't a good way of doing it as you get the latest version and it's only an add-on module to perl. And it's unpackaged, therefore rpm/yum know absolutely nothing about it which may well lead to conflicts down the road. There is also the it's unpackaged so therefore it may well lack in applied updates issue. While _you_ may well be disciplined enough to check for and apply updates as necessary, the people that would be relying on your scripts may not be as disciplined - cookie cutter solutions such as _packaged_ applications are a better fit for most. perl-File-Scan-ClamAV is in rpmforge. If you are unhappy with the version they offer and you are willing to maintain it yourself then you can use cpanspec or cpan2rpm and create a binary rpm package; this process will use the sources available from cpan and build up an arch (i386/x86_64) or noarch binary package as necessary. phpmyadmin What is so wrong about downloading the latest html files direct from the developers website? Nothing is 'installed' into the system and the repositories rarely have the latest version. You are basically asking the CentOS uses to stay in the dark from new and improved versions of software until you 'have the time' to add them to the repositories! Because latest != greatest. Oh! Shiny! isn't generally worth the trouble that comes with it. And phpmyadmin is a very good example. The versions in rpmforge/epel are tested and vetted which is more than can be said for phpmyadmin itself. And I am not asking users to do anything except understand what an enterprise system is and how to work with it instead of against it. It's your box, do with it as you please. But when you are writing solutions for others it's best to stay with Best Practice for the platform. UTC timezone The timezone script was for simplicity with my setup only and can obviously be removed. Although I'm sure a half-witted donkey can figure out how to change it. That's not the point. You are making a change to someone else's box that may have significant operational impact. Yes, it can be argued that people should review scripts before they run them, but let's face it, most people don't bother. Remi over rpmforge I tried to install mysql from rpmforge but it just wasn't happening. Their mysql_libs are still old and thus causes a warning in phpmyadmin. Why would you go outside the distribution for an alternate mysql package for something as ridiculous as phpmyadmin? Additionally rpmforge has
Re: [CentOS-docs] Mail / Web server guides
Ok, The scripts have been rewritten :) All packages are now downloaded from base or IUS (or rpmforge for perl-file-clamav) and I've left selinux enabled, writing some te files :) Changes have been uploaded http://www.itmanx.com/downloads/scripts.tar.gz The only problem now is when I log into phpmyadmin, I get the following and I can't find a solution. Your PHP MySQL library version 5.1.61 differs from your MySQL server version 5.5.30. This may cause unpredictable behavior. # rpm -qa mysql* mysql55-libs-5.5.30-1.ius.el6.x86_64 mysql55-5.5.30-1.ius.el6.x86_64 mysqlclient16-5.1.61-1.ius.el6.x86_64 mysql55-server-5.5.30-1.ius.el6.x86_64 Kind regards, Christian Salway -Original Message- From: centos-docs-boun...@centos.org [mailto:centos-docs-boun...@centos.org] On Behalf Of John R. Dennison Sent: 25 March 2013 13:17 To: centos-docs@centos.org Subject: Re: [CentOS-docs] Mail / Web server guides On Mon, Mar 25, 2013 at 10:41:31AM -, Christian Salway wrote: Firstly, If such issues could possibly be resolved I feel these scripts would be very beneficial to many users., who better to help out with that than you by the sounds of it. I've already worked this space and have had solutions in place for such provisioning for many, many years; I was not including myself in that many users category :) Anyway, although I would love a perfect system the way CentOS org intended it, there are many reasons why I have done the scripts the way I have. Mainly because there is not always the documentation out there to be able to achieve the centos perfect result, or the packages available in the 'preferred' repos are out-of-date, so people like me find the 'best' solution they can. But the point is... your solution leaves one wide-open for security problems down the road from 1) lack of policy enforcement and 2) unpackaged solutions that will, more than likely, end up missing some updates down the line. Especially when you are talking about such poor codebases as phpmyadmin with sarcasmit's absolutely stellar record of no security issues/sarcasm. selinux I'm all about security but there just isn't any good documentation for managing selinux! That's patently untrue. If there was, SELINUX would still be enabled. For instance, how to allow selinux to let pureftp and apache share the same files, show me a simple guide on that! You mean like the one on the centos wiki or any of the documentation provided by Redhat and Fedora? Here's a list of links to get you started: http://wiki.centos.org/HowTos/SELinux http://wiki.centos.org/TipsAndTricks/SelinuxBooleans http://docs.fedoraproject.org/en-US/Fedora/13/html/Security-Enhanced_Linux/ http://fedorasolved.org/security-solutions/selinux-module-building http://centoshelp.org/security/selinux-common-commands-troubleshooting There are, of course, many, many additional resources. Really... this endless loop I hear about lack of documentation might have been true a number of years ago but it is not the case, nor has it been the case for quite some time. perl-File-Scan-ClamAV I used http://wiki.apache.org/spamassassin/ClamAVPlugin to interact ClamAV and spamassassin which mentions File::Scan::ClamAV but which wasn't available in the repositories I had chosen, so clicking on the link took me to cpan, which I then found a way to automate the install off. I see no reason why it wasn't a good way of doing it as you get the latest version and it's only an add-on module to perl. And it's unpackaged, therefore rpm/yum know absolutely nothing about it which may well lead to conflicts down the road. There is also the it's unpackaged so therefore it may well lack in applied updates issue. While _you_ may well be disciplined enough to check for and apply updates as necessary, the people that would be relying on your scripts may not be as disciplined - cookie cutter solutions such as _packaged_ applications are a better fit for most. perl-File-Scan-ClamAV is in rpmforge. If you are unhappy with the version they offer and you are willing to maintain it yourself then you can use cpanspec or cpan2rpm and create a binary rpm package; this process will use the sources available from cpan and build up an arch (i386/x86_64) or noarch binary package as necessary. phpmyadmin What is so wrong about downloading the latest html files direct from the developers website? Nothing is 'installed' into the system and the repositories rarely have the latest version. You are basically asking the CentOS uses to stay in the dark from new and improved versions of software until you 'have the time' to add them to the repositories! Because latest != greatest. Oh! Shiny! isn't generally worth the trouble that comes with it. And phpmyadmin is a very good example. The versions in rpmforge/epel are tested and vetted which is more than can be said for phpmyadmin itself. And I am not asking users to do anything except understand what an
Re: [CentOS-docs] Mail / Web server guides
I didn't have that problem before when using remi :) --Original Message-- From: Manuel Wolfshant Sender: centos-docs-boun...@centos.org To: Mail list for wiki articles ReplyTo: Mail list for wiki articles Subject: Re: [CentOS-docs] Mail / Web server guides Sent: 25 Mar 2013 20:00 On 03/25/2013 09:56 PM, Christian Salway wrote: [...] The only problem now is when I log into phpmyadmin, I get the following and I can't find a solution. Your PHP MySQL library version 5.1.61 differs from your MySQL server version 5.5.30. This may cause unpredictable behavior. # rpm -qa mysql* mysql55-libs-5.5.30-1.ius.el6.x86_64 mysql55-5.5.30-1.ius.el6.x86_64 mysqlclient16-5.1.61-1.ius.el6.x86_64 mysql55-server-5.5.30-1.ius.el6.x86_64 You will keep seeing that warning for as long as phpmyadmin is compiled against the stock mysql libs while the server runs a different mysql version. Normally it's benign. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-announce] CEBA-2013:0678 CentOS 5 cman Update
CentOS Errata and Bugfix Advisory 2013:0678
Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0678.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
4a7f784bba1c838388c37e4ef955b10997d0a43fb15028d2a241fbcd1b007f9c
cman-2.0.115-109.el5.1.i386.rpm
9686f73d8e6c5fd31bb4417c00801309b70781881c1f4deb007f3a8bb73d
cman-devel-2.0.115-109.el5.1.i386.rpm
x86_64:
318d1de1b537d49ce45bd4408564aa1d8100345341b03cbcdfa486afa0d76709
cman-2.0.115-109.el5.1.x86_64.rpm
9686f73d8e6c5fd31bb4417c00801309b70781881c1f4deb007f3a8bb73d
cman-devel-2.0.115-109.el5.1.i386.rpm
d0e7f5d640a9e6321e7a88a2abe060562e0aa81a3980a3bf224fdc2238b09cee
cman-devel-2.0.115-109.el5.1.x86_64.rpm
Source:
204fd4a6bd56f0319a9ebe8182e7301787f0f9efb901c17f37835b60c2df942c
cman-2.0.115-109.el5.1.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
___
CentOS-announce mailing list
CentOS-announce@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CESA-2013:0683 Moderate CentOS 5 axis Update
CentOS Errata and Security Advisory 2013:0683 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0683.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
b6235d3a74e62c9c9a29709d6c08f929887057c0556a3e5f1485d8133fb4160b
axis-1.2.1-2jpp.7.el5_9.i386.rpm
2186648502e1e67ba6ee53360191cf3e03811d8c36f2ddf1843e654b77e29842
axis-javadoc-1.2.1-2jpp.7.el5_9.i386.rpm
7022df95b8fb6e03d8db13309257ddebe59ea1ceeebd290cfdc81fea67eb86cf
axis-manual-1.2.1-2jpp.7.el5_9.i386.rpm
x86_64:
681e19cc4c4a716f2973476e64cb7d8224de668eaf00eff68e1b58eec31cb378
axis-1.2.1-2jpp.7.el5_9.x86_64.rpm
a12becca6c282eb2c00f0600a1d11fee227f8639c1d3ea9e6b2397a325002725
axis-javadoc-1.2.1-2jpp.7.el5_9.x86_64.rpm
a2d033d830bdc598b8c71c92931c8703f8473444a8f0f33d2d900c944f65c09a
axis-manual-1.2.1-2jpp.7.el5_9.x86_64.rpm
Source:
4a1d19a94f2718aeb962dec15086b5ef12d9422111f25a0336daa67bacf964ec
axis-1.2.1-2jpp.7.el5_9.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
___
CentOS-announce mailing list
CentOS-announce@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
Re: [CentOS-virt] GFS2 hangs after one node going down
Il 22/03/2013 16:27, Digimer ha scritto: On 03/22/2013 11:21 AM, Maurizio Giungato wrote: Il 22/03/2013 00:34, Digimer ha scritto: On 03/21/2013 02:09 PM, Maurizio Giungato wrote: Il 21/03/2013 18:48, Maurizio Giungato ha scritto: Il 21/03/2013 18:14, Digimer ha scritto: On 03/21/2013 01:11 PM, Maurizio Giungato wrote: Hi guys, my goal is to create a reliable virtualization environment using CentOS 6.4 and KVM, I've three nodes and a clustered GFS2. The enviroment is up and working, but I'm worry for the reliability, if I turn the network interface down on one node to simulate a crash (for example on the node node6.blade): 1) GFS2 hangs (processes go in D state) until node6.blade get fenced 2) not only node6.blade get fenced, but also node5.blade! Help me to save my last neurons! Thanks Maurizio DLM, the distributed lock manager provided by the cluster, is designed to block when a known goes into an unknown state. It does not unblock until that node is confirmed to be fenced. This is by design. GFS2, rgmanager and clustered LVM all use DLM, so they will all block as well. As for why two nodes get fenced, you will need to share more about your configuration. My configuration is very simple I attached cluster.conf and hosts files. This is the row I added in /etc/fstab: /dev/mapper/KVM_IMAGES-VL_KVM_IMAGES /var/lib/libvirt/images gfs2 defaults,noatime,nodiratime 0 0 I set also fallback_to_local_locking = 0 in lvm.conf (but nothing change) PS: I had two virtualization enviroments working like a charm on OCFS2, but since Centos 6.x I'm not able to install it, there is same way to achieve the same results with GFS2 (with GFS2 sometime I've a crash after only a service network restart [I've many interfaces then this operation takes more than 10 seconds], with OCFS2 I've never had this problem. Thanks I attached my logs from /var/log/cluster/* The configuration itself seems ok, though I think you can safely take qdisk out to simplify things. That's neither here nor there though. This concerns me: Mar 21 19:00:14 fenced fence lama6.blade dev 0.0 agent fence_bladecenter result: error from agent Mar 21 19:00:14 fenced fence lama6.blade failed How are you triggering the failure(s)? The failed fence would certainly help explain the delays. As I mentioned earlier, DLM is designed to block when a node is in an unknowned state (failed but not yet successfully fenced). As an aside; I do my HA VMs using clustered LVM LVs as the backing storage behind the VMs. GFS2 is an excellent file system, but it is expensive. Putting your VMs directly on the LV takes them out of the equation I used 'service network stop' to simulate the failure, the node get fenced through fence_bladecenter (BladeCenter HW) Anyway, I took qdisk out and put GFS2 aside and now I've my VM on LVM LVs, I'm trying for many hours to reproduce the issue - only the node where I execute 'service network stop' get fenced - using fallback_to_local_locking = 0 in lvm.conf LVM LVs remain writable also while fencing take place All seems to work like a charm now. I'd like to understand what was happening. I'll try for same day before trusting it. Thank you so much. Maurizio Testing testing testing. It's good that you plan to test before trusting. I wish everyone had that philosophy! The clustered locking for LVM comes into play for activating/inactivating, creating, deleting, resizing and so on. It does not affect what happens in an LV. That's why an LV remains writeable when a fence is pending. However, I feel this is safe because rgmanager won't recover a VM on another node until the lost node is fenced. Cheers Thank you very much! The cluster continue working like a charm. Failure after failure I mean :) We are not using rgmanager fault management because doesn't have a check about the memory availability on the destination node, then we prefer to manage this situation with custom script we wrote. last questions: - have you any advice to improve the tollerance against network failures? - to avoid having a gfs2 only for VM's xml, I've thought to keep them on each node synced with rsync. Any alternatives? - If I want to have only the clustered LVM without no other functions, can you advice about a minimal configuration? (for example I think that rgmanager is not necessary) Thank you in advance ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] GFS2 hangs after one node going down
On 03/25/2013 08:44 AM, Maurizio Giungato wrote: Il 22/03/2013 16:27, Digimer ha scritto: On 03/22/2013 11:21 AM, Maurizio Giungato wrote: Il 22/03/2013 00:34, Digimer ha scritto: On 03/21/2013 02:09 PM, Maurizio Giungato wrote: Il 21/03/2013 18:48, Maurizio Giungato ha scritto: Il 21/03/2013 18:14, Digimer ha scritto: On 03/21/2013 01:11 PM, Maurizio Giungato wrote: Hi guys, my goal is to create a reliable virtualization environment using CentOS 6.4 and KVM, I've three nodes and a clustered GFS2. The enviroment is up and working, but I'm worry for the reliability, if I turn the network interface down on one node to simulate a crash (for example on the node node6.blade): 1) GFS2 hangs (processes go in D state) until node6.blade get fenced 2) not only node6.blade get fenced, but also node5.blade! Help me to save my last neurons! Thanks Maurizio DLM, the distributed lock manager provided by the cluster, is designed to block when a known goes into an unknown state. It does not unblock until that node is confirmed to be fenced. This is by design. GFS2, rgmanager and clustered LVM all use DLM, so they will all block as well. As for why two nodes get fenced, you will need to share more about your configuration. My configuration is very simple I attached cluster.conf and hosts files. This is the row I added in /etc/fstab: /dev/mapper/KVM_IMAGES-VL_KVM_IMAGES /var/lib/libvirt/images gfs2 defaults,noatime,nodiratime 0 0 I set also fallback_to_local_locking = 0 in lvm.conf (but nothing change) PS: I had two virtualization enviroments working like a charm on OCFS2, but since Centos 6.x I'm not able to install it, there is same way to achieve the same results with GFS2 (with GFS2 sometime I've a crash after only a service network restart [I've many interfaces then this operation takes more than 10 seconds], with OCFS2 I've never had this problem. Thanks I attached my logs from /var/log/cluster/* The configuration itself seems ok, though I think you can safely take qdisk out to simplify things. That's neither here nor there though. This concerns me: Mar 21 19:00:14 fenced fence lama6.blade dev 0.0 agent fence_bladecenter result: error from agent Mar 21 19:00:14 fenced fence lama6.blade failed How are you triggering the failure(s)? The failed fence would certainly help explain the delays. As I mentioned earlier, DLM is designed to block when a node is in an unknowned state (failed but not yet successfully fenced). As an aside; I do my HA VMs using clustered LVM LVs as the backing storage behind the VMs. GFS2 is an excellent file system, but it is expensive. Putting your VMs directly on the LV takes them out of the equation I used 'service network stop' to simulate the failure, the node get fenced through fence_bladecenter (BladeCenter HW) Anyway, I took qdisk out and put GFS2 aside and now I've my VM on LVM LVs, I'm trying for many hours to reproduce the issue - only the node where I execute 'service network stop' get fenced - using fallback_to_local_locking = 0 in lvm.conf LVM LVs remain writable also while fencing take place All seems to work like a charm now. I'd like to understand what was happening. I'll try for same day before trusting it. Thank you so much. Maurizio Testing testing testing. It's good that you plan to test before trusting. I wish everyone had that philosophy! The clustered locking for LVM comes into play for activating/inactivating, creating, deleting, resizing and so on. It does not affect what happens in an LV. That's why an LV remains writeable when a fence is pending. However, I feel this is safe because rgmanager won't recover a VM on another node until the lost node is fenced. Cheers Thank you very much! The cluster continue working like a charm. Failure after failure I mean :) We are not using rgmanager fault management because doesn't have a check about the memory availability on the destination node, then we prefer to manage this situation with custom script we wrote. last questions: - have you any advice to improve the tollerance against network failures? - to avoid having a gfs2 only for VM's xml, I've thought to keep them on each node synced with rsync. Any alternatives? - If I want to have only the clustered LVM without no other functions, can you advice about a minimal configuration? (for example I think that rgmanager is not necessary) Thank you in advance For network redundancy, I use two switches and bonded (mode=1) links with one link going to either switch. This way, losing a NIC or a switch won't break the cluster. Details here: https://alteeve.ca/w/2-Node_Red_Hat_KVM_Cluster_Tutorial#Network Using rsync to keep the XML files in sync is fine, if you really don't want to use GFS2. You do not need rgmanager for clvmd to work. All you need is the base cluster.conf (and working fencing, as you've seen). If you are over-provisioning VMs and need to
Re: [CentOS-virt] GFS2 hangs after one node going down
Il 25/03/2013 17:49, Digimer ha scritto: On 03/25/2013 08:44 AM, Maurizio Giungato wrote: Il 22/03/2013 16:27, Digimer ha scritto: On 03/22/2013 11:21 AM, Maurizio Giungato wrote: Il 22/03/2013 00:34, Digimer ha scritto: On 03/21/2013 02:09 PM, Maurizio Giungato wrote: Il 21/03/2013 18:48, Maurizio Giungato ha scritto: Il 21/03/2013 18:14, Digimer ha scritto: On 03/21/2013 01:11 PM, Maurizio Giungato wrote: Hi guys, my goal is to create a reliable virtualization environment using CentOS 6.4 and KVM, I've three nodes and a clustered GFS2. The enviroment is up and working, but I'm worry for the reliability, if I turn the network interface down on one node to simulate a crash (for example on the node node6.blade): 1) GFS2 hangs (processes go in D state) until node6.blade get fenced 2) not only node6.blade get fenced, but also node5.blade! Help me to save my last neurons! Thanks Maurizio DLM, the distributed lock manager provided by the cluster, is designed to block when a known goes into an unknown state. It does not unblock until that node is confirmed to be fenced. This is by design. GFS2, rgmanager and clustered LVM all use DLM, so they will all block as well. As for why two nodes get fenced, you will need to share more about your configuration. My configuration is very simple I attached cluster.conf and hosts files. This is the row I added in /etc/fstab: /dev/mapper/KVM_IMAGES-VL_KVM_IMAGES /var/lib/libvirt/images gfs2 defaults,noatime,nodiratime 0 0 I set also fallback_to_local_locking = 0 in lvm.conf (but nothing change) PS: I had two virtualization enviroments working like a charm on OCFS2, but since Centos 6.x I'm not able to install it, there is same way to achieve the same results with GFS2 (with GFS2 sometime I've a crash after only a service network restart [I've many interfaces then this operation takes more than 10 seconds], with OCFS2 I've never had this problem. Thanks I attached my logs from /var/log/cluster/* The configuration itself seems ok, though I think you can safely take qdisk out to simplify things. That's neither here nor there though. This concerns me: Mar 21 19:00:14 fenced fence lama6.blade dev 0.0 agent fence_bladecenter result: error from agent Mar 21 19:00:14 fenced fence lama6.blade failed How are you triggering the failure(s)? The failed fence would certainly help explain the delays. As I mentioned earlier, DLM is designed to block when a node is in an unknowned state (failed but not yet successfully fenced). As an aside; I do my HA VMs using clustered LVM LVs as the backing storage behind the VMs. GFS2 is an excellent file system, but it is expensive. Putting your VMs directly on the LV takes them out of the equation I used 'service network stop' to simulate the failure, the node get fenced through fence_bladecenter (BladeCenter HW) Anyway, I took qdisk out and put GFS2 aside and now I've my VM on LVM LVs, I'm trying for many hours to reproduce the issue - only the node where I execute 'service network stop' get fenced - using fallback_to_local_locking = 0 in lvm.conf LVM LVs remain writable also while fencing take place All seems to work like a charm now. I'd like to understand what was happening. I'll try for same day before trusting it. Thank you so much. Maurizio Testing testing testing. It's good that you plan to test before trusting. I wish everyone had that philosophy! The clustered locking for LVM comes into play for activating/inactivating, creating, deleting, resizing and so on. It does not affect what happens in an LV. That's why an LV remains writeable when a fence is pending. However, I feel this is safe because rgmanager won't recover a VM on another node until the lost node is fenced. Cheers Thank you very much! The cluster continue working like a charm. Failure after failure I mean :) We are not using rgmanager fault management because doesn't have a check about the memory availability on the destination node, then we prefer to manage this situation with custom script we wrote. last questions: - have you any advice to improve the tollerance against network failures? - to avoid having a gfs2 only for VM's xml, I've thought to keep them on each node synced with rsync. Any alternatives? - If I want to have only the clustered LVM without no other functions, can you advice about a minimal configuration? (for example I think that rgmanager is not necessary) Thank you in advance For network redundancy, I use two switches and bonded (mode=1) links with one link going to either switch. This way, losing a NIC or a switch won't break the cluster. Details here: https://alteeve.ca/w/2-Node_Red_Hat_KVM_Cluster_Tutorial#Network Using rsync to keep the XML files in sync is fine, if you really don't want to use GFS2. You do not need rgmanager for clvmd to work. All you need is the base cluster.conf (and working fencing, as
Re: [CentOS-es] Red wifi en Centos 6.3
El 24/03/13, Rodrigo Pichiñual Norin rodrigo.pichin...@gmail.com escribió: Trance echale un vistazo a esto http://www.alcancelibre.org/staticpages/index.php/08-parametros-red Yo simplemente me baso en la documentación oficial, y mi experiencia usando CentOS, de todas maneras voy a instalarme una maquina virtual y revisar, me causas confusión, hasta donde yo sabía todavía no se implementa esos nombres aún en CentOS, pero puedo estar equivocado y saldré de la duda, saludos. El 23 de marzo de 2013 14:05, Tranc3 Music edgarr...@gmail.com escribió: El 21/03/13, Rodrigo Pichiñual Norin rodrigo.pichin...@gmail.com escribió: Antes de instalar Centos tenia fedora 18 en mi laptop y me reconocía amabas redes cableada e inalambrica (p1p2 wlan0), pero con centos no me reconoce ni una, la red cableada tuve que meterle mano yo. Si ocupo ifconfig -a solo me muestra la local lo Si muestra esa salida posiblemente no tienes interfaces, estan dañadas o no estan haciendo contacto, ES MUY raro que no reconozca que yo sepa ahora CentOS en la versión 6.x debe reconocer mucho hardware ya no es como CentOS 5, posiblemente también tu hardware es muy reciente y poco comun. después de configurar la red cableada y al hacer un ifconfig -a ,uestra Cómo haz configurado? no llego a entender si no lo veías antes cómo has hecho y TODAVIA PARA VERLO con ese nombre, no se si estoy mal (LO DUDO) pero hasta donde vi en CentOS 6.0 las interfaces se nombran todavía con eth0, eth1, ..., wlan0 (wifi) y NO P1P2 eso es de fedora que en nueva release introduce nueva forma de nombrar a las interfaces, yo soy el único que esta hablando de esto? hay varios en la lista que usan CentOS y no dicen si p1p2 es válido en CentOS, que yo sepa NO lo p1p2 Muy extraño, deamasiado diría CentOS no nombra de esa manera a las interfaces, por ahora, fedora si nombra de esa manera. me captas? Causa confusión lo que muestras, mira que dice la docuentación redhat el 6 https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html No existe p1p2, eso es de fedora, en Centos debería de ser eth..., asi debería de verse si es que reconoce, aunque podría cambiarse, pero mejor sería dejar con ese nombre. Gracias. El 21 de marzo de 2013 02:23, Tranc3 Music edgarr...@gmail.com escribió: El 20/03/13, Rodrigo Pichiñual Norin rodrigo.pichin...@gmail.com escribió: Hola a todos, Resulta que instala CentOS en su versión *minimal Desktop*, una vez terminada la instalación pude ver que no tenia red, en un principio * NetworkManager* intentaba configurar mi red, pero aun así no tenia net, me puse a configurar la red cableada (Ethernet) el dispositivo por defecto era *p1p2* y ahora tengo internet cableada el Drama es con el dispositivo ¿p1p2? que yo sepa esa es la forma que fedora (las últimas releases) le da nombre a las interfaces, pero CentOS todavía no da esos nombres, que yo sepa sigue con eth0,eth1,..., estas seguro que estas usando CentOS? :o, o estoy equivocado? :o wifi, no tengo un WLAN0 en /etc/sysconfig/netwok-scripts/, me interesa configurar esto ya instale centos en mi portatil tanto de forma manual o con Network Manager ?¿? no entender pro completo: ya instale centos en mi portatil tanto de forma manual o con Network Manager Pero bueno segun lo que entiendo..., primero por qué no usas ifconfig -a, para ver tus interfaces, si tienes interfaz wifi seguro que se verá usando ifconfig -a, no estan congiguradas aún, también por defecto en CentOS no se inicializa las interfaces, a menos que en la isntalación le hayas dicho que si. Si tienes NetworkManager por qué no usas y configuras? debes hacerlo también, lee las opciones que ves por ahí hay una que te permite configurar tanto la cableada y la inalambrica (si es que la detecta, creo que si, CentOS 6.3 es un fedora 12 ó 13 debería de detectar hardware en su mayoría), saludos y suerte. *Gracias* ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es -- UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity. -- Dennis M. Ritchie Mis bits: http://bitsenlared.wordpress.com Live free or die! ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es -- *Rodrigo Pichiñual * *Ingeniero en Computación* *87272971 * rodrigo.pichin...@gmail.com / rodr...@latitud33.cl rodrigo.pichin...@gmail.com ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es -- UNIX is
Re: [CentOS-es] Red wifi en Centos 6.3
El 24/03/13, Rodrigo Pichiñual Norin rodrigo.pichin...@gmail.com escribió: Trance echale un vistazo a esto http://www.alcancelibre.org/staticpages/index.php/08-parametros-red Hola otra vez, pues ya revisé amigo y las interfaces siguen en CentOS 6.4 nombrandose de la forma que conozco, eth0, eth1, eth2, ..., ethn para todas las interfaces Ethernet (cableada) y para las inalámbricas wlan0 y asi, instalé CentOS 6.4 minimal, tengo una pc media moderna y reconoció el hardware, dudo mucho que no reconozca hardaware nuestro querido CentOS 6.x, trae bastante soporte en estas versiones, pero puede ser también que no reconozca, y pues ahí si hay que hacer otras cosas, en alcance libre Joel Barrios decía si OpenSUSE, Fedora y Ubuntu no reconoce la mayoría de hardware tu máquina no es para Linux y creo que es cierto, ademas recuerda que CentOS esta más enfocada a Servidores y no tanto para desktop, yo más uso CentOS para servidor sin interfaz gráfica, para escritorio uso Ubuntu, Fedora u OpenSUSE traen más soporte en drivers y software para uso diario. Como te digo ya configuré parametros de red en CentOS 6.4 y trato de ver en página man y por ahí en otra ayuda y no veo que nombren a p1p2, etc como monbre para interfáz de red, mirando más ayuda: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/appe-Consistent_Network_Device_Naming.html Pues te digo que no veo aún en forma explicita la nueva forma de nombrarse o posible forma como dice en alcance libre.org, leyendo esa web dice que depende de qué hardware se tenga, y pone comandos que deberías de usarlos, posiblemente estés en lo cierto amigo, si cumple esas condiciones, pero la verdad no sé de donde sacó información alcancelibre para decir que las nuevas versiones de CentOS nombra de esa manera, traté de buscar por ahi en la referencia oficial y no veo, en fin esas cosas avanzadas escapan de mi conocimiento :(, solo traté de ayudarte indicandote lo que segun mi experiencia y cosas que hago veo con CentOS, saludos y suerte. P.D.: si alguien d ela lsita podría aclararnos ese detalle estaré muy agradecido, si es posible el mismo Joel Barrios que también esta suscrito a la lista, saludos. Nota: como sabemos Redhat toma algunas cosas de Fedora para sus nuevas liberaciones entonces no sería de extrañar que dentro de próximas releases, pero dentro varias recién usaran esa forma de nombrar a las interfaces, pro ahora creo que no en la mayoría de los casos. El 23 de marzo de 2013 14:05, Tranc3 Music edgarr...@gmail.com escribió: El 21/03/13, Rodrigo Pichiñual Norin rodrigo.pichin...@gmail.com escribió: Antes de instalar Centos tenia fedora 18 en mi laptop y me reconocía amabas redes cableada e inalambrica (p1p2 wlan0), pero con centos no me reconoce ni una, la red cableada tuve que meterle mano yo. Si ocupo ifconfig -a solo me muestra la local lo Si muestra esa salida posiblemente no tienes interfaces, estan dañadas o no estan haciendo contacto, ES MUY raro que no reconozca que yo sepa ahora CentOS en la versión 6.x debe reconocer mucho hardware ya no es como CentOS 5, posiblemente también tu hardware es muy reciente y poco comun. después de configurar la red cableada y al hacer un ifconfig -a ,uestra Cómo haz configurado? no llego a entender si no lo veías antes cómo has hecho y TODAVIA PARA VERLO con ese nombre, no se si estoy mal (LO DUDO) pero hasta donde vi en CentOS 6.0 las interfaces se nombran todavía con eth0, eth1, ..., wlan0 (wifi) y NO P1P2 eso es de fedora que en nueva release introduce nueva forma de nombrar a las interfaces, yo soy el único que esta hablando de esto? hay varios en la lista que usan CentOS y no dicen si p1p2 es válido en CentOS, que yo sepa NO lo p1p2 Muy extraño, deamasiado diría CentOS no nombra de esa manera a las interfaces, por ahora, fedora si nombra de esa manera. me captas? Causa confusión lo que muestras, mira que dice la docuentación redhat el 6 https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html No existe p1p2, eso es de fedora, en Centos debería de ser eth..., asi debería de verse si es que reconoce, aunque podría cambiarse, pero mejor sería dejar con ese nombre. Gracias. El 21 de marzo de 2013 02:23, Tranc3 Music edgarr...@gmail.com escribió: El 20/03/13, Rodrigo Pichiñual Norin rodrigo.pichin...@gmail.com escribió: Hola a todos, Resulta que instala CentOS en su versión *minimal Desktop*, una vez terminada la instalación pude ver que no tenia red, en un principio * NetworkManager* intentaba configurar mi red, pero aun así no tenia net, me puse a configurar la red cableada (Ethernet) el dispositivo por defecto era *p1p2* y ahora tengo
Re: [CentOS] Can't find root device with lvm root after moving drive on CentOS 6.3
On 03/24/2013 10:43 PM, Joakim Ziegler wrote: I haven't actually tried writing anywhere in the rescue shell before vgchange and mount. I'll give it a try, that would simplify things. If nothing else, you probably can fit most or all of that in the shell's environment. In case it's ever useful: # debug=$(lvm pvdisplay; lvm vgdisplay; lvm lvdisplay; blkid; dmesg) # vgchange -a y # mount ... # echo $debug /mnt/sysroot/root/debug ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 6.3 Network bnx2 Problem on HP DL360
Hello Svavar
This was the first time that this problem occurred - with 60 Servers and about
half a year of Centos 6 (5 before).
But because the interfaces have a permanent load - really 24x7 - problems with
power management would be a disaster.
I will try to switch off.
Thanks
Hartmut
How often are you getting these crashes ?
I had simular problem on my HP DL380 G7 server.
I disabled Active State PowerManagement on the PCI-E express.
Try it.
Add pcie_aspm=off as optional boot option.
Best regards,
Svavar O
Reykjavik - Iceland
On 19.3.2013, at 15:32, Woehrle Hartmut SBB CFF FFS (Extern) wrote:
Hello Mailing List
I got a severe network error message at a HP DL360 Server.
The kernel log says:
--- /var/log/messages
-
Mar 19 15:45:06 server kernel: do_IRQ: 2.168 No irq handler for vector
(irq -1) Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1:
DEBUG: intr_sem[0] PCI_CMD[00100446] Mar 19 15:45:17 server kernel:
bnx2 :02:00.1: eth1: DEBUG: PCI_PM[19002108]
PCI_MISC_CFG[9288] Mar 19 15:45:17 server kernel: bnx2
:02:00.1: eth1: DEBUG: EMAC_TX_STATUS[0008]
EMAC_RX_STATUS[0006] Mar 19 15:45:17 server kernel: bnx2
:02:00.1: eth1: DEBUG: RPM_MGMT_PKT_CTRL[4088] Mar 19 15:45:17
server kernel: bnx2 :02:00.1: eth1: DEBUG:
HC_STATS_INTERRUPT_STATUS[017f0080]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG:
PBA[] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1:
--- start MCP states dump --- Mar 19 15:45:17 server kernel: bnx2
:02:00.1: eth1: DEBUG: MCP_STATE_P0[0003610e]
MCP_STATE_P1[0003610e] Mar 19 15:45:17 server kernel: bnx2
:02:00.1: eth1: DEBUG: MCP mode[b880] state[80008000]
evt_mask[0500] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1:
DEBUG: pc[0800adec] pc[0800aeb0] instr[8fb10014] Mar 19 15:45:17 server
kernel: bnx2 :02:00.1: eth1: DEBUG: shmem states:
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG:
drv_mb[0103000f] fw_mb[000f] link_status[006f]
drv_pulse_mb[432b] Mar 19 15:45:17 server kernel: bnx2
:02:00.1: eth1: DEBUG: dev_info_signature[44564903]
reset_type[01005254] condition[0003610e] Mar 19 15:45:17 server
kernel: bnx2 :02:00.1: eth1: DEBUG: 03cc:
0a3c Mar 19 15:45:17 server kernel: bnx2 :02:00.1:
eth1: DEBUG: 03dc: 0ffe Mar 19
15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03ec:
0002 Mar 19 15:45:17 server kernel:
bnx2 :02:00.1: eth1: DEBUG: 0x3fc[] Mar 19 15:45:17 server
kernel: bnx2 :02:00.1: eth1: --- end MCP states dump --- Mar 19
15:45:17 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is
Down Mar 19 15:45:20 server kernel: bnx2 :02:00.1: eth1: NIC
Copper Link is Up, 1000 Mbps full duplex
--
-
Does anyone know that problem?
System is Centos 6.3 Kernel
Linux server 2.6.32-279.5.2.el6.centos.plus.x86_64 #1 SMP Fri Aug 24
00:25:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Thanks
Hartmut
___
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] Centos 6.3 Network bnx2 Problem on HP DL360
After you have tried the pcie_aspm boot option, also try :
echo performance /sys/module/pcie_aspm/parameters/policy
This will disable ASPM on PCIe and operate with maximum performance.
This is what I use today on the DL380 G7.
On 25.3.2013, at 09:06, Woehrle Hartmut SBB CFF FFS (Extern) wrote:
Hello Svavar
This was the first time that this problem occurred - with 60 Servers and
about half a year of Centos 6 (5 before).
But because the interfaces have a permanent load - really 24x7 - problems
with power management would be a disaster.
I will try to switch off.
Thanks
Hartmut
How often are you getting these crashes ?
I had simular problem on my HP DL380 G7 server.
I disabled Active State PowerManagement on the PCI-E express.
Try it.
Add pcie_aspm=off as optional boot option.
Best regards,
Svavar O
Reykjavik - Iceland
On 19.3.2013, at 15:32, Woehrle Hartmut SBB CFF FFS (Extern) wrote:
Hello Mailing List
I got a severe network error message at a HP DL360 Server.
The kernel log says:
--- /var/log/messages
-
Mar 19 15:45:06 server kernel: do_IRQ: 2.168 No irq handler for vector
(irq -1) Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1:
DEBUG: intr_sem[0] PCI_CMD[00100446] Mar 19 15:45:17 server kernel:
bnx2 :02:00.1: eth1: DEBUG: PCI_PM[19002108]
PCI_MISC_CFG[9288] Mar 19 15:45:17 server kernel: bnx2
:02:00.1: eth1: DEBUG: EMAC_TX_STATUS[0008]
EMAC_RX_STATUS[0006] Mar 19 15:45:17 server kernel: bnx2
:02:00.1: eth1: DEBUG: RPM_MGMT_PKT_CTRL[4088] Mar 19 15:45:17
server kernel: bnx2 :02:00.1: eth1: DEBUG:
HC_STATS_INTERRUPT_STATUS[017f0080]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG:
PBA[] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1:
--- start MCP states dump --- Mar 19 15:45:17 server kernel: bnx2
:02:00.1: eth1: DEBUG: MCP_STATE_P0[0003610e]
MCP_STATE_P1[0003610e] Mar 19 15:45:17 server kernel: bnx2
:02:00.1: eth1: DEBUG: MCP mode[b880] state[80008000]
evt_mask[0500] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1:
DEBUG: pc[0800adec] pc[0800aeb0] instr[8fb10014] Mar 19 15:45:17 server
kernel: bnx2 :02:00.1: eth1: DEBUG: shmem states:
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG:
drv_mb[0103000f] fw_mb[000f] link_status[006f]
drv_pulse_mb[432b] Mar 19 15:45:17 server kernel: bnx2
:02:00.1: eth1: DEBUG: dev_info_signature[44564903]
reset_type[01005254] condition[0003610e] Mar 19 15:45:17 server
kernel: bnx2 :02:00.1: eth1: DEBUG: 03cc:
0a3c Mar 19 15:45:17 server kernel: bnx2 :02:00.1:
eth1: DEBUG: 03dc: 0ffe Mar 19
15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03ec:
0002 Mar 19 15:45:17 server kernel:
bnx2 :02:00.1: eth1: DEBUG: 0x3fc[] Mar 19 15:45:17 server
kernel: bnx2 :02:00.1: eth1: --- end MCP states dump --- Mar 19
15:45:17 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is
Down Mar 19 15:45:20 server kernel: bnx2 :02:00.1: eth1: NIC
Copper Link is Up, 1000 Mbps full duplex
--
-
Does anyone know that problem?
System is Centos 6.3 Kernel
Linux server 2.6.32-279.5.2.el6.centos.plus.x86_64 #1 SMP Fri Aug 24
00:25:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Thanks
Hartmut
___
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
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] maintaining patches across releases
Keith Keller wrote: I was looking at this bug which my machines are currently experiencing: https://bugzilla.redhat.com/show_bug.cgi?id=883905 The proposed patch is literally one new line in the XFS codebase. So since the patch is so straightforward, I had a crazy idea that I would build my own kernel with this patch, and test it out to see if it worked. (It's been many years since I built my own kernel, so that would be an adventure in and of itself.) Looks like this problem will be fix in kernel-2.6.32-358.5.1.el6 - see https://bugzilla.redhat.com/show_bug.cgi?id=921958 James Pearson ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Bonded interfaces - testing
Hi, I have 2 servers running CentOS 6.3. Each has four 1gb Ethernet ports. I have bonded all four ports on each server and patched them to the same switch (following the instructions at http://wiki.centos.org/TipsAndTricks/BondingInterfaces). I have created aggregated trunks for the servers respective ports on the switch. The switch reports that the ports are up and that the Link Aggregation is enabled. I was under the impression, perhaps falsely, that I would see an improvement in the throughput. I am not sure that I am. I used a utility call nuttcp before the trunking and after to test the throughput. I am seeing miniscule differences in the Mbps. I am not sure that I am testing correctly. Perhaps the speed will not change but the available bandwidth has increased. Is there some way to demonstrate that I am able to transfer data from these two servers at a rate of 4,000Mbs? Does anyone have any thoughts? I pasted some details below increase they have a bearing. Thanks in advance Dermot. ./nuttcp otherserver 1125.6573 MB / 10.03 sec = 941.4967 Mbps 10 %TX 47 %RX cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: slow Aggregator selection policy (ad_select): stable Active Aggregator Info: Aggregator ID: 2 Number of ports: 4 Actor Key: 17 Partner Key: 420 Partner Mac Address: 10:0d:7f:4c:16:ca Slave Interface: eth0 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 2c:76:8a:5d:28:1c Aggregator ID: 2 Slave queue ID: 0 Slave Interface: eth1 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 2c:76:8a:5d:28:1d Aggregator ID: 2 Slave queue ID: 0 Slave Interface: eth2 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 2c:76:8a:5d:28:1e Aggregator ID: 2 Slave queue ID: 0 Slave Interface: eth3 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 2c:76:8a:5d:28:1f Aggregator ID: 2 Slave queue ID: 0 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Bonded interfaces - testing
Does anyone have any thoughts? I pasted some details below increase they have a bearing. Remember that LACP (802.3ad) uses a hash algorithm (configurable on how it's carried out and whether you use mac addresses, dst/src IPs and ports will vary quite often for optimisation) to pick a physical connection for the TCP flow ... and that will stay over the physical connection. As such for any one given flow you'll see up to the speed of the physical interface the data is going over... the speed increases come with multiple systems communicating with that server and with the right pick of hashing function having those connections go over differing interfaces. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Bonded interfaces - testing
In which case, an appropriate test would be to have several servers push data to one the server while it's interface is un-bonded. We'd anticipate that the results would be under 1000Mbps. Then do the same with the bonded interface and the results would hopefully be more consistently around 1000Mpbs. So I should not expect fastest throughput, simply a fatter pipe? If it matters these are the hashing options available on the switch: Thanks, Dermot Src MAC, VLAN, EType, incoming port Dest MAC, VLAN, EType, incoming port Src/Dest MAC, VLAN, EType, incoming port Src IP and Src TCP/UDP Port fields Dest IP and Dest TCP/UDP Port fields Src/Dest IP and TCP/UDP Port fields Enhanced hashing mode On 25 March 2013 14:56, James Hogarth james.hoga...@gmail.com wrote: Does anyone have any thoughts? I pasted some details below increase they have a bearing. Remember that LACP (802.3ad) uses a hash algorithm (configurable on how it's carried out and whether you use mac addresses, dst/src IPs and ports will vary quite often for optimisation) to pick a physical connection for the TCP flow ... and that will stay over the physical connection. As such for any one given flow you'll see up to the speed of the physical interface the data is going over... the speed increases come with multiple systems communicating with that server and with the right pick of hashing function having those connections go over differing interfaces. ___ 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] nscd
Has anyone had problems accessing random websites since going up to 6.4? Since about the day after I got partly upgraded, if I try to access nytimes.com, or orbitz.com, I get server not found. With a lot of work, I, my manager, and the other admin, found that setting options edns0 in /etc/resolv.conf fixed it - I suspect that the network folks updated their internal nameservers (which are M$) about that time... but... we got this Thurs. Friday, I went to look, lunchtime, at a story, and back to the same. Later, and I think I was playing around, it came back. Just now, over lunch, it failed... until I restarted nscd. My manager tells me it's caching... but it seems to be caching momentary failures. So: has anyone else seen oddness that might be related to nscd? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nscd
m.r...@5-cent.us wrote: Has anyone had problems accessing random websites since going up to 6.4? Since about the day after I got partly upgraded, if I try to access nytimes.com, or orbitz.com, I get server not found. With a lot of work, I, my manager, and the other admin, found that setting options edns0 in /etc/resolv.conf fixed it - I suspect that the network folks updated their internal nameservers (which are M$) about that time... but... we got this Thurs. Friday, I went to look, lunchtime, at a story, and back to the same. Later, and I think I was playing around, it came back. Just now, over lunch, it failed... until I restarted nscd. My manager tells me it's caching... but it seems to be caching momentary failures. So: has anyone else seen oddness that might be related to nscd? A quick followup of myself to provide more info: I see, in /etc/nscd.conf, that all the negative ttl's appear to be 20 sec, but I'm resonably sure that once I lose it, it's 20 sec before go back to try again, and it's still not gone. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] [Partially Solved] -Re: PHP Questions on move from CentOS 5.x to CentOS 6.x
On Sun, 24 Mar 2013, Johnny Hughes wrote: On 03/24/2013 10:45 AM, Max Pyziur wrote: [...] Apache's log files show a 503 (for postgresql) and 500 (for mysql) errors I'm troubleshooting this through obvious channels (looking at logfiles, searching google, sdiff'ing configuration files). However, if someone has suggestions or answers, please do speak up! The php versions in CentOS-5 and CentOS-6 are different. You don't say what version you are using and what version you moved to WRT php. However, if you were running the default, the versions of software that run on CentOS-5 might have to be upgraded to run on the newer php in CentOS-6. (from php-5.1.6 to php-5.3.3) You might also need to follow the upgrade procedures when moving from the older version of mysql and postgresql in CentOS-5 to the newer versions in CentOS-6. (mysql-5.0.95 to mysql-5.1.67, postgresql-8.1.23 to postgresql-8.4.13) Upgrading for major versions (ie, from CentOS-5.x to CentOS-6.x) is a major undertaking and data/configuration files usually have to upgraded. This is unlike moving between point releases within the same major version (ie, moving from 5.8 to 5.9 or 6.3 to 6.4). This is because minor version upgrades are designed to just work because of backporting and freezing ABI/API changes inside the Major version ... whereas changing Major versions is a major upgrade and should be planned and testing accordingly. The problems are separated here (divide and conquer). The PHP/Mysql websites now function. The issue was a default directive in /etc/php.ini; the directive is short_open_tag. On CentOS 5 it is on; on CentOS 6 is off. Dropping the following into relevant .htaccess files: php_value short_open_tag 1 fixed the problem. On the PostgreSQL/Drupal/PHP side: I installed four minor releases of Drupal (6.14 - 6.28), creating new test sites. Each works as designed. So the PHP/PostgreSQL stack isn't the problem. Existing websites (using Drupal releases ranging from 6.14- 6.22) are where the errors are occuring. One person suggested deleting cache* content and session* content in relevant tables. That hasn't restored things; but the hunch now is that it is somewhere in the data. fyi, MP p...@brama.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nscd
On Tue, Mar 26, 2013 at 6:26 AM, m.r...@5-cent.us wrote: Has anyone had problems accessing random websites since going up to 6.4? Since about the day after I got partly upgraded, if I try to access nytimes.com, or orbitz.com, I get server not found. With a lot of work, I, my manager, and the other admin, found that setting options edns0 in /etc/resolv.conf fixed it - I suspect that the network folks updated their internal nameservers (which are M$) about that time... but... we got this Thurs. Friday, I went to look, lunchtime, at a story, and back to the same. Later, and I think I was playing around, it came back. Just now, over lunch, it failed... until I restarted nscd. My manager tells me it's caching... but it seems to be caching momentary failures. So: has anyone else seen oddness that might be related to nscd? Do you want the whole book? 'nscd' is a synonym for weird. I've had many strange DNS issues which have been solved by either bouncing nscd or purging its cache entries. However, you appear to be using nscd on your machine to cache DNS and using the internal MS DSN servers to do the actual lookups. Am I correct? In which case, the MS DNS server should be caching the DNS lookups anyway, so you probably don't derive a lot of benefit from the nscd unless you do a lot of repeated DNS lookups. Cheers, Cliff ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nscd
On Tuesday, Cliff Pratt wrote: On Tue, Mar 26, 2013 at 6:26 AM, m.r...@5-cent.us wrote: Has anyone had problems accessing random websites since going up to 6.4? Since about the day after I got partly upgraded, if I try to access nytimes.com, or orbitz.com, I get server not found. With a lot of work, I, my manager, and the other admin, found that setting options edns0 in /etc/resolv.conf fixed it - I suspect that the network folks updated their internal nameservers (which are M$) about that time... but... we got this Thurs. Friday, I went to look, lunchtime, at a story, and back to the same. Later, and I think I was playing around, it came back. Just now, over lunch, it failed... until I restarted nscd. My manager tells me it's caching... but it seems to be caching momentary failures. So: has anyone else seen oddness that might be related to nscd? Do you want the whole book? 'nscd' is a synonym for weird. I've had many strange DNS issues which have been solved by either bouncing nscd or purging its cache entries. However, you appear to be using nscd on your machine to cache DNS and using the internal MS DSN servers to do the actual lookups. Am I correct? In which case, the MS DNS server should be caching the DNS lookups anyway, so you probably don't derive a lot of benefit from the nscd unless you do a lot of repeated DNS lookups. Cheers, Cliff NSCD is also necessary if you're running an LDAP or NIS environment, so don't just turn it off if you're using external authentication services. In a Winbind environment, NSCD is unnecessary however. -- Gary L. Greene, Jr. Sr. Systems Administrator IT Operations Minerva Networks, Inc. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nscd
On Mon, Mar 25, 2013 at 11:06:31PM +, Gary Greene wrote: NSCD is also necessary if you're running an LDAP or NIS environment, Not necessary in a NIS environment on a LAN 'cos NIS is UDP based and very very fast to respond. LDAP, however, pretty much needs nscd (or sssd) in order to be halfway near performant. -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to make a network interface come up automatically on link up?
On 24/03/13 4:01, Nux! wrote: On 24.03.2013 02:27, Joakim Ziegler wrote: I have a recently installed Mellanox VPI interface in my server. This is an InfiniBand interface, which, through the use of adapters, can also do 10GbE over fiber. I have one of the adapter's two ports configured for 10GbE in this way, with a point to point link to a Mac workstation with a Myricom 10GbE card. I've configured this interface on the Linux box (eth2) using /etc/sysconfig/network-scripts/ifcfg-eth2 , setting its IP address, MTU, subnet, etc. Try adding HOTPLUG=yes in the cfg file. Neither HOTPLUG=yes or MANAGED=no seems to make this interface come back up when the cable is unplugged and then plugged, unfortunately. For instance, before unplugging anything, ifconfig says: eth2 Link encap:Ethernet HWaddr 00:02:C9:29:64:8F inet addr:10.10.0.1 Bcast:10.10.255.255 Mask:255.255.0.0 inet6 addr: fe80::2:c900:129:648f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:47 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14924 (14.5 KiB) TX bytes:3940 (3.8 KiB) Then I unplug the cable, which, in dmesg, gives me: mlx4_en: eth2: Link Down And in /var/log/messages: Mar 25 11:36:24 resolve02 ntpd[4819]: Deleting interface #14 eth2, 10.10.0.1#123, interface stats: received=0, sent=0, dropped=0, active_time=163 secs (Which I guess is just ntpd reacting) And then I plug the cable back in, and in dmesg, I have: mlx4_en: eth2: Link Up Mar 25 11:38:09 resolve02 kernel: mlx4_en: eth2: Link Up Mar 25 11:38:09 resolve02 NetworkManager[4429]: info (eth2): carrier now ON (device state 2) Mar 25 11:38:09 resolve02 NetworkManager[4429]: info (eth2): device state change: 2 - 3 (reason 40) But ifconfig gives me: eth2 Link encap:Ethernet HWaddr 00:02:C9:29:64:8F inet6 addr: fe80::2:c900:129:648f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:104 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:25567 (24.9 KiB) TX bytes:3940 (3.8 KiB) So no IP address, and no joy. ifup eth2 brings me back to: eth2 Link encap:Ethernet HWaddr 00:02:C9:29:64:8F inet addr:10.10.0.1 Bcast:10.10.255.255 Mask:255.255.0.0 inet6 addr: fe80::2:c900:129:648f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:104 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:25567 (24.9 KiB) TX bytes:6493 (6.3 KiB) Ideas? -- Joakim Ziegler - Supervisor de postproducción - Terminal joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nscd
On 03/25/2013 10:26 AM, m.r...@5-cent.us wrote: Just now, over lunch, it failed... until I restarted nscd. My manager tells me it's caching... but it seems to be caching momentary failures. That could be coincidence. As far as I know, Firefox will not use nscd for hostname lookups. I confirmed Firefox using strace, but not others. If edns0 changed your system's behavior, I would suspect that someone recently turned on DNSSEC, and it's not working correctly. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nscd
On 03/25/2013 04:06 PM, Gary Greene wrote: NSCD is also necessary if you're running an LDAP or NIS environment, so don't just turn it off if you're using external authentication services. In a Winbind environment, NSCD is unnecessary however. I would advise all users to migrate to sssd from nscd. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] LVM filters not working?
Hi, I'm trying to set up a redundant DRBD system but I'm running into trouble when I try to define a volume group. The physical backing device for the drbd resource /dev/drbd0 is /dev/vdb1. The problem is that when I do a pvs on the command line the physical volume is shown as /dev/vdb1. So I tried the following filter in /etc/lvm/lvm.conf: filter = [ r|/dev/vdb.*|, a/.*/ But this doesn't seem to haven any effect at all. The system still sees the volumen group on /dev/vdb1. Also various how-to's on the net say I should pay attention to deleting /etc/lvm/cache/.cache which makes sense but this file is never created. Any ideas what might be going on here? I'm trying all of this on CentOS 6. Regards, Dennis ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't find root device with lvm root after moving drive on CentOS 6.3
Hi, Gordon, this was indeed a very good idea. I'm attaching that file here, as it's a bit large. Thanks in advance for help and ideas. -- Joakim Ziegler - Supervisor de postproducción - Terminal joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864 On 25/03/13 0:21, Gordon Messmer wrote: On 03/24/2013 10:43 PM, Joakim Ziegler wrote: I haven't actually tried writing anywhere in the rescue shell before vgchange and mount. I'll give it a try, that would simplify things. If nothing else, you probably can fit most or all of that in the shell's environment. In case it's ever useful: # debug=$(lvm pvdisplay; lvm vgdisplay; lvm lvdisplay; blkid; dmesg) # vgchange -a y # mount ... # echo $debug /mnt/sysroot/root/debug ___ 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] Can't find root device with lvm root after moving drive on CentOS 6.3
On 25/03/13 19:26, Joakim Ziegler wrote: Hi, Gordon, this was indeed a very good idea. I'm attaching that file here, as it's a bit large. Thanks in advance for help and ideas. Hm, it seems the list strips attachments, and just pasting it makes the mail too big to go through, so, pastebin to the rescue: http://pastebin.com/x4wqzHyc That's the output of, like you suggested: lvm pvdisplay; lvm vgdisplay; lvm lvdisplay; blkid; dmesg In that order. -- Joakim Ziegler - Supervisor de postproducción - Terminal joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to make a network interface come up automatically on link up?
On Mon, 2013-03-25 at 18:09 -0600, Joakim Ziegler wrote: On 24/03/13 4:01, Nux! wrote: On 24.03.2013 02:27, Joakim Ziegler wrote: I have a recently installed Mellanox VPI interface in my server. This is an InfiniBand interface, which, through the use of adapters, can also do 10GbE over fiber. I have one of the adapter's two ports configured for 10GbE in this way, with a point to point link to a Mac workstation with a Myricom 10GbE card. I've configured this interface on the Linux box (eth2) using /etc/sysconfig/network-scripts/ifcfg-eth2 , setting its IP address, MTU, subnet, etc. Try adding HOTPLUG=yes in the cfg file. Neither HOTPLUG=yes or MANAGED=no seems to make this interface come back up when the cable is unplugged and then plugged, unfortunately. For instance, before unplugging anything, ifconfig says: eth2 Link encap:Ethernet HWaddr 00:02:C9:29:64:8F inet addr:10.10.0.1 Bcast:10.10.255.255 Mask:255.255.0.0 inet6 addr: fe80::2:c900:129:648f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:47 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14924 (14.5 KiB) TX bytes:3940 (3.8 KiB) Then I unplug the cable, which, in dmesg, gives me: mlx4_en: eth2: Link Down And in /var/log/messages: Mar 25 11:36:24 resolve02 ntpd[4819]: Deleting interface #14 eth2, 10.10.0.1#123, interface stats: received=0, sent=0, dropped=0, active_time=163 secs (Which I guess is just ntpd reacting) And then I plug the cable back in, and in dmesg, I have: mlx4_en: eth2: Link Up Mar 25 11:38:09 resolve02 kernel: mlx4_en: eth2: Link Up Mar 25 11:38:09 resolve02 NetworkManager[4429]: info (eth2): carrier now ON (device state 2) Mar 25 11:38:09 resolve02 NetworkManager[4429]: info (eth2): device state change: 2 - 3 (reason 40) But ifconfig gives me: eth2 Link encap:Ethernet HWaddr 00:02:C9:29:64:8F inet6 addr: fe80::2:c900:129:648f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:104 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:25567 (24.9 KiB) TX bytes:3940 (3.8 KiB) So no IP address, and no joy. ifup eth2 brings me back to: eth2 Link encap:Ethernet HWaddr 00:02:C9:29:64:8F inet addr:10.10.0.1 Bcast:10.10.255.255 Mask:255.255.0.0 inet6 addr: fe80::2:c900:129:648f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:104 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:25567 (24.9 KiB) TX bytes:6493 (6.3 KiB) Ideas? I am just shooting in the dark what happen if you have NM_CONTROLLED=yes in the eth2 network script? -- Kind Regards Earl Ramirez GPG Key: http://trinipino.com/PublicKey.asc signature.asc Description: This is a digitally signed message part ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nscd
On Tue, Mar 26, 2013 at 12:06 PM, Gary Greene ggre...@minervanetworks.com wrote: On Tuesday, Cliff Pratt wrote: On Tue, Mar 26, 2013 at 6:26 AM, m.r...@5-cent.us wrote: Has anyone had problems accessing random websites since going up to 6.4? Since about the day after I got partly upgraded, if I try to access nytimes.com, or orbitz.com, I get server not found. With a lot of work, I, my manager, and the other admin, found that setting options edns0 in /etc/resolv.conf fixed it - I suspect that the network folks updated their internal nameservers (which are M$) about that time... but... we got this Thurs. Friday, I went to look, lunchtime, at a story, and back to the same. Later, and I think I was playing around, it came back. Just now, over lunch, it failed... until I restarted nscd. My manager tells me it's caching... but it seems to be caching momentary failures. So: has anyone else seen oddness that might be related to nscd? Do you want the whole book? 'nscd' is a synonym for weird. I've had many strange DNS issues which have been solved by either bouncing nscd or purging its cache entries. However, you appear to be using nscd on your machine to cache DNS and using the internal MS DSN servers to do the actual lookups. Am I correct? In which case, the MS DNS server should be caching the DNS lookups anyway, so you probably don't derive a lot of benefit from the nscd unless you do a lot of repeated DNS lookups. Cheers, Cliff NSCD is also necessary if you're running an LDAP or NIS environment, so don't just turn it off if you're using external authentication services. In a Winbind environment, NSCD is unnecessary however. Ah, yes, indeed. Thanks Gary, Cliff ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to make a network interface come up automatically on link up?
Mar 25 11:38:09 resolve02 kernel: mlx4_en: eth2: Link Up Mar 25 11:38:09 resolve02 NetworkManager[4429]: info (eth2): carrier now ON (device state 2) Mar 25 11:38:09 resolve02 NetworkManager[4429]: info (eth2): device state change: 2 - 3 (reason 40) Is the network manager REALLY disabled on that interface? -- Eero ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to make a network interface come up automatically on link up?
Well, /etc/sysconfig/network-scripts/ifcfg-eth2 looks like this: DEVICE=eth2 BOOTPROTO=none ONBOOT=yes NETWORK=10.10.0.0 NETMASK=255.255.0.0 IPADDR=10.10.0.1 USERCTL=no MTU=9000 HOTPLUG=yes NM_MANAGED=no -- Joakim Ziegler - Supervisor de postproducción - Terminal joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864 On 24/03/13 7:38, Patrick Lists wrote: On 24-03-13 08:03, Joakim Ziegler wrote: How do I do that? I've not used network manager to set it up, I just made the ifcfg-eth2 file from scratch. Besides the other two suggestions you may also want to set a proper SELinux label on the ifcfg-eth2 file with something like: /sbin/restorecon -v -F /etc/sysconfig/network-scripts/ifcfg-eth2 The SELinux label I have on my ifcfg-eth0 is: -rw-r--r--. root root system_u:object_r:net_conf_t:s0 ifcfg-eth0 Regards, Patrick ___ 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] How to make a network interface come up automatically on link up?
2013/3/26 Joakim Ziegler joa...@terminalmx.com: Well, /etc/sysconfig/network-scripts/ifcfg-eth2 looks like this: DEVICE=eth2 BOOTPROTO=none ONBOOT=yes NETWORK=10.10.0.0 NETMASK=255.255.0.0 IPADDR=10.10.0.1 USERCTL=no MTU=9000 HOTPLUG=yes NM_MANAGED=no try changing BOOTPROTO=static, instead of none. -- Eero ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to make a network interface come up automatically on link up?
2013/3/26 Eero Volotinen eero.voloti...@iki.fi: 2013/3/26 Joakim Ziegler joa...@terminalmx.com: Well, /etc/sysconfig/network-scripts/ifcfg-eth2 looks like this: DEVICE=eth2 BOOTPROTO=none ONBOOT=yes NETWORK=10.10.0.0 NETMASK=255.255.0.0 IPADDR=10.10.0.1 USERCTL=no MTU=9000 HOTPLUG=yes NM_MANAGED=no try changing BOOTPROTO=static, instead of none. some documentation also like NM_CONTROLLED=no : http://wiki.centos.org/FAQ/CentOS6 -- Eero ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't find root device with lvm root after moving drive on CentOS 6.3
On 03/25/2013 06:35 PM, Joakim Ziegler wrote: That's the output of, like you suggested: And you ran that before you ran vgchange -a y? That doesn't make any sense. The commands show the volume group active. I can't see any reason why the system wouldn't boot. I hate for you to keep rebooting your server, but do the device nodes look correct in both /dev/mapper and /dev/vg_resolve02 at that point? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't find root device with lvm root after moving drive on CentOS 6.3
Yes, I ran that immediately after getting dropped to the shell. I can take a look at the device nodes tomorrow, but if I remember correctly, /dev/mapper contained only the file control before running vgchange -ay, that is, there was no vg_resolve02-lv_root device there. That device only shows up after I run vgchange -ay. I did not check whether /dev/vg_resolve02 exists, I can do that tomorrow. -- Joakim Ziegler - Supervisor de postproducción - Terminal joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864 On 25/03/13 23:26, Gordon Messmer wrote: On 03/25/2013 06:35 PM, Joakim Ziegler wrote: That's the output of, like you suggested: And you ran that before you ran vgchange -a y? That doesn't make any sense. The commands show the volume group active. I can't see any reason why the system wouldn't boot. I hate for you to keep rebooting your server, but do the device nodes look correct in both /dev/mapper and /dev/vg_resolve02 at that point? ___ 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
