Discuss March 2013

discuss@lists.centos.org

206 participants
228 discussions

mixing MX and CNAME
by aurfalien 27 Aug '14

27 Aug '14

Hi, Has any one had problems with mail clients were your DNS is like this; doman.com MX 50 mail.domain.com domain.com MX 100 mail2.domain.com domain.com CNAME www.domain.com -aurf

8 12

Create Virtual Machine via HTTP or FTP
by cbulist＠gmail.com 08 Jun '14

08 Jun '14

Hi, I'm trying to create a Virtual Machine using Network Install mode (I tried HTTP and FTP). The HTTP/FTP server where the installation files are located is the Host Machine. The URL that I'm using is: http://192.168.1.104/inst and the Automatic detect option detects the OS without problem. When the installation starts I got an error: Unable to retrieve http://192.168.1.104/inst/images/install.img I tried different path but I always get the same error. The host machine is a Centos 6.2 (2.6.32.-220.el6.x86_64) I really appreciate any help with this problem. Thanks in advance,

5 7

Building CentOS 6.2 custom install media
by Daniel Drake 14 Sep '13

14 Sep '13

Hi, For the OLPC school server ("XS") we are planning to move from our dated F9 setup to CentOS 6.2. Thanks for all the effort involved in producing this distro. One important part of this project is a 'respin' of the install media - we need to add a handful of packages from external repositories, and maybe run a command late in the install. Are the scripts/configurations used to produce the CentOS official CD/DVDs available? I guess this would be our most reliable/sensible starting point. I am familiar with pungi, kickstart, anaconda, etc, so just a simple git link would be enough to get me started. Thanks, Daniel

5 7

Help with thread Centos 6.4 won't reboot on install
by Robert Benjamin 26 Jul '13

26 Jul '13

Newbie here. Need help with a thread that has about 25 posts. No replies in a few days. The thread is in software support for centos 6 and the subject of the thread is Centos 6.4 won't reboot on install. Have had limited success in getting a login screen but once I logout, I can't get back in again. It was mentioned in the thread that the problem is likely in Network Configuration. I have no GUI (gnome) no mouse, no terminal, and keyboard use only with Ctl+Alt+F2. Can login as root but have no luck getting the GUI to appear or to get a user login screen. Thanks in advance for your help. Bob

11 79

No more support for chrome/chromium on rhel6
by Robert Arkiletian 26 Jun '13

26 Jun '13

https://plus.google.com/u/0/100132233764003563318/posts/Y1s6T44Soby Not 100% this is true but the problem apparently is that rhel6 uses an old version of gtk2. If this is true, then it affects my school and my students. I like google-chrome and it works very well with google services. I was planning on using C6 for a long time. Does anyone know of a repo that intends to keep Chromium working for C6? -- Robert Arkiletian Eric Hamber Secondary, Vancouver, Canada

14 26

Re: [CentOS] sieveshell fails to start on CentOS 6.0
by Devin Reade 12 Jun '13

12 Jun '13

--On Wednesday, August 10, 2011 01:52:21 PM -0400 Harold Pritchett <harold(a)uga.edu> wrote: > [harold@newmick ~]$ sieveshell localhost > connecting to localhost > unable to connect to server at /usr/bin/sieveshell line 170. Try specifying both --user and --authname as appropriate. sieveshell can be misleading in its error messages, and you may actually have an authentication error rather than a connection error there. You could run it under strace to make sure. Devin

3 2

How to make a network interface come up automatically on link up?
by Joakim Ziegler 24 Apr '13

24 Apr '13

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. Everything seems to work fine, with a single exception. If I reboot the Mac on the other end, causing the link state of the fiber interface to bounce, the network interface on the Linux box doesn't come back up when the link comes back up. That is, ifconfig shows it as having the link up, but it doesn't do the equivalent of "ifup eth2" when the link comes back, so it doesn't get an IP, the routing table doesn't get updated, etc. So, my question is, how can I make CentOS automatically configure this interface when the link comes back up? It's a bit annoying having to log in and do ifup eth2 every time... -- Joakim Ziegler - Supervisor de postproducción - Terminal joakim(a)terminalmx.com - 044 55 2971 8514 - 5264 0864

11 26

"Can't find root device" with lvm root after moving drive on CentOS 6.3
by Joakim Ziegler 22 Apr '13

22 Apr '13

I have an 8-core SuperMicro Xeon server with CentOS 6.3. The OS is installed on a 120 GB SSD connected by SATA, the machine also contains an Areca SAS controller with 24 drives connected. The motherboard is a SuperMicro X9DA7. When I installed the OS, I used the default options, which creates an LVM volume group to contain / and /home, and keeps /boot and /boot/efi outside the volume group. The machine is a couple of months old, and has been stable. While installing some new hardware, I decided to also clean up the cabling in the box, since it was a bit messy. In doing this, I probably moved the boot SSD disk to another port on the motherboard (it has a bunch, 2 SATA 6GBps and 6 SATA 3GBps). When I booted the box after this, I got a kernel panic, the typical "Can't find root device". I read some docs, and first tried to boot from a rescue disc and reinstal GRUB, but that didn't change anything. Further Googling got me the rdshell kernel parameter, and that dropped me to a shell when it failed to find the root device. Reading https://fedoraproject.org/wiki/How_to_debug_Dracut_problems , I did the following: # lvm vgscan # lvm vgchange -ay And then # ln -s /dev/mapper/<volumegroup>-<root_volume> /dev/root # exit After this, the box boots up normally, and everything works as it should. However, when I reboot, it again fails to find the root device. So, after all this, my question is, how do I make Dracut (I'm assuming) understand that this LVM volume is my root device and pick it up automatically? And, is there a way to avoid this problem in the future, if I move drives around? Surely it can't be normal for this to happen just because I connect a drive to another port? -- Joakim Ziegler - Supervisor de postproducción - Terminal joakim(a)terminalmx.com - 044 55 2971 8514 - 5264 0864

4 21

Virtual Machine Manager error
by Rajagopal Swaminathan 10 Apr '13

10 Apr '13

Greetings, I am getting the following error when I start the Virtual machine manager [root@centos Desktop]# uname -a Linux blah.blah.blah 2.6.32-220.2.1.el6.x86_64 #1 SMP Fri Dec 23 02:21:33 CST 2011 x86_64 x86_64 x86_64 GNU/Linux 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 any clues? TIA -- Regards, Rajagopal

12 17

Does CentOS support dual graphics cards with 2 monitors each?
by Alfred von Campe 07 Apr '13

07 Apr '13

I have a user who wants to have 4 monitors attached to his CentOS 6.4 system. I know that you can't use both on-board video and a PCI video card at the same time, but what about two PCI video cards? The system seems to recognize them as shown by the lspci -v output below, but I can't get Xorg to use the second card. Has anyone done this? If so, what is the trick to get it to work? Alfred 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Dell Device 04ad Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information <?> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 00004000-00004fff Memory behind bridge: ed000000-ee0fffff Prefetchable memory behind bridge: 00000000e0000000-00000000e9ffffff Capabilities: [88] Subsystem: Dell Device 04ad Capabilities: [80] Power Management version 3 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [a0] Express Root Port (Slot+), MSI 00 Capabilities: [100] Virtual Channel <?> Capabilities: [140] Root Complex Link <?> Kernel driver in use: pcieport 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Dell Device 04ad Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at eebb0000 (64-bit, non-prefetchable) [size=16] Capabilities: [50] Power Management version 3 Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+ 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) Subsystem: Dell Device 047e Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at eeb00000 (32-bit, non-prefetchable) [size=128K] Memory at eeb80000 (32-bit, non-prefetchable) [size=4K] I/O ports at 5040 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] PCI Advanced Features Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI]) Subsystem: Dell Device 04ad Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at eeb70000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci_hcd 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) Subsystem: Dell Device 04ad Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at eeb60000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel <?> Capabilities: [130] Root Complex Link <?> Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell Device 04ad Capabilities: [a0] Power Management version 2 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 00003000-00003fff Memory behind bridge: ee100000-eeafffff Prefetchable memory behind bridge: 00000000ea100000-00000000eaafffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell Device 04ad Capabilities: [a0] Power Management version 2 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: 00002000-00002fff Memory behind bridge: eb000000-ec0fffff Prefetchable memory behind bridge: 00000000d0000000-00000000d9ffffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell Device 04ad Capabilities: [a0] Power Management version 2 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI]) Subsystem: Dell Device 04ad Flags: bus master, medium devsel, latency 0, IRQ 17 Memory at eeb50000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) (prog-if 01 [Subtractive decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=05, subordinate=05, sec-latency=0 Capabilities: [50] Subsystem: Dell Device 04ad 00:1f.0 ISA bridge: Intel Corporation Q65 Express Chipset Family LPC Controller (rev 04) Subsystem: Dell Device 04ad Flags: bus master, medium devsel, latency 0 Capabilities: [e0] Vendor Specific Information <?> Kernel modules: iTCO_wdt 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 04) (prog-if 01 [AHCI 1.0]) Subsystem: Dell Device 04ad Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 30 I/O ports at 5090 [size=8] I/O ports at 5080 [size=4] I/O ports at 5070 [size=8] I/O ports at 5060 [size=4] I/O ports at 5020 [size=32] Memory at eeb40000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA <?> Capabilities: [b0] PCI Advanced Features Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) Subsystem: Dell Device 04ad Flags: medium devsel, IRQ 18 Memory at eeb30000 (64-bit, non-prefetchable) [size=256] I/O ports at 5000 [size=32] Kernel modules: i2c-i801 01:00.0 VGA compatible controller: NVIDIA Corporation Device 104a (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device 809f Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at ed000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=128M] Memory at e8000000 (64-bit, prefetchable) [size=32M] I/O ports at 4000 [size=128] Expansion ROM at ee000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information <?> Capabilities: [100] Virtual Channel <?> Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information <?> Kernel driver in use: nouveau Kernel modules: nouveau, nvidiafb 01:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1) Subsystem: Micro-Star International Co., Ltd. Device 809f Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at ee080000 (32-bit, non-prefetchable) [size=16K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel 04:00.0 VGA compatible controller: NVIDIA Corporation Device 104a (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device 809f Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at eb000000 (32-bit, non-prefetchable) [size=16M] Memory at d0000000 (64-bit, prefetchable) [size=128M] Memory at d8000000 (64-bit, prefetchable) [size=32M] I/O ports at 2000 [size=128] Expansion ROM at ec000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information <?> Capabilities: [100] Virtual Channel <?> Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information <?> Kernel driver in use: nouveau Kernel modules: nouveau, nvidiafb 04:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1) Subsystem: Micro-Star International Co., Ltd. Device 809f Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at ec080000 (32-bit, non-prefetchable) [size=16K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel

7 13

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss March 2013