From mertensb at mazdaeur.com Wed Nov 10 07:39:15 2010 From: mertensb at mazdaeur.com (Mertens, Bram) Date: Wed, 10 Nov 2010 08:39:15 +0100 Subject: [rhn-users] LVM- LV snapshots size? In-Reply-To: References: Message-ID: <1EF123869BB2CC4EAC0A1AA45CFFC2FA02524E11A9@DEFRWPMB001.ad.fdc.mazdaeur.com> Please direct this question either to an LVM specific list or at least the general red hat mailing list. You have far more chance of getting a reply on such a list. This list is reserved for topics concerning RHN. I have no experience with this myself but I'd the space you need depends on the expected amount of changes made to the file system and the time you need the snapshot. At least this is true for VMWare snapshots. But as I said you'd better as someone who has experience with this on a different list. Regards Bram Mazda Motor Logistics Europe NV, Blaasveldstraat 162, B-2830 Willebroek VAT BE 0406.024.281, RPR Mechelen, ING 310-0092504-52, IBAN : BE64 3100 0925 0452, SWIFT : BBRUBEBB From: rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com] On Behalf Of Rogelio Bazan Sent: donderdag 28 oktober 2010 17:47 To: rhn-users at redhat.com Subject: [rhn-users] LVM- LV snapshots size? Hi All i would like to know how much size should be assigned to a snapshot of a LV? I've seen several examples, but not much people talks about that topic... should it be the same as the used-space? thanx in advance! -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Caetano at hp.com Wed Nov 17 04:53:48 2010 From: Greg.Caetano at hp.com (Caetano, Greg) Date: Wed, 17 Nov 2010 04:53:48 +0000 Subject: [rhn-users] question on RHEL6 yum updates Message-ID: I am working with a custom distribution and see the following behavior when doing a "yum update" to rhn.redhat.com [root at dl360g306]# rpm -qa yum yum-3.2.27-14.el6_0.1.noarch [root at dl360g306]# rpm -q --whatprovides /etc/sysconfig/rhn/up2date rhn-client-tools-1.0.0-38.el6.noarch [root at dl360g306]# rhn_check [root at dl360g306]# yum update Loaded plugins: downloadonly, refresh-packagekit, rhnplugin, security Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-i386-server-6. Please verify its path and try again If I edit /etc/sysconfig/rhn/up2date and change the protocol from https to https by modifying the serverURL serverURL=http://xmlrpc.rhn.redhat.com/XMLRPC [root at dl360g306]# yum update Loaded plugins: downloadonly, refresh-packagekit, rhnplugin, security rhel-i386-server-6 | 1.8 kB 00:00 Error: failed to retrieve repodata/216454a6b5f351413c3656390b31f2c2cf4a1496b333d7ecb950c258a001ca99-primary.xml.gz from rhel-i386-server-6 error was [Errno 14] Peer cert cannot be verified or peer cert invalid Suggestions? Greg Caetano Chicago, IL greg.caetano at hp.com Red Hat Certified Engineer From inode0 at gmail.com Wed Nov 17 05:33:55 2010 From: inode0 at gmail.com (inode0) Date: Tue, 16 Nov 2010 23:33:55 -0600 Subject: [rhn-users] question on RHEL6 yum updates In-Reply-To: References: Message-ID: On Tue, Nov 16, 2010 at 10:53 PM, Caetano, Greg wrote: > I am working with a custom distribution and see the following behavior when doing a "yum update" to > rhn.redhat.com > > [root at dl360g306]# rpm -qa yum > yum-3.2.27-14.el6_0.1.noarch > [root at dl360g306]# rpm -q --whatprovides /etc/sysconfig/rhn/up2date > rhn-client-tools-1.0.0-38.el6.noarch > [root at dl360g306]# rhn_check > > [root at dl360g306]# yum update > Loaded plugins: downloadonly, refresh-packagekit, rhnplugin, security > Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-i386-server-6. Please verify its path > and try again > > > If I edit /etc/sysconfig/rhn/up2date and change the protocol from https to https by modifying the serverURL > serverURL=http://xmlrpc.rhn.redhat.com/XMLRPC > > > [root at dl360g306]# yum update > Loaded plugins: downloadonly, refresh-packagekit, rhnplugin, security > rhel-i386-server-6 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? | 1.8 kB ? ? 00:00 > Error: failed to retrieve > repodata/216454a6b5f351413c3656390b31f2c2cf4a1496b333d7ecb950c258a001ca99-primary.xml.gz from > rhel-i386-server-6 > error was [Errno 14] Peer cert cannot be verified or peer cert invalid > > Suggestions? While I haven't seen this yet with RHEL6 it is getting to be a fairly common sight with RHEL5. Usual causes I think are being unlucky enough to try to update while the metadata is still rebuilding after new updates have been pushed or the CDN node you happen to be connecting to just has broken metadata. In the first case it clears up usually in an hour or two. In the second case it can last longer. You can disable using CDN on that machine's RHN system page preferences and see if that helps. John From Mc_Kiernan at Oeconomist.com Wed Nov 17 14:26:51 2010 From: Mc_Kiernan at Oeconomist.com (Mc Kiernan Daniel Kian) Date: Wed, 17 Nov 2010 06:26:51 -0800 Subject: [rhn-users] Characters not Displayed Message-ID: <4CE3E62B.6040601@Oeconomist.com> Prior to my migrating from RHEL 5.5 to 6.0, when I used characters U+223b, U+227b, U+227f, U+2280 in formulae coded within OpenOffice Math (the formula editor) of OO 3.2.1, the document displayed these when viewed in OpenOffice, and an exported PDF displayed these when viewed with Acrobat readers. Now, when the very same version of OpenOffice is used in RHEL 6.0, the character becomes invisible both in .ODTs and in .PDFs. My suspicion is that the system UI used to make substitutions from another font file when a character were not in a specified font file, but is now not doing this. Can someone either disabuse me of this suspicion, or tell me how to re-establish the substitutions? From Greg.Caetano at hp.com Wed Nov 17 15:03:44 2010 From: Greg.Caetano at hp.com (Caetano, Greg) Date: Wed, 17 Nov 2010 15:03:44 +0000 Subject: [rhn-users] question on RHEL6 yum updates In-Reply-To: References: Message-ID: Progress..... Going to the RHN page for the system on rhn.redhat.com and removing the checkmark for the "location aware updates", I am now able to use yum to get updates as long as the serverURL is NOT using SSL. (maintaining http as the protocol instead of https). If I edit the serverURL back to https, I receive the same error "Cannot retrieve repository metadata (repomd.xml)" -----Original Message----- From: rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com] On Behalf Of inode0 Sent: Tuesday, November 16, 2010 11:34 PM To: Discussions about Red Hat Network (rhn.redhat.com) Subject: Re: [rhn-users] question on RHEL6 yum updates On Tue, Nov 16, 2010 at 10:53 PM, Caetano, Greg wrote: > I am working with a custom distribution and see the following behavior when doing a "yum update" to > rhn.redhat.com > > [root at dl360g306]# rpm -qa yum > yum-3.2.27-14.el6_0.1.noarch > [root at dl360g306]# rpm -q --whatprovides /etc/sysconfig/rhn/up2date > rhn-client-tools-1.0.0-38.el6.noarch > [root at dl360g306]# rhn_check > > [root at dl360g306]# yum update > Loaded plugins: downloadonly, refresh-packagekit, rhnplugin, security > Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-i386-server-6. Please verify its path > and try again > > > If I edit /etc/sysconfig/rhn/up2date and change the protocol from https to https by modifying the serverURL > serverURL=http://xmlrpc.rhn.redhat.com/XMLRPC > > > [root at dl360g306]# yum update > Loaded plugins: downloadonly, refresh-packagekit, rhnplugin, security > rhel-i386-server-6 | 1.8 kB 00:00 > Error: failed to retrieve > repodata/216454a6b5f351413c3656390b31f2c2cf4a1496b333d7ecb950c258a001ca99-primary.xml.gz from > rhel-i386-server-6 > error was [Errno 14] Peer cert cannot be verified or peer cert invalid > > Suggestions? While I haven't seen this yet with RHEL6 it is getting to be a fairly common sight with RHEL5. Usual causes I think are being unlucky enough to try to update while the metadata is still rebuilding after new updates have been pushed or the CDN node you happen to be connecting to just has broken metadata. In the first case it clears up usually in an hour or two. In the second case it can last longer. You can disable using CDN on that machine's RHN system page preferences and see if that helps. John _______________________________________________ rhn-users mailing list rhn-users at redhat.com https://www.redhat.com/mailman/listinfo/rhn-users