Discuss May 2015

discuss@lists.centos.org

140 participants
129 discussions

Openssl C6 distro tag different from upstream
by Leonard den Ottolander 28 May '15

28 May '15

Hi, Just noticed that the distro tag used in openssl is different from upstream. Upstream and the last update (openssl-1.0.1e-30.el6_6.7) use "el6_6" where as the latest update (openssl-1.0.1e-30.el6.8) uses "el_6". Any reason for this discrepancy? Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research

3 3

CentOS-announce Digest, Vol 123, Issue 10
by centos-announce-request＠centos.org 28 May '15

28 May '15

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. CEEA-2015:1029 CentOS 6 tg3 Enhancement Update (Johnny Hughes) 2. CEBA-2015:1032 CentOS 5 pam BugFix Update (Johnny Hughes) 3. CentOS-7 beta candidate for AArch64 platforms (Jim Perrin) 4. CEBA-2015:1033 CentOS 6 glibc BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 27 May 2015 12:37:17 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2015:1029 CentOS 6 tg3 Enhancement Update Message-ID: <20150527123717.GA61453(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2015:1029 Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-1029.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5dff711b2e373e9659765e628fc5ba969313021fc81608078af40dad90442a5f kmod-tg3-3.137-2.el6_6.i686.rpm x86_64: 3dc5c70e00006a0188efa931a453a0a8d6eaba50032abf7f3cfec428842099bd kmod-tg3-3.137-2.el6_6.x86_64.rpm Source: 532e79131f1bef630ec4607b1d05b6c21d8addc979eea37eca318de4786cf416 tg3-3.137-2.el6_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 27 May 2015 14:35:01 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:1032 CentOS 5 pam BugFix Update Message-ID: <20150527143501.GA26646(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:1032 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1032.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: abdd6996f2976fec625db70ade1ae4693196f67105b688feaad382d3ac17ae60 pam-0.99.6.2-14.el5_11.i386.rpm 784578b99de9d56f32a49325896d046321feafdcc9fd0d7c417ecfbdca3cfafd pam-devel-0.99.6.2-14.el5_11.i386.rpm x86_64: abdd6996f2976fec625db70ade1ae4693196f67105b688feaad382d3ac17ae60 pam-0.99.6.2-14.el5_11.i386.rpm 5e2d0e23ae1e63ac116ae0b96f3d8b523d9f035dcae03b0a5670374842e2579d pam-0.99.6.2-14.el5_11.x86_64.rpm 784578b99de9d56f32a49325896d046321feafdcc9fd0d7c417ecfbdca3cfafd pam-devel-0.99.6.2-14.el5_11.i386.rpm 22d657e3ee8612afc3d75582e1717013582cd03690258f58303fabfb459c28aa pam-devel-0.99.6.2-14.el5_11.x86_64.rpm Source: 1d0d664b4815216f0df166264bf5d5adb15bffcbb8d7cd207e63af168a5c3edb pam-0.99.6.2-14.el5_11.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Wed, 27 May 2015 11:20:19 -0500 From: Jim Perrin <jperrin(a)centos.org> To: centos-announce(a)centos.org, arm-dev(a)centos.org Subject: [CentOS-announce] CentOS-7 beta candidate for AArch64 platforms Message-ID: <5565EEC3.7010905(a)centos.org> Content-Type: text/plain; charset=utf-8 We are pleased to announce the public beta release of CentOS Linux 7 for AArch64 compatible hardware. We've addressed a number of issues discovered from the previous 2 weeks of alpha testing, and feel that the release is stable enough to transition to beta. Improvements from Alpha ======================= Improved package selection: A number of additional packages have been added, including libreoffice, evolution, abrt, and more. Updated kernel: Some non-fatal kernel errors have been address by moving to a 4.1rc based kernel version. This also adds ACPI functionality to the platform. Improved Group selection: The installer now offers a larger group selection from the previous minimal-only install. Installation ============ Installation guides and documentation will be provided via the CentOS wiki, at http://wiki.centos.org/SpecialInterestGroup/AltArch/AArch64 Download ======== The full (unsigned) install tree is available at http://buildlogs.centos.org/centos/7/os/aarch64/ ============ Contributing The AArch64 effort is meant to be a community effort as part of the AltArch SIG (http://wiki.centos.org/SpecialInterestGroup/AltArch), and we welcome enthusiasts and vendors to contribute patches, fixes, documentation, etc. In the AArch64 Extras repository, we have provided the mock package and dependencies so that community members can more easily contribute, as well as testing their own builds locally. Please submit patches, fixes, etc to the Arm-Dev list (http://lists.centos.org/mailman/listinfo/arm-dev) for discussion and acceptance. We encourage vendors to come and join this effort, we have a loose organization focused on the alternative architectures build process and welcome interaction at the group level. Please get in touch with me (jperrin(a)centos.org) or K Singh ( kbsingh(a)centos.org ) to find out more details. The wider CentOS Ecosystem is also welcome to engage with us, both at the project and code level. If you are working with a project that interfaces, manages or develops on top of CentOS, specially in the virtualization, cloud, container and infrastructure management areas - we would love to have you guys get involved. While we don't have a lot of resources, we are working with a few vendors to build up a community resource pool that we would encourage other projects to share their development, testing and delivery around CentOS Linux for aarch64. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 ------------------------------ Message: 4 Date: Wed, 27 May 2015 15:14:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:1033 CentOS 6 glibc BugFix Update Message-ID: <20150527151406.GA14300(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:1033 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1033.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a193dd5a810304800b3c6c8c6ebe9cf7c812405c2c90c91a8d5e2f55c2808259 glibc-2.12-1.149.el6_6.9.i686.rpm a49df2dc9eb6106ed952593c72b1454e26eca771c68c659b426f458c3efb7a7b glibc-common-2.12-1.149.el6_6.9.i686.rpm f7c136221d3f6fb8d4c25ba4c1e4e49f052529608b350e29e5b2863275f29b33 glibc-devel-2.12-1.149.el6_6.9.i686.rpm afca31eff6e38e5a7b95e8737be5baff927d5b70b20bd93751148befa2745b02 glibc-headers-2.12-1.149.el6_6.9.i686.rpm 8ff405369f9bbc106364df0b169337c677fedcc1a501b8a92c86c9b9fb21fb14 glibc-static-2.12-1.149.el6_6.9.i686.rpm 70ddf8e976e4a4721ccfced10c5d1e07858afcb04b2fb00198c7641135daa295 glibc-utils-2.12-1.149.el6_6.9.i686.rpm 1c395ae1da4e73c7d60dc3ff4b372ea6d881d8102a15bb76f127a4ffea367cf2 nscd-2.12-1.149.el6_6.9.i686.rpm x86_64: a193dd5a810304800b3c6c8c6ebe9cf7c812405c2c90c91a8d5e2f55c2808259 glibc-2.12-1.149.el6_6.9.i686.rpm 712f9c468fa39edcb974433852db80d5cb6ce6cacb6d24f2050c04de62c834e3 glibc-2.12-1.149.el6_6.9.x86_64.rpm 62c09f50b6bb09105f34733e0ddf68f7313925c08b736e364fb4f9ee3ff6e137 glibc-common-2.12-1.149.el6_6.9.x86_64.rpm f7c136221d3f6fb8d4c25ba4c1e4e49f052529608b350e29e5b2863275f29b33 glibc-devel-2.12-1.149.el6_6.9.i686.rpm 3705c8079805449b4a01aa97aa6a7d8f467fedbf2ac88e5e9c3d58ebf15fc23e glibc-devel-2.12-1.149.el6_6.9.x86_64.rpm 9910a446ca5782bf4c8745abe63357ab368b6d36d8723a4ce978fec49064262d glibc-headers-2.12-1.149.el6_6.9.x86_64.rpm 8ff405369f9bbc106364df0b169337c677fedcc1a501b8a92c86c9b9fb21fb14 glibc-static-2.12-1.149.el6_6.9.i686.rpm ef0c6146fc033accef8e61c4821114d264db034643a254e2d2676b89f80f2cbf glibc-static-2.12-1.149.el6_6.9.x86_64.rpm 097fea253a97bdfc5bbf1114986cedfd24cc1bd3548c206b3986ee96175fad26 glibc-utils-2.12-1.149.el6_6.9.x86_64.rpm 74af55bb1cca30aa6e682230be1db3f6478cf8d0eff46b89e14ab93bdd4edd9a nscd-2.12-1.149.el6_6.9.x86_64.rpm Source: 707d103e880ad41fb7996eaa7f74575c942601b85cbbbec47363384619e1e869 glibc-2.12-1.149.el6_6.9.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 123, Issue 10 ************************************************

1 0

What does "4m[terminated]" mean?
by Nan Xiao 28 May '15

28 May '15

Hi all, After installing CentOS 7 and restart it, it always promptd "4m[terminated]". What does this prompt mean? Does it will affect normal OS functions? Thanks in advance! Best Regards Nan Xiao

1 0

dummy interface shenanigans - CentOS6
by Frank Even 28 May '15

28 May '15

tl;dr - a renamed dummy interface is not persisting across reboots on Cent6. I have a situation where I need to rename a dummy interface on my system. I have a total of 3 dummy interfaces: dummy0 dummy1 adummy0 I've been doing some puppet testing in a vbox VM to get this all sorted out to deploy to a group of boxes. Every time I reboot my VM, it comes up WITHOUT adummy0, but I notice there is now an unconfigured dummy2. I've tried everything from adding aliases to /etc/modprobe.d/dummyopts.conf to renaming the interface via "ip" (ip link set dummy2 name adummy0). This is all fine during use, even during a network restart. But as soon as I restart the VM, it comes back up broken. I for the life of me have been unable to figure out why. I could use some help in narrowing down why this won't persist across reboots. I can write a startup script to deal with it, but it doesn't seem like a good solution. Thanks, Frank

2 3

Command line mp3 player
by Bowie Bailey 27 May '15

27 May '15

I have a CentOS 7 server that I want to use as an audio source for our hold music. It does not have a GUI installed, so I am looking for a program with a command line interface that will let me play a folder full of mp3 files on a continuous loop. MOC seems to do what I want, but I can't find a build for CentOS 7. Is there another program that I can use for this? Thanks. -- Bowie

7 10

Re: [CentOS] firefox 38 question
by johan.vermeulen7 27 May '15

27 May '15

m.roth(a)5-cent.usschreef: Chuck Campbell wrote: > Is Firefox 38 still borked for Centos 5? > > It shows up as available for update, but I don't recall seeing anything > saying the problems noted here have been fixed. Dunno 'bout 5; I'd been waiting, since I thought I remembered folks here complaining about it breaking language support for 6, and I *know* that some folks here have Chinese and Japanese support set, so I didn't want to break it. However, the other admin did updates yesterday, and no one's screamed yet. Note they're all on 6. mark Hello, I can say the language thing is fixed for Dutch for Centos6. Dunno for Centos5. There has been no announcement for Centos7. Greetings Johan _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

2 1

firefox 38 question
by Chuck Campbell 27 May '15

27 May '15

Is Firefox 38 still borked for Centos 5? It shows up as available for update, but I don't recall seeing anything saying the problems noted here have been fixed. thanks, -chuck --

3 2

serious problem with torque
by m.roth＠5-cent.us 27 May '15

27 May '15

Hi, folks, The other admin updated torque without testing it on one machine, and we had Issues. The first I knew was when a user reported qstat returning socket_connect_unix failed: 15137 socket_connect_unix failed: 15137 socket_connect_unix failed: 15137 qstat: cannot connect to server (null) (errno=15137) could not connect to trqauthd Attempting to restart the pbs_server did the same. Working with my manager, we found: a) torque had been updated from 2.x to 4.2.10, which is huge. b) Apparently, it no longer uses munged. Instead, it uses trqauthd, and that wasn't in the updated packages. c) We could not downgrade!!! d) My manager updated from testing, and installed, and then running trqauthd, and restarting pbs_server, it appears to be working again. Should I be filing a bug report? mark

4 9

unreachable peer
by Leon Fauster 27 May '15

27 May '15

Hey all, I have a public peer system (yy.yy.yy.yy) that is reachable via my home uplink (xx.xx.xx.xxx). 15:59:30.244199 IP xx.xx.xx.xxx.42958 > yy.yy.yy.yy.https: tcp 0 15:59:30.281931 IP yy.yy.yy.yy.https > xx.xx.xx.xxx.42958: tcp 0 15:59:30.281945 IP xx.xx.xx.xxx.42958 > yy.yy.yy.yy.https: tcp 0 15:59:30.305020 IP xx.xx.xx.xxx.42958 > yy.yy.yy.yy.https: tcp 105 15:59:30.344004 IP yy.yy.yy.yy.https > xx.xx.xx.xxx.42958: tcp 1412 15:59:30.344013 IP xx.xx.xx.xxx.42958 > yy.yy.yy.yy.https: tcp 0 15:59:30.344016 IP yy.yy.yy.yy.https > xx.xx.xx.xxx.42958: tcp 23 At the office we have a EL5 based router that can not reach the mentioned system. It does not give any hint about the problem. 15:57:51.751591 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0 15:57:54.750834 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0 15:58:00.749351 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0 15:58:12.746408 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0 15:58:36.740454 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0 15:59:24.728605 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0 I tried to connect with a removed ecn bit [1] [1] https://en.wikipedia.org/wiki/Explicit_Congestion_Notification but this was not the solution. Any ideas? -- Thanks in advance! LF

3 5

specify port on check_memcached.pl
by Tim Dunphy 27 May '15

27 May '15

Hey guys, I'm trying use check_memcached.pl to monitor a couple of memcached services running on two ports. I have my command definition setup like this: # 'check_memcached' command definition define command { command_name check_memcached command_line $USER1$/check_memcached.pl -H $HOSTADDRESS$ -p $ARG1$ } And I have my service definitions setup like this: # Define a service to check memcached on web1 (just the basics for right now). define service{ use local-service ; Name of service template to use host_name web1 service_description Check Memcached 11211 contact_groups linux-admins check_command check_memcached!web1.example.com !11211 notifications_enabled 1 } # Define a service to check memcached on web1 (just the basics for right now). define service{ use local-service ; Name of service template to use host_name web1 service_description Check Memcached 11212 contact_groups linux-admins check_command check_memcached!web1.example.com !11212 notifications_enabled 1 } And if I run both checks manually they succeed: [root@monitor1:/usr/local/nagios/etc/objects/servers] #../../../libexec/ check_memcached.pl -H web1.example.com -p 11211 MEMCACHE OK: memcached 1.4.22 on web1.example.com:11211, up 22 minutes 52 seconds [root@monitor1:/usr/local/nagios/etc/objects/servers] #../../../libexec/ check_memcached.pl -H web1.example.com -p 11212 MEMCACHE OK: memcached 1.4.22 on web1.example.com:11212, up 12 minutes 2 seconds Yet, in my nagios web interface, I'm getting this error: Check Memcached 11211 <https://nagios.jokefire.com/nagios/cgi-bin/extinfo.cgi?type=2&host=web1&ser…> CRITICAL 05-24-2015 14:28:31 0d 0h 10m 19s 4/4 CRITICAL ERROR - Can not connect to '162.243.60.6' on port 0 Check Memcached 11212 <https://nagios.jokefire.com/nagios/cgi-bin/extinfo.cgi?type=2&host=web1&ser…> CRITICAL 05-24-2015 14:29:12 0d 0h 11m 8s 4/4 CRITICAL ERROR - Can not connect to '162.243.60.6' on port 0 I thought I could specify the command in the service definition like this: check_memcached!web1.example.com!11211 To reproduced the command as it's executed on the command line. How can I specify the port correctly here? Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss May 2015