Discuss

discuss@lists.centos.org

34758 discussions

XORG and LCD Projector
by Andrew 'Dewa' B. Osmond 11 Sep '11

11 Sep '11

dear guys, I have a problem between my CentOS 5.5 (on Axioo notebook) and LCD Projector. When I connect my notebook to LCD Projector, it can detect my notebook. But when I press Fn + F7 to activate dual monitor between my notebook and LCD Projector it goes to blank screen. FYI, the LCD Projector is NEC but I don't know the series. I've tried to change display using dual head monitor but it has no effects. Do I need some driver?? and this is my xorg configuration : Section "Device" Identifier "Videocard0" Driver "openchrome" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x800" "1024x768" "800x600" "640x480" EndSubSection EndSection Hope you guys can help me. Thanks. Andrew.

6 8

Centos NFS-Utils
by Rita 11 Sep '11

11 Sep '11

Just wondering, We have been using RHEL 6.1 for a while and its NFS-utils support the fsc option for caching. Will Centos 5.6(or .7) ever support this feature? -- --- Get your facts first, then you can distort them as you please.--

1 0

Postfix Question - CentOS 6
by John Hinton 10 Sep '11

10 Sep '11

I'm trying to figure out if this is a bug... I'm running Postfix with Dovecot Authentication and have Amavisd-new as the front end. I fought with the install and in particular being able to send mail.... Auth failed. Hours of looking through all the config files yielded nothing... so I started Googling about. I finally found a comment at the bottom of a blog to check permissions on: /var/spool/postfix/private/auth It seems this must be owned by postfix but it was owned by root. So, can somebody check to see if this is there in a CentOS 6 Postfix install where Amavis is not installed? And if so, what are the default permissions? Thanks, John Hinton

3 4

Re: [CentOS] CentOS 6 Installation on Thinkpad X220
by Janne Nyman 10 Sep '11

10 Sep '11

> Hi > > unless you are doing this for a specific reason (ie eval/training) would > advise that centos is not really a laptop distribution despite what > redhat may try to suggest. > > best desktop/laptop in my opinion is mageia > > regards peter >> I am trying to install CentOS 6 x86_64 on a Lenovo Thinkpad x220. >> >> During the installation it asks me to insert a driver. >> >> Has anyone done this successfully? >> > > Hi Peter, thanks for your feedback. I guess the reason I am doing it, is as I love the way CentOS works, I.e. the stability and performance. I am currently running it on a ThinkPad Edge 11 and all seems to work great. Just looks like the e1000e NIC driver is not working with the kernel in 6.0. I have also tried this with RHEL 6.1 but that also gets me stuck at the booting of the x220. I have tried to understand how the "load driver disk" works with CentOS and RHEL based systems, but I am failing to get it working. I have got my hands on the e1000e driver and patched the initrd but still no go. That's why I wanted to check if anyone else has got this working :) Anyone else? Kind regards, Janne Nyman E: jnyman(a)jbtec.org

7 7

Conga problems
by James Edwards 09 Sep '11

09 Sep '11

Hi all, I've spent the past little while attempting to setup Conga on a two node CentOS 6 cluster. While I do have the cluster up and running, I'm running into problems attempting to start services through luci on either node. A little background information: -Both nodes have dual NICs, one interface on each node will be used for the WAN, the other is a private gigabit crossover link between the nodes. -Both nodes are in /etc/hosts -The nodes are up to date, and both are running x86_64 -SELinux and iptables have both been disabled -To get the cluster running, luci, ricci, and their dependencies were installed, and 'service start ricci', then 'service start luci' where issued. ricci created certs when first run. The problem is: I've successfully created an IP resource through luci, but when attempting to start it through 'Services', it fails to start and I get the following error in /var/log/luci/luci.log: 07:32:33,648 INFO [luci.controllers.cluster] User "root" started service "ip failover" in cluster "MailCluster" 07:32:33,654 ERROR [luci.lib.ricci_communicator] Unable to establish an SSL connection to mail01.mydomain.com:11111: _ssl.c:480: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/luci/lib/ricci_communicator.py", line 56, in __init__ self.ss.connect((self.__hostname, self.__port)) File "/usr/lib64/python2.6/ssl.py", line 309, in connect self.do_handshake() File "/usr/lib64/python2.6/ssl.py", line 293, in do_handshake self._sslobj.do_handshake() SSLError: [Errno 1] _ssl.c:480: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol When I connect to port 11111 using openssl, I receive 'Clients_SSL_certificate_required' and the connection closes. Also, netstat reports: tcp 0 0 :::11111 :::* LISTEN 9745/ricci I hope I've provided enough information, but any input or thoughts would be greatly appreciated. Thanks, James

3 4

Emulate RHEV On CentOS
by Gene Poole 09 Sep '11

09 Sep '11

Anyone familiar with RHEV (Red Hat Enterprise Virtualization)? Any ideas on how to emulate this on CentOS? Thanks, Gene Poole

12 25

Where are the CentOS 6 security updates?
by Lintula 09 Sep '11

09 Sep '11

The release announcement for CentOS-6.0 posted on CentOS-announce on Sun Jul 10 mentioned that: > Since upstream has a 6.1 version already released, we will be using a > Continous Release repository for 6.0 to bring all 6.1 and post 6.1 > security updates to all 6.0 users, till such time as CentOS-6.1 is > released itself. There will be more details about this posted within the > next 48 hours. I have not noticed anything said about this since, and I can't find any security updates. Firefox, for instance, is at 3.6.9. This is about a year old with many known security problems, so it really shouldn't be used. CentOS 5 and RHEL 6 have 3.6.18. Are there still no security updates available for CentOS 6, or have I just managed to completely miss how to access them?

9 8

CentOS5 with Dell Broadcom iSCSI Offload, does it work ?
by Antonio da Silva Martins Junior 09 Sep '11

09 Sep '11

Hi all, After finding multiples answers to this question via google, but without making it work on my servers. Has anybody iSCSI Offload working on a Dell Server with Broadcom NICs ? My environment: I'm running CentOS 5.6 CR, on a Dell PowerEdge R710 with Broadcom Corporation NetXtreme II BCM5709 conecting to an EMC CX4-120 SAN, via 2x Cisco 2960G-24TC-L switches. It's working without the iSCSI offload. Thanks in advance, Antonio. -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Antonio S. Martins Jr. - Support Analyst | "Only The Shadow Knows | | Universidade Estadual de Maringá - Brasil| what evil lurks in the | | NPD - Núcleo de Processamento de Dados | Heart of Men!" | | E-Mail: asmartins(a)uem.br / shadow(a)uem.br | !!! Linux User: 52392 !!! | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ "Real Programmers don’t need comments — the code is obvious."

4 4

Re: [CentOS] CentOS5 with Dell Broadcom iSCSI Offload, does it work ?
by Antonio da Silva Martins Junior 09 Sep '11

09 Sep '11

----- "Steve Walsh" <steve(a)nerdvana.net.au> escreveu: > De: "Steve Walsh" <steve(a)nerdvana.net.au> > Para: centos(a)centos.org > Enviadas: Sexta-feira, 9 de Setembro de 2011 9:17:50 (GMT-0300) Auto-Detected > Assunto: Re: [CentOS] CentOS5 with Dell Broadcom iSCSI Offload, does it work ? > > On 09/09/2011 10:05 PM, Drew Weaver wrote: > > Hi, > > > > I could be wrong here but don't you go into the Broadcom NIC > > configuration while the server is booting and add the iSCSI target in > > there and then it should appear as "Just Another Volume (TM)" to the > > operating system? > > > > I've never tried it but I assume thats how the 'offloading' works. > > close, but not. TCP Offloading (obviously) offloads the TCP protocol > processing from the server CPU onto the server adapter. This preserves > valuable CPU cycles for applications processing and improves overall > server performance and network efficiency, as the heavy lifting for > iSCSI is done on the card, by the card. > > <snip> > > After finding multiples answers to this question via google, but > > without making it work on my servers. Has anybody iSCSI Offload > > working on a Dell Server with Broadcom NICs ? > > Depending on how the Broadcom is in the server (ie - Physical Card vs > onboard mezzanine card) depends on if you enable it in BIOS, or switch > into the firmware when prompted at boot time to enable it. Hi, Well... I looked into the NICs config to make sure it's on. On BIOS I can see the 4 onboard NICs. On these I can chage from "no boot" / PXE / iSCSI boot. And the BIOS "detect" that this NICs are TOE & ISOE "capable". I had PXE on the first one and "no boot" on the other 3. From the NICs firmware menu I can see all the 8 NICs (including the 4 onboard), I can change the same options, no option to enable/disable iSCSI Offload, only iSCSI boot. I'm trying the instructions from: - http://www.open-iscsi.org/docs/README - http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/pdf/Online_Sto… - http://webpages.marshall.edu/~wolfe21/papers/rhel5-iscsi-HOWTO.pdf All of these say almost the same, and I can configure open-iscsi to access the EMC SAN using the two broadcom NICs using dm-multipath. But when I tryed to use the second MAC on the NIC (to activate iSCSI Offload) then I can't connect on the SAN. I can discovery it using the second MAC, but can't connect. Using "default" iface, it will conect using eth1 or eth2: [root@vHst-153-NEAD03 ~]# iscsiadm -m discoverydb -t st -p 10.252.1.1:3260 -I default --discover -P 1 Target: iqn.1992-04.com.emc:cx.ckm00091500140.a2 Portal: 10.252.1.1:3260,1 Iface Name: default Target: iqn.1992-04.com.emc:cx.ckm00091500140.b2 Portal: 10.252.1.2:3260,2 Iface Name: default Target: iqn.1992-04.com.emc:cx.ckm00091500140.a3 Portal: 10.252.2.1:3260,3 Iface Name: default Target: iqn.1992-04.com.emc:cx.ckm00091500140.b3 Portal: 10.252.2.2:3260,4 Iface Name: default [root@vHst-153-NEAD03 ~]# iscsiadm -m node -I default -lLogging in to [iface: default, target: iqn.1992-04.com.emc:cx.ckm00091500140.a3, portal: 10.252.2.1,3260] Logging in to [iface: default, target: iqn.1992-04.com.emc:cx.ckm00091500140.b2, portal: 10.252.1.2,3260] Logging in to [iface: default, target: iqn.1992-04.com.emc:cx.ckm00091500140.b3, portal: 10.252.2.2,3260] Logging in to [iface: default, target: iqn.1992-04.com.emc:cx.ckm00091500140.a2, portal: 10.252.1.1,3260] Login to [iface: default, target: iqn.1992-04.com.emc:cx.ckm00091500140.a3, portal: 10.252.2.1,3260] successful. Login to [iface: default, target: iqn.1992-04.com.emc:cx.ckm00091500140.b2, portal: 10.252.1.2,3260] successful. Login to [iface: default, target: iqn.1992-04.com.emc:cx.ckm00091500140.b3, portal: 10.252.2.2,3260] successful. Login to [iface: default, target: iqn.1992-04.com.emc:cx.ckm00091500140.a2, portal: 10.252.1.1,3260] successful. [root@vHst-153-NEAD03 ~]# iscsiadm -m session tcp: [5] 10.252.2.1:3260,3 iqn.1992-04.com.emc:cx.ckm00091500140.a3 tcp: [6] 10.252.1.2:3260,2 iqn.1992-04.com.emc:cx.ckm00091500140.b2 tcp: [7] 10.252.2.2:3260,4 iqn.1992-04.com.emc:cx.ckm00091500140.b3 tcp: [8] 10.252.1.1:3260,1 iqn.1992-04.com.emc:cx.ckm00091500140.a2 [root@vHst-153-NEAD03 ~]# iscsiadm -m session -P 1 Target: iqn.1992-04.com.emc:cx.ckm00091500140.a3 Current Portal: 10.252.2.1:3260,3 Persistent Portal: 10.252.2.1:3260,3 ********** Interface: ********** Iface Name: default Iface Transport: tcp Iface Initiatorname: iqn.1994-05.com.redhat:vHst-153-NEAD03 Iface IPaddress: 10.252.2.153 Iface HWaddress: <empty> Iface Netdev: <empty> SID: 5 iSCSI Connection State: LOGGED IN iSCSI Session State: LOGGED_IN Internal iscsid Session State: NO CHANGE <snip> But, if I try the same with the eth1 offload, I get: [root@vHst-153-NEAD03 ~]# ifconfig eth1 eth1 Link encap:Ethernet Endereço de HW BC:30:5B:FD:F7:E7 inet end.: 10.252.1.153 Bcast:10.252.1.255 Masc:255.255.255.0 endereço inet6: fe80::be30:5bff:fefd:f7e7/64 Escopo:Link UP BROADCASTRUNNING MULTICAST MTU:9000 Métrica:1 RX packets:735 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 colisões:0 txqueuelen:1000 RX bytes:47040 (45.9 KiB) TX bytes:620 (620.0 b) IRQ:26 Memória:d2000000-d2012800 [root@vHst-153-NEAD03 ~]# iscsiadm -m iface default tcp,<empty>,<empty>,<empty>,<empty> iser iser,<empty>,<empty>,<empty>,<empty> bnx2i.bc:30:5b:fd:f7:e8 bnx2i,bc:30:5b:fd:f7:e8,10.252.1.53,<empty>,<empty> bnx2i.bc:30:5b:fd:f7:ea bnx2i,bc:30:5b:fd:f7:ea,10.252.2.53,<empty>,<empty> [root@vHst-153-NEAD03 ~]# iscsiadm -m iface -I bnx2i.bc:30:5b:fd:f7:e8 # BEGIN RECORD 2.0-872 iface.iscsi_ifacename = bnx2i.bc:30:5b:fd:f7:e8 iface.net_ifacename = <empty> iface.ipaddress = 10.252.1.53 iface.hwaddress = bc:30:5b:fd:f7:e8 iface.transport_name = bnx2i iface.initiatorname = <empty> # END RECORD [root@vHst-153-NEAD03 ~]# iscsiadm -m discoverydb -t st -p 10.252.1.1:3260 -I bnx2i.bc:30:5b:fd:f7:e8 --discover -P 1 Target: iqn.1992-04.com.emc:cx.ckm00091500140.a2 Portal: 10.252.1.1:3260,1 Iface Name: bnx2i.bc:30:5b:fd:f7:e8 Target: iqn.1992-04.com.emc:cx.ckm00091500140.b2 Portal: 10.252.1.2:3260,2 Iface Name: bnx2i.bc:30:5b:fd:f7:e8 Target: iqn.1992-04.com.emc:cx.ckm00091500140.a3 Portal: 10.252.2.1:3260,3 Iface Name: bnx2i.bc:30:5b:fd:f7:e8 Target: iqn.1992-04.com.emc:cx.ckm00091500140.b3 Portal: 10.252.2.2:3260,4 Iface Name: bnx2i.bc:30:5b:fd:f7:e8 [root@vHst-153-NEAD03 ~]# iscsiadm -m node -I bnx2i.bc:30:5b:fd:f7:e8 -l Logging in to [iface: bnx2i.bc:30:5b:fd:f7:e8, target: iqn.1992-04.com.emc:cx.ckm00091500140.a3, portal: 10.252.2.1,3260] Logging in to [iface: bnx2i.bc:30:5b:fd:f7:e8, target: iqn.1992-04.com.emc:cx.ckm00091500140.b2, portal: 10.252.1.2,3260] Logging in to [iface: bnx2i.bc:30:5b:fd:f7:e8, target: iqn.1992-04.com.emc:cx.ckm00091500140.b3, portal: 10.252.2.2,3260] Logging in to [iface: bnx2i.bc:30:5b:fd:f7:e8, target: iqn.1992-04.com.emc:cx.ckm00091500140.a2, portal: 10.252.1.1,3260] iscsiadm: Could not login to [iface: bnx2i.bc:30:5b:fd:f7:e8, target: iqn.1992-04.com.emc:cx.ckm00091500140.a3, portal: 10.252.2.1,3260]. iscsiadm: initiator reported error (8 - connection timed out) iscsiadm: Could not login to [iface: bnx2i.bc:30:5b:fd:f7:e8, target: iqn.1992-04.com.emc:cx.ckm00091500140.b2, portal: 10.252.1.2,3260]. iscsiadm: initiator reported error (8 - connection timed out) iscsiadm: Could not login to [iface: bnx2i.bc:30:5b:fd:f7:e8, target: iqn.1992-04.com.emc:cx.ckm00091500140.b3, portal: 10.252.2.2,3260]. iscsiadm: initiator reported error (8 - connection timed out) iscsiadm: Could not login to [iface: bnx2i.bc:30:5b:fd:f7:e8, target: iqn.1992-04.com.emc:cx.ckm00091500140.a2, portal: 10.252.1.1,3260]. iscsiadm: initiator reported error (8 - connection timed out) iscsiadm: Could not log into all portals Well, has anybody make this to work ? What I'm missing ? Thanks in advance, Antonio. -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Antonio S. Martins Jr. - Support Analyst | "Only The Shadow Knows | | Universidade Estadual de Maringá - Brasil| what evil lurks in the | | NPD - Núcleo de Processamento de Dados | Heart of Men!" | | E-Mail: asmartins(a)uem.br / shadow(a)uem.br | !!! Linux User: 52392 !!! | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ "Real Programmers don’t need comments — the code is obvious."

1 0

CentOS-announce Digest, Vol 79, Issue 4
by centos-announce-request＠centos.org 09 Sep '11

09 Sep '11

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2011:1264 Important CentOS 4 i386 gstreamer-plugins - security update (Tru Huynh) 2. CESA-2011:1264 Important CentOS 4 x86_64 gstreamer-plugins - security update (Tru Huynh) 3. CESA-2011:1267 Important CentOS 4 i386 thunderbird - security update (Tru Huynh) 4. CESA-2011:1267 Important CentOS 4 x86_64 thunderbird - security update (Tru Huynh) 5. CESA-2011:1266 Important CentOS 4 i386 seamonkey - security update (Tru Huynh) 6. CESA-2011:1266 Important CentOS 4 x86_64 seamonkey - security update (Tru Huynh) 7. CESA-2011:1268 Important CentOS 4 i386 firefox - security update (Tru Huynh) 8. CESA-2011:1268 Important CentOS 4 x86_64 firefox - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Thu, 8 Sep 2011 19:33:02 +0200 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2011:1264 Important CentOS 4 i386 gstreamer-plugins - security update To: centos-announce(a)centos.org Message-ID: <20110908173302.GA2605(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2011:1264 gstreamer-plugins security update for CentOS 4 i386: https://rhn.redhat.com/errata/RHSA-2011-1264.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/gstreamer-plugins-0.8.5-1.EL.4.i386.rpm updates/i386/RPMS/gstreamer-plugins-devel-0.8.5-1.EL.4.i386.rpm source: updates/SRPMS/gstreamer-plugins-0.8.5-1.EL.4.src.rpm You may update your CentOS-4 i386 installations by running the command: yum update gstreamer-plugins Tru -- Tru Huynh (mirrors, CentOS i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss