Discuss December 2016

discuss@lists.centos.org

115 participants
118 discussions

Server turns off unexpectedly
by Gary Stainburn 12 Dec '16

12 Dec '16

A few weeks back I built a new Centos 7 server from a 4 year old workstation PC, and a brand new HDD. This PC had no prior problems other than it ran Windows 7. Thew new HDD is because I'm planning to also use it as a Bacula storage device. For the moment is purely an AirPrint server, using CUPS and Avahi so is ide 99.9% of the time. My priblem is that twice now it has turned itself off, the last time being at 7:40am today. There is nothing I can find in the logs prior to it going off, just the normal start-up entries when it's turned back on. Can anyone suggest why i may be happening, or how I can diagnose it. The server is in a UPS protected cabinet in locked room

4 7

Plain requirement: desktop search
by Leon Fauster 12 Dec '16

12 Dec '16

Just wondering, what exactly is supported/suggested: I need a comprehensive desktop search functionality. Not only searching for file names but also for content and meta data. The environment is EL6.8 / Gnome2. I have noticed that "beagle" is not part of the distro anymore. Any suggestions for such requirement? Thanks! LF

4 8

OT: a USB barcode scanner?
by m.roth＠5-cent.us 11 Dec '16

11 Dec '16

Hi, folks, I'm about to go googling, but thought I'd ask here if anyone's using a barcode scanner with CentOS, and if so, a) what scanner are you using, and b) what, if any, software are you using to record what it scans? <mutter, mutter, the serial number of every bloody h/d that we're asking them to deGauss...mutter,mutter> mark

3 2

kmod-nvidia problems
by Rob Kampen 11 Dec '16

11 Dec '16

Hi List, I use the kmod-nvidia package on my CentOS workstations. Always this has "just worked". Doing a yum update this morning I now get this: 09:15:28 : ERROR: Package: kmod-nvidia-367.57-2.el7.elrepo.x86_64 (elrepo) Requires: kernel(drm_atomic_helper_plane_reset) = 0xabd4c98d Installed: kernel-3.10.0-327.28.2.el7.x86_64 (@updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Installed: kernel-3.10.0-327.28.3.el7.x86_64 (@updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Installed: kernel-3.10.0-327.36.1.el7.x86_64 (@updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Installed: kernel-3.10.0-327.36.2.el7.x86_64 (@updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Installed: kernel-3.10.0-327.36.3.el7.x86_64 (@updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Available: kernel-3.10.0-327.el7.x86_64 (base) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Available: kernel-3.10.0-327.3.1.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Available: kernel-3.10.0-327.4.4.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Available: kernel-3.10.0-327.4.5.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Available: kernel-3.10.0-327.10.1.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Available: kernel-3.10.0-327.13.1.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Available: kernel-3.10.0-327.18.2.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Available: kernel-3.10.0-327.22.2.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb23805db Available: kernel-debug-3.10.0-327.el7.x86_64 (base) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.3.1.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.4.4.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.4.5.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.10.1.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.13.1.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.18.2.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.22.2.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.28.2.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.28.3.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.36.1.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.36.2.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Available: kernel-debug-3.10.0-327.36.3.el7.x86_64 (updates) kernel(drm_atomic_helper_plane_reset) = 0xb92b713d Anyone else get this? any pointers? TIA Rob

5 5

Has deleted user, why I can still get info of it
by truename 10 Dec '16

10 Dec '16

I del user 'u1': # userdel u1 But: # groups u1 u1 : g1 Is 'u1' delete? Thansk

2 2

trouble installing centos 6.8
by Emma M Birath 09 Dec '16

09 Dec '16

Dear all, I'm having trouble installing Centos 6.8, in a VM using VirtualBox, and hoping that someone on this distribution can help. I'm running VirtualBox Version 5.1.4 r110228 (Qt5.5.1). I downloaded .iso files for Centos 6.8: - CentOS-6.8-x86_64-bin-DVD1.iso - CentOS-6.8-x86_64-bin-DVD2.iso I proceeded to set up a new VM, selecting Linux / RedHat 64 bit. I selected the DVD1 iso file above as "IDE Primary Master" and the DVD2 as "IDE Secondary Master". I then clicked "Start", expecting to be able to install the operating system. Instead of gives me a bunch of output I don't understand, and then it just hangs. I've attached a screen-shot. I tried to re-download the iso files, from a different mirror. Same issue. Any ideas? Thank you Emma

5 7

bash on ubuntu (centos) on windows
by Jerry Geis 08 Dec '16

08 Dec '16

HI All - I was searching for "bash on centos on windows" as opposed to "bash on ubuntu on windows". Will there be or is there a centos on windows version? Thanks, Jerry

5 4

You have not permission to view content of this location
by truename 08 Dec '16

08 Dec '16

OS: CentosOS 7 I have installed samba + openldap + smbldap-tools + pam by: yum --enablerepo=extras install -y epel-release yum install -y smbldap-tools yum install -y samba openldap openldap-clients openldap-servers migrationtools yum install -y nss-pam* I know that smbldap-tools is a dead project, but I'm interested in it and would like research on it. I create users and groups by: sudo smbldap-groupadd -a g1 sudo smbldap-groupadd -a g2 sudo smbldap-useradd -a -P -g 1001 u1 sudo smbldap-useradd -a -P -g 1002 u1 groups u1 u1 : g1 groups u2 u2 : g2 I create shared folder: cd / sudo mkdir data sudo chown u1 /data sudo chgrp g1 /data sudo chmod ugo+rwx /data I edit /etc/samba/smb.conf: [data] comment = data path = /data valid users = u1,u2 write list = u1,u2 create mask = 0777 sync always = Yes ; hide dot files = yes ; writeable = no And then: sudo service smb restart When I open file manager and input following in location box: smb://127.0.0.1 The shared folder data is shown, I click the shared folder and input username u1 and password, I get error message: You have not permission to view content of this location The error message is Chinese in my system, I translate it into English. Thanks

3 4

Re: [CentOS] BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
by KM 08 Dec '16

08 Dec '16

Not sure if this was the last email on this. If not ignore me. However I found a post for new operating systems that says to set the watchdog_thresh value instead of softlockup_thresh. http://askubuntu.com/questions/592412/why-is-there-no-proc-sys-kernel-softl… this is an Ubuntu post, but on my CentOS 7 system this parameter exists, and softlockup_thresh does not. I have set it but I will need to see if I still get the CPU lock up messages on my VM. I hope this helps.KM From: correomm <correomm(a)gmail.com> To: CentOS mailing list <centos(a)centos.org> Sent: Thursday, August 18, 2016 1:50 PM Subject: Re: [CentOS] BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0] Yes, I tried it, but does not exists: vmguest # cat /proc/sys/kernel/softlockup_thresh cat: /proc/sys/kernel/softlockup_thresh: No such file or directory On Thu, Aug 18, 2016 at 2:06 PM, Carlos A. Carnero Delgado < carloscarnero(a)gmail.com> wrote: > 2016-08-18 12:39 GMT-04:00 correomm <correomm(a)gmail.com>: > > > This bug is reported only on the VM's with CentOS 7 running on on VMware > > ESXi 5.1. > > The vSphere performance graph shows high CPU consume and disk activity > only > > on VM's with CentOS 7. Sometimes I can not connect remotely with ssh > > (timeout error). > > > > I'm also seeing those errors in several servers, running under 5.5. > Currently investigating if this > <https://kb.vmware.com/selfservice/microsites/search. > do?language=en_US&cmd=displayKC&externalId=1009996> > has anything to do (the resource overcommit bit). > > HTH, > Carlos. > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

Unusual System State
by Chris Olson 07 Dec '16

07 Dec '16

Our smallest network of systems has only four computers connected via Gigabit Ethernet. The oldest and most stable platform is an eight year old Dell E520 running CentOS 6.8. We often try out applications on this Dell/CentOS machine before moving them to other systems on our other networks. Last night, one of our users decided to create a single, 228GB home directory tar archive on an empty, 500GB, external, USB, Ext4 disk drive. This was obviously a poor decision. The extent of the results were not obvious until this morning. All disk activity had stopped and the system appeared to be hibernation. A push on the power button usually brings the system back to life, but in this case, the unlock screen was presented for only three seconds and then the hibernation mode was resumed. Repeated attempts to log on were all thwarted due to this behavior. ssh from other systems wasalso not possible. Holding the power button in order to initiate power down did not work either. The result was the same as a one second press of front panel power button bringing up the unlock screen for only a short time. We eventually removed the power cord for five minutes and then restarted the machine. The system is running normally once again. The corrupted file system on the USB disk has been restored by re-partitioning and building a new Ext4 file system on it. The user no longer gets to use external disks. Examination of log files and the dmesg output did not yield any useful information regarding the unusual state of the system when unlock logon was not possible. Is there somewhere else we should look for evidence of what actually happened and the unusual state of the system. Thanks. [user@computer ~]$ uname -a Linux computer 2.6.32-642.11.1.el6.x86_64 #1 SMP Fri Nov 18 19:25:05 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux [user@computer ~]$

3 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss December 2016