Discuss March 2019

discuss@lists.centos.org

85 participants
68 discussions

CentOS 7 Installation Problems
by Eugene Poole 12 Mar '19

12 Mar '19

I attempted to install CentOS 7 x86_64 on my machine that has the following hardware: Motherboard: ASRock X99 Taichi BIOS: AMI v P1.40 08/04/2016 CPU: Intel Core I7-5820K RAM: 64 GB (8 x 8 GB DIMM) Optical: LG Blu Ray 25 G / 50 G burner Storage: 2 - 120GB PNY CS1311 SSD 4 - 4 TB Western Digital hard drives The 2 SSD drives are divided into 3 software RAID-1 devices: /dev/sda1 | /dev/sdb1 = /dev/md0 (2 GB) /dev/md0 /boot /dev/sda2 | /dev/sdb2 = /dev/md1 (77 GB) LVM /dev/VG_opsys /dev/vg_opsys/lv_root / 8 GB /dev/vg_opsys/lv_archive /archive 2 GB /dev/vg_opsys/lv_opt /opt 2 GB /dev/vg_opsys/lv_tmp /tmp 5 GB /dev/vg_opsys/lv_usr /usr 12 GB /dev/vg_opsys/lv_usr_local /usr/local 2 GB /dev/vg_opsys/lv_var /var 8 GB /dev/sda3 | /dev/sdb3 = /dev/md2 (32 GB) LVM /dev/vg_sysswap /dev/vg_sysswap/lv_sysswap swap 16 GB 4 - 4 TB Western Digital hard drives The 4 WD drives are divided into a single software RAID-10 device: /sdc1 | /sdd1 | /sde1 | /sdf1 = /dev/md3 (7.28 TB) LVM /dev/vg_jpd1data /dev/vg_jpd1data/lv_dbmsu00 /dbmsu00 160 GB /dev/vg_jpd1data/lv_websoft /websoft 70 GB ... ETC ... I like this configuration so I thought ... Installation attempt 1: Machine had been running CentOS 6.10 x86_64 with no problems at all. But I wanted to do some things on this machine and I didn't want to have to do a upgrade next year. I backed up all of the data on another machine so I wouldn't suffer a data loss. Inserted the CentOS 7 DVD and rebooted - for whatever reason it didn't see the DVD. Installation attempt 2: Rebooted and selected F11 for the boot menu and selected the SATA device for the Blu Ray (BTW, there was another selection that allowed me to boot UEFI for the Blu Ray). The installation continued and when I got the the storage screen I selected all 6 storage devices. When I got to the point where I tried to select all of the file systems (BTW, the /boot device was listed as unknown) I wanted format the volumes /boot, OpSys, and swap and I wanted to just mount the devices defined on the RAID-10 device. When I tried to accept the definitions the install just hung at the point. I had to power off the machine. Installation attempt 3: I decided to start from scratch so I went into rescue mode and removed all of the partitions on all 6 disks. So when I got the the storage screen I only selected the 2 120GB disks and went through a complete definition for /boot, vg_opsys, and vg_sysswap. But once again when I got to the point where I had to accept what was to be formatted it hung and had to be powered off t restart the install. I thought it might be my DVD so I downloaded a minimal install to try again. Installation attempt 4. I remembered that there are instructions on how to add software raid-1 on a running machine. So I did the allocations on a single 120 GB drive (/dev/sda). When I got to the same point as the first 3 attempts it once again hung. I rebooted on my GParted DVD and removed all the partitions on all 6 drives. Then rebooted using the CentOS 6 DVD and did the complete install including the RAID-10 devices. Why could I install completely CentOS 6 but not CentOS 7? Note: When booting I saw a selection for PF2 so I could setup UEFI. Also PF11 allows me to make a choice to boot from SATA3 standard MBR or UEFI boot. What am I doing wrong? -- Eugene Poole Woodstock, Georgia

2 1

C7 on Dell Precision 7530
by wwp 11 Mar '19

11 Mar '19

Hello, does anybody have experience with installing and running CentOS 7 on Dell Precision 7530 series (w/ Intel gfx chipset if that matters)? It can be bought w/ Ubuntu 16.04 LTS pre-installed (which doesn't attract me at all), but prior to use such hw model at work, I'd like to understand where I'm going to. Especially after my bad experiences installing C7 on "modern" (read since skylake variants) hardware whereas Ubuntu variants went better, gosh. Or maybe I should wait for C8. Of course I did dig the Internet for intel, found very few stuff and this: https://access.redhat.com/ecosystem/hardware/3431551 Regards, -- wwp

2 1

CentOS 8 Artwork needed
by Rich Bowen 08 Mar '19

08 Mar '19

To all the artists and designers here, we need your help. With RHEL 8 beta released, we need to start producing artwork for CentOS 8. It's time for the CentOS Artwork SIG, and anyone else that's interested in contributing to this effort, to start working on everything that will be needed for the new release. What we know we need is anaconda artwork, and new desktop backgrounds to replace the current '7' themed stuff. As we dig, we may find more things that need to be updated to the new 8 theme. Additionally, we will need to update some of the assets listed here: https://wiki.centos.org/ArtWork/Identity ... and produce new assets for 8 to be listed here: https://wiki.centos.org/ArtWork/Brand/Logo And, finally, we need someone to step up to lead this effort. While we don't yet know for certain when RHEL 8 will officially release, it's safe to assume that it's soon, and we need your help. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

5 4

elasticsearch connection refused
by Ralf Prengel 08 Mar '19

08 Mar '19

Hallo, is anyone here using elasticsearch on centos? I tried several configs to configure external access but nothing is working. My tests: telnet localhost or 127.0.0.1 9200 works local on the machine telnet 192.168.242.4 9200 connection refused local on the machine. So it is clear that access from other systems can not work. Is there perhaps something special to consider when using centos 7? Thanks for hints. Ralf

6 10

syslog / logstah problem with timestamp
by Ralf Prengel 08 Mar '19

08 Mar '19

Hallo, I try to send my centos 7 logfiles to an logstsah server. Can anyone give me an hint how to fix this problem? Thanks Ralf > {"index"=>{"_index"=>"%{[@metadata][comline]}-%{[@metadata][version]}", > "_type"=>"doc", "_id"=>"U1XLXGkBpfl5FoHeY4J8", "status"=>400, > "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to > parse field [timestamp] of type [date]", > "caused_by"=>{"type"=>"illegal_argument_exception", > "reason"=>"Invalid format: \"Mar 8 11:13:54\""}}}}} [2019-03-08T11:13:47,125][WARN ][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"%{[@metadata][comline]}-%{[@metadata][version]}", :_type=>"doc", :routing=>nil}, #<LogStash::Event:0x3af3f839>], :response=>{"index"=>{"_index"=>"%{[@metadata][comline]}-%{[@metadata][version]}", "_type"=>"doc", "_id"=>"VFXLXGkBpfl5FoHeY4Ly", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse field [timestamp] of type [date]", "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"Invalid format: \"Mar 8 11:13:54\""}}}}} [2019-03-08T11:13:47,202][WARN ][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"%{[@metadata][comline]}-%{[@metadata][version]}", :_type=>"doc", :routing=>nil}, #<LogStash::Event:0x4fedebdc>], :response=>{"index"=>{"_index"=>"%{[@metadata][comline]}-%{[@metadata][version]}", "_type"=>"doc", "_id"=>"VVXLXGkBpfl5FoHeZII_", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse field [timestamp] of type [date]", "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"Invalid format: \"Mar 8 11:13:54\""}}}}} ^C

2 1

Restarting nfs-server using systemctl resulted in error
by Nurdiyana Ali 08 Mar '19

08 Mar '19

Hi All, I am having strange issues with NFS server on CentOS 7.2. I am unable to restart the nfs-server: [root@hostname ~]# systemctl restart nfs-server ** (pkttyagent:20603): WARNING **: Unable to register authentication agent: Timeout was reached Error registering authentication agent: Timeout was reached (g-io-error-quark, 24) Failed to restart nfs-server.service: Connection timed out Googling doesn't seem to yield answers. How do I restart this service? Sincerely, Nurdiyana Ali.

2 2

C 7 anacron issue
by mark 08 Mar '19

08 Mar '19

Has anyone else seen a problem recently (like, the last few weeks) with anacron? We've got a couple of recently-built systems and we're seeing Mar 4 17:20:01 <system> crond[25767]: (root) PAM ERROR (Failure setting user credentials) Mar 4 17:20:01 <system> crond[25767]: (root) FAILED to authorize user with PAM (Failure setting user credentials) mark

2 3

CentOs 7 i386 & PAE Kernel
by Mike McTernan (wavemobile) 07 Mar '19

07 Mar '19

Hi Gurus, I've been playing with CentOS 7's AltArch i386 builds with some good results on one machine, but can't get it to boot properly on another with a newer Bay Trail CPU. Previously CentOS 6 i386 worked on both, and that set a legacy I'd like to recreate... I *think* the problem is that the 7 kernel is non-PAE, and that has some peculiar knock on effect that prevents some PCI devices being seen, notably the device with the rootfs. CentOS 6 worked on both machines with the PAE kernel. Looking around, I found the following repo: https://mirrors.dotsrc.org/centos-altarch/7/kernel/i386/ This carries 4.14 (long term support) based -PAE kernels (as well as non-PAE) which look to fix my problem. However, I can't find any description of this repo or policy on how it is updated or the intended use. Or why PAE kernels aren't provided as an option in the 'normal' i386 CentOS 7 builds. If anyone could help explain this repo and the view on PAE for the AltArch i386 builds of CentOS 7, I would be really grateful as I can't find the info anywhere else! Kind Regards, Mike -- wavemobile Warning: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender immediately and delete the material from any computer. wavemobile Ltd is registered in England and Wales, Registration Number: 04780898.

3 7

CentOS 7.6 kickstart error
by isdtor 07 Mar '19

07 Mar '19

I am testing a CentOS 7.6 kickstart installation. After kickstart was initiated, the installation stops at some point where a sort of table is printed under "Installation", and the item that fails is 4 - Software selection, Error checking software selection. I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot find any errors here that would prevent installation. Poor error messages, no usable lead for debug.

3 3

Re: [CentOS] Network Bridge - error
by Larry Sevilla 07 Mar '19

07 Mar '19

Hi Andrija, Got the same error message, but different details. systemctl status network.service https://pastebin.com/NjtXUwci journalctl -xe https://pastebin.com/Kn0Dggmm My network settings: https://pastebin.com/JDGJJYVc On Wed, Mar 6, 2019 at 4:57 PM Andrija Panic <andrija.panic(a)shapeblue.com> wrote: > Hi Larry, > > Log says: Bridge support not available: brctl not found > > Fix with: yum install bridge-utils > > Let me know once you are finished with guide - you are perfect for testing > this guide (since new to CentOS completely) > > I will update the guide once you are done with it - let me know please! > > Kind regards, > Andrija > > andrija.panic(a)shapeblue.com > www.shapeblue.com > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > > -----Original Message----- > From: Larry Sevilla <sevilla.larry.oss(a)gmail.com> > Sent: 06 March 2019 09:45 > To: users(a)cloudstack.apache.org; CentOS(a)centos.org > Subject: Network Bridge - error > > Hi, > > I'm new to CentOS. (I have tried Debian, Ubuntu, Devuan & Gentoo). > And also new to CloudStack. > > I'm trying the Quick Installation Guide of CloudStack as pointed by > Andrija Panic of ShapeBlue > https://github.com/apache/cloudstack-documentation/blob/master/source/quick… > > At Configuring the Network topic, I got an error: > > [root@localhost ~]# systemctl restart network Job for network.service > failed because the control process exited with error code. See "systemctl > status network.service" and "journalctl -xe" > for details. > > systemctl status network.service > https://pastebin.com/KzBqJN65 > > journalctl -xe > https://pastebin.com/PLQGuLeR >

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss March 2019