Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Samba won't start on Centos 7.3.1611
by Alan McKay 09 Oct '17

09 Oct '17

Hi folks, I've been googling for an hour on this which seems to be awfully basic. But I cannot find anything definitive. [root@centos-gig ~]# systemctl enable smb.service Failed to execute operation: Access denied [root@centos-gig ~]# setenforce 0 [root@centos-gig ~]# systemctl enable smb.service Failed to execute operation: No such file or directory Have tried things like : chcon -t samba_share_t /home/amckay Also took the output from: getsebool -a | grep samba and set all them to "on" Stripped my config down to the most basic. What am I missing? # Global parameters [global] netbios name = centos security = USER idmap config * : backend = tdb [homes] comment = Home Directories browseable = No inherit acls = Yes read only = No valid users = %S %D%w%S -- "You should sit in nature for 20 minutes a day. Unless you are busy, then you should sit for an hour" - Zen Proverb

2 3

New CentOS/RHEL group on Facebook
by Nicolas Kovacs 09 Oct '17

09 Oct '17

Hi, There are currently two competing CentOS groups on Facebook. The "main" group is managed by a small group of autocrats with very unilateral communication skills. The other one is not managed at all, judged by the amount of non-CentOS-related stuff published there (Ubuntu tutorials, Windows games, cheap Ray-Ban sunglasses). I was a bit frustrated by this state of things, the more so since I've successfully managed the Slackware Linux Facebook group for a couple of years, regulating publications, keeping folks on topic and banning the odd spammer. So I decided to do the same thing I would do in a software development context. Fork the project and create a different CentOS/RHEL Facebook group. The goal of this group would simply be to provide a no-nonsense discussion platform for all the CentOS and Red Hat Enterprise Linux users out there. Publications would be strictly CentOS/RHEL-centered, but on the other hand, you'd be free to share your CentOS-related blog posts, tutorials and documentation without getting flamed or banned by an admin. Anyway, feel free to join the new group: https://www.facebook.com/groups/2136021589748759/ Cheers from the sunny South of France, Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

5 6

Intel turbo mode
by hw 09 Oct '17

09 Oct '17

Hi, is there a way in Centos to find out if the Intel turbo mode will be used? Using the 'stress' utility and checking the frequency with cpupower tells me that a CPU is running at it´s maximum frequency as reported by cpupower --- and this frequency is less than the frequency it would run at if it used the turbo mode. All the other CPUs are at their minimum frequency. I have verified that turbo mode is enabled in the BIOS. Is cpupower unable to report frequencies used in turbo mode despite it always says it gets its information from the hardware? -- "Didn't work" is an error.

2 4

SCSI block device name/multipath question
by Matthias Leopold 09 Oct '17

09 Oct '17

hi, i have a host with a LSI SAS 3108 RAID controller in JBOD mode with 4 SSD SATA disks. i installed oVirt node (= CentOS 7) on the first two disks configured as SW RAID 1 (in the oVirt node/CentOS installer). when i look at the device names in the running OS i get # lsscsi --scsi_id -g [0:0:0:0] disk ATA SAMSUNG MZ7LM480 204Q /dev/sda - /dev/sg0 [0:0:1:0] disk ATA SAMSUNG MZ7LM480 204Q /dev/sdb - /dev/sg1 [0:0:2:0] disk ATA SAMSUNG MZ7LM480 204Q /dev/sdc SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102216 /dev/sg2 [0:0:3:0] disk ATA SAMSUNG MZ7LM480 204Q /dev/sdd SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102214 /dev/sg3 # ls -l /dev/disk/by-id/*SAMSUNG* lrwxrwxrwx. 1 root root 9 9. Okt 12:07 /dev/disk/by-id/ata-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102212 -> ../../sdb lrwxrwxrwx. 1 root root 10 9. Okt 12:07 /dev/disk/by-id/ata-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102212-part1 -> ../../sdb1 lrwxrwxrwx. 1 root root 10 9. Okt 12:07 /dev/disk/by-id/ata-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102212-part2 -> ../../sdb2 lrwxrwxrwx. 1 root root 9 9. Okt 12:07 /dev/disk/by-id/ata-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102214 -> ../../sdd lrwxrwxrwx. 1 root root 9 9. Okt 12:07 /dev/disk/by-id/ata-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102216 -> ../../sdc lrwxrwxrwx. 1 root root 9 9. Okt 12:07 /dev/disk/by-id/ata-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102222 -> ../../sda lrwxrwxrwx. 1 root root 10 9. Okt 12:07 /dev/disk/by-id/ata-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102222-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 9. Okt 12:07 /dev/disk/by-id/ata-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102222-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 10 9. Okt 12:07 /dev/disk/by-id/dm-name-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102214 -> ../../dm-6 lrwxrwxrwx. 1 root root 10 9. Okt 12:07 /dev/disk/by-id/dm-name-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102216 -> ../../dm-5 lrwxrwxrwx. 1 root root 10 9. Okt 12:07 /dev/disk/by-id/dm-uuid-mpath-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102214 -> ../../dm-6 lrwxrwxrwx. 1 root root 10 9. Okt 12:07 /dev/disk/by-id/dm-uuid-mpath-SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102216 -> ../../dm-5 disks 2:0 + 3:0 are configured as multipath devices (and subsequently set up by device mapper), disks 0:0 + 1:0 are not. SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102216 and SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102214 are listed in /etc/multipath/wwids (and get re-listed after reboot when i manually remove them). why are two of the four local disks configured as multipath devices? As far as i understood documentation this shouldn't happen thx 4 help matthias

1 0

CentOS-announce Digest, Vol 152, Issue 3
by centos-announce-request＠centos.org 07 Oct '17

07 Oct '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:2860 Moderate CentOS 6 postgresql Security Update (Johnny Hughes) 2. CESA-2017:2863 Moderate CentOS 6 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 6 Oct 2017 13:53:23 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2860 Moderate CentOS 6 postgresql Security Update Message-ID: <20171006135323.GA24910(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2860 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:2860 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8ce524d7594d44842dbf2c6a918fba0df6eb4aba61456a1afac2956b49cea425 postgresql-8.4.20-8.el6_9.i686.rpm 8c7e2ce2e6675384b6d956d35b4728a0121b4083e903c0c6a77517a44ba4db27 postgresql-contrib-8.4.20-8.el6_9.i686.rpm c042b88e603be8a8ae99a6e7907e4f4e63f06662050190e244b611b5d1e99606 postgresql-devel-8.4.20-8.el6_9.i686.rpm b844f907373eaca72848348cb2e963b10e4943679e4ade53577ad9ada098e257 postgresql-docs-8.4.20-8.el6_9.i686.rpm a5c1706f6612fe59990fea062966a84e332de1b2d2b7dda7af419bca7c91c2c6 postgresql-libs-8.4.20-8.el6_9.i686.rpm 8d918cdb4dd0897195233e773d22a87678422f579e18c1f2f91b1d15593fcfff postgresql-plperl-8.4.20-8.el6_9.i686.rpm 884286c1308c821035257bdaf49dd2e0500b2257a7e75a0396a39809026b205a postgresql-plpython-8.4.20-8.el6_9.i686.rpm baf83a6c4b6385021d71cb554ed2ac12dd8c6fc81ed58375ca01bd9ff966a901 postgresql-pltcl-8.4.20-8.el6_9.i686.rpm 44247e758c63bbca45ae553ad9638a9683fdcce537a3fae8ee2eaf2bb369e113 postgresql-server-8.4.20-8.el6_9.i686.rpm eb054e4c49dc685efcc79b539864ddadd79e01c9124980d9384d01fc3d02f319 postgresql-test-8.4.20-8.el6_9.i686.rpm x86_64: 8ce524d7594d44842dbf2c6a918fba0df6eb4aba61456a1afac2956b49cea425 postgresql-8.4.20-8.el6_9.i686.rpm e8edd19f1c1933915dca670a83fed033ddb6b5477526403600ace511db54cf34 postgresql-8.4.20-8.el6_9.x86_64.rpm 53c6b606ea888a80acedecd905475d9ce6c5a6c5802f176e93e65c55cfc3fc61 postgresql-contrib-8.4.20-8.el6_9.x86_64.rpm c042b88e603be8a8ae99a6e7907e4f4e63f06662050190e244b611b5d1e99606 postgresql-devel-8.4.20-8.el6_9.i686.rpm df1b83944c4f26d6fda923214143c4a79693ee2bab175e19a548c69c8727e2f2 postgresql-devel-8.4.20-8.el6_9.x86_64.rpm d7e6dd950b9f460a4925e5c5ae0e9ec8e026c069566c4fc49b788c630bcbc3e1 postgresql-docs-8.4.20-8.el6_9.x86_64.rpm a5c1706f6612fe59990fea062966a84e332de1b2d2b7dda7af419bca7c91c2c6 postgresql-libs-8.4.20-8.el6_9.i686.rpm 5328bfa0d6716b342cb63c3399a05bcf98f9b3becab22808173228c6cbc5cc33 postgresql-libs-8.4.20-8.el6_9.x86_64.rpm 37265b681d255e811a18f10492ac561fb53c972a057aaa18072627a4d7d194c7 postgresql-plperl-8.4.20-8.el6_9.x86_64.rpm 0b287aaf1379d4a4a52dc277c3ae00865741bb925ccf263ba5b7bcacceafea62 postgresql-plpython-8.4.20-8.el6_9.x86_64.rpm b6db989f8f62f398245327f23ee4e7e40aee863a0128e38cf75375cdff534624 postgresql-pltcl-8.4.20-8.el6_9.x86_64.rpm 48953d6e0660015f54c206bc03886289ed40ab3753e313309bbc2a82bd562e1c postgresql-server-8.4.20-8.el6_9.x86_64.rpm ef618101d88d7cc74e147788928640fc6b3435bb583ba05ad8007f414d307215 postgresql-test-8.4.20-8.el6_9.x86_64.rpm Source: 3c04d99dc0fdc81ddce150b0fea603ff006c630ed33e8fb726d775df61752a08 postgresql-8.4.20-8.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Fri, 6 Oct 2017 13:56:12 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2863 Moderate CentOS 6 kernel Security Update Message-ID: <20171006135612.GA25393(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2863 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:2863 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f44aa5fe35ee6057f09d3ae976a1ac20b9484680d5ad74ab3188ef786105b4c6 kernel-2.6.32-696.13.2.el6.i686.rpm e504863f5d383083501f9857d958562a4c9be4900c2e1d64b3cac99234b0773f kernel-abi-whitelists-2.6.32-696.13.2.el6.noarch.rpm c29d4c8d691d0e7dea47beeabba025e1e6dbacf03777e01859365c0a363e7ed8 kernel-debug-2.6.32-696.13.2.el6.i686.rpm 22e5ff5d05ef0c4527aaa3fdad61c6ca0bc7e71dbbc2c8574ac904bc5359ed26 kernel-debug-devel-2.6.32-696.13.2.el6.i686.rpm 81d7ac3ef8a4281f36d89db8476b891bbc645ba008976ceed011f33cae441bc5 kernel-devel-2.6.32-696.13.2.el6.i686.rpm 6c2d32bc2e8c9a3fa45fd9ad75487460fe68d379d5d505fb632e750e271912ce kernel-doc-2.6.32-696.13.2.el6.noarch.rpm 14d7950349061ce64a544879e2aefae16dd393f4b39f7485a9a0f904a3af7270 kernel-firmware-2.6.32-696.13.2.el6.noarch.rpm 108b88d25312495470eca583fc0faa2636d1d4d4e6bef1b41f8875cbf9f9dba2 kernel-headers-2.6.32-696.13.2.el6.i686.rpm 24353c78854e3deee2b827a66eb778480b40d9eb30d4bd4f54dbe6339fda3375 perf-2.6.32-696.13.2.el6.i686.rpm 60ef719c1ca0e982ce841d16d39378eb44f40ff4b6313d61cdd51ed2b372596b python-perf-2.6.32-696.13.2.el6.i686.rpm x86_64: a7cc641a5c25aa0c4e941d71a3f2922334d6b983cf159aced75d20a34a360804 kernel-2.6.32-696.13.2.el6.x86_64.rpm e504863f5d383083501f9857d958562a4c9be4900c2e1d64b3cac99234b0773f kernel-abi-whitelists-2.6.32-696.13.2.el6.noarch.rpm 0a261cb6a266e4758c9e758ba16f86bae71a4cb79563905f6959870163195b6d kernel-debug-2.6.32-696.13.2.el6.x86_64.rpm 22e5ff5d05ef0c4527aaa3fdad61c6ca0bc7e71dbbc2c8574ac904bc5359ed26 kernel-debug-devel-2.6.32-696.13.2.el6.i686.rpm 494cf193e2e344e0025e04ee64a5008d45734fc9a1ad522143359d99a9bbd2da kernel-debug-devel-2.6.32-696.13.2.el6.x86_64.rpm 5a4ad9b4a4c839043e6206f81603583aac5cacd9a099e8d0dce9d50c6de6624d kernel-devel-2.6.32-696.13.2.el6.x86_64.rpm 6c2d32bc2e8c9a3fa45fd9ad75487460fe68d379d5d505fb632e750e271912ce kernel-doc-2.6.32-696.13.2.el6.noarch.rpm 14d7950349061ce64a544879e2aefae16dd393f4b39f7485a9a0f904a3af7270 kernel-firmware-2.6.32-696.13.2.el6.noarch.rpm 9fe0d82754b6d94574a47c56dd6b2a06cda59d41fe86dc16ef86e17f7970578e kernel-headers-2.6.32-696.13.2.el6.x86_64.rpm b740603e24f3a7610e4ebc59910cc4fa0a750b90f6600c86edf118a879a00969 perf-2.6.32-696.13.2.el6.x86_64.rpm 6ab0f3a9bd23d658836462a4380865a8b43518a18203bcb071928ea8e9e1f9e7 python-perf-2.6.32-696.13.2.el6.x86_64.rpm Source: 83c3adc56d5967741a73085c049b5cdb876de1dfb4cb4fb8a88d73b5ddad7b4a kernel-2.6.32-696.13.2.el6.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 152, Issue 3 ***********************************************

1 0

SpamAssassin vs. SELinux
by Nicolas Kovacs 06 Oct '17

06 Oct '17

Hi, I just installed SpamAssassin on two servers running CentOS 7 and Postfix. One is my sandbox server for experimenting, the other one is the server that hosts my company's web site, blog, mail, etc. So far, SpamAssassin seems to work as expected. I sent a test mail, which was duly flagges as [SPAM], and I already see the odd incoming spam message correctly flagged as [SPAM]. For testing purposes, I switched SELinux to permissive mode (usually I activate SELinux for everything). It looks like it's causing a bit of a problem here. # sealert -a /var/log/audit/audit.log And here's what I get. --8<------------------------------------------------------ SELinux is preventing /usr/bin/perl from create access on the directory .spamassassin. ***** Plugin catchall (100. confidence) suggests ********* If you believe that perl should be allowed create access on the .spamassassin 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: # ausearch -c '7370616D64206368696C64' --raw | audit2allow -M my-7370616D64206368696C64 # semodule -i my-7370616D64206368696C64.pp ... --8<------------------------------------------------------ Usually sealert's suggestions are to the point and work perfectly. Except in this case it doesn't. Here's what I get: # ausearch -c '7370616D64206368696C64' --raw | audit2allow -M my-7370616D64206368696C64 Nothing to do Any suggestions? Cheers from the sunny South of France, Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

1 1

firefox and D state
by Michael Hennebry 06 Oct '17

06 Oct '17

Previously when firefox went catatonic to the point that I could not even scroll, its CPU usage had gone to 100%+. Now top tells me that firefox, Web Content (with a space) or sometimes kswap... has process state D, uninterruptable sleep. Any suggestions on how to deal? I often have a lot of tabs open, so discovering the right one was hard enough before. Usually, it was something relatively new, so that helped. Not so much anymore. I think a lot of it is just waiting (D) for ads or running them. Closing and reopening sometimes works, but then I have to go find all the video ads and stop them one at a time. -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

3 6

Voice/Fax Modem advice
by david 06 Oct '17

06 Oct '17

Folks A have a PCIe modem (Conexant ChipSet, PCI id = 14f1:2f83. It interfaces to my land-line (POTS) telephone line in the United States. On Windows, I had a good answering machine package (Ventafax) that reported CallerID, recorded messages, sent/received fax, and had a scripting language that let me say "To leave a message for Alice, press 1; to leave a message for Bob, press 2", etc. I'm trying to move this function to a Centos-based system without going to the expense or complexity of Asterisk (expense because of specialized telephony cards). My research found a driver (at www.linuxant.com) but it required that I recompile the driver. I got absolutely lost trying to follow the directions which seemed to be steering me towards a custom Kernel. So, my question to the group wisdom is: - Is there any hope in trying to find a suitable driver for this device without building a custom kernel? And if a custom "module" is needed, I might need help compiling it. - Is there a inexpensive modem that Centos 7 supports with the needed functions? and maybe some software applications that might help? Thanks in advance. David

4 7

Re: [CentOS] CUDA tools?
by James Hogarth 06 Oct '17

06 Oct '17

On 6 Oct 2017 8:34 am, "John Hodrien" <J.H.Hodrien(a)leeds.ac.uk> wrote: On Fri, 6 Oct 2017, Pete Biggs wrote: I suppose the epel kmod-nvidia might count - it will allow CUDA apps to > run but you can't develop with it. > The ELRepo drivers are just the drivers, not the SDK. That said, my experience is they're packaged much better than the ones nVidia releases as part of the CUDA repo. The approach I've gone with is to use ELRepo for the drivers, and then use environment modules to provide the CUDA SDK to users. That for me offers little downsides. You easily get to provide multiple releases of the SDK for users, and you get to use the best packaged drivers. jh _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos Mark why are you so determined to take the most difficult, fragile and high maintenance route? Just use the Negativo Nvidia repo which includes CUDA etc https://negativo17.org/nvidia-driver/

1 0

CUDA tools?
by m.roth＠5-cent.us 06 Oct '17

06 Oct '17

Hi, again. So, kmod-nvidia installed. Trouble is, I have no tool to test it. And my user might need nvcc, which, of course, is only provided by the NVidia CUDA, which won't install, because it conflicts with kmod-nvidia. Has *anyone* dealt with this? If so, what was your solution? mark

4 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss