Discuss

discuss@lists.centos.org

34758 discussions

Overdue upgrade of bind
by Robert Moskowitz 13 Feb '13

13 Feb '13

I am **FINALLY** starting in on upgrading my domain server. Right now it is still on bind-9.3.6 via Centos 5.5. Stepping right up to 9.8.2 in Centos 6.3. I am pretty good with zone files and the like, though I will finally get to tackle DNSSEC (and I can go to the sources Austien, Vixie, and Liu if need be or even the bind list!), but right now I have much more mundane issues. Like it looks a bit like the chroot tree has changed! In particular under /var/named/chroot/etc I use to put my named.conf with all the include files. Now I see sub-directories named and pki there. I am ASSuMEing that pki will be for the DNSSEC; but where is the documentation? I tried looking for readme files, but can't find anything related to the chrooted bind environment. What file is the location of named.conf set up in? The zone files look to go in the same place I have them on the old server under /var/named/chroot/named/var/named.

4 8

CentOS-announce Digest, Vol 96, Issue 7
by centos-announce-request＠centos.org 13 Feb '13

13 Feb '13

1 0

Intel video
by Birta Levente 13 Feb '13

13 Feb '13

Hi all Please someone tell me how can I enable intel video driver on centos 6.3 x86_64? It's an acer laptop (5736z) with Mobile intel 4 Series graphics. I tried with Xorg -configure, but give me an error something like number of created screens not match number of detected screens. Anyway, I tried to copy xorg.conf.new to /etc/X11/xorg.conf and reboot, removed nomodeset ... on laptop display I can't see anything, even the backlight is turned off, but on the VGA output appear the desktop background without menu, taskbar and icons and I can switch between tty-s. Could anyone help me? Thanks Levi

1 0

RHSA-2013:0223-1 - moderate kernel update
by m.roth＠5-cent.us 12 Feb '13

12 Feb '13

CentOS team: has the CentOS kernel update come out yet that addresses what upstream sent out the email this morning RHSA-2013:0223-1, which mentions a bugfix for a deadlock when oom-killer's invoked? mark

4 4

mdadm: hot remove failed for /dev/sdg: Device or resource busy
by Keith Keller 12 Feb '13

12 Feb '13

Hello all, I have run into a sticky problem with a failed device in an md array, and I asked about it on the linux raid mailing list, but since the problem may not be md-specific, I am hoping to find some insight here. (If you are on the MD list, and are seeing this twice, I humbly apologize.) The summary is that during a reshape of a raid6 on an up to date CentOS 6.3 box, one disk failed, and was marked as such in the array, but is not allowing me to remove it: # mdadm /dev/md127 --fail /dev/sdg mdadm: set /dev/sdg faulty in /dev/md127 # mdadm /dev/md127 --remove /dev/sdg mdadm: hot remove failed for /dev/sdg: Device or resource busy And in dmesg, I get an error like so: md: cannot remove active disk sdg from md127 ... More details, including mdadm -D output and other diagnostics, are at http://www.spinics.net/lists/raid/msg41928.html . As I note there, the array seems fine otherwise, but is not currently in active use (so perhaps my options are greater than if I wished to keep it deployed). As the other messages in that thread show, I think I've already done the ''obvious'' steps to try to remove the device from the array. Checking things out further, I found that it may be that udev did not completely remove the disk, even though the controller no longer believes that the exported unit exists. (udevadm output is here: http://www.spinics.net/lists/raid/msg41950.html ) So my hypothesis is that if I can somehow force udev to drop the references to the disk completely, perhaps I can remove sdg from the array and start a rebuild with the spare already available. I found these docs for Fedora: https://docs.fedoraproject.org/en-US/Fedora/14/html/Storage_Administration_… But of course I can't do step 3, since md is refusing to give up sdg. But sdg is already gone, so I really don't care about outstanding IO, and it's a bit too late to worry about a 100% clean removal. So my questions are, will step 7 actually clean up references to sdg, and how likely is it that doing so would let me remove it from the array? And finally, if the above is not a wise way to go, are there better things to try? If other diagnostic output is desired please let me know. Thanks! --keith -- kkeller(a)wombat.san-francisco.ca.us

2 3

Disabling the shutdown buttons in graphical login screen of CentOS 6.3
by Andrea*s Jackie Klaura 12 Feb '13

12 Feb '13

Hi, I am not sure if I probably have overlooked some important clue, but I am stuck with a problem with the gdm-greeter in CentOS 6.3 here since three days without finding any suitable solution. The problem: * I have to somehow deactivate the "Suspend", "Restart" and "Shutdown" options in the login screen. * This has to be done in CLI mode, as I have to change this on many machines Tried out solutions: * As far as I could figure out gdm-simple-greeter would be the programm I'd have to tweak. But changing options in /etc/gdm/custom.conf does not change anything (as if this file would be ignored). * Another thing would be to set the /apps/gdm/simple-greeter/disable_restart_buttons option to true through gconftool-2. But this option also seems to be ignored. Several posts on the web point to this being a bug which is fixed in RHEL but not CentOS. * I also tried to limit access to all the poweroff, reboot and halt commands through pam.d so that only root would be allowed to shutdown. This did not work either. * I even tried to rename the /sbin/reboot command (and therefore deactivate all the different links pointing to it). Still clicking the buttons still lead to a shutdown (although at some point it got stuck, but the system was not reachable any more). Additional remarks: * I did also delete /etc/acpi/events/power.conf in order to disable the physical power button on the machine. At least that did work, but the problem still is that normal users can shutdown the machine through the gdm login screen. If anyone has any hints, I would be very glad. And sorry if I overlooked anything, but meanwhile I am getting a bit desperate. Looking through the web and different mailing lists and fora gave me the impression that there are still several people out there with this problem and no real solution is around. thanks, cheers, jackie -- Andrea*s Jackie Klaura University of Vienna Institute of Theoretical Chemistry Waehringerstr. 17 A-1090 Vienna, Austria tel: +43 (0)1 4277 52756

2 2

Re: [CentOS] firefox problem
by James B. Byrne 12 Feb '13

12 Feb '13

On Mon, February 11, 2013 13:20, Les Mikesell wrote: > On Mon, Feb 11, 2013 at 11:59 AM, SilverTip257 > <silvertip257(a)gmail.com> wrote: >> >> But there's bad news for Google Chrome on RHEL 6 ... >> http://www.muktware.com/5203/google-says-red-hat-enterprise-linux-6-obsolete >> > > Google doesn't understand the concept of code getting past beta test > versions. > Neither does Mozilla.org. -- *** 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

A workaround to dhclient problems
by Stephen Harris 12 Feb '13

12 Feb '13

Summary: if you have C5 guests with dhclient "bad udp checksum" issues then this entry on the host will fix it: iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM --checksum-fill Detail: If anyone else is seeing this... Feb 11 19:22:11 mercury dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x63be132a) Feb 11 19:22:56 mercury last message repeated 3 times Feb 11 19:23:12 mercury dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x63be132a) Feb 11 19:23:12 mercury dhclient: 5 bad udp checksums in 5 packets Feb 11 19:23:20 mercury dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x63be132a) Feb 11 19:23:51 mercury last message repeated 2 times Feb 11 19:24:09 mercury last message repeated 2 times Feb 11 19:24:09 mercury dhclient: 5 bad udp checksums in 5 packets The client eventually expires the lease and goes back to DISCOVER state and then gets an IP address. This only seems to happen with C5 (RH5?) guests on a KVM host. C6 guests don't have the problem. Googling also shows Debian with issues, and the problem may be in the ISC code base. The work-around is to add an iptables entry on the host: iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM --checksum-fill With this in place dhclient on C5 guests can happily renew their address Feb 12 00:02:02 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x63be132a) Feb 12 00:02:02 mercury dhclient: DHCPACK from 10.0.0.134 (xid=0x63be132a) Feb 12 00:02:02 mercury dhclient: bound to 10.0.0.135 -- renewal in 16918 seconds. Feb 12 04:44:00 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x63be132a) Feb 12 04:44:00 mercury dhclient: DHCPACK from 10.0.0.134 (xid=0x63be132a) Feb 12 04:44:00 mercury dhclient: bound to 10.0.0.135 -- renewal in 18447 seconds. -- rgds Stephen

1 0

Centos 6 and VLAN-ID7 for vDSL (Telekom)
by Michael Nausch 12 Feb '13

12 Feb '13

AHOI! I've big trouble by setting up CentOS 6.3 for my new vDSL. As I've found out, the German Telekom is using VLAN7 for her internet-(data) connections. => http://workaround.org/blog/vdsl O.K. what I've done: The NIC where's my DSL-modem is connectet is eth0. cat /etc/sysconfig/network-scripts/ifcfg-eth0 # device for vDSL-modem DEVICE=eth0 HWADDR=00:30:1B:14:08:67 ONBOOT=yes HOTPLUG=no TYPE=Ethernet IPV6INIT=no IPV6-AUTOCONF=no cat /etc/sysconfig/network-scripts/ifcfg-eth0 # VLAN7 device for vDSL DEVICE=eth0.7 ONBOOT=yes HOTPLUG=no TYPE=Ethernet VLAN=yes with pppoe-setup I've generated /etc/sysconfig/network-scripts/ifcfg-ppp0 cat /etc/sysconfig/network-scripts/ifcfg-ppp0 # generated with pppoe-setup USERCTL=yes BOOTPROTO=dialup NAME=DSLppp0 DEVICE=ppp0 TYPE=xDSL ONBOOT=yes PIDFILE=/var/run/pppoe-adsl.pid FIREWALL=NONE PING=. PPPOE_TIMEOUT=80 LCP_FAILURE=3 LCP_INTERVAL=20 CLAMPMSS=1412 CONNECT_POLL=6 CONNECT_TIMEOUT=60 DEFROUTE=yes SYNCHRONOUS=no ETH=eth0.7 PROVIDER=DSLppp0 USER=feste-ip/<benutzerkennung>@t-online-com.de PEERDNS=no DEMAND=no /etc/ppp/chap-secret an /etc/ppp/pap_secret hast follewing content: # Secrets for authentication using PAP/CAHP # client server secret IP addresses "feste-ip/-benutzerkennung(a)t-online-com.de" * "<PASSWORD>" cat /rpc/betvlan/eth0.7 is showing: eth0.7 VID: 7 REORDER_HDR: 1 dev->priv_flags: 1 total frames received 0 total bytes received 0 Broadcast/Multicast Rcvd 0 total frames transmitted 6 total bytes transmitted 192 total headroom inc 0 total encap on xmit 0 Device: eth0 INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0 EGRESS priority mappings: If I try to start my internet-connection with: ifup ppp0 After a while I can read at command line: /usr/sbin/adsl-start: line 217: 7297 Terminated $CONNECT "$@" > /dev/null 2>&1 Syslog reports: Feb 11 22:37:40 pml010050 pppd[7321]: pppd 2.4.5 started by django, uid 0 Feb 11 22:37:40 pml010050 pppd[7321]: Using interface ppp0 Feb 11 22:37:40 pml010050 pppd[7321]: connect: ppp0 <--> /dev/pts2 Feb 11 22:38:11 pml010050 pppd[7321]: LCP: timeout sending Config-Request Feb 11 22:38:11 pml010050 pppd[7321]: Connection terminated. Feb 11 22:38:11 pml010050 pppd[7321]: Modem hangup Feb 11 22:38:15 pml010050 pppd[7325]: Timeout waiting for PADO packets Feb 11 22:38:15 pml010050 pppd[7321]: Exit. Feb 11 22:38:15 pml010050 pppoe-connect: PPPoE connection lost; attempting re-connection Feb 11 22:38:20 pml010050 pppd[7391]: pppd 2.4.5 started by django, uid 0 Feb 11 22:38:20 pml010050 pppd[7391]: Using interface ppp0 Feb 11 22:38:20 pml010050 pppd[7391]: connect: ppp0 <--> /dev/pts2 Feb 11 22:38:51 pml010050 pppd[7391]: LCP: timeout sending Config-Request Feb 11 22:38:51 pml010050 pppd[7391]: Connection terminated. Feb 11 22:38:51 pml010050 pppd[7391]: Modem hangup Feb 11 22:38:55 pml010050 pppd[7395]: Timeout waiting for PADO packets Feb 11 22:38:55 pml010050 pppd[7391]: Exit. So, where's the BUG? Thanx 4 help! Django

2 1

CentOS-announce Digest, Vol 96, Issue 6
by centos-announce-request＠centos.org 12 Feb '13

12 Feb '13

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-2013:0250 Moderate CentOS 5 elinks Update (Johnny Hughes) 2. CESA-2013:0250 Moderate CentOS 6 elinks Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 11 Feb 2013 18:29:01 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2013:0250 Moderate CentOS 5 elinks Update To: centos-announce(a)centos.org Message-ID: <20130211182901.GA12400(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2013:0250 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0250.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 75cbe33f5bb7ea55bd2ef978c7b8d0c674db4e2fa67a1c627e63cb308ec58fb1 elinks-0.11.1-8.el5_9.i386.rpm x86_64: b86b0351c799febfde895c99f8ccc281f07fc6529760189c47963c733f261e6f elinks-0.11.1-8.el5_9.x86_64.rpm Source: a259dfb31a06a91d662ade06515e66e0b19c9bfc41833eaa97cb44191f986c1a elinks-0.11.1-8.el5_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Mon, 11 Feb 2013 21:46:30 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2013:0250 Moderate CentOS 6 elinks Update To: centos-announce(a)centos.org Message-ID: <20130211214630.GA22843(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2013:0250 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0250.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0c56454480f1d2a95dfadc180f7ea2c9bfc19e730347e8082d86684f9e5e0e50 elinks-0.12-0.21.pre5.el6_3.i686.rpm x86_64: 3f6544d1b39eef3902cc5ec9e08af8ea21bf8218351d09763729df86684ffa12 elinks-0.12-0.21.pre5.el6_3.x86_64.rpm Source: 3564a3acee40c543fc33c4022b8e326e4e8f9ca3a55192dbe513c428d0da28ba elinks-0.12-0.21.pre5.el6_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 96, Issue 6 **********************************************

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