Discuss May 2012

discuss@lists.centos.org

193 participants
202 discussions

problems with luci on CentOS 6.2
by Riccardo Veraldi 14 May '12

14 May '12

Hello, I have a 5 node cluster. virtsrv1n1 virtsrv2n2 virtsrv3n3 virtsrv4n4 virtsrv5n5 From Luci I am unable to manage virtsrv3n3 machine. Luci is unable to reboot it for example and if I select the node properties it shows me no status for Cluster Daemons for this specific node. All the other nodes are fully manageable from luci. from command line everything seems to work fine. net-cluster @ Sat May 12 00:53:33 2012 Member Status: Quorate Member Name ID Status ------ ---- ---- ------ virtsrv1n1.mydomain.org 1 Online, Local, rgmanager virtsrv2n2.mydomain.org 2 Online, rgmanager virtsrv3n3.mydomain.org 3 Online, rgmanager virtsrv4n4.mydomain.org 4 Online, rgmanager virtsrv5n5.mydomain.org 5 Online, rgmanager Looking the luci log i see this error if i try for exmaple to reboot the node from luci: 00:12:19,603 ERROR [luci.lib.ricci_helpers] Unable to retrieve the batch number from virtsrv3n3 ricci is working ok on the node as well as cman rgmanager and gfs2, and I do not have iptables active. Any hints ? thank you Rick

2 3

openLDAP under CentOS-6
by Timothy Murphy 13 May '12

13 May '12

I've been hard hit by the lack of CentOS-6 documentation mentioned in another thread. The openLDAP setup has been changed completely between CentOS 5 and 6, and I haven't been able to find any reasonably coherent instructions explaining how to upgrade. If anyone knows of such a document I should be most grateful to learn of it. Actually I have openLDAP working (though unencrypted) with my CentOS-5 data after a series of more or less random steps. But I can't work out how to set the password for the web interface at <server>/phpLDAPadmin . Again, if anyone can tell me how to do this I shall be most thankful. Incidentally, I looked at the RHEL documentation on this, <http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/ 6/html/Migration_Planning_Guide/ch07s03.html>, but it was so sparse as to be more or less useless. -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College Dublin

4 4

Allow updates but not upgrades
by Gregory Machin 13 May '12

13 May '12

Hi. At the moment it seems my machines just update to the latest current release . I install a 6.0 machine and run yum update , and next thing its 6.2 . I have a requirement where I need machines to only upgrade to even numbered sub releases eg: 6.0 , 6.2, 6.4 and only on my approval. But will allow updates within a given release. How can I achieve this ? If I sync the repositories for eg: 6.0 , 6.2, 6.4 separately in Spacewalk and only allow access to the ones I want to give access to, would that work ? Thanks G

11 23

Error connecting to KVM on CentOS 6.2
by Earl Ramirez 12 May '12

12 May '12

Hello List Mates, I don't know if here is the right place for this question if it's not I will appreciate it if you can point me to the right mailing list. I have successfully installed KVM on my x86_64 laptop, however I am getting the following error when I try to connect "QEMU" from the Virtual Machine Manager Error polling connection 'qemu:///system': internal error Cannot find suitable emulator for x86_64 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 440, in _tick conn.tick() File "/usr/share/virt-manager/virtManager/connection.py", line 1414, in tick newNets, self.nets) = self._update_nets() File "/usr/share/virt-manager/virtManager/connection.py", line 1277, in _update_nets lookup_func, build_class) File "/usr/share/virt-manager/virtManager/connection.py", line 1209, in _poll_helper if not check_support(): File "/usr/share/virt-manager/virtManager/connection.py", line 501, in is_network_capable virtinst.support.SUPPORT_CONN_NETWORK) File "/usr/lib/python2.6/site-packages/virtinst/support.py", line 574, in check_conn_support return _check_support(conn, feature, conn) File "/usr/lib/python2.6/site-packages/virtinst/support.py", line 443, in _check_support actual_drv_ver = _hv_ver(conn, uri) File "/usr/lib/python2.6/site-packages/virtinst/support.py", line 376, in _hv_ver ret = cmd(*args) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2823, in getVersion if ret == -1: raise libvirtError ('virConnectGetVersion() failed', conn=self) libvirtError: internal error Cannot find suitable emulator for x86_64 I using CentOS 6.2 [user1@trining ~]$ cat /etc/redhat-release CentOS release 6.2 (Final) Below are the processor that I am using, however I do not see any svm or vmx flags and there is no option to change anything in the BIOS for the processor. Does this mean I need to replace my current laptop to get KVM to work? [user1@training ~]$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz stepping : 10 cpu MHz : 1200.000 cache size : 2048 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dts bogomips : 3990.12 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz stepping : 10 cpu MHz : 1200.000 cache size : 2048 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dts bogomips : 3990.11 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: I am running the x86-64 version of CentOS 6.2 with the latest updates [user1@training ~]$ uname -a Linux training 2.6.32-220.13.1.el6.x86_64 $1 SMP Tue Apr 17 23:56:34 BST 2012 x86_64 x86_64 x86_64 GNU/Linux All the required packages have been installed [user1@training ~]$ rpm -qa | grep kvm qemu-kvm-0.12.1.2-2.209.el6_2.4.x86_64 qemu-kvm-tools-0.12.1.2-2.209.el6_2.4.x86_64 [user1@training ~]$ rpm -qa | grep virt virt-v2v-0.8.3-5.el6.x86_64 libvirt-client-0.9.4-23.el6_2.8.x86_64 libvirt-0.9.4-23.el6_2.8.x86_64 virt-who-0.3-3.el6.noarch virt-manager-0.9.0-7.el6.x86_64 python-virtinst-0.600.0-5.el6.noarch libvirt-snmp-0.0.2-3.el6.x86_64 virt-viewer-0.4.1-7.el6.x86_64 virt-top-1.0.4-3.11.el6.x86_64 virt-what-1.11-1.1.el6.x86_64 libvirt-python-0.9.4-23.el6_2.8.x86_64 libvirt-java-0.4.7-1.el6.noarch libvirt-cim-0.5.14-2.el6.x86_64 libvirt-qmf-0.3.0-7.el6_2.x86_64 None of the modules are installed, which I believe is related to the svm and vmx missing from the processor flags [user1@training ~]$ lsmod | grep kvm [user1@training ~]$ modprobe kvm [user1@training ~]$ lsmod | grep kvm kvm 305988 0 [user1@training ~]$ I have been googling all night everything that I have tried did not resolved. Any thoughts? -- Kind Regards Earl Ramirez

4 4

xulrunner 1.9.2.26 available in repackaged form for use with legacy programs
by Robert Heller 12 May '12

12 May '12

I have re-packaged xulrunner 1.9.2.26 for CentOS 5 for use with older applications which can't be run with xulrunner 10.0.4. I created 'compatibity' RPMs that can be safely installed alongside xulrunner 10.0.4. I needed it to run the Evergreen 2.1 and 2.2 Staff Clients at our local library. The RPMs are available in the Deepwoods Software repo at the URL: ftp://ftp.deepsoft.com/pub/deepwoods-repo/. Files available, with MD5sums: 1b0591ea0349003bd52a9315618bb714 xulrunner19-1.9.2.26-1.i386.rpm 25266e2ab9c4a2eccf6fe3d12c2cc26e xulrunner19-1.9.2.26-1.src.rpm 4b55490c4a1a8afecb9dd3d8ab4449b8 xulrunner19-1.9.2.26-1.x86_64.rpm b333cd37474acd0344d4367fb5d36504 xulrunner19-debuginfo-1.9.2.26-1.i386.rpm 4307465967bef17d506c307ee23d3fc1 xulrunner19-debuginfo-1.9.2.26-1.x86_64.rpm 05ec3872af564e3702c6c6ecb893f945 xulrunner19-devel-1.9.2.26-1.i386.rpm 04ab68b5ce6c7252114e57f224a47cbe xulrunner19-devel-1.9.2.26-1.x86_64.rpm -- Robert Heller -- 978-544-6933 / heller(a)deepsoft.com Deepwoods Software -- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments

2 1

Documentation question
by Nate Duehr 12 May '12

12 May '12

Apologies if this is a FAQ or it's simply due to a lack of volunteers. I'm curious why the CentOS Documentation here: http://www.centos.org/docs/5/ ...stops at CentOS 5.5. And also why there is no: http://www.centos.org/docs/6/ *** Curiosity killed the cat. *** Thanks, Nate

5 5

OT: PCI express questions???
by mcclnx mcc 12 May '12

12 May '12

We have several DELL servers run under CENTOS 5. I check server spec and found some servers expansion slot say PCIE and some say PCIE generation 2. My questions are: 1. does PCI express meaning PCIE 1.0??? 2. does PCIE generation 2 same like PCIE 2.0??? 3. what is speed on following: PCI X4: PCI X8: PCI generation 2 X4: PCI generation 2 X8: Thanks.

2 1

when is the o.s. considered to be at a certain minor version? Or, is it safe to apply only certain package updates from the next release version?
by Jon Detert 11 May '12

11 May '12

Two related questions about the minor release numbers (e.g. the 'x' in 5.x or 6.x) : 1) What constitutes the o.s. being at a particluar minor release? Typically, when you install you are getting a package set available from a specific minor release number. But what minor release is the o.s. at if I just update the centos-release package, and no other package? Typically, a 'yum update' is said to take your whole package set to the latest minor release. But what minor release is the o.s. if you just update certain packages (instead of taking all avaailable updates)? 2) Can I apply package updates made in a minor release greater than my current release without detriment to the integrity of the o.s.? E.g. Suppose all my packages are at versions delivered in v5.6. Suppose also, that I have a package xyz installed, and that an update to it was made available in v5.8. Can I upgrade xyz to the updated version from 5.8 without updating other packages (except for any dependencies xyz has) to the versions available in v5.8? Thanks, -- Jon Detert Sr. Systems Administrator Infinity Healthcare Milwaukee, Wisconsin 414-290-6759

8 9

How to prevent virtual machines running twice on the disk images?
by Theo Band 11 May '12

11 May '12

I use KVM on two identical centos5 hosts. I can live migrate the virtual machines from one to the other and it works great. Once I do this, I can see VM definitions on both hosts using virt-manager or virsh list --all On one machine the VM is running, on the other it reports "shut off". The disk images are accessible to both host machines and I want to have only one running a the time (of course). If the VM locks up, I could by mistake think that the machine is not running and try to start it on the wrong host. My question is, how can I prevent host A from starting a "shut off" VM that actually has been migrated to host B? The VM could actually be running on any another host. It could also have been crashed. The most simple solution would be some sort of lock file placed next to the disk image location, so seen by all hosts. But perhaps there is another way of working with virt-manager that I am not aware of? Theo

4 6

Cyrus-imapd update from 2.2.12 to 2.3.16
by James B. Byrne 11 May '12

11 May '12

We are trying to move our mail store from a host running cyrus-imapd 2.2.12 under CentOS-4 to one running 2.3.16 under CentOS-6. The current host is a 32 bit architecture. The new host is 64 bit. We have followed the update guide found at: http://www.cyrusimap.org/docs/cyrus-imapd/2.3.16/install-upgrade.php The steps we followed were: 1. Install cyrus-imapd et al on the new host. 2. Modify /etc/cyrus.conf and /etc/imapd.conf to suit our requirements. 3. On the old host dump the mailbox.db in flat format using /var/lib/cyrus-imapd/ctl_mboxlist -d > mboxlist.txt 4. Copy the mboxlist.txt file and the mail spool from the old to the new system 5. Run SELinux restorecon -fr on /var/spool/imap to set the correct contexts and ownership. 6. Load mailbox.db from mboxlist.txt using cat mboxlist.txt | /usr/lib/cyrus-imapd/ctl_mboxlist -u 7. Run /usr/lib/imapd-cyrus/reconstruct -rfg user 8. Run /usr/lib/imapd-cyrus/reconstruct -G user 9. Run /usr/lib/imapd-cyrus/quota -f 10. Start saslauthd and cyrus-imapd services. All the transferred mailboxes are seen and the imapd configuration data seems correct. The problem is that the quotas reported for each mailbox tree do not seem to aggregate under 2.3 as they did on 2.2. So, for example a user with an overall allocation of 500Mb reporting 70% utilization for the INBOX on the 2.2.13 version reports 3% on the 2.3.16 server even though the contents of the mailbox trees are identical. It seems that the new version calculates quota only for the INBOX itself, and not for all of the sub-directory contents. Is this a change in behaviour for 2.3 vice 2.2 or do I have a problem? Has anyone run into this and if so, how was it resolved? -- *** 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

2 1

← Newer
1
...
11
12
13
14
15
16
17
...
21
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss May 2012