Discuss

discuss@lists.centos.org

34753 discussions

Xen-4.4 branch End of Life
by Johnny Hughes 01 Mar '17

01 Mar '17

The CentOS VIrtualization Special Interest Group wants to remind everyone that the End of Life for the Xen-4.4 branch (currently 4.4.4-19) will be March 31st, 2017. This is because the Xen Project will no longer support Xen-4.4 after that date, based on this link: https://wiki.xenproject.org/wiki/Xen_Project_Release_Features Xen-4.6 is still available and will be maintained until October 2018 (on both CentOS-6 and CentOS-7) and Xen-4.8 will be available soon. Thanks, Johnny Hughes

1 0

Nvidia related kernel panic on boot, *unless* the keyboard is tapped
by Duncan Brown 01 Mar '17

01 Mar '17

So here is an odd one Ever since the upgrade to 7.3, when using the el-repo kmod-nvidia, boot hangs around the 'mounted /boot' point. If left it then kernel panics However at that point, tapping the keyboard gets it going again. As I'm using a wireless keyboard, even the act of switching the keyboard on gets it going again This doesn't happen without the kmod, and I'm in the process of capturing the panic to file the bug report with el-repo, but for the sake of conversation has anyone seen anything like this before, or have any idea why that could happen? cheers Dunc

1 0

Systemd debug logging turned on in CentOS 7
by Thomas Eriksson 28 Feb '17

28 Feb '17

Hi, I noticed that some, but not all, of my CentOS 7 machines have these kernel parameters for turning on systemd debug level logging added to the grub.cfg file. systemd.log_level=debug systemd.log_target=kmsg The parameters are *not* in the /etc/default/grub file, so if I rebuild grub.cfg with grub2-mkconfig, they disappear. I am a bit puzzled over how they got introduced. Has anyone else seen this? thanks, Thomas

5 8

sshd Match Group directive problem
by Bernard Fay 28 Feb '17

28 Feb '17

I try to set up two "Match Group" directives in sshd_config. I have an LDAP server. All users including admins are part of the LDAP group users. The admins users are also part of the LDAP group wheel. For example: [~]groups admin1 admin1 : users wheel [~]groups users user1 : users On a client server to LDAP, I try to configure two "Match Group" directives in sshd_config as follows: Match Group wheel some keywords... Match Group users some keywords... The problem is that even if a user is a member of LDAP group wheel, the "Match Group wheel" directive is skipped in favor of the "Match Group users" directive. Is it possible to have two "Match Group" directives as I like to do it? If yes, what is wrong in my configuration? Thanks,

2 2

Checksums for git repo content?
by Leonard den Ottolander 27 Feb '17

27 Feb '17

Hi all, Since the vault for 7.3.1611 has been cleared out last sunday (20170207) - why is that? - I'm using git to download a "SRPM", or more accurately, its contents. However, using git has one major drawback: It is missing checksums for the files. Are there any plans to provide checksums for the files in git so I can be sure that what I download is actually not tampered with? SRPMS are signed so we can be sure there content is what you provided. Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research

8 20

kernel update/reboot best practice question
by Valeri Galtsev 27 Feb '17

27 Feb '17

Dear All, Quite some time ago I have noticed that kernel updated quite often "come in pairs". That is, if there was no kernel update for quite some time, and, say, today kernel update for some system level (say, CentOS 6) was released, then it is quite likely that there will be yet one more kernel update for the same system level 3-5 days later. As if the kernel is first patched quick and dirty, then more careful and comprehensive work is done. Not that I would disagree with this practice, to the contrary, from some prospective it makes a lot of sense to me. I wonder what best practices everybody follows: do you tolerate two reboots separated by few days, or you wait till final kernel update comes, and reboot only once then? Thanks a lot for your insights! Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

2 2

All Samba shares suddenly becoming read only
by Gary Stainburn 27 Feb '17

27 Feb '17

I have a Centos 7 server – ZEPPO - which I use for file sharing. The clients are all Win7 PC's and I use Samba to serve the files. It has been working fine ever since I put it live late last year. Now, all of a sudden, all files are read-only. I recently added a USB WiFi dongle to give the server a presence on the WiFi VLAN. Using this I am able to provide an Air Print service for our mobile devices. For some reason this made the server unavailable to some clients, including a Fedora box (GROUCHO) that does host health checks using ping. What I found was that if the WiFi was up on Zeppo (10.6.103.1/24) then Groucho (10.6.1.1/24) could not ping Zeppo's LAN address 10.6.1.101/24. Groucho only has the LAN and has no WiFi. However, Zeppo could still ping groucho. If the WiFi was down on Zeppo then Groucho could ping Zeppo. Also, the clients could access the file shares. Although I didn't get to the bottom of it, I did make it go away by * removing an obsolete alias on the LAN interface 10.6.1.3/24 * changed the WiFi from DHCP to manual, although still with the same settings. Once I'd done this, I was happy until the users started telling me that they could only open documents as read-only. On testing this I found that all of the Samba shares are now read only. I can't even create a new empty file in an existing folder. I have not changed any file permissions on the server, nor have I changed and Samba config. I've had a look in /var/log/samba and can't see anything. The log.smbd and log.nmbd don't show anyting relating to this. The log.10.6.5.2 file is empty I've tried disabling selinux as a test but that made no difference. The samba user = the linux user and if I ssh in as that user I can create files and folders. Can anyone suggest what I need to do next to stop these shares being read only. Ta -- https://fundraise.cancerresearchuk.org/page/garys-march-march

1 0

CentOS-announce Digest, Vol 144, Issue 9
by centos-announce-request＠centos.org 26 Feb '17

26 Feb '17

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-2017:0323 Important CentOS 5 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Sat, 25 Feb 2017 15:02:03 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0323 Important CentOS 5 kernel Security Update Message-ID: <20170225150203.GA30594(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0323 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0323.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 019a5946e25b89c2d0ee356e588f0fa0899a8e0742d7fb54ff075c8ba2085d41 kernel-2.6.18-419.el5.i686.rpm 04999d388f09b47faad898788ddb48706ae83e941ba8d4f8b3d0922b0d757937 kernel-debug-2.6.18-419.el5.i686.rpm bce1ad740f84730eac3e6ad8153c4748e45485fea938ddcb512c8fab5200bec6 kernel-debug-devel-2.6.18-419.el5.i686.rpm 2029c432d99fb27611918b74a087d4280b13d5b08a80211b30fb7d61ee6b427f kernel-devel-2.6.18-419.el5.i686.rpm 44c69f8dc8622d48b018ca658b6ffebb2ab9a4bde2e2ab996bf55c8395c32bb4 kernel-doc-2.6.18-419.el5.noarch.rpm f50709be8b7678576e31dd4f0be48a56373ea9dff41de1518f1f1a72344487a4 kernel-headers-2.6.18-419.el5.i386.rpm a95b656d0a233a9c65b503524ae9153052ca16f1932140e7d8bd0a5a9d020969 kernel-PAE-2.6.18-419.el5.i686.rpm 913b066902e9a694cd8dacfed10cccad3828ea117705df72b31c44e0174f534e kernel-PAE-devel-2.6.18-419.el5.i686.rpm 1df361995538b14778060829f9bdc2506b91fe56135570e53f0b6c8d348998ab kernel-xen-2.6.18-419.el5.i686.rpm 626c4071b7811031ed605c17e54fd1185765d38d2912bf377a23d3486836e729 kernel-xen-devel-2.6.18-419.el5.i686.rpm x86_64: 6c4558babe0b37022c1999231ad64116767001ef414bd8b65d66918a56dcaed1 kernel-2.6.18-419.el5.x86_64.rpm e7dec9fb687ef00bb29351361e7e5365b324046a9223f8fe363a809f6344c597 kernel-debug-2.6.18-419.el5.x86_64.rpm 687f5550c5a35526c37f213f303b635078e9cdfa13534a84f7be88d2d37b5954 kernel-debug-devel-2.6.18-419.el5.x86_64.rpm dd57d4ca8c328a0701a4bdf2c571ba16d28cfadfda4d7329a1d89b74d2a45f1b kernel-devel-2.6.18-419.el5.x86_64.rpm 44c69f8dc8622d48b018ca658b6ffebb2ab9a4bde2e2ab996bf55c8395c32bb4 kernel-doc-2.6.18-419.el5.noarch.rpm ab01f7fe8a199ec0debbbe8ee672eb3d9ad7191305b75d5b4afdff957b15f569 kernel-headers-2.6.18-419.el5.x86_64.rpm f846028137b73dc155e20b78ad9726ed54936ca4953743cad43d35907229962a kernel-xen-2.6.18-419.el5.x86_64.rpm 1f37799de9f2a3910ce1ca37be50b325943e9842051a633e6ba1d041ac784dd9 kernel-xen-devel-2.6.18-419.el5.x86_64.rpm Source: c37156be43391a11612a558e2b9732fdf37da0002d0eeb0d4aecd57bcd497cce kernel-2.6.18-419.el5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 144, Issue 9 ***********************************************

1 0

RHEL 8 speculation ???
by Alice Wonder 25 Feb '17

25 Feb '17

Is there any blog that has information on a potential RHEL 8 release date? boost in 7 is now too old for some things, in addition to gcc. There are solutions in 7 to those issues but it's starting to feel like 6 felt shortly before 7 came out, so I wonder if it is getting near to time. I'm working on a major project bitcoin related and it would be frustrating to deploy a bunch of CentOS 7 virtual machines only to have 8 come out fairly soon afterwards.

5 5

Problem loading the VM after reboots.
by Subscriber 25 Feb '17

25 Feb '17

I had a strange problem. After restarting the VM can not always run. The last line in the console (virsh console): init: Re-executing /sbin/init Please stand by while rebooting the system... Restarting system. machine restart At this time, one of the CPU core is loaded 100% (qemu-kvm process, top command) %Cpu7 : 41.8 us, 57.6 sy, 0.0 ni, 0.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st # free total used free shared buff/cache available Mem: 8009692 377744 1164076 9392 6467872 7299800 Swap: 2097148 0 2097148 This behavior only when the virtual machine CentOS 6.8 and HV CentOS 7.3.1116. Unsuccessful restart may occur after 2 successful, and maybe after 5 successful, and maybe on the first reboot. No clear pattern of a problem I have not seen. Tested different VM. Here's how behaved virtual machine if its reboot through virsh reboot: virsh # reboot test1 Domain test1 is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # destroy test1 Domain test1 destroyed virsh # start test1 Domain test1 started virsh # reboot test1 Domain test1 is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # destroy test1 Domain test1 destroyed virsh # start test1 Domain test1 started virsh # reboot test1 Domain test1 is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # reboot test1 Domain test1 is being rebooted virsh # destroy test1 Domain test1 destroyed If the VM shutdown and then start, the problem does not occur. The problem does not occur if the VM CentOS 7.3.1611 (10 successful reboots of 10) or if the VM Windows Server 2008 R2 (10 successful reboots of 10). If the VM CentOS 6.8 and HV CentOS 6.8 the problem does not occur. First HV is: CentOS 7.3.1611 with 3.10.0-514.6.2.el7.x86_64 and 3.10.0-514.6.1.el7.x86_64 qemu-kvm-ev.x86_64 10:2.6.0-28.el7_3.3.1 libvirt.x86_64 2.0.0-10.el7_3.4 Kernel module: kvm_intel 170181 kvm 554609 Second HV is: CentOS 7.3.1611 with 3.10.0-514.6.2.el7.x86_64 qemu-kvm.x86_64 10:1.5.3-126.el7_3.3 libvirt.x86_64 2.0.0-10.el7_3.4 Kernel module: kvm_intel 170181 kvm 554609

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss