Discuss September 2017

discuss@lists.centos.org

128 participants
124 discussions

bind named fails after logrotate
by Götz Reinicke 12 Sep '17

12 Sep '17

Hi, on our centos 7.3.1611 server the named dies after the log rotates script is executed. systemctl status named ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Di 2017-09-12 14:27:57 CEST; 2s ago Process: 20714 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=1/FAILURE) Process: 20684 ExecReload=/bin/sh -c /usr/sbin/rndc reload > /dev/null 2>&1 || /bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 14496 (code=killed, signal=ABRT) Any suggestions or hints or is that a known problem? logrotate-3.8.6 bind-9.9.4 Thanks and regards . Götz

1 0

Missing CentOS 7 Updates
by Ken Gramm 12 Sep '17

12 Sep '17

I must be missing something, because I can't believe that there haven't been any updates since July 27 9fa12aadcd2ea45fdcb91bd125b619545993defa2032cf99b8a89cf6099723e8-primary.xml.gz 27-Jul-2017 15:12 4.0M [ ] 23b0e14a9667597b69a8719f0eea709721cc32f9f3b6c8202da0f5a36b9f1759-other.xml.gz 27-Jul-2017 15:12 137M [ ] 33fdce604445f67a26ce5ddc354ea0c835ed119ac8cb7404cc2b565bf80722a1-primary.sqlite.bz2 27-Jul-2017 15:16 7.8M [ ] 732f62a4c48e764e2ebe276eef7e6bf25eaf477452260a03805512a6a7a6ce80-filelists.sqlite.bz2 27-Jul-2017 15:16 4.4M [ ] 36288cdc93433b594aed022edabca28fe92c3497e23da598c59f890c0ddd7255-other.sqlite.bz2 27-Jul-2017 15:16 93M [ ] a6fd2af929647636c10531913d7c0b3a4277732a694d9aff9093dbb7890c4094-prestodelta.xml.gz 27-Jul-2017 15:14 954K [ ] bab46e0e0fd6233a1d50ad0cebcc6bae42c43fb85bf143f6ec415fd3458e882d-filelists.xml.gz 27-Jul-2017 15:12 4.8M [TXT] repomd.xml 27-Jul-2017 15:16 3.4K [TXT] repomd.xml.asc 27-Jul-2017 15:21 811

3 4

Corosync on a home network
by J Martin Rushton 11 Sep '17

11 Sep '17

I've been trying to build a model cluster using three virtual machines on my home server. Each VM boots off its own dedicated partition (CentOS 7.3). One partition is designated to be the common /home partition for the VMs, (on the real machine it will mount as /cluster). I'm intending to run GFS2 on the shared partition, so I need to configure DLM and corosync. That's where I'm getting bogged down. The VMs and the real machine are bridged onto one ethernet. There is another ethernet in the main machine on a different network, but that is not used for clustering. The ethernet port is connected to a switch which in turn connects to a BT Home Hub 6. All four adresses are static, Network Manager is off, ssh works across the nodes without a password and ping gives sensible times. --------------%<------------------- # brctl show bridge name bridge id STP enabled interfaces br3 XXXXXXXXX no enp3s0 vnet0 vnet1 vnet2 virbr0 XXXXXXXXX yes virbr0-nic --------------%<------------------- When I start corosync each node starts up but does not see the others. For instance I see: --------------%<---------------------- # corosync-quorumtool Quorum information ------------------ Date: Sun Sep 10 12:56:56 2017 Quorum provider: corosync_votequorum Nodes: 1 Node ID: 3 Ring ID: 3/28648 Quorate: No Votequorum information ---------------------- Expected votes: 4 Highest expected: 4 Total votes: 1 Quorum: 3 Activity blocked Flags: Membership information ---------------------- Nodeid Votes Name 3 1 192.168.1.52 (local) ----------------%<------------------- All four nodes are similar, but with different node IDs, IP addresses and Ring IDs. The documentation warns that not all routers will handle multicast datagrams correctly. I therefore attempted to force unicast communication by making the following changes from the distributed corosync.conf: transport: updu cluster_name: <set to the same as the domain> # crypto_cipher: none # crypto_hash: none # mcastaddr: 239.255.1.1 # mcastport: 5405 # ttl: 1 The following are unchanged: version: 2 secauth: off ringnumber: 0 bindnetaddr: 192.168.1.0 The nodelist is: ---------%<---------------- nodelist { node { ring0_addr: 192.168.1.2 nodeid: 1 } node { ring0_addr: 192.168.1.51 nodeid: 2 } node { ring0_addr: 192.168.1.52 nodeid: 3 } node { ring0_addr: 192.168.1.53 nodeid: 4 } } --------%<------------------ logging and quorum are as supplied. Any help will be gratefully received. Regards, Martin

4 5

Kernel Updates
by Michael Rapuano 11 Sep '17

11 Sep '17

We are running kernel-3.10.0-514.26.2.el7 and need to update to kernel-3.10.0-693.el7. The new kernel is in the CR repo but not in the base/update repos. When will the updates in the CR repo be in the base/update repos? This is a high priority security issue for us. -- Michael Rapuano michael.rapuano(a)cloudlock.com

3 2

centos-7.4 elfutils
by Jack Bailey 11 Sep '17

11 Sep '17

Hello, I'm taking 7.4 for a spin. I did the minimal install, and ran into trouble with groupinstall base. The trouble seems to stem from elfutils. One command claims elfutils-libs-0.166-2.el7.x86_64 is missing, and another one claims it's installed. Not sure what's going on here. [root@ip-172-31-34-187 ~]# yum -y install elfutils.x86_64 Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.web-ster.com * extras: mirror.chpc.utah.edu * updates: mirrors.cat.pdx.edu Resolving Dependencies --> Running transaction check ---> Package elfutils.x86_64 0:0.166-2.el7 will be installed --> Processing Dependency: elfutils-libs(x86-64) = 0.166-2.el7 for package: elfutils-0.166-2.el7.x86_64 --> Processing Dependency: elfutils-libelf(x86-64) = 0.166-2.el7 for package: elfutils-0.166-2.el7.x86_64 --> Finished Dependency Resolution Error: Package: elfutils-0.166-2.el7.x86_64 (base) Requires: elfutils-libelf(x86-64) = 0.166-2.el7 Installed: elfutils-libelf-0.168-8.el7.x86_64 (@anaconda) elfutils-libelf(x86-64) = 0.168-8.el7 Available: elfutils-libelf-0.166-2.el7.x86_64 (base) elfutils-libelf(x86-64) = 0.166-2.el7 Error: Package: elfutils-0.166-2.el7.x86_64 (base) Requires: elfutils-libs(x86-64) = 0.166-2.el7 Installed: elfutils-libs-0.168-8.el7.x86_64 (@anaconda) elfutils-libs(x86-64) = 0.168-8.el7 Available: elfutils-libs-0.166-2.el7.x86_64 (base) elfutils-libs(x86-64) = 0.166-2.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@ip-172-31-34-187 ~]# yum -y install elfutils-libs.x86_64 Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.web-ster.com * extras: mirror.chpc.utah.edu * updates: mirrors.cat.pdx.edu Package matching elfutils-libs-0.166-2.el7.x86_64 already installed. Checking for update. Nothing to do

3 3

SNMP V3 libraries not found, SNMPV3 disabled.
by Alex Tang 11 Sep '17

11 Sep '17

Dear all, I have installed mrtg via yum on centos 7, and using cron job to load mrtg every 5 mins. Everything work fine but just snmp v3 graph no show up. I try to load the command LAND=C /usr/bin/mrtg /etc/mrtg/metg.cfg it will show an error "SNMP V3 libraries not found, SNMPV3 disabled.". so, i installed all the net-snmp but still showing the error. I can't find any suggestion on google. can anyone have the same problem ? Thanks Alex

1 0

systemctl poweroff
by Nicolas Kovacs 11 Sep '17

11 Sep '17

Hi, I've been using CentOS since versions 4.x, and I see a weird trend in recent Linux distributions. Under CentOS 4.x, 5.x and 6.x, shutting down a server (workstation, laptop) simply meant issuing 'shutdown -h now' (or choosing 'Shutdown' from the GUI menu), and the machine would simply shut down. Whatever crazy process went haywire, shutting down the system meant exactly that. No questions asked. Now with CentOS 7.x, sometimes the machine would simply hang during the shutdown process, or I would get a message like "a stop job is running", and I would end up having to hit the Reset button to stop the system, as I did when I used Microsoft Windows (before 2001). Cheers, 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

2 1

Flush memory on a server?
by Nicolas Kovacs 11 Sep '17

11 Sep '17

Hi, A few days ago I checked the health of my main public server running CentOS 7, a quad-core machine with 16 GB RAM. It had been running non-stop for 65 days, hosting only a handful of services (BIND, NTP, Apache, Postfix, Dovecot) for two domains. I was surprised to see that RAM consumption was relatively high, and apparently, the machine even had to swap at some time. I read up a bit on RAM consumption, and now I wonder if flushing the memory cache regularly is a good idea. https://tecadmin.net/flush-memory-cache-on-linux-server/ Any suggestions? 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 9

CentOS 7 on PPC64le booting from a MD RAID volume
by Tom Leach 08 Sep '17

08 Sep '17

I've been trying to install CentOS 7 AltArch ppc64le onto a new Power 8 system and I want to configure mdraid for the volumes. I can get everything working if I install to a single disk, but when I configure for RAID 1, the system fails to boot. So, is mdraid1 supported for booting a Power 8 system? Tom Leach leach(a)coas.oregonstate.edu

1 0

Re: [CentOS] login case sensitivity
by James B. Byrne 08 Sep '17

08 Sep '17

On Thu, September 7, 2017 14:07, hw wrote: > Gordon Messmer wrote: >> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>> This was always problematic because DNS hostnames and >>> email addresses in the RFC standards were case insensitive >> >> >> Not quite. SMTP is required to treat the "local-part" of the RCPT >> argument as case-sensitive, and to preserve case when relaying mail. >> The destination is allowed to treat addresses according to local >> policy, but in general SMTP is case sensitive with regard to the >> user identifier. > > Last time I checked, RFCs said that local parts *should not* be case > sensitive, and cyrus defaulted to treat them case sensitive, which > is a default that usually needs to be changed because senders of > messages tend to not pay any attention to the case sensitiveness > of recipient addresses at all, which then confuses them like any > other error. > > https://tools.ietf.org/html/rfc5321 Updated by: 7504 DRAFT STANDARD Errata Exist Network Working Group J. Klensin Request for Comments: 5321 October 2008 Obsoletes: 2821 Updates: 1123 Category: Standards Track . . . 2.4. General Syntax Principles and Transaction Model . . . Verbs and argument values (e.g., "TO:" or "to:" in the RCPT command and extension name keywords) are not case sensitive, with the sole exception in this specification of a mailbox local-part (SMTP Extensions may explicitly specify case-sensitive elements). That is, a command verb, an argument value other than a mailbox local-part, and free form text MAY be encoded in upper case, lower case, or any mixture of upper and lower case with no impact on its meaning. __The local-part of a mailbox MUST BE treated as case sensitive.__ Therefore, SMTP implementations MUST take care to preserve the case of mailbox local-parts. In particular, for some hosts, the user "smith" is different from the user "Smith". However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged. Mailbox domains follow normal DNS rules and are hence not case sensitive. . . . Case munging of the local part is handled by the local delivery agent in my experience. The Cyrus LMTP service can be, and often is, configured to force lower case munging (imapd.conf 'lmtp_downcase_rcpt: 1') of the local part. That decision is site specific. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

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 September 2017