Discuss May 2013

discuss@lists.centos.org

151 participants
121 discussions

CentOS-announce Digest, Vol 99, Issue 10
by centos-announce-request＠centos.org 22 May '13

22 May '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:0847 Moderate CentOS 5 kernel Update (Johnny Hughes) 2. CEBA-2013:0846 CentOS 5 xen Update (Johnny Hughes) 3. CEEA-2013:0852 CentOS 5 rgmanager Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 22 May 2013 00:42:18 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2013:0847 Moderate CentOS 5 kernel Update To: centos-announce(a)centos.org Message-ID: <20130522004218.GA2167(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2013:0847 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0847.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ab5044367344e995cb1eae8cfae59c2b6df68a8366ab6830b1b7fff6311de88e kernel-2.6.18-348.6.1.el5.i686.rpm 098b89256fe94e488bc11c7d7d5c9c633f26e6ce2f556027cb6a4c09d83c6b1a kernel-debug-2.6.18-348.6.1.el5.i686.rpm 07934a3d05a145d04f3174247f261ec83865876335ec30735b690a16d2155ffc kernel-debug-devel-2.6.18-348.6.1.el5.i686.rpm 9844fb6c5aa44ab6c81d364f5297d0a79312be417eaff79e14fc857b198c00c6 kernel-devel-2.6.18-348.6.1.el5.i686.rpm c677268f2a1d2eb32508693ccef0813e236b12909e8b32a785ccb472d53740e0 kernel-doc-2.6.18-348.6.1.el5.noarch.rpm de801934133ee709e3c513299db6f9e5876767e6a00ac55928ecad7d9762fdcd kernel-headers-2.6.18-348.6.1.el5.i386.rpm fe04425d4d7c8314ab42b7601be855c02d79a94dbeb5badce6c701acc35c11e6 kernel-PAE-2.6.18-348.6.1.el5.i686.rpm ef9181b7ff77bce3f1bec28a5e37360b8e64932f44531bc66c83216699e7e7e6 kernel-PAE-devel-2.6.18-348.6.1.el5.i686.rpm 765cf57dab52afb57f18bb84cc354f11ae3fa264b9b157bf84914cacb6db2b83 kernel-xen-2.6.18-348.6.1.el5.i686.rpm 347a8b9e89eea05d6b53e1b30fa5569593d62282c16561aff945e1604c7e4465 kernel-xen-devel-2.6.18-348.6.1.el5.i686.rpm x86_64: 02a6c7c2f002543eb61596fc3b16a3cb4a8a9d97218adb4caa8f2482fa062a94 kernel-2.6.18-348.6.1.el5.x86_64.rpm 4d0acfe18f15a26f2d32274a03e2daee04c7cd14043de85348c3e50cc513b5b8 kernel-debug-2.6.18-348.6.1.el5.x86_64.rpm 750bd839ca73cf262309eec0a34b82a2e14e2a5a64f1ad6d67eea47a8b8c95de kernel-debug-devel-2.6.18-348.6.1.el5.x86_64.rpm 1a2351ac39b3080b13e0904b6de03e4daa604f428ffdd038ff53402531977e30 kernel-devel-2.6.18-348.6.1.el5.x86_64.rpm c677268f2a1d2eb32508693ccef0813e236b12909e8b32a785ccb472d53740e0 kernel-doc-2.6.18-348.6.1.el5.noarch.rpm 0e84f4daf0c476e555c6ebf1ff261bd44c5e72a5bbe75fe5f574abb3376f7de4 kernel-headers-2.6.18-348.6.1.el5.x86_64.rpm 2df8bbdbb154d41d699bfec546d64d4ce80fddee4800657cd4c7d981f2519bc0 kernel-xen-2.6.18-348.6.1.el5.x86_64.rpm 96add8d6aeaa2c3cfc8fa2ea93b8ced13230353fbef3025e850d7e3858e704c3 kernel-xen-devel-2.6.18-348.6.1.el5.x86_64.rpm Source: 79f0fd50d589af4bc5772082dfd03ac7a6f1e1954f930c8c18583a84c9afdd56 kernel-2.6.18-348.6.1.el5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 22 May 2013 01:26:35 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2013:0846 CentOS 5 xen Update To: centos-announce(a)centos.org Message-ID: <20130522012635.GA3891(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:0846 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0846.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ec631cb6cef6d16171547387d83540ee421f208c37e735064f03a4b61f920930 xen-3.0.3-142.el5_9.3.i386.rpm 52625a828dc04a4f501cad0e3e76c0f760a3934be4d079bad86c88b9ac730b1b xen-3.0.3-142.el5_9.3.i686.rpm a37c1d767aabc0be5a3510f2654ccccb7543fdfe31c9571d982f97666268674d xen-devel-3.0.3-142.el5_9.3.i386.rpm 81f01c550d014391e5008eae46189bee65229401ff197737cc4c7ecb1df7df16 xen-devel-3.0.3-142.el5_9.3.i686.rpm 558ccfff31589f7e2b46a501e9f730d7aea01b81941dd82746b49a4871c36abd xen-libs-3.0.3-142.el5_9.3.i386.rpm 6b1cd54270c7cedf43126b650d6cac68a7441badcaaed58639d439b0a7df8bc2 xen-libs-3.0.3-142.el5_9.3.i686.rpm x86_64: e98666d9db0a5110cc81e925a594ea7bda9a1a5e0fde99c521755db29ac92924 xen-3.0.3-142.el5_9.3.x86_64.rpm a37c1d767aabc0be5a3510f2654ccccb7543fdfe31c9571d982f97666268674d xen-devel-3.0.3-142.el5_9.3.i386.rpm 5feb695b37fd5dde27d223b55fcdf8437321f63f4cf6a228356b77e7ab4024a0 xen-devel-3.0.3-142.el5_9.3.x86_64.rpm 558ccfff31589f7e2b46a501e9f730d7aea01b81941dd82746b49a4871c36abd xen-libs-3.0.3-142.el5_9.3.i386.rpm 1d3f7879976677794109e382f561a36452e02035bb037b897f62e8d3861b0496 xen-libs-3.0.3-142.el5_9.3.x86_64.rpm Source: 9dbfd13241c4e3249f424d32ed6526e2b3662d969f3518dab3287b92926ae32b xen-3.0.3-142.el5_9.3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Wed, 22 May 2013 11:50:54 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEEA-2013:0852 CentOS 5 rgmanager Update To: centos-announce(a)centos.org Message-ID: <20130522115054.GA3369(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2013:0852 Upstream details at : https://rhn.redhat.com/errata/RHEA-2013-0852.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1c3221b07eb1f14878c380a15e89e9467121295070034d3e3b45175e918bda9f rgmanager-2.0.52-37.el5.centos.2.i386.rpm x86_64: 4b8b522fb08f2002f9a407bc40f4e5bda7d17d22d25847de64c1643408d5ce85 rgmanager-2.0.52-37.el5.centos.2.x86_64.rpm Source: 6a4c446af0a5f6fde288b3385adae0fcaf02b2a4bb4001dd0b3d17b451656bd7 rgmanager-2.0.52-37.el5.centos.2.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 99, Issue 10 ***********************************************

1 0

Re: [CentOS] Centos 6.4: Possible bug in system-config-network-cmd
by Glenn Eychaner 22 May '13

22 May '13

m.roth: > Hmmm... have you looked at /etc/udev/rules.d/70-persistant-net.rules? # PCI device 0x8086:0x104b (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:xx:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x10b7:0x9200 (3c59x) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:04:xx:xx;xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" Not sure there's anything relevant there... -G. -- Glenn Eychaner (geychaner(a)lco.cl) Telescope Systems Programmer, Las Campanas Observatory

1 0

SuperMicro with LSI MegaRaid with Centos 6.0
by Gregory P. Ennis 21 May '13

21 May '13

Everyone, I am trying to install a Centos 6.0 system on a SuperMicro with an LSI MegaRaid SCSI 320-2 controller. I had originally tried to install 6.4, but the 6.4 install DVD does not boot with this configuration. See : http://bugs.centos.org/view.php?id=5377 Fortunately, the 6.0 install DVD worked fine until it failed to identify the hard disc controller. I checked the lsi.com site which had a driver for RH 3 and RH4, but not 5 and not 6. The interesting thing about this machine is that I had Centos 5.0 installed without difficulty (that over time upgraded to 5.9) Does anyone have any idea of a driver I could use to get Centos 6.0 up and running. Thanks!!!! Greg Ennis

2 5

Force anaconda to use GPT labels on all drives?
by Tucker 21 May '13

21 May '13

I did a quick search through the archive and couldn't find anything that mapped to my need, so I figured I should ping the community and see if anyone has the requisite knowledge and could point me in the right direction. *Succinct Version* Is there a way to, using updates.img, monkey patching or swapping in a newer Anaconda (>= 16) to force all disks to have gpt labels and not just disks> 2TB? *TL;DR Version* I'm working on setting up an installation environment and am trying to make it as machine agnostic as possible. We're currently using CentOS 6.3 (will start 6.4 work soon). Getting software on a machine is simple but laying out disks is less so. Some of our machines have eight disks and some twelve and some others have two. Normenpoughaalizing on a single hardware profile is not an option, due to the various types of systems we need. What I'm currently having to do is wipe the partition information and set a gpt label, in a %pre section, on the first two disks only. After that, I have to use our post installation installer to create the partitions on the remaining disks. Because of the way it works, unless we manually remove the partitions from the remaining partitions, prior to doing the post installation steps (which setup the host for its role), we will end up with drives that have old information (read as: not formatted). I understand that that normal way to do this is to use zerombr and clearpart but this leaves me with some disks that have msdos labels (<= 2TB) and some with gpt labels (> 2TB). In order to simplify everything, without having to be deterministic about hardware type, we need to use gpt labels on everything. It appears that Anaconda 16 and beyond use gpt labels by default (unless "nogpt" is provided as a kernel option) but CentOS (even 6.4) is using Anaconda 13. I've read about updates.img but I'm not sure that's the solution (if so, I don't grok it yet). I've managed to get Anaconda 17 to build from source (wow... that was "fun") but don't know enough kickstart/anaconda to know how and if I can swap that in place of the existing Anaconda images and still get CentOS to install. -- --tucker

2 3

ReiserFS - status?
by Rafał Radecki 21 May '13

21 May '13

Hi All. What is the status of ReiserFS in CentOS at the moment? I have some servers which use it as a loadable kernel module. I am thinking about a filesystem for database systems and would like to know if ReiserFS will be maintained in CentOS/Linux kernel in the future? Best regards, Rafal.

5 4

ICMPv6 Neighbour Solication request is not answered by linux when IPv6 address is assigned via Netlink code.
by Kevin Peterson 21 May '13

21 May '13

Hi, I have a process which is running as a linux service and assigns IP addresses using netlink to configued interface in linux. For IPv4 addresses i do not see any issue with this assignment. When i try to assign an IPv6 address, the address gets assigned successfully to the interface, but the Neighbour Solication request received for that address is not responded with and hence ping6 from a different machine doesn't work. When i take the same netlink code and run it in a sample program the address gets assigned and the Neighbour solicitation is responded with a advertisement and hence ping6 works. IP assigned by the program : 7000::15/32 IP on client machine from where ping6 is done : 7000::17/32. Bot machines are connected to same Layer-2 switch. I have flushed the ip6tables on both the machines just to rule out any firewall issues. Thanks, Kevin Peterson

2 3

semi-OT: flashing the BIOS on an HP dl580 GT, afterward
by m.roth＠5-cent.us 21 May '13

21 May '13

When last we saw our hero, er, sysadmin, he'd found that the "noarch" BIOS update was, in fact, a self-extracting .exe file, and he'd extracted it. Finally getting the ok to take the system down, the following hilarity (for small values of hilarity) ensued. First, booting off unetbootin to freedos was fine... except it was try to guess which version - freedos + emm386 + himem, no himem, live CD only, or, finally, "no drivers loaded", which works. It gags on something orders of magnitude larger than it was written for, y'know. Then I discover that the builtin type command does *not* have /p, and there's no more command, and I should have read the longer files before I started this. Fun with <ctrl-s> ensues. Finally, I find what are actually DOS config.sys files, with different extensions, and read them - they're one-liners, and find out how to run the rompaq.exe that runs the utility to flash the drives, and run it. And again. And again. And *finally* get the reason it's failing, and (to save the original name) copied the actual data from an 8.3 name into 7 char, which the utility demands: *exactly* seven chars, no more, no less. And unlike the Dell utility, which give you lots of warm fuzzies ("collecting data", "this is for this hardware, this is newer, do you want to update?"), this just does it. Fortunately, this HBS contains a backup ROM, just in case.... And a three-finger kill later, it's up. And I put the memory boards back in, so we'll see if the BIOS update fixed the memory problems (remember them? this song's about them).... mark

1 0

security breach - ftp?
by Philipp Duffner 21 May '13

21 May '13

Hi, I'm running Plesk 11.0.9 on a Centos 5.5. A website on that box got hacked last week and malicious code got inserted into some html/php files. So I went to find out what happened... I found no back doors by using rkhunter or manually searching for suspicious files in /tmp, etc. No activity at all in the php logs at the time of the attack. I also analysed of course the system logs (messages, secure, ...) - nothing that I could see either - except for an entry of an successful login to that domain via FTP just before the the modified dates of the infected files. I found one of the oldest infected files were in the folder of a hopelessly outdated version of a WYSIWYG editor and decided to blame that due to probability. So in order to recover I did in this order... * delete httpdocs from the website * change the FTP password * upgrade and update Plesk from 10.0.4 to 11.0.9 * upgrade php to php53 via plesk - this also updates mysql and phpmyadmin * yum update everything, also made sure I have the latest version of proftp * restore the entire website from a clean backup * delete the WYSIWYG folder that I believed had caused the vulnerability The next days I slept ok hoping I removed the attacker's entry point(s). ...so I thought! Today the website got hacked again - the same exploit on the pages, meaning same attacker. And again I can see nothing suspicious except for the successful FTP logon just before the modification time of the infected html/php: 2013-05-18T15:01:25.195559-07:00 MyServer proftpd: Deprecated pam_stack module called from service "proftpd" 2013-05-18T15:01:25.204731-07:00 MyServer proftpd: Deprecated pam_stack module called from service "proftpd" 2013-05-18T15:01:25.204831-07:00 MyServer proftpd: Deprecated pam_stack module called from service "proftpd" 2013-05-18T15:01:25.205183-07:00 MyServer proftpd: pam_unix(proftpd:session): session opened for user WEBSITEUSER by (uid=0) 2013-05-18T15:01:25.205244-07:00 MyServer proftpd: Deprecated pam_stack module called from service "proftpd" 2013-05-18T15:01:25.231034-07:00 MyServer proftpd[20243]: 127.0.0.1 (188.190.126.105[188.190.126.105]) - USER WEBSITEUSER: Login successful. 2013-05-18T15:04:08.095351-07:00 MyServer proftpd: Deprecated pam_stack module called from service "proftpd" 2013-05-18T15:04:08.095379-07:00 MyServer proftpd: pam_env(proftpd:setcred): Unable to open config file: /etc/security/pam_env.conf: No such file or directory 2013-05-18T15:04:08.095445-07:00 MyServer proftpd: Deprecated pam_stack module called from service "proftpd" 2013-05-18T15:04:08.095455-07:00 MyServer proftpd: pam_succeed_if(proftpd:session): error retrieving information about user 0 2013-05-18T15:04:08.095463-07:00 MyServer proftpd: pam_unix(proftpd:session): session closed for user WEBSITEUSER I know for a fact it couldn't have been the website owner because I didn't give him the new FTP password yet. # yum list | grep proftp psa-proftpd.i386 1.3.4a-cos5.build110121114.13 installed proftpd.i386 1.3.3g-2.el5 epel proftpd-ldap.i386 1.3.3g-2.el5 epel proftpd-mysql.i386 1.3.3g-2.el5 epel proftpd-postgresql.i386 1.3.3g-2.el5 epel I think I really hit a snag with this one - I have no idea where to go forward from here. I'd appreciate any ideas. Thanks. Philipp

6 5

CentOS-announce Digest, Vol 99, Issue 9
by centos-announce-request＠centos.org 21 May '13

21 May '13

1 0

NIC interrupts and packets per second ratio, how to calculate? There must be some way...
by Alex Flex 21 May '13

21 May '13

Hello again guys, Iam trying to asses the best hardware for a machine that procceses a high number of packets per second on its NIC. THe only way I can achieve this without guesses is If iam able to understand or test what the number of interrupts available per core and how to translate that to PPS capabilities. So far ive been testing an Core I5 CPU and was able to achieve up to 400k packets (small syn packets) in a single core (2.8Ghz i think..) untill the point where 100% was reported to serve as hardware interrupts, yet what is the math behind this? In any case, i find this rather low and confused as I know for a fact that small home routers even on gigabit have specs that detail they can do packet forwarding at rates up to 1.4 million pps and iam sure there CPU is no where as powerfull as a 2.8Ghz Core I5 core. Any orientation is much appreciated. Alex

2 1

← Newer
1
2
3
4
5
6
7
8
9
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss May 2013