- Discuss - lists.centos.org

CentOS-announce Digest, Vol 133, Issue 1
by centos-announce-request＠centos.org 02 Mar '16

02 Mar '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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-2016:0298 CentOS 6 findutils FASTTRACK BugFix Update (Johnny Hughes) 2. CESA-2016:0301 Important CentOS 6 openssl Security Update (Johnny Hughes) 3. CESA-2016:0301 Important CentOS 7 openssl Security Update (Johnny Hughes) 4. CESA-2016:0302 Important CentOS 5 openssl Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 1 Mar 2016 13:06:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:0298 CentOS 6 findutils FASTTRACK BugFix Update Message-ID: <20160301130638.GA3583(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:0298 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0298.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ed1a7580800b4cb68fd882f39eafe9c4a0d8b2ec9ff6d25358f2f10d9cc35555 findutils-4.4.2-9.el6.i686.rpm x86_64: fbbb4d9e91b0a7cac328167d09a3591d9ee50e990d86da45bee99f8020a03db3 findutils-4.4.2-9.el6.x86_64.rpm Source: 8f0afaba4a8461e71ea4001750df754ff6406e5a68e5276c8aae4a36a6a9632c findutils-4.4.2-9.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 1 Mar 2016 16:09:29 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0301 Important CentOS 6 openssl Security Update Message-ID: <20160301160929.GA26137(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0301 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0301.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 31cacdfe88b5e4b420bd2dd1fe6b491b35a2a57c7e3b4ef5b960573b095fc519 openssl-1.0.1e-42.el6_7.4.i686.rpm a57701c0598a7c91de1eac55fa5b6ffe2bc096c07f757723d6de65dd092dbc66 openssl-devel-1.0.1e-42.el6_7.4.i686.rpm 3e62aef02b5a465d587a3c3dfec494b27d55ec2a5dac0a13e6ac842188728d66 openssl-perl-1.0.1e-42.el6_7.4.i686.rpm 621cd98e6d221febb477906443a1692afd64ffcc79cb843a146ee4583e7224f7 openssl-static-1.0.1e-42.el6_7.4.i686.rpm x86_64: 31cacdfe88b5e4b420bd2dd1fe6b491b35a2a57c7e3b4ef5b960573b095fc519 openssl-1.0.1e-42.el6_7.4.i686.rpm e5fc87d5031ea23db0eb2be92743a557d8574caa583fad6a1cd16a757ed436f3 openssl-1.0.1e-42.el6_7.4.x86_64.rpm a57701c0598a7c91de1eac55fa5b6ffe2bc096c07f757723d6de65dd092dbc66 openssl-devel-1.0.1e-42.el6_7.4.i686.rpm 17b6a4dbe2f844d3944fa7c4cafe9ccf4d54a8dc23d26201a513fc86bd08d256 openssl-devel-1.0.1e-42.el6_7.4.x86_64.rpm 4b9ec40e680ad72d6134283f3ab6179d2c4c8a34433aed4f42c5117bfeb300a5 openssl-perl-1.0.1e-42.el6_7.4.x86_64.rpm aaaf4d42ef5f48f424ed9d6d04744e906a15d3ae66097bcd3ec60be226879cd6 openssl-static-1.0.1e-42.el6_7.4.x86_64.rpm Source: 152d1ec6f40854680bbad1524f2b7766c8f583de6b1a136b635ec9b257d4b088 openssl-1.0.1e-42.el6_7.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 1 Mar 2016 16:41:22 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0301 Important CentOS 7 openssl Security Update Message-ID: <20160301164122.GA26845(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0301 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0301.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b2aaed03ed2d01d2a6482ed97a95aec0545ffc4c00ad46c7cafc10c9554e1b58 openssl-1.0.1e-51.el7_2.4.x86_64.rpm b1aa349c2ea3a99cc65d031850d415b7feb7924f0a121593c12b439934440eb4 openssl-devel-1.0.1e-51.el7_2.4.i686.rpm 3e194452a2616702ee91e791b163b739d012da52957f6e91927de9d554e4e203 openssl-devel-1.0.1e-51.el7_2.4.x86_64.rpm 2e193ea886626e3e8b151f905920503e2e505cc2bdfef31a8d38a581c99e210f openssl-libs-1.0.1e-51.el7_2.4.i686.rpm 249cc7d68c0d8d48a26b50066ed29da2d70c7a573d23dc566ee7c99f5c5f71c9 openssl-libs-1.0.1e-51.el7_2.4.x86_64.rpm 61cfe9edcb1d521b2978fee1acda2a9cba73f2c371bc9217b44bd527569938c5 openssl-perl-1.0.1e-51.el7_2.4.x86_64.rpm a5d2395db7a0c87d069e3fc80e55deacffeea5acc5162058075a746871954ce7 openssl-static-1.0.1e-51.el7_2.4.i686.rpm e48dd73a4f9bc7d3b6617842414a1b50fc086c720795451ca4795ecd08ba3b22 openssl-static-1.0.1e-51.el7_2.4.x86_64.rpm Source: 26fa86503898fa5fcf91188aa6f56172ea1896e4d4943bd407aa54d21d330618 openssl-1.0.1e-51.el7_2.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 1 Mar 2016 16:57:33 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0302 Important CentOS 5 openssl Security Update Message-ID: <20160301165733.GA16183(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0302 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0302.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 045550a5b7552b7a9cd5ea7a1f866de367e3bf677d240925d633a1b7938cd07a openssl-0.9.8e-39.el5_11.i386.rpm 8c73a864ce991ba4e6c950cc6ca642c09a7753fc5aa793a0a23e683ba5df99e9 openssl-0.9.8e-39.el5_11.i686.rpm 230b07861835e3a65052e45b617a73cbbd3057c6db38d315dbed7b3d01f1fba6 openssl-devel-0.9.8e-39.el5_11.i386.rpm c63d611b4519928413ed611a020d7e7113ccbf6890b264b4b8399f9af7bf6140 openssl-perl-0.9.8e-39.el5_11.i386.rpm x86_64: 8c73a864ce991ba4e6c950cc6ca642c09a7753fc5aa793a0a23e683ba5df99e9 openssl-0.9.8e-39.el5_11.i686.rpm d7e159cfd9e991adf152df48cb97751c8a26601b1f3f3a70a3e137efb05e0c35 openssl-0.9.8e-39.el5_11.x86_64.rpm 230b07861835e3a65052e45b617a73cbbd3057c6db38d315dbed7b3d01f1fba6 openssl-devel-0.9.8e-39.el5_11.i386.rpm f6bc29a1ab08303174206210af09b37ec53f0c0d643f18bf98427b20f2cb4a67 openssl-devel-0.9.8e-39.el5_11.x86_64.rpm 7953dcc480ff7815f39943f62fc848b3ce7ecb66217d2829332d95be4400c13d openssl-perl-0.9.8e-39.el5_11.x86_64.rpm Source: e0dab71e400c340b8eed7770c582ce6f3768888a61b4c492411d20e81ae1a9a6 openssl-0.9.8e-39.el5_11.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 133, Issue 1 ***********************************************

1 0

Any experiences with newer WD Red drives?
by Emmanuel Noobadmin 02 Mar '16

02 Mar '16

Might be slightly OT as it isn't necessarily a CentOS related issue. I've been using WD Reds as mdraid components which worked pretty well for non-IOPS intensive workloads. However, the latest C7 server I built, ran into problems with them on on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error write fpdma queued". Googling on it threw up old suggestions to limit SATA link speed to 1.5Gbps using libata.force boot options and/or noncq. Lowering the link speed helped to reduce the frequency of the errors (from not getting a smartctl output to getting a complete listing within 2 tries). Tried two Reds produced in Jan 2016, two HGST, two SSDs on the same combination of cable/bay/SATA port as well as different combos. SSD maxed out at 450Mbps dd write test so doesn't appear to be lousy cables or board problem. Basically only the Reds were having problems. Strange thing is a netinstall of CentOS 7.0 "minimal" worked with one of the Reds before starting to cough. Now that I think about it, could be due to an update to 7.2 after installing. Needed to get the server out the door ASAP so didn't have time to try C6 once I confirmed it was the drive and promptly replaced it with another HGST. Since I'm likely to use Reds again, it is a bit of a concern. So wondering if I just happen to get an unlucky batch, or is there some incompatibility between the Reds and the Intel C236 chipset, or between Red / C236 / Centos 7 combo or the unlikely chance WD has decided to do something with the firmware to make them work on on NAS and not workstation/server chipsets to make people buy better stuff. Anybody has recent experiences with them recently on the same chipset with C7?

6 10

ssh issues with centos 6
by William Warren 01 Mar '16

01 Mar '16

I have a new centos 6 install. Randomly i get out of memory messages and my ssh file transfer dies. I have tried this in filezilla as well as winscp. I have disabled motd in ssh and i also had entropy problems so i enacted rngd -r /dev/urandom -o /dev/random but did not stop the out of memory errors. I am seeing the below in the logs. It only occurs during ssh file transfers. Feb 28 17:18:19 web1 t of memory [13604]

3 2

making a new initrd
by Philip Manuel 01 Mar '16

01 Mar '16

Hi, I built a new kernel for C7 that contains the required driver for a new motherboard we have here. I'd like to take this initramfs and rebuild it/modify it so that it is suitable for pxe booting. I have tried dracut -v --force --add "anaconda" initramfs.img # results in an image that is too large for tftp Or dracut --nofscks --nomdadmconf --nolvmconf --xz --no-early-microcode -m "anaconda" --force initramfs.img # kernel panics What steps should I be taking to create an initrd image suitable for pxe boot ? Thanks

1 0

Pi 2 Alternatives
by Chris Olson 01 Mar '16

01 Mar '16

We have a requirement for a new application that will be used fixed, portable, and mobile. The hardware requirements drive the need for networking as well as some general purpose and special purpose interfaces. The software requirements are quite simple in comparison to many of our much larger systems with similar hardware requirements. We are not significantly restricted in choice of storage peripherals or other devices that may be needed. We believe that a small, single board computer will meet all requirements as long as it can run Linux. We have identified the need for approximately six prototyping units to support the initial production of about 200 to 300 operational systems. Our development and deployment time frame does not drive the need for an extremely rapid product decision, and there are pre-planned upgrade cycles over the next five years. An internal group has achieved a significant head of steam in support of using the Pi 2 Model B. The support enthusiasm may be partly technical and partly the hype associated with jumping into the Pi community. The number of suppliers does appear to support our supply chain and sustainment requirements, however the Linux available for the Pi 2 does not appear to be optimal. It would be better if there were choices that include a standard Linux distribution such as CentOS. This certainly seems like one of those situations where a trade of single board computer products is appropriate and achievable. There are products similar to the Pi 2 capable of running a more standard Linux distribution that we might consider. Does anyone have an experience-based single board computer recommendation? Thanks in advance for any product recommendations.

4 3

Hung kernel task on CentOS 7.2, fprintd and libvirtd
by Warren Young 01 Mar '16

01 Mar '16

A CentOS 7 box here recently started being very slow to give the Password prompt when using sudo. (25 seconds!) I eventually tracked this down to the following complaint in the kernel message log: > Feb 26 12:55:05 badboy kernel: INFO: task fprintd:1932 blocked for more than 120 seconds. > Feb 26 12:55:05 badboy kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > Feb 26 12:55:05 badboy kernel: fprintd D ffff88021f7300f8 0 1932 1 0x00000080 > Feb 26 12:55:05 badboy kernel: ffff88022354bdc0 0000000000000086 ffff8800c54e8000 ffff88022354bfd8 > Feb 26 12:55:05 badboy kernel: ffff88022354bfd8 ffff88022354bfd8 ffff8800c54e8000 ffff88021f7300f0 > Feb 26 12:55:05 badboy kernel: ffff88021f7300f4 ffff8800c54e8000 00000000ffffffff ffff88021f7300f8 > Feb 26 12:55:05 badboy kernel: Call Trace: > Feb 26 12:55:05 badboy kernel: [<ffffffff8163b9e9>] schedule_preempt_disabled+0x29/0x70 > Feb 26 12:55:05 badboy kernel: [<ffffffff816396e5>] __mutex_lock_slowpath+0xc5/0x1c0 > Feb 26 12:55:05 badboy kernel: [<ffffffff81638b4f>] mutex_lock+0x1f/0x2f > Feb 26 12:55:05 badboy kernel: [<ffffffff81449729>] read_descriptors+0x39/0x110 > Feb 26 12:55:05 badboy kernel: [<ffffffff8125c28b>] ? read+0x6b/0x1f0 > Feb 26 12:55:05 badboy kernel: [<ffffffff8125c2fb>] read+0xdb/0x1f0 > Feb 26 12:55:05 badboy kernel: [<ffffffff811de43c>] vfs_read+0x9c/0x170 > Feb 26 12:55:05 badboy kernel: [<ffffffff811def8f>] SyS_read+0x7f/0xe0 > Feb 26 12:55:05 badboy kernel: [<ffffffff81645909>] system_call_fastpath+0x16/0x1b Since fprintd is the fingerprint reader daemon and this server doesn’t have such a peripheral, I removed the service. Now sudo is fast again. [*] Although that solves my immediate problem, while debugging all of this I noticed substantially the same error message also appearing for libvirtd: > Feb 26 12:57:05 badboy kernel: INFO: task libvirtd:1514 blocked for more than 120 seconds. > Feb 26 12:57:05 badboy kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > Feb 26 12:57:05 badboy kernel: libvirtd D ffff88021f7300f8 0 1514 1 0x00000080 > Feb 26 12:57:05 badboy kernel: ffff8800c08ffde0 0000000000000086 ffff8800c550e780 ffff8800c08fffd8 > Feb 26 12:57:05 badboy kernel: ffff8800c08fffd8 ffff8800c08fffd8 ffff8800c550e780 ffff88021f7300f0 > Feb 26 12:57:05 badboy kernel: ffff88021f7300f4 ffff8800c550e780 00000000ffffffff ffff88021f7300f8 > Feb 26 12:57:05 badboy kernel: Call Trace: > Feb 26 12:57:05 badboy kernel: [<ffffffff8163b9e9>] schedule_preempt_disabled+0x29/0x70 > Feb 26 12:57:05 badboy kernel: [<ffffffff816396e5>] __mutex_lock_slowpath+0xc5/0x1c0 > Feb 26 12:57:05 badboy kernel: [<ffffffff81638b4f>] mutex_lock+0x1f/0x2f > Feb 26 12:57:05 badboy kernel: [<ffffffff81449100>] manufacturer_show+0x20/0x50 > Feb 26 12:57:05 badboy kernel: [<ffffffff813f1c20>] dev_attr_show+0x20/0x60 > Feb 26 12:57:05 badboy kernel: [<ffffffff8125928a>] sysfs_read_file+0x9a/0x1a0 > Feb 26 12:57:05 badboy kernel: [<ffffffff811de43c>] vfs_read+0x9c/0x170 > Feb 26 12:57:05 badboy kernel: [<ffffffff811def8f>] SyS_read+0x7f/0xe0 > Feb 26 12:57:05 badboy kernel: [<ffffffff81645909>] system_call_fastpath+0x16/0x1b I don’t want to employ the same solution in this case — i.e. disable libvirtd — because while I don’t yet use KVM on that server, I actually had plans to do so soon. I could host those VMs elsewhere, but that feels like sweeping the problem under the rug. I want to fix this, but I’m now stuck. I’ve ruled out several possible causes already: 1. It isn’t DNS. DNS responds quickly. 2. It isn’t a flaky OS drive. Swapping the spinning rust drive out for an SSD was already on the wish list for this system, so I took the opportunity to reinstall the OS fresh on a brand new SSD. The same problem occurred shortly after booting CentOS 7.2 for the first time, and it continues to happen periodically. The only thing I’ve copied over from the old spinning drive so far is /home and /usr/local, and I can’t see how that could affect the kernel. Besides, the problem still occurs while booted into single-user mode. 3. It isn’t the RAID card. A RAID verify pass completed successfully, as did smartctl -t long tests on all of the individual drives. I even disabled the RAID card’s OPROM and blacklisted its driver at one point, just to see if the driver or RAID BIOS were the cause of the problem. I haven’t actually pulled the card yet, but that seems unlikely to solve anything, given that the array seems to be storing data reliably. 4. It isn’t the RAM. It just passed a memtest86+ run. That probably exonerates the CPU and north bridge, too. (I used v4.20 from the CentOS 7.2 install ISO.) 5. It isn’t stale packages. The OS reinstall proves that. It’s currently running the tip of CentOS 7.2 and still showing the same symptoms. 6. It isn’t high-uptime kernel space cruft, since it’s been rebooted a bunch of times during all of this, including several hard reboots. Rebooting is especially painful at the moment because the system hangs on shutdown waiting for libvirtd to respond. While I had fprintd installed, that was causing 3-minute hangs on boot, too. Very frustrating! [*] In case it isn’t clear how fprintd could affect sudo, it’s because fprintd installs a PAM module, and sudo uses PAM for authentication. If fprintd is stuck, the PAM call stalls until it gives up and moves on. I tracked this down with strace. The 25 seconds above is the timeout value passed to poll(2); that timeout is hit while sudo (via PAM) is trying to talk to dbus, since apparently fprintd communicates via dbus. Because the problem is in PAM and not sudo, it also affected su. It did not affect console or ssh user logins for some reason. I’m posting these details in case this diagnosis helps someone. While chasing this, I found a bunch of postings on the net from people who have run into such problems before, but none of the threads mentioned this particular failure mode. For all I know, I’m the first person it’s ever happened to, so this needs to be in the archives.

2 2

Discarding empty lines in rsyslog
by Anand Buddhdev 29 Feb '16

29 Feb '16

Dear CentOS folk, I've been try to solve one issue with rsyslog on CentOS 6, but can't figure it out. I've searched through rsyslog documentation, and used Google but not found anything that matches my issue. I'm sending output of a program to rsyslog using "logger -t progname". I've got the following config snippet in /etc/rsyslog.d: $FileCreateMode 0644 if $programname == 'progname' then /var/log/prog.log & ~ This works. However, the program sometimes produces blank lines its output, and they get logged by rsyslog as well. I want to make rsyslog ignore empty lines. I am trying the following, but it doesn't work: if $programname == 'progname' and $msg != '\n' then /var/log/prog.log Does anyone know how to get this to work in rsyslog? This is rsyslog 5 on CentOS 6. Regards, Anand

1 1

Odd selinux complaints on new, fully updated CentOS 7
by m.roth＠5-cent.us 29 Feb '16

29 Feb '16

Just installed 7.2, and I'm seeing this - is this a bug in the policy? ************************** SELinux is preventing systemd-readahe from add_name access on the directory .readahead.new. ***** Plugin catchall_labels (83.8 confidence) suggests ******************* If you want to allow systemd-readahe to have add_name access on the .readahead.new directory Then you need to change the label on .readahead.new Do # semanage fcontext -a -t FILE_TYPE '.readahead.new' where FILE_TYPE is one of the following: device_t, init_var_run_t, readahead_var_lib_t, readahead_var_run_t, root_t, var_run_t. Then execute: restorecon -v '.readahead.new' ***** Plugin catchall (17.1 confidence) suggests ************************** If you believe that systemd-readahe should be allowed add_name access on the .readahead.new directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep systemd-readahe /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:readahead_t:s0 Target Context system_u:object_r:mnt_t:s0 Target Objects .readahead.new [ dir ] Source systemd-readahe Source Path systemd-readahe Port <Unknown> Host <hostname> Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-60.el7_2.3.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name <hostname> Platform Linux <hostname> 3.10.0-327.10.1.el7.x86_64 #1 SMP Tue Feb 16 17:03:50 UTC 2016 x86_64 x86_64 Alert Count 4 First Seen 2016-02-29 10:06:27 EST Last Seen 2016-02-29 16:50:22 EST Local ID 0ba32e6a-e502-45be-a2dc-cda4c380a2bb Raw Audit Messages type=AVC msg=audit(1456782622.230:435): avc: denied { add_name } for pid=410 comm="systemd-readahe" name=".readahead.new" scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:mnt_t:s0 tclass=dir Hash: systemd-readahe,readahead_t,mnt_t,dir,add_name ***************************************** mark

1 0

Changing default file type in Centos 6
by H 28 Feb '16

28 Feb '16

It turns out my markdown files - extension .md - are of the "Genesis ROM" file type in Centos 6. Googling did not turn up any obvious places to change this in Gnome - neither in my local directory or in /etc/gnome. Where would I be able to change this default file type for files with the extension .md? I have already changed the default application to geany (with the markdown extension.) Thank you.

4 12

Restoring session status
by H 27 Feb '16

27 Feb '16

I am running CentOS 6.6 on both a couple of servers and on a laptop. When I let the laptop sleep, window states and positions are restored correctly when I awaken it. However, when I shut down the laptop, later turn it on and log in, none of the terminal windows and directory windows are restored correctly to e.g. minimized state, instead they are restored to when they last were in use. Naturally, this is a little bit annoying: have I missed a setting somewhere? Thanks.

2 2

CentOS-announce Digest, Vol 132, Issue 7
by centos-announce-request＠centos.org 27 Feb '16

27 Feb '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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. Release for CentOS Linux 7 Rolling media Feb 2016 (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Sat, 27 Feb 2016 00:37:51 +0000 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] Release for CentOS Linux 7 Rolling media Feb 2016 Message-ID: <56D0EFDF.5040304(a)centos.org> Content-Type: text/plain; charset=utf-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am pleased to announce general availability of the Feb 2016 snapshot for CentOS Linux. This release includes CentOS Linux 7 iso based install media, Generic Cloud images, Atomic Host, Docker containers, Vagrant images, vendor hosted cloud images. This release set is tag'd 1602 CentOS Linux rolling builds are point in time snapshot media rebuild from original release time, to include all updates pushed to mirror.centos.org's repositories. This includes all security, bugfix, enhancement and general updates for CentOS Linux. Machines installed from this media will have all these updates pre-included and will look no different when compared with machines installed with older media that have been yum updated to the same point in time. All rpm/yum repos remain on mirror.centos.org with no changes in either layout or content. - -------- CentOS Linux 7 / x86_64 install media is available at http://buildlogs.centos.org/rolling/7/isos/x86_64/ File: CentOS-7-x86_64-Minimal-1602-01.iso Sha: 741a28e3d42c40ded2e42b83eda4d8d09137b36ceef584753b94abd298d4dfed File: CentOS-7-x86_64-Everything-1602-01.iso Sha: 6cc79d3f3183318d0089cb04dbfd97418ff009f6fb01bce4849289ede96df45d File: CentOS-7-x86_64-DVD-1602-01.iso Sha: 34120f3bc02e1edd6d5b19516876c8456a1300de4b98da79fb0a7d444d1df3d8 - -------- CentOS Linux 7 / x86_64 Cloud Images are available at : http://cloud.centos.org/centos/7/images/ File: CentOS-7-x86_64-GenericCloud-1602.qcow2 Sha: 1b777fa1ea2b2cf0be7ed6ecce54ef18ece5c6551fb291549b887e33b78d7c78 File: CentOS-7-x86_64-GenericCloud-1602.qcow2c Sha: bc0f51d9376001f8973595b71105b9d53c8c27b3e0969676aab2ab036cc4d835 File: CentOS-7-x86_64-GenericCloud-1602.qcow2.xz Sha: dd0f5e610e7c5ffacaca35ed7a78a19142a588f4543da77b61c1fb0d74400471 File: CentOS-7-x86_64-GenericCloud-1602.raw.tar.gz Sha: f4e679eef79af695bd8f2cb32d37fa93c7cb4644eb79f689bde6bd86100e4af5 - -------- CentOS Atomic Host was released earlier, details for the release are available at : https://lists.centos.org/pipermail/centos-devel/2016-February/014446.htm l - -------- CentOS Linux 6 and 7 AMIs have been updated as well, as follows: CentOS Linux 6 : https://aws.amazon.com/marketplace/pp/B00NQAYLWO/ CentOS Linux 7 : https://aws.amazon.com/marketplace/pp/B00O7WM7QW/ These images are also now enabled across all Amazon EC2 regions, and available on all HVM instance types. This includes the Amazon AWS free tier. - -------- CentOS Linux 7 / x86_64 Vagrant images are updated at https://vagrantcloud.com/centos/boxes/7 and the backing files can be downloaded for libvirt and virtualbox providers at : Libvirt: http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-x86_64-V agrant-1602_02.LibVirt.box Virtualbox: http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-x86_64-V agrant-1602_02.VirtualBox.box - -------- CentOS Linux 5 / 6 and 7 docker images are updated at http://index.docker.io/_/centos - -------- We welcome all feedback around these rolling builds and media updates at the centos-devel mailing list ( http://lists.centos.org/ ). enjoy! - -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJW0O/fAAoJEI3Oi2Mx7xbt0KwH/RUBoINSas2fADErpw0HFJI+ 8QmRa5sH6X5vvBodWMT5qiulkof06IgX6psrniCzYejt88OP0XUjuA0lEh9MUq4a Ie7X5TnXIndH0eGU3UQIivXRojeSTdDjNmbdTQehxTN5WfA/tml29eppMBRt6xEi K56/Ml2FxdU/b1EkCBO68VWcZvAl6gxmtLJv38sFn2WxepDjyrHGF+A10sJqGYt6 V7E32iZqZDwkSmuWwHdf7T0NH9DE9TxcIH/IsRUnYAcwqLcGZm+WqFoD6KRafVAM e2KvLr/L9NwaU6C6rZVWJ1yHwBaYH87xNEGcr69mpR2HJQt3PrlkiTC4wXVKpRg= =015B -----END PGP SIGNATURE----- ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 132, Issue 7 ***********************************************

1 0

Question about cleanly unmounting slave bind mounts
by likan_999.student＠sina.com 27 Feb '16

27 Feb '16

Hi, I asked the question on stackexchange (http://unix.stackexchange.com/questions/264931/centos-7-unable-to-cleanly-u…) and CentOS 7 bug report (https://bugs.centos.org/view.php?id=10414) but didn't get any useful response, so I am thinking if I can get some help here. The problem arose when I tried to rbind mount /dev and /proc to a chroot sandbox and to unmount it, I have to set the mount to slave so that unmounting submounts of <sandbox-root>/dev (e.g. /dev/pts) won't unmount submounts of /dev. This works for other distributions such as Fedora 23 and Ubuntu 14.04, but under CentOS 7, umount succeeds but the directory can't be removed. For some reason, I have to stick to CentOS 7, so I wonder if there is a work around for it. The steps to reproduce: [hidden]$ mkdir -p A B/a C/b [hidden]$ sudo mount --bind A B/a [hidden]$ sudo mount --rbind B C/b [hidden]$ sudo mount --make-rslave C/b [hidden]$ sudo umount C/b/a [hidden]$ sudo umount C/b [hidden]$ rmdir C/b rmdir: failed to remove ‘C/b’: Device or resource busy None of mount, cat /proc/mounts, cat /etc/mtab, sudo lsof, sudo fuser C/b shows any process using the directory C/b; stat C/b shows it is different inode than B, meaning it has already been unmounted successfully. The kernel version is 3.10.0-327.10.1.el7.x86_64. Any suggestion is welcomed.附件（0个）全部下载超大附件（0个）

1 0

CentOS Extras SRPMs for 7.1 / 7.2
by Pierre Riteau 26 Feb '16

26 Feb '16

Hello, I noticed that recent source repositories for CentOS Extras packages do not have SRPMs for each available RPM. In particular, I wanted to download the SRPM for cloud-init. After enabling the extras-source repository, `yumdownloader --source cloud-init` doesn't find any package. This used to work on CentOS 7.0. See the content of the following two repos: http://vault.centos.org/7.2.1511/extras/Source/SPackages/ http://vault.centos.org/7.1.1503/extras/Source/SPackages/ compared with http://vault.centos.org/7.0.1406/extras/Source/SPackages/ It looks like only packages which were updated have made it in the newer repositories. Thanks, Pierre

2 1

Internet Storm Center blogpost on rootcheck (a system auditor)
by Gilbert Sebenste 26 Feb '16

26 Feb '16

Hello everyone, If you haven't seen it: https://isc.sans.edu/forums/diary/Quick+Audit+of+NIX+Systems/20771/ I just compiled and ran it on CentOS 5 and 6. The audit came up clean for me. It's worth a run to see if you have anything blatant wrong...or to see if you have been rooted. Gilbert ******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************

1 0

Skylake Installs on CentOS-7
by Johnny Hughes 26 Feb '16

26 Feb '16

We were informed that many people were having issues on newer intel (Skylake) platforms installing the latest CentOS-7 and asked if we could find/fix the problem. We found that the latest kernel, kernel-3.10.0-327.10.1.el7, fixes this issue on some machines, so we rebuilt the installer for people having issues. Please see this mail for the new isos: https://lists.centos.org/pipermail/centos-devel/2016-February/014444.html If you are not having issues, you will want to continue to use the standard installers as they provide better support for 3rd party kernel modules, etc. Thanks, Johnny Hughes

1 0

CentOS install disable USB keyboard on Acer AXC 603G UW13
by Juan De Mola 26 Feb '16

26 Feb '16

Hi. I am triying to set up CentOS 5 on an Acer AXC 603G UW13. The install turn off my USB keyboard between /sbin/loader and the media check prompt screen. What I can do to get the install working with the USB keyboard? Thanks. Juan De Mola molaxp(a)aol.com

5 13

IPtables block user from outbound ICMP
by John Cenile 26 Feb '16

26 Feb '16

Hello, Is it possible at all to block all users other than root from sending outbound ICMP packets on an interface? At the moment we have the following two rules in our IPtables config: iptables -A OUTPUT -o eth1 -m owner --uid-owner 0 -j ACCEPT iptables -A OUTPUT -o eth1 -j DROP But this still allows ICMP for some reason (but *does* block other TCP/UDP packets, which is what we want, as well as ICMP). Thanks.

7 8

CentOS 7 SELinux issue
by Alice Wonder 25 Feb '16

25 Feb '16

Trying to add SELinux support to my bitcoin package. Keep getting this on install: SELinux: Could not downgrade policy file /etc/selinux/targeted/policy/policy.29, searching for an older version. SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.29: No such file or directory /sbin/load_policy: Can't load policy: No such file or directory libsemanage.semanage_reload_policy: load_policy returned error code 2. I Tried yum reinstall selinux-policy selinux-policy-targeted restorecon -R -v /etc/selinux as suggested on some mailing lists. Didn't work, same issue. How can I troubleshoot what is causing this? The policy.29 file exists. The RPM responsible for it verifies (and was reinstalled) I don't ordinarily run SELinux and do not have it enabled. Things like that are why, it always ALWAYS got in the way of productivity and when I did run it and I was never hacked without it, so... but I need to figure out what the problem is here.

4 4

Bitcoin for CentOS 7
by Alice Wonder 24 Feb '16

24 Feb '16

For those interested I have a working spec file for Bitcoin 0.12.0 https://github.com/AliceWonderMiscreations/bitcoin/blob/master/contrib/rpm/… I believe the only BuildRequires that isn't in CentOS/EPEL is miniupnpc-devel but that's trivial to build as well. With Bitcoin 0.12.0 the ECC stuff that Red Hat ripped out of OpenSSL doesn't matter anymore. -=- That spec file is somewhat based on what https://www.ringingliberty.com/bitcoin/ does for Fedora / CentOS with a couple noted differences - A) I don't have SELinux stuff (yet). His SELinux stuff is broken on CentOS 7. Only matters for the bitcoin-server package, the GUI client doesn't seem to matter. B) He uses system BerkeleyDB. I build BerkeleyDB when building bitcoin because BerkeleyDB is fragile enough that changes to it can cause a wallet that can't be read by other clients. C) He adds a patch that adds functionality needed by a very small demographic - hardware machines that sell bitcoins. I prefer to not add that patch because I prefer pristine source rather than modifying what the devs produced for a feature 99.9% of the population doesn't need. So I prefer to stick with the precise version that bitcoin.org uses in the binary builds they distribute. Happens to be same version CentOS 7 has now but that may not always be the case. It isn't with CentOS 6. Anyway if anyone one this list has interest, figured I'd share the spec file. Adding SELinux to the server package I will work on. Oh the referenced patch that is there is only needed for LibreSSL, you can comment it out to build against OpenSSL. 0.12.0 seems much faster at indexing than previous versions, and catches up faster when it is behind on blocks.

3 8

CentOS 7, odd message from nfsdcltrack
by m.roth＠5-cent.us 23 Feb '16

23 Feb '16

Is this normal, or a bug, perhaps a mismatch in two pieces (and this server was just updated late yesterday afternoon, and rebooted this morning): <timestamp> <servername> nfsdcltrack[12128]: sqlite_insert_client: insert statement prepare failed: table clients has 2 columns but 3 values were supplied mark

2 1

Substitute pdftk with other command
by Dario Lesca 22 Feb '16

22 Feb '16

Hi, I must migrate a Centos5 server on Centos7 On server Centos5 there is a shell procedure witch add to PDF a timestamp like this example: http://i.stack.imgur.com/OBsqX.png with this command: $ pdftk input.pdf stamp overlay.pdf output stamped.pdf Into Centos7 pdftk it is no longer allowed Someone knows some other command to replace it or other ways to do this? Or how I can install pdftk on Centos7. Many thanks for your help. -- Dario Lesca (inviato dal mio Linux Fedora 23 Workstation)

3 4

Network hangs after several hours (Centos 6 recently upgraded kernel/glibc)
by Ian B 22 Feb '16

22 Feb '16

Hi all, We have a development server we have just tried updating the kernel & glibc after recent recommendations. Its been stable previously for a few years with only scheduled reboots. Its running Centos 6.6(final) 2.6.32-573.18.1.el6.x86_64 GNU libc 2.12 Upgraded via YUM, rebooted, all fine for several hours, and then network seemed to hang. Not much happening as its a dev server we are testing before moving to production. Googling, I see there is some history of e100e driver having issues, and I'm wondering if it could be related. Does anyone have any thoughts on where to do with it, as I'm assuming it will hang again later. Thanks, Ian Feb 18 05:04:36 kernel: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x26d/0x280() (Not tainted) Feb 18 05:04:36 kernel: Hardware name: X9SCL/X9SCM Feb 18 05:04:36 kernel: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Feb 18 05:04:36 kernel: Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 ext4 jbd2 e1000e serio_raw i2c_i801 i2c_core sg iTCO_wdt iTCO_vendor_support shpchp ext3 jbd mbcache raid1 sd_mod crc_t10dif ahci dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] Feb 18 05:04:36 kernel: Pid: 0, comm: swapper Not tainted 2.6.32-220.4.2.el6.x86_64 #1 Feb 18 05:04:36 kernel: Call Trace: Feb 18 05:04:36 kernel: <IRQ> [<ffffffff81069a17>] ? warn_slowpath_common+0x87/0xc0 Feb 18 05:04:36 kernel: [<ffffffff81069b06>] ? warn_slowpath_fmt+0x46/0x50 Feb 18 05:04:36 kernel: [<ffffffff8144a4fd>] ? dev_watchdog+0x26d/0x280 Feb 18 05:04:36 kernel: [<ffffffff8108b3fd>] ? insert_work+0x6d/0xb0 Feb 18 05:04:36 kernel: [<ffffffff8144a290>] ? dev_watchdog+0x0/0x280 Feb 18 05:04:36 kernel: [<ffffffff8107c7f7>] ? run_timer_softirq+0x197/0x340 Feb 18 05:04:36 kernel: [<ffffffff810a0a10>] ? tick_sched_timer+0x0/0xc0 Feb 18 05:04:36 kernel: [<ffffffff8102ad6d>] ? lapic_next_event+0x1d/0x30 Feb 18 05:04:36 kernel: [<ffffffff81072001>] ? __do_softirq+0xc1/0x1d0 Feb 18 05:04:36 kernel: [<ffffffff81095610>] ? hrtimer_interrupt+0x140/0x250 Feb 18 05:04:36 kernel: [<ffffffff8100c24c>] ? call_softirq+0x1c/0x30 Feb 18 05:04:36 kernel: [<ffffffff8100de85>] ? do_softirq+0x65/0xa0 Feb 18 05:04:36 kernel: [<ffffffff81071de5>] ? irq_exit+0x85/0x90 Feb 18 05:04:36 kernel: [<ffffffff814f4d70>] ? smp_apic_timer_interrupt+0x70/0x9b Feb 18 05:04:36 kernel: [<ffffffff8100bc13>] ? apic_timer_interrupt+0x13/0x20 Feb 18 05:04:36 kernel: <EOI> [<ffffffff812c49de>] ? intel_idle+0xde/0x170 Feb 18 05:04:36 kernel: [<ffffffff812c49c1>] ? intel_idle+0xc1/0x170 Feb 18 05:04:36 kernel: [<ffffffff813f9ef7>] ? cpuidle_idle_call+0xa7/0x140 Feb 18 05:04:36 kernel: [<ffffffff81009e06>] ? cpu_idle+0xb6/0x110 Feb 18 05:04:36 kernel: [<ffffffff814d40ca>] ? rest_init+0x7a/0x80 Feb 18 05:04:36 kernel: [<ffffffff81c1ff76>] ? start_kernel+0x424/0x430 Feb 18 05:04:36 kernel: [<ffffffff81c1f33a>] ? x86_64_start_reservations+0x125/0x129 Feb 18 05:04:36 kernel: [<ffffffff81c1f438>] ? x86_64_start_kernel+0xfa/0x109 Feb 18 05:04:36 kernel: ---[ end trace 21915186e9d87b29 ]--- modinfo e1000e | grep version version: 3.2.5-k srcversion: 8CCA78B3C15DE6229299348 vermagic: 2.6.32-573.18.1.el6.x86_64 SMP mod_unload modversions 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 Processor Family DRAM Controller (rev 09) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation C202 Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)

5 8

where did SCL go?
by jason welsh 22 Feb '16

22 Feb '16

monsterjam:/etc/letsencrypt/archive/monsterjam # yum --enablerepo=extras install centos-release-SCL Loaded plugins: fastestmirror, remove-with-leaves Setting up Install Process Loading mirror speeds from cached hostfile * base: mirror.dattobackup.com * epel: mirror.us.leaseweb.net * extras: distro.ibiblio.org * updates: mirror.netdepot.com No package centos-release-SCL available. Error: Nothing to do monsterjam.org:/etc/letsencrypt/archive/monsterjam # cat /etc/centos-release CentOS release 6.7 (Final) monsterjam:/etc/letsencrypt/archive/monsterjam # any ideas?

3 3

Kernel panic and crash, was Re: [CentOS-announce] CEBA-2016:0150 CentOS 6 kernel BugFix Update
by Max Pyziur 21 Feb '16

21 Feb '16

Greetings, I just tried upgrading one of my CentOS boxes to this kernel. It crashes; the screen looks like this: http://www.brama.com/~deckard/P1010308.JPG So, I'm continuing to run on kernel-2.6.32-504.23.4.el6.x86_64 I had previously reported this, and I was told that the reported bug was here: https://bugs.centos.org/view.php?id=9374 Looking at it now, I see that it is closed. It's odd that CentOS is releasing a production kernel that fails. fyi, Max Pyziur pyz(a)brama.com On Wed, 10 Feb 2016, Johnny Hughes wrote: > > CentOS Errata and Bugfix Advisory 2016:0150 > > Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0150.html > > The following updated files have been uploaded and are currently > syncing to the mirrors: ( sha256sum Filename ) > > i386: > b5f33a81b28d0a89af970bc08c4a07856c13f9789fe520e90d237dc7a2e5df65 kernel-2.6.32-573.18.1.el6.i686.rpm > 8b375b6d363800343bc325966b4db96347e2508db458547b0df5dc63581e2793 kernel-abi-whitelists-2.6.32-573.18.1.el6.noarch.rpm > cba169e9faf5ebc0ba25011f3b920de1a3a2943b7e46be6292193b31df7b8a5a kernel-debug-2.6.32-573.18.1.el6.i686.rpm > a4bf157c52dc0d736ef7a65a073e543b3f2cf0070aa938da41eeecaca11e783d kernel-debug-devel-2.6.32-573.18.1.el6.i686.rpm > 5151ae3d0f6dde51c1ec991e14b88f0308ef7d46975ee7e9ed036f1381153901 kernel-devel-2.6.32-573.18.1.el6.i686.rpm > 74ff6b30bd2603f2e859e899a653aaac2daa0ee534abd5ab3e32a8ffc2cdb2fb kernel-doc-2.6.32-573.18.1.el6.noarch.rpm > 38a27fbf4e7fa229fe8ab6b8cf25ec08031c376cf51ec38400197bc478d0255a kernel-firmware-2.6.32-573.18.1.el6.noarch.rpm > f318d66d12c72c060e8f644aa90d0c10099f1ab8ba5e24875f2a1ace22e35a57 kernel-headers-2.6.32-573.18.1.el6.i686.rpm > 81ef77b0d7841946bf8825e599c1f6a6015082013b5ea02a836db34e19ca7fbc perf-2.6.32-573.18.1.el6.i686.rpm > a8fa3ef717f09235052dd6bd4285be52ff494ea8c242788df16eda5b9aed7fb6 python-perf-2.6.32-573.18.1.el6.i686.rpm > > x86_64: > 1cb5031871e077e7d70fec7801901a948438d10f226ffb4311540c28f9253a55 kernel-2.6.32-573.18.1.el6.x86_64.rpm > 8b375b6d363800343bc325966b4db96347e2508db458547b0df5dc63581e2793 kernel-abi-whitelists-2.6.32-573.18.1.el6.noarch.rpm > 9f31b8f7f4db48d8ba30c16564cb6ad614d04b7d63811c274134654607cbce08 kernel-debug-2.6.32-573.18.1.el6.x86_64.rpm > a4bf157c52dc0d736ef7a65a073e543b3f2cf0070aa938da41eeecaca11e783d kernel-debug-devel-2.6.32-573.18.1.el6.i686.rpm > 16cb431b4a01c6b3b915e646c971fa0c79e62f4feeffd57939f39df687ebc6a3 kernel-debug-devel-2.6.32-573.18.1.el6.x86_64.rpm > b81c297339078d80dda73d86a1aec61c50d7fb05728585c1ebbe81bb088851bf kernel-devel-2.6.32-573.18.1.el6.x86_64.rpm > 74ff6b30bd2603f2e859e899a653aaac2daa0ee534abd5ab3e32a8ffc2cdb2fb kernel-doc-2.6.32-573.18.1.el6.noarch.rpm > 38a27fbf4e7fa229fe8ab6b8cf25ec08031c376cf51ec38400197bc478d0255a kernel-firmware-2.6.32-573.18.1.el6.noarch.rpm > 9dd3a3533ebb6646bafafef2229b6142fa0277f34a534e7c74f3c8cacafd7296 kernel-headers-2.6.32-573.18.1.el6.x86_64.rpm > 5ff27ecbdca7013f093d697f4ba3bcaa9b14be03ef79cafb4a3ed3d0aef1bf69 perf-2.6.32-573.18.1.el6.x86_64.rpm > c5fee073bee1f19dc848a8302e07e4241e49cbff55f35a3db5ae903352f11dc4 python-perf-2.6.32-573.18.1.el6.x86_64.rpm > > Source: > ef3c944af9b7e94448e3c343da7d6f582b267aa9a5653586b8b9332351b01afc kernel-2.6.32-573.18.1.el6.src.rpm > > > >

2 1

centos7 :: ks.cfg :: customisation of sshd
by Adrian Sevcenco 19 Feb '16

19 Feb '16

Hi! I want to change the sshd port at install for centos7 but i am not sure if i am on the good track (and it is time expensive to make many try-outs).. So, i would be grateful if someone with experience can spot if i have problems with my planning.. (the actual purpose is that after installation i have access for my ansible provisioning) first make sure ssh is started services --enabled=sshd,chronyd then .. i imagine that in the %post section %post --interpreter=/usr/bin/bash --log=/root/ks-post.log 1. i could use sed to change the port sed -i 's/#Port\ 22/Port 60000/' /etc/ssh/sshd_config 2. sed -i 's/#PermitRootLogin\ yes/PermitRootLogin\ yes/' /etc/ssh/sshd_config 3. enable key access mkdir -p /root/.ssh chmod 700 /root/.ssh cat << EOF >> /root/.ssh/authorized_keys my_ssh_pubkey EOF 4. semanage port -a -t ssh_port_t -p tcp 60000 5. firewall-cmd --permanent --zone=public --add-port=60000/tcp 6. systemctl enable firewalld.service did i miss anything? Thank you! Adrian

4 4

CentOS-announce Digest, Vol 132, Issue 6
by centos-announce-request＠centos.org 19 Feb '16

19 Feb '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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-2016:0258 Important CentOS 7 thunderbird Security Update (Johnny Hughes) 2. CESA-2016:0258 Important CentOS 6 thunderbird Security Update (Johnny Hughes) 3. CESA-2016:0258 Important CentOS 5 thunderbird Security Update (Johnny Hughes) 4. CEBA-2016:0268 CentOS 6 ptlib FASTTRACK BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 18 Feb 2016 17:19:24 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0258 Important CentOS 7 thunderbird Security Update Message-ID: <20160218171924.GA56122(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0258 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0258.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d97294b0f502e02f49e4d2ca9a3fb5cc368a3ad6c08162e06e509e607a00a307 thunderbird-38.6.0-1.el7.centos.x86_64.rpm Source: 2555990fee9e57f5a64ea43642860f30fe807d073e48d048665adadb1bc489f1 thunderbird-38.6.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 18 Feb 2016 18:42:37 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0258 Important CentOS 6 thunderbird Security Update Message-ID: <20160218184237.GA57736(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0258 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0258.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b6943f1cda53a9c502ee9839f608c29d0e75cf44673490822c93f395e3f40141 thunderbird-38.6.0-1.el6.centos.i686.rpm x86_64: 5a1261b9965569d707060f8e7ff869288d7e0361efe4e5637086bf6295afe27a thunderbird-38.6.0-1.el6.centos.x86_64.rpm Source: 4f89116b8b8bda266f2063760ceb136832e8e2d874ffd33d9e424d479d980a63 thunderbird-38.6.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Fri, 19 Feb 2016 04:09:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0258 Important CentOS 5 thunderbird Security Update Message-ID: <20160219040941.GA32077(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0258 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0258.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: fc47e7fd94bd3079266b27f1307d954fd5a9f9442a91c3a2cb6172e86faa9224 thunderbird-38.6.0-1.el5.centos.i386.rpm x86_64: ec8dcb696078c89e8aa535036e750f5e4e06e40dbcd883e255287ea6b69bd61e thunderbird-38.6.0-1.el5.centos.x86_64.rpm Source: 2e6c718b8d5ce3cf2919e8c44995d1048ae923f32159b06cfc6f0dd06caa2088 thunderbird-38.6.0-1.el5.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 4 Date: Fri, 19 Feb 2016 04:19:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:0268 CentOS 6 ptlib FASTTRACK BugFix Update Message-ID: <20160219041941.GA19991(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:0268 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0268.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0348146563840e96432128fce8893e5c1e052b8c7a04731580b71ef6ec88d928 ptlib-2.6.5-5.el6.i686.rpm f15fb5b00ef80df31948e084c9746c4d38af9b8f6f17f435ee35a2a420a1805b ptlib-devel-2.6.5-5.el6.i686.rpm x86_64: 0348146563840e96432128fce8893e5c1e052b8c7a04731580b71ef6ec88d928 ptlib-2.6.5-5.el6.i686.rpm 9591b407f7f281255041138bea978c25fa450d4db068cc267396eef5f47e82d4 ptlib-2.6.5-5.el6.x86_64.rpm f15fb5b00ef80df31948e084c9746c4d38af9b8f6f17f435ee35a2a420a1805b ptlib-devel-2.6.5-5.el6.i686.rpm 16d22c5bd3e7e1f8c2030c3c9cfedbb8d8163bd079d91fa284e299ec4d2f9e77 ptlib-devel-2.6.5-5.el6.x86_64.rpm Source: 77f35943cb9f218305dad4478269b10bc9b932a7376710c6a4ad147b6aeeab52 ptlib-2.6.5-5.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 132, Issue 6 ***********************************************

1 0

dhcpd frequent renewals
by david 19 Feb '16

19 Feb '16

Folks This might be the wrong place to ask, but I don't know where to turn. My internal home network, including wireless, is controlled by a Centos6 server, which provides dhcpd services, along with NAT. I have DHCPD configured with the addresses 192.168.155.200 through 192.168.155.254 as the range for dynamic allocations. The default-lease time is 1800 seconds, the maximum is 3600 seconds. My windows clients, and even an ipad-mini behave nicely, asking for DHCP renewals once ever five minutes, or at about 80% of the default lease time, a behavior I can understand. However, several of my guests, with their own iPads, I-watches, iPhones, connect to my network (via a wireless access point which does not do routing functions) and they're renewing once every 20-30 seconds. In addition, these devices also loose connectivity for brief intervals, which seems to be roughly synchronized with dhcp renewal. This last fact I deduce by doing "tail -f /etc/log/messages" and hearing them say "lost connection" at just about the same moment the DHCPREQUEST and DHCPACK statements show up. It's difficult to believe that Apple IOS devices (all of which are running apple's latest) have a dhcp client problem not shared by windows or even linux hosts. Does anyone have any clues? David Kurn San Francisco DHCPD.CONF file is excerpted below: ---------------------------------------- ddns-update-style none; subnet 192.168.155.0 netmask 255.255.255.0 { authoritative; option routers 192.168.155.2; option subnet-mask 255.255.255.0; option broadcast-address 192.168.155.255; option domain-name "daku.org"; option domain-name-servers 192.168.155.2; option netbios-name-servers 192.168.155.2; option time-offset -28800; # Pacific standard time range dynamic-bootp 192.168.155.200 192.168.155.254; default-lease-time 1800; max-lease-time 3600; } --------------------------------------------

2 3

CentOS 7, Xeon CPUs, not booting
by m.roth＠5-cent.us 18 Feb '16

18 Feb '16

This is happening on anything other than plain vanilla Dell servers. One R730, with dual Tesla cards, one R420, with a fibre card for a RAID device, it never switches root. All these systems have Xeons, not AMD CPUs. We've had this with every one of the 327 kernels. In addition, it seems to happen also with the 229.20.1; the 229.14.1 has no such problem. >From the rdsosreport: starting at line 126: /dev/disk/by-label: total 0 lrwxrwxrwx 1 root 0 10 Jan 27 19:03 SWAP -> ../../sda2 lrwxrwxrwx 1 root 0 10 Jan 27 19:03 \x2f -> ../../sda3 lrwxrwxrwx 1 root 0 10 Jan 27 19:03 \x2fboot -> ../../sda1 Then, starting at line 1283: [ 3.317027] <servername> systemd[1]: Found device ST500NM0003-9ZM172 /. [ 3.317974] <servername> systemd[1]: Starting File System Check on /dev/disk/by-label/\x2f... [ 3.320089] <servername> systemd-fsck[590]: Failed to detect device /dev/disk/by-label// [ 3.320567] <servername> systemd[1]: systemd-fsck-root.service: main process exited, code=exited, status=1/FAILURE [ 3.320972] <servername> systemd[1]: Failed to start File System Check on /dev/disk/by-label/\x2f. Does *ANYONE* have any clues as to what's going on? Meanwhile, on a plain vanilla Dell R420, I see: ll /dev/disk/by-label/ total 0 lrwxrwxrwx. 1 root root 10 Feb 17 10:06 SWAP -> ../../sda2 lrwxrwxrwx. 1 root root 10 Feb 17 10:06 boot -> ../../sda1 lrwxrwxrwx. 1 root root 10 Feb 17 10:06 root -> ../../sda3 So, what is this by-label with the x2f, and why can't it find the drives? Or do I have to file a bug report? This is a true show-stopper. mark

3 4

Can't install CentOS 7 on SuperMicro X7DB3 with Adaptec AIC-9410 Controller
by homeryan＠sina.com 18 Feb '16

18 Feb '16

I have a server with Super Micro X7DB3 motherboard and Adaptech AIC-9410 controller (http://www.supermicro.com/products/motherboard/Xeon1333/5000P/X7DB3.cfm) The hard disk is single SeaGate SAS disk (300Gb). I'd like to install CentOS 7 on the server, but unfortunately, the CentOS installer can't find any hard disk. I think the problem maybe caused by the disk controller. Can you please tell me how to fix the problem ? Thanks for your help!

2 1

Thunderbird can not import S/MIME certificate
by Timo Schoeler 18 Feb '16

18 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, in May 2015 I reported [0] that I can not import my S/MIME certificate. Issuer is GlobalSign. Jan Horak reassigned it to the nss guys ("This seems to be problem in NSS code, reassigning to nss component"), but then the ticket idled and was eventually closed by EOL of Fedora 21 (though I stated it persists with F22). I just reopened the ticket because it still doesn't work. The certificate itself is okay, it works on other platforms. Nobody else using S/MIME? Best, Timo https://bugzilla.redhat.com/show_bug.cgi?id=1218977 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlbFgGYACgkQuSPmkPhAW0r2QQD+Pn97WYQNwItYmJ4eqgMm4ufk SSWrC4Yjm7iEYNotTkEA/RbB9lLTjecLaCpkQ33zV1bVCcHdsvQfi/WLhZH5zwur =/SFq -----END PGP SIGNATURE-----

2 1

New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
by Johnny Hughes 18 Feb '16

18 Feb '16

I normally just let the daily announce post to this list show what is available for updates, but there is a CVE (CVE-2015-7547) that needs a bit more attention which will be on today's announce list of updates. We released a new glibc yesterday for CentOS-6 and CentOS-7 .. it is VERY important that all users update to these versions: This update is rated as Critical by Red Hat, meaning that it is remotely exploitable under some circumstances. Make sure this update works in your environments and update as soon as you can. CentOS-7: https://lists.centos.org/pipermail/centos-announce/2016-February/021672.html https://rhn.redhat.com/errata/RHSA-2016-0176.html CentOS-6: https://lists.centos.org/pipermail/centos-announce/2016-February/021668.html https://rhn.redhat.com/errata/RHSA-2016-0175.html These mitigate CVE-2015-7547: https://access.redhat.com/security/cve/CVE-2015-7547 https://bugzilla.redhat.com/show_bug.cgi?id=1293532 Can't stress how important this update is .. here are a couple stories: http://arstechnica.com/security/2016/02/extremely-severe-bug-leaves-dizzyin… http://www.theregister.co.uk/2016/02/16/glibc_linux_dns_vulernability/ Please note that the ONLY way this is tested to work is with ALL updates from CentOS-6 or CentOS-7 applied along with the glibc updates. So a yum update with base and updates repo enabled is the ONLY tested scenario. Did I say *ONLY* enough? Thanks, Johnny Hughes

6 16

CentOS 6.7 Drivers for Compaq Storageworks TL891 Minilibrary
by Mustafa Mohammed 18 Feb '16

18 Feb '16

Hello all I am trying to setup a backup system using Bacula on CentOS 6.7 installed on eserver x345 but cannot find the drivers Any help in finding the drivers will be much appreciated Regards Mustafa

3 3

Systemd persistent change to service file
by Michael H 18 Feb '16

18 Feb '16

Hi All, I had my database fall over earlier, Initially I thought it was due to a change in the OS but the postgresql update overwrote my systemd service file. How can I create a file for my postgresql service that will not be overwritten when updates are applied? Am I correct in thinking it will be something like vi /etc/systemd/system/postgresql.service.d/postgresql-limit-stack.conf #with the contents: .include /etc/systemd/system/multi-user.target.wants/postgresql.service [Service] LimitSTACK=17825792 thanks Michael

3 2

slightly off-topic, RAID program for on-board SAS 2308-4i ?
by Zube 17 Feb '16

17 Feb '16

Does anyone know what program can be used to query the RAID status from the OS for an on-board LSI SAS 2308-4i? On this page: http://docs.avagotech.com/docs/12351997 there is a curious note on the left that reads: "Integrated MegaRAID support available upon request" After one mostly fruitless round of chatting with LSI/Avago/Broadcom and one completely fruitless round of chatting with HP, I found confirmation under the storage section here: http://www8.hp.com/us/en/mpc/workstations/product-detail.html?oid=5225041#!… It looks like HP didn't "request" MegaRAID support, so MegaCli and StorCli don't see anything and neither does lsiutils (nor hpacucli, tried just for a laugh). Any clues appreciated. Thanks for your time. Cheers, Zube

3 4

Openswan <-> VyOS
by John Cenile 17 Feb '16

17 Feb '16

Hello, I'm having a bit of trouble connecting our current CentOS Openswan server with a Vyos server via IPSec. I've posted this on the VyOS forums, but haven't had many helpful responses, so I thought I would ask here. http://forum.vyos.net/showthread.php?tid=26504&pid=29703#pid29703 Basically our Openswan configuration is as follows: conn VYOS keyingtries=0 keylife=20m ikelifetime=2h left=<VYOS IP> right=<OPENSWAN IP> leftsubnets={ 10.1.1.0/24,10.1.2.0/24,10.1.3.0/24,10.1.4.0/24,10.1.5.0/24} rightsubnets={10.2.1.0/24,10.2.2.0/24,10.2.3.0/24,10.2.4.0/24} auto=start authby=secret dpddelay=30 dpdtimeout=120 dpdaction=hold phase2alg=aes256-sha1;modp1536 phase2=esp ike=aes256-sha1;modp1536 Our VyOS configuration is posted in the above forum post, except now I have followed their advice and created 20 tunnels (each subnet to each subnet, if that makes sense). However, when I enabled this, I got the following errors on the Openswan server: Feb 18 01:24:27 OPENSWAN pluto[8010]: "VYOS/3x3" #70: next payload type of ISAKMP Hash Payload has an unknown value: 243 Feb 18 01:24:27 OPENSWAN pluto[8010]: "VYOS/3x3" #70: malformed payload in packet Feb 18 01:24:27 OPENSWAN pluto[8010]: "VYOS/3x3" #70: sending notification PAYLOAD_MALFORMED to <VYOS IP>:500 Feb 18 01:24:27 OPENSWAN pluto[8010]: "VYOS/4x4" #69: next payload type of ISAKMP Hash Payload has an unknown value: 170 Feb 18 01:24:27 OPENSWAN pluto[8010]: "VYOS/4x4" #69: malformed payload in packet Feb 18 01:24:27 OPENSWAN pluto[8010]: "VYOS/5x4" #68: next payload type of ISAKMP Hash Payload has an unknown value: 63 Feb 18 01:24:27 OPENSWAN pluto[8010]: "VYOS/5x4" #68: malformed payload in packet And on our VyOS server we got the following errors: Feb 18 01:17:19 VYOS pluto[20807]: "peer-<OPENSWAN IP>-tunnel-20" #381: sending encrypted notification INVALID_ID_INFORMATION to <OPENSWAN IP>:500 Feb 18 01:17:19 VYOS pluto[20807]: "peer-<OPENSWAN IP>-tunnel-20" #381: cannot respond to IPsec SA request because no connection is known for 10.1.1.0/24===<VYOS IP>[<VYOS IP>]...<OPENSWAN IP>[<OPENSWAN IP>]=== 10.2.3.0/24 Feb 18 01:17:19 VYOS pluto[20807]: "peer-<OPENSWAN IP>-tunnel-20" #381: sending encrypted notification INVALID_ID_INFORMATION to <OPENSWAN IP>:500 Feb 18 01:17:23 VYOS pluto[20807]: "peer-<OPENSWAN IP>-tunnel-11" #422: cannot install eroute -- it is in use for "peer-<OPENSWAN IP>-tunnel-3" #403 Feb 18 01:17:23 VYOS pluto[20807]: "peer-<OPENSWAN IP>-tunnel-16" #421: cannot install eroute -- it is in use for "peer-<OPENSWAN IP>-tunnel-4" #395 Feb 18 01:17:23 VYOS pluto[20807]: "peer-<OPENSWAN IP>-tunnel-20" #420: cannot install eroute -- it is in use for "peer-<OPENSWAN IP>-tunnel-5" #417 Feb 18 01:17:23 VYOS pluto[20807]: "peer-<OPENSWAN IP>-tunnel-20" #381: Informational Exchange message must be encrypted Feb 18 01:17:24 VYOS pluto[20807]: "peer-<OPENSWAN IP>-tunnel-20" #381: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x14702d90 (perhaps this is a duplicated packet) Feb 18 01:17:24 VYOS pluto[20807]: "peer-<OPENSWAN IP>-tunnel-20" #381: sending encrypted notification INVALID_MESSAGE_ID to <OPENSWAN IP>:500 Does anyone have any idea what I might be doing wrong? I've tried doing only 5 tunnels, however then some subnets couldn't reach certain subnets (as I said in the VyOS forum thread), and now I've tried each subnet to each subnet. I can't find much (any) information on it, but does Openswan support VTI interfaces? Would that solve my problem? Thanks in advance.

3 2

Nearly Instant Karma
by Chris Olson 17 Feb '16

17 Feb '16

Our smallest network has just three systems permanently attached to a 100/1000 router. There is one additional port available to temporarily plug in a laptop. The largest systems are both Dells, one running Windows 7 and one running CentOS 6.7. The Windows 7 system supports three flavors of Linux as virtual machines. The CentOS system is often used for data file import from USB-attached devices such as cell phones, charging batteries in the USB-attached devices, and for access to external email accounts. The CentOS system was in power save mode when I plugged in a Samsung cell phone for charging and extraction of several photo files. I then moved to the Windows 7 system to do some "paper work" on a web site that is known to require the use of IE for browser access. While on the Windows 7 system I did a quick email check and responded to one of our contacts at a remote site. He was having "difficulty" with file from an external site downloaded on his Windows 7 system. I took the opportunity in my email reply to comment on the great safety and stability of Linux systems. After about two hours I returned to the CentOS 6.7 system to check on the charging status and move the photo files. Yellow lights were showing on both computer and monitor. The system display, and the optical mouse would not return to normal operation as they usually do with a quick push on the front power button. The power button light did turn green and I was able to log in via ssh from a Cygwin shell on the Windows 7 system. It took two reboots executed remotely to bring back full display and mouse functionality. I believe that this was the first time anyone has plugged in a USB device into the CentOS 6.7 system while it is in power save mode.We now have a warning tag hanging over the USB ports on the system. Is there some characteristic of CentOS systems that we should have known about that could have caused this problem? Does Yahoo web mail have an easy way to retract my gloating email?

1 0

Alternative IP addresses
by Timothy Murphy 17 Feb '16

17 Feb '16

My CentOS-7 home server has a static IP address. Is there a simple way of organizing the hpptd server so that it is accessible through this address at a remote host, but is accessed at its 192.168 address by a laptop on the WiFi LAN? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

5 8

heads up: /boot space on kernel upgrade
by Devin Reade 16 Feb '16

16 Feb '16

I have a CentOS 6 machine that was initially installed as CentOS 6.4 in May of 2013. It's /boot filesystem is 200M which, IIRC, was the default /boot size at the time. The most recent kernel update (2.6.32-573.18.1.el6) fails because of lack of space in /boot. The workaround is edit /etc/yum.conf, reduce installonly_limit from 5 to something lower (I used 3), remove the oldest kernel via 'rpm -e', and then re-apply the update. In this case, it was necessary to use the 'yum update' command line vs the Update Applet due to an incomplete transaction from the failed update. Devin

14 20

nfs v3 issues on Centos 7
by Edsall, William (WJ) 16 Feb '16

16 Feb '16

Hello list, So I'm having a strange issue with Centos 7 mounting NFS V3. It starts with autofs. For example, my auto.share file: apps -nfsvers=3 some-server:/mnt/xfs1/& This will mount, but the first mount takes ~30 sec. After this, eventually the mount becomes stale but it still shows as connected in 'mount'. At this point, I can no longer mount NFS shares. Manual mounting example shown below. Any feedback would be appreciated - thank you! /etc/centos-release :::::::::::::: CentOS Linux release 7.1.1503 (Core) mount -t nfs -o vers=3 mdstor:/mnt/xfs1/apps tmpx -v mount.nfs: timeout set for Tue Feb 16 08:33:31 2016 mount.nfs: trying text-based options 'vers=3,addr=143.219.41.19' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 143.219.41.19 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 143.219.41.19 prog 100005 vers 3 prot UDP port 892 mount.nfs: mount(2): Input/output error mount.nfs: mount system call failed Thanks, William

2 2

Update on Kernel panic executing gkrellm.
by Lamar Owen 16 Feb '16

16 Feb '16

For what it's worth, back in April of last year I reported that gkrellm had started generating kernel panics with 7.1503's kernel. I can now report that with the latest 7.1511 kernels (327.4.5 being the latest I have installed) gkrellm is once again behaving for me. Just wanted to close the loop and say that whatever had broken has been fixed, for my hardware.

1 0

How to install packages from git.centos.org
by Tim 16 Feb '16

16 Feb '16

Hi all, how can I install rpms from git.centos.org? I'd like to install and test the realtime-kernel. It seems to me that https://wiki.centos.org/Sources only means to build srpms. What I ned is an rt-kernel with headers for further compiling. Purpose: I'd like to build a digital audio workstation and for this I'd like to try out CentOS with the following packages first: - kernel-rt - ardour - calf-plugins BTW: Is there an audio SIG? Thanks in advance Tim

2 4

USB Serial ports (ttyACMn) CentOS 6.7 (64-bit) vs. CentOS 6.7 (64-bit)
by Robert Heller 16 Feb '16

16 Feb '16

I have two computers: both running CentOS 6.7, 64-bit, with kernel 2.6.32-573.12.1.el6.x86_64. One is a laptop with an 2 core Intel processor and the other is a desktop machine with a 4 core AMD processor. Both with selinux enabled. I have a USB serial port device (a RR-CirKits LCC-Buffer USB). On the desktop I am getting this error: sauron.deepsoft.com% sudo minicom Device /dev/ttyACM0 access failed: No such file or directory. sauron.deepsoft.com% dir -lZ /dev/ttyACM0 crw-rw----. root dialout system_u:object_r:tty_device_t:s0 /dev/ttyACM0 But it is working on the laptop! gollum.deepsoft.com% dir -lZ /dev/ttyACM1 crw-rw----. root dialout system_u:object_r:tty_device_t:s0 /dev/ttyACM1 Same kernel, same device (except it is showing up as ttyACM1 on the laptop). What is going on here? -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

5 8

rpm containing gmessage???
by ken 16 Feb '16

16 Feb '16

Maybe I haven't run the correct yum commands or looked in the right repo, but I haven't found a utility called 'gmessage'. Anyone know where to find it?

2 8

Re: [CentOS] USB Serial ports (ttyACMn) CentOS 6.7 (64-bit) vs. CentOS 6.7 (64-bit)
by Robert Heller 15 Feb '16

15 Feb '16

At Sun, 14 Feb 2016 19:20:48 -0500 Robert Heller <heller(a)deepsoft.com> wrote: > > At Mon, 15 Feb 2016 09:41:32 +1100 CentOS mailing list <centos(a)centos.org> wrote: > > > > > On 14/02/16 02:14, Robert Heller wrote: > > > I sent this out about a week or so ago, but I have heard nothing. I am > > > *thinking* it is a SELINUX problem, but I cannot figure out what. > > > > > > > If you suspect SELinux is to blame, have you tried putting SELinux into > > permissive mode to see that resolves the issues? > > > > setenforce 0 (re-enable with setenforce 1) > > I guess I can try that. > > > > > If everything works with SELinux in permissive mode, then you'll need to > > create a policy for it *[0]*. > > That would imply that somehow the policies on my laptop are *different* than > the policies on my desktop. *I* don't remember setting any such policies... OK, I just tested it: sauron.deepsoft.com% sudo /usr/sbin/setenforce permissive sauron.deepsoft.com% sudo minicom Device /dev/ttyACM0 access failed: No such file or directory. sauron.deepsoft.com% sudo /usr/sbin/setenforce enforcing Nope, that did not help. > > > > > > > ak. > > > > *[0]*: > > https://wiki.centos.org/HowTos/SELinux#head-faa96b3fdd922004cdb988c1989e561… > > > > > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > https://lists.centos.org/mailman/listinfo/centos > > > > > -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

2 1

safest way to mount iscsi loopback..
by lejeczek 15 Feb '16

15 Feb '16

.. what is? fellow centosians. how to you mount your loopback targets? I'm trying lvm backstore, I was hoping I would do it with uuid, but it's exposed more than once and how would kernel decide which device to use I don't know. thanks

3 4

abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected
by Michael H 15 Feb '16

15 Feb '16

Hi All, I've been tuning a server recently and just today this has started to appear in my top/htop output. [root@db1 ~]# ps -aux | grep kernel root 1011 0.0 0.0 212048 4532 ? Ss 13:34 0:00 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD I had made a few changes to sysctl.conf which I have now reverted and the error still exists. my sysctl.conf contained; vm.swappiness=0 vm.overcommit_memory=2 vm.overcommit_ratio=90 - this was only added this morning because of an 'out of memory' error in postgresql. kernel.shmmax=35433480192 kernel.shmall=2214592512 which I have now removed. Can anyone shine any light on this? A little search on Google mentions faulty memory, I will install memtest today and see what the output is like. Thanks Michael

2 1

A repo with latest httpd for http2?
by SternData 13 Feb '16

13 Feb '16

Is there a well-run package repo that has httpd-2.4.17 or mod_http2 (or mod_h2)? I'd like to try out http2 without having to compile my own httpd. -- -- Steve

7 7

ananconda update.img creation fails: generated but with wrong python version in /usr/sbin/anaconda contained
by David Copperfield 11 Feb '16

11 Feb '16

Hi all, I've created an anaconda update.img file per instructions at https://fedoraproject.org/wiki/Anaconda/Updates for Centos 7.2. The problem is that the update.img file contains references to python3 (say, file /usr/sbin/anaconda), and so the all installation fails immediately. My question is: what are the steps to create an anaconda update image appropriate for a particular centos release? Thanks a lot. The steps I have performed (to create an update.img) are listed below: 1) find the version of ananconda that centos 7.2 installation media: 21.48.22.56-1. 2) follow the instructions at the above wiki page, and wiki https://fedoraproject.org/wiki/Anaconda. Run the following command (to generate update.img): 2.1 yum -y install git 2.2 git clone https://fedoraproject.org/wiki/Anaconda 2.3 cd anaconda 2.4 scripts/makeupdates -t anaconda-21.48.22.56-1 3) save the generated image to place under .../images directory. >From what I see, all PXE clients did download the new update.img file and merge the changes contained. But because the updated anaconda pointed to python3 instead of python 2.7.5 (the version comes with installation media), the installation process failed immediately. Thanks. Best,David

1 0

OpenSwan Drop Out Issue
by John Cenile 11 Feb '16

11 Feb '16

Hello, I'm cross posting this from the OpenSwan mailing list, in case someone here can help. We have two sites connected via OpenSwan 2.6.32-9 on CentOS 5, sharing 6 /24 subnets each (so 12 in total). The problem we're having is completely randomly, be it in the middle of the day, or in the middle of the night (so I don't believe it's traffic related), certain (and sometimes all) routes will drop. They usually recover after a few minutes, but it's still long enough for our monitoring to detect downtime. The configuration we have on each device is: conn site-a keyingtries=0 keylife=1h ikelifetime=8h left=1.1.1.1 right=2.2.2.2 leftsubnets={x.x.x.x/24,x.x.x.x/24,x.x.x.x/24,x.x.x.x/24,x.x.x.x/24,x.x.x.x/24} rightsubnets={x.x.x.x/24,x.x.x.x/24,x.x.x.x/24,x.x.x.x/24,x.x.x.x/24,x.x.x.x/24} pfs=yes auto=start authby=secret dpddelay=30 dpdtimeout=120 dpdaction=hold phase2alg=aes256-sha1;modp1536 phase2=esp ike=aes256-sha1;modp1536 It's mirrored exactly the same on the other side. I have tried changing the dead peer detection timeout to something high (5 minutes), and removing it completely (which I believe defaults it to 30 seconds), neither of which made any difference. I can't see any very obvious errors in the logs, however the most recent drop out produced the following message around the same time: Feb 10 00:53:09 site-b-vpn pluto[30584]: "site-a/5x5" #39: max number of retransmissions (2) reached STATE_QUICK_I1 Feb 10 00:53:09 site-b-vpn pluto[30584]: "site-a/5x5" #39: starting keying attempt 2 of an unlimited number Feb 10 00:53:09 site-b-vpn pluto[30584]: "site-a/5x5" #95: initiating Quick Mode PSK+ENCRYPT+TUNNEL+PFS+UP+IKEv2ALLOW+SAREFTRACK to replace #39 {using isakmp#52 msgid:119495de proposal=AES(12)_256-SHA1(2)_160 pfsgroup=OAKLEY_GROUP_MODP1536} and also Feb 10 00:52:25 site-a-vpn pluto[2414]: "site-b/6x6" #1: ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xde58eea3) not found (maybe expired) Feb 10 00:52:25 site-a-vpn pluto[2414]: "site-b/6x6" #1: received and ignored informational message Feb 10 00:52:25 site-a-vpn pluto[2414]: "site-b/6x6" #1: ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0xa5298d7d) not found (maybe expired) Feb 10 00:52:25 site-a-vpn pluto[2414]: "site-b/6x6" #1: received and ignored informational message Before we move to another solution, does anyone have any suggestions on what the problem might be? Running a constant ping between the two hosts doesn't drop *any* packets (even when the IPSec connection itself drops out). Thanks in advance.

3 8

CentOS 7 workstation, mutter CRITICAL...
by m.roth＠5-cent.us 11 Feb '16

11 Feb '16

A fully updated, just built last month, CentOS 7 workstation. The system has 16G of ram, and the real work is done on servers. I'm seeing a ton of complaints in the logs. Feb 10 18:06:00 <workstation> gnome-session: (gnome-shell:3248): mutter-CRITICAL **: meta_window_raise: assertion '!window->override_redirect' failed I found a bug report from last summer, but as I said, all updates are done. Also, is there a bug in the firefox package? Feb 10 17:07:51 <workstation> <user>: IcedTea-Web java error manual log: Feb 10 17:07:51 <workstation> <user>: Application title was not found in manifest. Check with application vendor mark

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss