Discuss October 2013

discuss@lists.centos.org

179 participants
158 discussions

VNCserver not starting due to errors
by Gilbert Sebenste 09 Oct '13

09 Oct '13

Hello everyone, Following the directions I found here: http://wiki.centos.org/HowTos/VNC-Server I get to part 2.4, and when I start the vncservice, I get this error message: Starting VNC server: 1:blah Invalid null command. if: Expression Syntax. A VNC server is already running as :1 else: endif not found. [FAILED] If I stop it, and then restart it, I get the same error message. "blah" has been changed for security purposes on this email, but the real name is a valid user. I want to be on window "0", not 1. Any tips or suggestions would be greatly appreciated! Gilbert ******************************************************************************* Gilbert Sebenste (My opinions only!) *******************************************************************************

2 4

CentOS 6.4 Installation on Dell R720
by Kaushal Shriyan 09 Oct '13

09 Oct '13

Hi, I am planning to install CentOS 6.4 on Dell R720 which has hardware raid card and 6 hard disk slots available. I have planned with the below set up :- *2 Hard disks configured in RAID 1 for installing OS * *4 Hard disks configured in RAID 10 for data drive.* Please suggest and recommend if the above approach is correct and let me know if i am missing anything which is crucial to set up a production server. This server will host MySQL DB server. Regards, Kaushal

4 5

"Enterprise Class Hard Drive" - Scam Warning
by Steve Brooks 09 Oct '13

09 Oct '13

Hi All, I know many of us here manage RAID on our Centos based servers so this may be of interest to us all. I ordered three new "Enterprise hard drives" this month from a well known UK online retailer. The drives arrived as new in their anti-static packaging. Before using one of the drives in a mission critical hardware raid I checked the SMART attributes and was amazed at what I saw; see a few of the attributes listed below 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail - 2600 9 Power_On_Hours 0x0032 098 097 000 Old_age - 2106 12 Power_Cycle_Count 0x0032 100 100 000 Old_age - 80 198 Offline_Uncorrectable 0x0030 196 196 000 Old_age - 398 200 Multi_Zone_Error_Rate 0x0008 180 180 000 Old_age - 4077 So for a brand new packaged drive this was a bit of a surprise. "2106" power on hours, obviously should be zero for a new drive and "398" "Offline_Uncorrectable sectors" this is a well used and faulty drive. I contacted the (very well known) manufacturer of the drive and asked for information on the serial number. I was told the serial number of the drive was region specific to the USA and should not even be in the UK. I opened and tested the second and third drives with similar results. I was told two of the drives had already been returned under warranty and replaced with new drives. Wow... I was also told by the online retailer this is known as a grey import and is not that uncommon.. So it may be a good policy to check the SMART attributes of drives before deployment! Cheers, Steve

11 16

how to find RAID card world wide ID?
by mcclnx mcc 08 Oct '13

08 Oct '13

we have DELL server with PERC RAID card in it. O.S> is CENTOS 5.5. Can anyone tell me how to find SAS address (World wide ID) on RAID card? Thanks.

1 0

boot fails with dracut warning
by g 08 Oct '13

08 Oct '13

greetings, had problems burning a dvd for 6.4, so i burned a livecd and installed it from boot menu to ext4 /dev/sdb3. during install, i defined mounting of /dev/sdb5 as /home and a second partition /dev/sdb6. both are ext4. first boot went well, set up user, rebooted. rebooted level 5, logged in as user, all looked good. rebooted level 5, logged in as root, made changes to /boot/grub/grub.conf to boot other os. rebooted level 5, logged in as user, opened terminal, su to root, tried to 'yum update', all mirrors failed. did not think of trying pings to see if was connected to internet. which could have explained failure. my bad. exited from root, closed terminal, rebooted to other os, logged in as user, opened terminal, pinged several sites, pings returned ok. closed terminal, rebooted, to centos, crashed during level 5 boot. shutdown system, rebooted level 3, boot crashed again. error message; =+=+= ACPI: wmi: Mapper loaded dracut Warning: No root device "block: /dev/disk/by=uuid/dbb9f9c4-8f67- \ 4d79-aaef-4f804f31c800" found dracut Warning: Boot has failed. To debug this issue add "rdshell" to the \ kernel command line. dracut Warning: Signal caught! dracut Warning: Boot has failed. To debug this issue add "rdshell" to the \ kernel command line. kernel Panic - not syncing: Attempted to kill init! Pid: 1, comm: init Tainted: G I-------2.6.32-358.el6.x86_64 #1 Call Trace: [<ffffffff8150cfc8>]? panic+0xa7/0x16f [<ffffffff81073ae2>]? do_exit0x25/0x870 [<ffffffff81182885>]? fput_+0x25/0x30 [<ffffffff81073b48>]? do_group_exit+0x58/0xd0 [<ffffffff81073bd7>]? sys_exit_group+0x17/0x20 [<ffffffff8100b072>]? system_call_fastpath+0x16/x1b Panic occurred, switching back to text console *note1*: block device sought is not shown in /dev/fstab. =+=+= block devices defined in centos /etc/fstab; UUID=16c4f70d-0aff-4760-859c-ecf05e1e025f / ext4 \ defaults 1 1 UUID=e13d224f-d9a3-4697-8693-5395a1477050 /hd/sdb/06 ext4 \ defaults 1 2 UUID=a8f5c9e9-b792-4e30-a80b-08ed8b371886 /home ext4 \ defaults 1 2 UUID=e7c13ca9-3dbc-4cc7-9c6a-50efc0688a61 swap swap \ defaults 0 0 *note2*: block devices listed does not show block device sought during boot. *note3*: block devices are same between different os's. =+=+= i ran a search for; dracut Warning: No root device "block: /dev/disk/by=uuid/ at centos.org only errors show where raid related. another thing that is strange, boot is looking for a device that is not listed in /dev/disk/by-uuid. =+=+= from other os; ]$ ll /dev/disk/by-uuid/ total 0 lrwxrwxrwx. 1 root root 10 Oct 8 07:56 10BDD0693BFCE1E5 -> ../../sdb1 lrwxrwxrwx. 1 root root 10 Oct 8 07:56 16c4f70d-0aff-4760-859c-ecf05e1e025f -> ../../sdb3 lrwxrwxrwx. 1 root root 10 Oct 8 07:56 2FEF848329A39323 -> ../../sda2 lrwxrwxrwx. 1 root root 10 Oct 8 07:56 a8f5c9e9-b792-4e30-a80b-08ed8b371886 -> ../../sdb5 lrwxrwxrwx. 1 root root 10 Oct 8 07:56 AE90166090162F79 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Oct 8 07:56 e13d224f-d9a3-4697-8693-5395a1477050 -> ../../sdb6 lrwxrwxrwx. 1 root root 10 Oct 8 07:56 e7c13ca9-3dbc-4cc7-9c6a-50efc0688a61 -> ../../sdb2 *note4*: sda1 and sdb1 are ntfs and are not included in centos /etc/fstab. *note5*: block devices are same between different os's. =+=+= any and all suggestions welcome. tia. -- peace out. in a world with out fences, who needs gates. tc.hago. g .

1 0

C6: kickstart problems with additional repo
by Rainer Traut 08 Oct '13

08 Oct '13

Hi, I'm kickstarting a vm in ESXi 5.1. ks.cfg is on floppy, install media is ISO file. This works great as long as I don't add an additional repo, in our case it is vmware tools on one of our webservers. If I add the repo line, anaconda asks then for the used network card and indeed, switching to console the interfaces are still unconfigured. Chosing eth0 in gui continues the installation! This is the relevant part of ks.cfg install cdrom lang de_DE.UTF-8 keyboard de-latin1 skipx network --onboot yes --device eth0 --bootproto static --ip=192.168.200.28 --netmask=255.255.255.0 --gateway=192.168.200.1 --nameserver=192.168.200.9 --noipv6 network --onboot no --device eth1 --bootproto static --noipv6 network --onboot no --device eth2 --bootproto static --noipv6 repo --name=vmware51 --baseurl=http://xxx/repo/vmware/5.1/rhel6Server-x86_64/ I'm beginning to think the problem is, my install media is ISO and I have an additional http repo which is not available in this stage... Is there any workaround? Thx Rainer

2 4

How to list openvpn clients?
by Timothy Murphy 08 Oct '13

08 Oct '13

I'm running an openvpn server on a CentOS machine - that is my excuse for posting my query here - and I'm wondering if there is some way of finding all the clients (not just those connected at this moment) who have been registered as clients of the openvpn server? -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

3 4

remote sudo script
by Tim Dunphy 08 Oct '13

08 Oct '13

Hey guys, I'm trying to write a simple bash script that will cp a configuration file to a backup (with the date) remotely to a bunch of machines, using sudo with ssh. I notice that if I run the commands individually, they both work (albeit with some strange output I'd like to suppress): [tdunphy@MIAGRBISSH01V ~]$ ssh -q -t -t -t MIAGRBIORCA00V sudo -S 'cp -v /data/solr-4.3.1/zoe/etc/logback.xml /tmp/logback.xml-${i}-$(date +%Y%m%d).bak' <<EOF > secret_sauce > EOF tcgetattr: Inappropriate ioctl for device `/data/solr-4.3.1/zoe/etc/logback.xml' -> `/tmp/logback.xml--20131007.bak' [tdunphy@MIAGRBISSH01V ~]$ ssh -q -t -t -t MIAGRBIORCA00V sudo -S 'ls -l /home/tdunphy/logback.xml-${i}-$(date +%Y%m%d).bak' <<EOF > secret_sauce > EOF tcgetattr: Inappropriate ioctl for device -rw-r--r-- 1 root root 3372 Oct 7 22:07 /home/tdunphy/logback.xml--20131007.bak The best part of the above is that I am passing my password (secret_sauce - not my real one for obvious reasons) to sudo and having the command executed. One thing I'd like to be able to figure out is how to suppress this message, which is a little distracting and useless to the process: tcgetattr: Inappropriate ioctl for device But more importantly, when I try to pop the above two working statements from the command line into a script, the following occurs: [tdunphy@MIAGRBISSH01V ~]$ for i in MIAGRBIORCA0{0..9}V MIAGRBIORCA1{0..2}V > > do > > ssh -q -t -t -t $i sudo -S 'cp -v /data/solr-4.3.1/zoe/etc/logback.xml /tmp/logback.xml-${i}-$(date +%Y%m%d).bak' <<EOF > secret_sauce > EOF > > ssh -q -t -t -t $i sudo -S 'ls -l /home/tdunphy/logback.xml-${i}-$(date +%Y%m%d).bak' <<EOF > secret_sauce > EOF > > done tcgetattr: Inappropriate ioctl for device `/data/solr-4.3.1/zoe/etc/logback.xml' -> `/tmp/logback.xml--20131007.bak' tcgetattr: Inappropriate ioctl for device -rw-r--r-- 1 root root 3372 Oct 7 22:07 /home/tdunphy/logback.xml--20131007.bak tcgetattr: Inappropriate ioctl for device [sudo] password for tdunphy: For some reason the <<EOF password EOF routine is not working to provide the password to sudo the way I was able to when running the commands individually. Any thoughts on how I should be going about this? Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

6 7

CentOS 6.4: Warning! Received an indication that the LUN assignments on this target have changed. The Linux SCSI layer does not automatically remap LUN assignments.
by Trevor T Kates (Services - 6) 08 Oct '13

08 Oct '13

All: ~> uname -srvmpio Linux 2.6.32-358.18.1.el6.x86_64 #1 SMP Wed Aug 28 17:19:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ~> rpm -qa kernel\* | sort kernel-2.6.32-358.18.1.el6.x86_64 kernel-2.6.32-358.el6.x86_64 kernel-devel-2.6.32-358.18.1.el6.x86_64 kernel-devel-2.6.32-358.el6.x86_64 kernel-firmware-2.6.32-358.18.1.el6.noarch kernel-headers-2.6.32-358.18.1.el6.x86_64 My department has several dozen servers using CentOS 6.4 connected to a HP P2000 G3 FC SAN via a Brocade switch. device-mapper-multipath is used to handle the multiple paths to the SAN storage. Our setup has two paths per two redundant controllers/switches. ~> rpm -qa device-mapper\* | sort device-mapper-1.02.77-9.el6.x86_64 device-mapper-event-1.02.77-9.el6.x86_64 device-mapper-event-libs-1.02.77-9.el6.x86_64 device-mapper-libs-1.02.77-9.el6.x86_64 device-mapper-multipath-0.4.9-64.el6_4.2.x86_64 device-mapper-multipath-libs-0.4.9-64.el6_4.2.x86_64 device-mapper-persistent-data-0.1.4-1.el6.x86_64 ~> sudo cat /etc/multipath.conf multipaths { multipath { wwid <redacted> alias <redacted> } } defaults { find_multipaths yes user_friendly_names yes } ~> sudo multipath -ll <redacted> (<redacted>) dm-1 HP,P2000G3 FC/iSCSI size=1.3T features='1 queue_if_no_path' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=130 status=active | |- 2:0:0:12 sdd 8:48 active ready running | `- 1:0:0:12 sdb 8:16 active ready running `-+- policy='round-robin 0' prio=10 status=enabled |- 1:0:1:12 sdc 8:32 active ready running `- 2:0:1:12 sde 8:64 active ready running We're having a problem where syslog on every server connected to the SAN is getting spammed with the following: kernel: sd X:0:0:Y [sdX] Warning! Received an indication that the LUN assignments on this target have changed. The Linux SCSI layer does not automatically remap LUN assignments. None of the LUN assignments of any of the volumes on the SAN have changed since mapping them to the ports connected to each individual server. So far my searches for a solution have turned up dead-ends and if anyone is able to help, I'd greatly appreciate it. Thanks, Trevor T. Kates CONFIDENTIALITY NOTICE: This electronic message contains information which may be legally confidential and/or privileged and does not in any case represent a firm ENERGY COMMODITY bid or offer relating thereto which binds the sender without an additional express written confirmation to that effect. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.

1 0

CentOS-announce Digest, Vol 104, Issue 3
by centos-announce-request＠centos.org 08 Oct '13

08 Oct '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. CEBA-2013:1406 CentOS 6 ypserv Update (Karanbir Singh) 2. CEEA-2013:1405 CentOS 6 NetworkManager Update (Karanbir Singh) 3. CESA-2013:1409 Moderate CentOS 6 xinetd Update (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Mon, 7 Oct 2013 13:44:08 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEBA-2013:1406 CentOS 6 ypserv Update To: centos-announce(a)centos.org Message-ID: <20131007134408.GA34064(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:1406 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-1406.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8389a7c0ba74106508f8f1fae32cd6e55e3a5803f0ff470febe98c249296b8e6 ypserv-2.19-26.el6_4.2.i686.rpm x86_64: 1c342a1772477d117f064c222c506d5c3999381ff4215280ef44f4d881b5c007 ypserv-2.19-26.el6_4.2.x86_64.rpm Source: a29428dd0dd11e396510e2ce6bcd0460ec184f871e137ade31e75574ecc9ef7f ypserv-2.19-26.el6_4.2.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Mon, 7 Oct 2013 13:44:22 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEEA-2013:1405 CentOS 6 NetworkManager Update To: centos-announce(a)centos.org Message-ID: <20131007134422.GA34182(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2013:1405 Upstream details at : https://rhn.redhat.com/errata/RHEA-2013-1405.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: aef82c1f575bdb5a247bc5e1745152836db2322301d9505a0b020008c47528fb NetworkManager-0.8.1-61.el6_4.i686.rpm 69e8e37cf997c93feca8eb775eaa1696abf5596801513bc61949223188b28a13 NetworkManager-devel-0.8.1-61.el6_4.i686.rpm 6a8b4e7841f582de33f33f7966e4c52c0dfbc19f006eb6f2fc61921b92cac389 NetworkManager-glib-0.8.1-61.el6_4.i686.rpm 725acdfb9ff4410d17db38b9a602885431df7464012c95b5e323b340c3973ca0 NetworkManager-glib-devel-0.8.1-61.el6_4.i686.rpm 1b2256b618e7e57a0a986644d7d3e76c53200ac573d1ef462a3392d45209c8b7 NetworkManager-gnome-0.8.1-61.el6_4.i686.rpm x86_64: 558e6736d638034a4be323c873e399dead57f6b27c43780928c60165c063d894 NetworkManager-0.8.1-61.el6_4.x86_64.rpm 69e8e37cf997c93feca8eb775eaa1696abf5596801513bc61949223188b28a13 NetworkManager-devel-0.8.1-61.el6_4.i686.rpm 362dfffe9a04608b1b8cc0c7ccd9858595c7b4364c2d180c9d80b6e88f045898 NetworkManager-devel-0.8.1-61.el6_4.x86_64.rpm 6a8b4e7841f582de33f33f7966e4c52c0dfbc19f006eb6f2fc61921b92cac389 NetworkManager-glib-0.8.1-61.el6_4.i686.rpm 6ed15d103b99a226bf20687aec1b0abc0275f308b7f7d9bda2f79335af05c864 NetworkManager-glib-0.8.1-61.el6_4.x86_64.rpm 725acdfb9ff4410d17db38b9a602885431df7464012c95b5e323b340c3973ca0 NetworkManager-glib-devel-0.8.1-61.el6_4.i686.rpm 0bf3261948dcc0fa9d2d5f5486b57ee7b404c37adc92a3c67a6bd6ee9c47dce5 NetworkManager-glib-devel-0.8.1-61.el6_4.x86_64.rpm 1e49662150be4abe5b54e7f7ff4349a9a1148aecf335dc46fb2d2d18e6000a2e NetworkManager-gnome-0.8.1-61.el6_4.x86_64.rpm Source: 098345f6ed2592459627a675bba6162715fdbbc1e7af6d4a666dc34176fd798c NetworkManager-0.8.1-61.el6_4.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Mon, 7 Oct 2013 21:45:03 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2013:1409 Moderate CentOS 6 xinetd Update To: centos-announce(a)centos.org Message-ID: <20131007214503.GA39369(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2013:1409 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-1409.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8b6ca635bdd172d22ee9f2eaef989e27df95e80151e9a9c7f4062afc71941140 xinetd-2.3.14-39.el6_4.i686.rpm x86_64: bc2abdac0f4e757715a3f87cdcab48579ff7e41674a06fafe28baaeb6cb71f46 xinetd-2.3.14-39.el6_4.x86_64.rpm Source: d7da128dd939f85a01dc146548bf59b70b66dc60d4d4943541aa54f0b4d3ba29 xinetd-2.3.14-39.el6_4.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #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 104, Issue 3 ***********************************************

1 0

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 October 2013