Discuss April 2017

discuss@lists.centos.org

114 participants
89 discussions

PUPPET - group IDS
by Ian Diddams 19 Apr '17

19 Apr '17

hope thus comes under the remit of this mailking list... We use puppet, and Im trying to come up with "code" that will create two user accounts with a shared groiup ID eg user1 with UID 1000user 2 with UID 1001 but I would like them BOTH to share the GID of 2000 I've tried the following accounts::groups: jointgroup: gid: '2000' accounts::users: user1: uid: '1000' gid: '2000' home: '/home/user1' shell: '/bin/bash' password: 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' user2: uid: '1001' gid: '200' home: '/home/user2' shell: '/bin/bash' password: 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' But when I trfy and use this puppet agent -tv complains when trying to create user2 that GID 2000 is slready used . how may I manage this? (Obvs I could have all users with their own GID and add users to a seperate group m... but this is just tidier to my mind? cheersdidds

3 2

centos 7 and nvme
by jsl6uy js16uy 19 Apr '17

19 Apr '17

Hello all, and hope all is well Has anyone installed / on an nvme ssd for Cent 7? Would anyone know if that is supported? I have installed using Arch Linux, but at the time, mid last year, had to patch grub to recognize nvme. Arch is obviously running a much more recent kernel. Not afraid todo some empirical leg work. Just asking if anyone had tried already thanks all for any/all help regards

2 2

OT: systemd Poll
by Anthony K 17 Apr '17

17 Apr '17

According to "Arthur Schopenhauer": "All truth passes through three stages. First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident." I must admit that I skipped through the first and second stages - I never found creating init scripts a joy and instead opted to write my own scripts that I launched via inittab. As such, I welcomed the simplicity systemd's service files without fuss. So, at which stage are you in w/ regards to adopting systemd? Are you still ridiculing it, violently opposed to it, or have you mellowed to it?

37 118

Pulseaudio
by Adrian van Bloois 17 Apr '17

17 Apr '17

Hi, I get this error message: ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused It does not say connection to what, ?????? And is this a matter of permission??? This is C7 latest and greatest. Any ideas??? Adrian -- Adri P. van Bloois "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

2 1

Help w/Error #14 in grub legacy in CentOS 6.8
by ejm 16 Apr '17

16 Apr '17

Hi all, I am getting Error #14 from grub version 0.97 when trying to boot for the first time into a newly installed partition with Scientific Linux 6.7 and need help resolving the error. The setup: MacPro with 2 HDs HD #1: ESP partition has rEFInd installed and running 2nd partition: Mac OSX 10.7.5 (lion) installed HD #2: 1st partition: Centos 6.8 (uses grub version 0.97) filesystem = ext4 2nd partition: Debian 8.7 (uses grub 2.0.2 beta). filesystem = ext4 3rd partition: Scientific Linux 6.7 (uses grub version 0.97). filesystem = ext4 The grub.conf in the CentOS partition has the following entries: title CentOS 6.8 (2.6.32-696.el6.x86_64) root (hd0,0) kernel /boot/vmlimuz-2.6.32-696.el6.x86_64 ro root=UUID=531c3b86-dc7e-4d14-9505-6df970dc8495 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_no_MD SYSFONT=latarcyrheb=sun16 crashkernel=128M KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /boot/initramfs-2.6.32-696.el6.x86_64.img title Debian 8.7 root (hd0,1) chainloader +1 title Scientific Linux 6.7 (Carbon) root(hd0,2) kernel /boot/vmlinuz-2.6.32-573.el6.x86_64 ro root=UUID=af382492-c826-4cf8-b134-9456fe5c100c initrd /boot/initramfs-2.6.32-573.el6.x86_64.img chainloader +1 I can boot fine into the Mac OSX from rEFInd. When I boot from rEFInd into the CentOS partition I get the Grub version 0.97 menu list with the 3 OSs listed above. I can then boot fine into CentOS 6.8 or Debian 8.7 just fine. I just added Scientific Linux 6.7 (SL) from a downloaded ISO image to the 3rd partition. SL installed fine. The installation itself was done using a PC (AMD64) running Windows 7 and the HD connected via USB and a mobile SATA dock. But using the above grub config for SL I get Error #14. If I comment-out the kernel and initrd lines in the SL entry I get Error #13. I confirmed that the kernel and the initramfs files both are in /boot in SL. I also checked the UUID for the 3rd partition with blkid and that is correct too. If I replace the kernel line for SL with the same one in the SL parititon I still get Error #14. The only difference with the full CentOS and SL kernel entries are the UUIDs of the partition and the minor version # (696 vs 573). I haven't seen anything specific to Error #14 in the blog entries I've seen. Everything I've tried results in either Error #14 or 13. I do think the SL partition will boot if given the correct grub conf to start with. Any tips or ideas would be greatly appreciated! Thanks, --Ed

1 0

OT: Controlling Chrome via policy
by C. L. Martinez 15 Apr '17

15 Apr '17

Hi all, I have installed Google Chrome in two CentOS7 workstations. I would like to setup some extensions by default and install automatically. Reading Chrome/Chromium docs, it is possible to accomplish this using master_preferences or via policy. According to Chromium's docs, policy files needs to be installed under /etc/opt/chrome/policies/managed/ (for Chrome) or /etc/chromium/policies/managed/ (for Chromium). I have tried to create a JSON file (custom.json) with my options, but no go. What am I doing wrong? On the other side, according to Chromium's docs, master_preferences needs to be placed under dir where chrome binary is. Tried and no go. Any light on this? Thanks. -- Greetings, C. L. Martinez

1 1

Primary DNS server with BIND on a public machine running CentOS 7
by Nicolas Kovacs 15 Apr '17

15 Apr '17

Hi, I just installed CentOS 7 on a public server. I'd like to setup BIND as a primary DNS server for a few domains. Until now, all my public machines were running Slackware Linux, and setting up BIND on a Slackware machine is relatively easy. In its out of the box configuration, it has a bone-headed caching nameserver role, which is quite easy to expand to a primary nameserver. Here's my documentation. It's in French, but the *nix bits are universal. http://blog.microlinux.fr/bind-slackware/ On my server running CentOS, I notice things are more complicated in the default configuration. The problem here is not so much documentation, but more like the wealth of information on the subject of BIND on CentOS, with often contradicting information. Is there a *reliable* more or less quick & dirty tutorial on how to get BIND up and running as a primary public nameserver, with the default configuration as a starting point? Think "recipe for pasta" and not "degree in food chemistry". :o) Cheers, Niki -- 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

8 17

Possible bug with latest 7.3 installer, md RAID1, and SATADOM.
by David C. Miller 14 Apr '17

14 Apr '17

I'm seeing a problem that I think maybe a bug with the mdraid software on the latest CentOS installer. I have a couple of new supermicro servers and each system has two innodisk 32GB SATADOM's that are experiencing the same issue. I used the latest CentOS-7-x86_64-1611 to install to the two SATADOM's a simple RAID1 for the root. The install goes just fine but when I boot off the new install I see one of two behaviours. It either hangs at boot, or boots fine but I start getting errors when using the system. For example it will give me the following error if I try to run yum update. error: rpmdb: damaged header #6 retrieved -- skipping. It will just hang giving that error over and over. I have to use a different login session to kill it or reboot. It doesn't even log anything to journelctl or /var/log/messages. At first I thought either the hardware was the issue(sata port, controller, SATADOM, etc). However, I do not see any issues if I don't try to raid the disks. Setting either of the SATADOM's up as a single system drive works just fine. It does not matter if I choose xfs or ext4 for the filesystem when I try to RAID them either. Making an md RAID1 out of the two disks with 7.3 installer is the only combination I see this issue with. If I use the previous 7.2 installer(CentOS-7-x86_64-1511) I don't see the problem at all. I can run yum update, reboot, and everything is still ok. I should also point out that I tested the CentOS 7.3 installer creating a md RAID1 system drive using two regular spinning hard drives and that worked just fine. I was wondering if anyone else has seen something similar or can confirm this problem before I submit it as a real bug.. TL/DR. Two different supermicro servers, both using innodisk 32GB SATADOM's and latest CentOS 7.3 installer to create a RAID1 system results in freezes and weird errors. Using the CentOS 7.2 installer works fine. David Miller.

2 2

email subject length issue
by Jerry Geis 13 Apr '17

13 Apr '17

Hello all I seem to be running into a subject length issue on email. Is there any way to increase that ? Thanks, jerry

7 16

bind vs. bind-chroot
by Nicolas Kovacs 13 Apr '17

13 Apr '17

Hi, On my public servers, I usually run BIND for DNS. I see CentOS offers a preconfigured (sort of) bind-chroot package. I wonder what's the effective benefit of this vs. a "normal" BIND setup without chroot. On my Slackware servers, I have a rather Keep-It-Simple approach to all things security, e. g. run no unneed services, open only needed ports etc. but I don't run the extra mile (and haven't been bitten so far). Any suggestions? (No flamefest please.) Niki -- 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

6 11

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss April 2017