Discuss

discuss@lists.centos.org

11 participants
34746 discussions

08 Jun '17

Hi, I have a server using its 4 physical network interfaces bonded, with the bonding interface added to a bridge. The bridge has the IP, and three VMs are using the bridge. Two of the VMs are running Debian, one is running Windoze 7. CPU load caused by the qemu-kvm processes is way higher than I´m happy with. One of the Debian machine causes around 22% while it´s basically idle, the other one is around 3%, and the Windoze one is around 50. They are all mostly idle. I can observe that when some network traffic is going on with the Windoze machine, it causes a CPU load of 200%. "Some network traffic" means that virt-top is showing 1M/2M RX/TX. Considering that the bonding interface is theoretically capable of handling 4Gbit full duplex, the 3Mbit are neglectable. Virtio drivers are being used. Currently, virt-top shows 1.9% CPU for the Windoze machine and top shows 22% CPU load for the corresponding qemu-kvm process. There is almost not network traffic. The VM has 4 CPUs assigned. What may cause the high CPU load? Something must be seriously wrong for an idle machine causing 22% CPU load and for the same machine, still basically idle, with a some network traffic to cause 200% CPU load on a Xeon 5690.

2 2

C6 or C7 for an old netbook
by m.roth＠5-cent.us 08 Jun '17

08 Jun '17

I've got an old HP Netbook, which is just fine for taking with when I'm travelling, to check email and news. I have a very old Ubuntu netbook-remix on it, and it really, *really* needs to be updated to something current. I, of course, would prefer CentOS.... The question is: I see that *if* the specs I just looked up (I'm at work, not home, where I could just turn it on, but they sound right) Atom N270 CPU, 2G RAM, 160GB drive - what should I put on it, C6 or C7? Upgrading the memory's not going to happen, so it's got to live with that size. Opinions (please, no flame wars), just what will be most responsive on a machine this small? mark

6 10

bind update flubbed somehow?
by Jason Welsh 07 Jun '17

07 Jun '17

hey folks, we upgraded bind last night to bind-9.8.2-0.62.rc1.el6_9.1.x86_64 and now our server seems to not be able to update. Whenever we add records and update the soa and reload, it still shows the old data.. so for example, we have [root@bind1 /var/named]$grep servername domainname.net.zone [root@bind1 /var/named]$nslookup -port=5353 servername 10.115.76.87 Server: 10.10.76.87 Address: 10.10.76.87#5353 Name: servername.domainname.net Address: 10.66.35.106 but when I grep the file from the zone file, it is not there.. grep servername domainname.net.zone <returns nothing> ive tried restarting the named a few times.. Im not seeing much that looks like its related in the logs.. any ideas? there is no selinux enabled here. Jason

3 3

Crazy thought about upgrading to new major release
by Jerry Geis 07 Jun '17

07 Jun '17

I have older systems out there that work fine, just for what ever reason would be great to upgrade from a C5 -> C7 (due to no longer supported) or C6 > C7 (for updated packages). Sounds like the upgrade tool is not quite an option... I was thinking... What would be wrong with any "easy" script that did the following: 1) Removed all packages with the --justdb option. 2) Import the RPM-GPG-KEY-CentOS-7 3) install the centos-release-7.3.1611 ... rpm 4) yum -y upgrade 5) yum groupinstall "GNOME Desktop" (for example) and reboot of course. Does that have any chance or working and be valid? Thanks, Jerry

5 5

Domain Logout, then domain login again, profile corrupt -> replaced by TEMP profile
by Jobst Schmalenbach 07 Jun '17

07 Jun '17

Hi I have had this problem for a while, but waited to post this until I upgraded to see whether the upgrade would fix it. I upgraded samba to the 4.2.X stream from 3.6.X stream, but it happens on both, 3.6.X and 4.2.10. Whenever someone logs out, then in again the profile gets corrupted and a new TEMP profile is created (the dreadful "creating new desktop"). Now I do not know where this problem is - the desktop or the server. It also happens if you wait 1/2 hour or so, never tried it longer. I can quickly fix this by: - tell the user to log out - rsync -avHAX the profile with yesterdays profile - tell the user to log in again Now if I log out on my workstation, then on the server I do a "smb reload", then log in again this problem does not happen. This morning a person logged out of his workstation, went over to the bigscreen in one of our training rooms and logged in there, then logged out, went over to his machine but got the dreadful "preparing desktop" on login .... Anybody got any idea? thanks Jobst Here is some info: ~~~~~~~~~~~~~~~~~~ All latest patches installed on everything. OS server: CentOS 6.X OS Workstations: Windows 7 Prof Samba: 4.2.10 (was 3.6.23) Other: roaming profiles (as we log into other stations, e.g. training rooms) smb.conf (important bits): [global] workgroup = LALA server string = Domain Server netbios name = LALAMACHINE username map = /etc/samba/smbusers interfaces = eth0, lo bind interfaces only = yes # these flags were recommended. socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=131072 SO_SNDBUF=131072 # Logging, what, how much, etc log level = 1 syslog = 0 log file = /var/log/samba/samba.log max log size = 10000000 # Auditing vfs objects = full_audit full_audit:prefix = %u|%I|%m|%S full_audit:failure = none full_audit:facility = LOCAL4 full_audit:priority = NOTICE full_audit:success = none full_audit:failure = none idmap config *: backend = tdb idmap config *: range = 1000000-1999999 idmap config LALA : default = Yes idmap config LALA : backend = <idmap backend> idmap config LALA : range = 500-999999 winbind use default domain = Yes winbind nested groups = Yes winbind normalize names = no # domain stuff logon script = user.cmd logon path = \\lalamachine\profiles\%u logon drive = Z: logon home = \\lalamachine\%u\samba-homeshare domain logons = Yes os level = 200 domain master = Yes dns proxy = No wins support = Yes security = user encrypt passwords = Yes hosts allow = 192.168.0., 127. guest account = nobody usershare allow guests = No # printer setup load printers = Yes printing = cups printcap name = cups printcap = cups printcap cache time = 750 cups options = raw read raw = yes write raw = yes oplocks = yes max xmit = 65535 dead time = 15 getwd cache = yes # Samba implements the CIFS UNIX unix extensions = no [netlogon] comment = Network Logon Service path = /samba/NetLogon browseable = Yes guest ok = yes admin users = root full_audit:success = none full_audit:failure = none # this is required for log files to be written to read only = No write list = @lalausers, @lalaadmins [profiles] comment = Roaming Profile Share path = /samba/Profiles/ read only = No create mask = 0600 directory mask = 0700 browseable = yes # you MUST disable caching on shares that have roaming profiles stored csc policy = disable guest ok = no valid users = @lalausers, @lalaadmins admin users = root store dos attributes = yes profile acls = yes full_audit:success = none full_audit:failure = none -- Keyboard not found - please clean up desktop! | |0| | Jobst Schmalenbach, jobst(a)barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia

1 1

weird SELinux denial
by Vanhorn, Mike 06 Jun '17

06 Jun '17

I keep seeing this in my audit.logs: type=AVC msg=audit(1496336600.230:6): avc: denied { name_connect } for pid=2411 comm="dbus-daemon" dest=111 scontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:portmap_port_t:s0 tclass=tcp_socket Was caused by: The boolean allow_ypbind was set incorrectly. Description: Allow system to run with NIS Allow access by executing: # setsebool -P allow_ypbind 1 The weirdness is that when I check allow_ypbind, it’s already on: # getsebool allow_ypbind allow_ypbind --> on # Does anyone with more experience with SELinux than me have any idea why this is happening? --- Mike VanHorn Senior Computer Systems Administrator College of Engineering and Computer Science Wright State University 265 Russ Engineering Center 937-775-5157 michael.vanhorn(a)wright.edu

2 6

Disabling user list in Gnome
by Daniel Ruiz Molina 06 Jun '17

06 Jun '17

Hello, how can I disable user list that has been logged, at least, one time into X environment in Gnome running Centos 7? Thanks.

2 1

CentOS-announce Digest, Vol 148, Issue 2
by centos-announce-request＠centos.org 06 Jun '17

06 Jun '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. CEEA-2017:1388 CentOS 7 kmod-redhat-i40evf Enhancement Update (Johnny Hughes) 2. CEEA-2017:1388 CentOS 7 kmod-redhat-i40e Enhancement Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 5 Jun 2017 14:31:40 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:1388 CentOS 7 kmod-redhat-i40evf Enhancement Update Message-ID: <20170605143140.GA48572(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:1388 Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-1388.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b28b4ff3b0afadb7c7b0f42ec738f7b9c71ad53cac2450a2358c0ad4ae5ac848 kmod-redhat-i40evf-1.6.27_k_dup7.3-1.el7_3.x86_64.rpm Source: f1294299b43cdb3096d30db51f3d82974c9ff5b36301280aebc617d02e1017f1 kmod-redhat-i40evf-1.6.27_k_dup7.3-1.el7_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Mon, 5 Jun 2017 14:32:32 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:1388 CentOS 7 kmod-redhat-i40e Enhancement Update Message-ID: <20170605143232.GA48656(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:1388 Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-1388.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: fc4079f76e3fb6e8d1fce4f0320b7d426d31d97abe170e0cd8c271e6b03ffc9b kmod-redhat-i40e-1.6.27_k_dup7.3-1.el7_3.x86_64.rpm Source: 7f4a6d484065c10c89d2f5e23ba6517eddd512174d70bcb560b48234f074f65e kmod-redhat-i40e-1.6.27_k_dup7.3-1.el7_3.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 148, Issue 2 ***********************************************

1 0

more recent perl version?
by hw 06 Jun '17

06 Jun '17

Hi, are there packages replacing the ancient perl version in Centos 7 with a more recent one, like 5.24? At least the state feature is required.

13 34

C7 ansible 2.3 become_method: su not working
by Mark Haney 05 Jun '17

05 Jun '17

I just don't know what else to try. I've beat my head on this for 3 days now and it's becoming obvious that either Ansible 2.3 is a complete disaster, or the CentOS 7 package is a complete cluster. Here's my problem. I am working on getting an ansible server to manage about 100 or so CentOS 6 servers. All have an unprivileged user account setup (up to 3 years before I got here in April) but that user account isn't setup with sudo access. The way to get to root is 'su'. I'm not a newbie with Ansible as I used it extensively in my previous position to manage ~70 or so Ubuntu servers. The Ansible is CentOS 7. I'm working on getting Ansible to play nice with privilege escalation using SU and NAFT has worked. Here's an example (very simple) playbook: Because I'm having to use 'su' I have to either add the user password to the inventory file or use the --ask-become-pass parameter to the command line. Every time I do, I get this: [root@ansible ~]# ansible-playbook playbooks/radtest.yml --ask-become-pass SUDO password: It bombs timing out on privilege escalation. Every single time. I'm absolutely frustrated and am almost ready to throw ansible to the curb for something that doesn't suck so bad. But before I do, I'm asking the list, anyone seen anything like this before? I could post to the ansible list, but it's a google group and God knows when I might get a reply. BTW, setting up root with key-only auth is an option, but would be a real PITA to configure 100+ external servers by hand with the keys and reconfig sshd for it.

2 2

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