Discuss

discuss@lists.centos.org

5 participants
34752 discussions

rsyslog stops logging on service reload?
by John Jasen 18 Aug '17

18 Aug '17

I have multiple servers running stock CentOS 7 rsyslog 7.4.7-16.el7, which are configured to log locally and over TCP to a remote logserver, also running stock CentOS 7 rsyslog. The remote server uses imptcp to receive, and pretty basic rules to parse and commit to disk. I have several systems that log prolifically, but periodically, they stop soon after the remote log server HUPs (daily logrotate). Very soon after they stop logging (completely, even to local files), the services on these systems block, and our monitoring system starts alerting. Restarting rsyslog on the clients proves ineffectual. The situation may clear itself without intervention after 90 minutes to several hours. However, this does not happen on all client systems in a similar situation (CentOS 7, large volume of constant log data); nor does it happen daily. Any ideas as to what's going on? Thanks in advance.

2 2

Power Fail Protection Update II
by Chris Olson 18 Aug '17

18 Aug '17

Many thanks once again to those that responded to my original posting (and my follow up message) with information about Network UPS Tools, other Linux-based tools like rtcwake, and commercial UPS products. We have quite a bit more evaluation and testing work to do before a power fail protection method is selected. I hope the discussion is as beneficial to others as it is to my organization. Along the way, one of our users pointed out that some of our CentOS 6 desktop/deskside machines actually throttle back power consumption in different ways than others. Instead of the yellow/amber LED display in the center of the power button, they flash green and then go solid green after the power button is pushed and the system wakes up. We have also noted that none of our CentOS 6 systems restart on their own when power is restored. This is the case whether power is lost during normal operation or when the systems are in a standby state when line power is lost. These two conditions or states (yellow/amber vs flashing green) have us wondering exactly what standby mode these systems are in and what settings may have been selected to send them to their standby state. Is there some sort of standard that applies to the standby states and are there BIOS settings or configuration files that control the what, how, and when standby is directed? Thanks to all and best regards.

1 0

fcitx-anthy request (for Japanese users)
by Scott Robbins 18 Aug '17

18 Aug '17

Apropos of the discussion this week with the person trying to get Chinese input going on CentOS, I filed a request for enhancement with Fedora's EPEL to add fcitx-anthy as a package. Currently, I'm able to get it working with the Fedora 20 rpm, but it would be nice to not have to search for it. It's been assigned (I'm not sure how meaningful that is, depending upon the assignee's free time), but anyone who would like to add their support to the request can view the bug at https://bugzilla.redhat.com/show_bug.cgi?id=1471924 -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

2 17

CentOS 7.x Russian certification
by Gorazd 18 Aug '17

18 Aug '17

Dear all, does anyone have any idea where to get a list of all CentOS 7.x versions that are certified to be used within Russia. My guess is that organizations, such as FSTEK, TR-CU declares those versions/distributions of CentOS that are certified to be used with commercial projects in Russia. Anyone with some information on this, plase advice, I would be very grateful. Regards, Gorazd

2 1

Power Fail Protection Update
by Chris Olson 17 Aug '17

17 Aug '17

Many thanks to those that responded to my original posting with information about Network UPS Tools and commercial UPS products. In our planning a path forward to implement UPS-based power fail protection, we have come across what appears to be an issue with the state of the CentOS 6 machines being UPS protected. Most of these machines are desktop/deskside machines that are likely to be idle during non-work hours. It is also likely that they will be hibernating or in a power save mode. In the power save mode, these machines do not respond to keyboard or mouse activity. They also do not respond to network traffic such as a ping from other systems on the network. The method we use to wake them up is a quick push on the power button when the hibernation state is indicated by the button's yellow LED display. This state of hibernation leaves us wondering if these systems will be able to respond to network messages sent by the UPS. We have not yet made it all the way through the NUT and UPS documentation. The hibernation answer may very well be therein, but we have not found it so far. Any help or direction regarding the hibernation issue as it relates to UPS power fail protection will be appreciated. Thanks again and best regards.

4 3

CentOS-announce Digest, Vol 150, Issue 2
by centos-announce-request＠centos.org 17 Aug '17

17 Aug '17

1 0

CentOS-announce Digest, Vol 150, Issue 1
by centos-announce-request＠centos.org 16 Aug '17

16 Aug '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. New CentOS Atomic Release and Kubernetes System Containers Now Available (Jason Brooks) 2. CESA-2017:2456 Critical CentOS 6 firefox Security Update (Johnny Hughes) 3. CESA-2017:2424 Critical CentOS 6 java-1.7.0-openjdk Security Update (Johnny Hughes) 4. CESA-2017:2478 Critical CentOS 6 httpd Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 11 Aug 2017 11:53:14 -0700 From: Jason Brooks <jbrooks(a)redhat.com> To: "The CentOS developers mailing list." <centos-devel(a)centos.org>, atomic-devel <atomic-devel(a)projectatomic.io>, atomic-announce(a)projectatomic.io, centos-announce(a)centos.org Subject: [CentOS-announce] New CentOS Atomic Release and Kubernetes System Containers Now Available Message-ID: <CAF=rfpDokA6CUrO2W0aY3gEuOpJ384ThhH-6fwJxwf6OueAg_Q(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Last week, the CentOS Atomic SIG released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1707), a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. The release, which came as part of the monthly CentOS release stream, was a modest one, including only a single glibc bugfix update (https://lists.centos.org/pipermail/centos-announce/2017-July/022505.html) The next Atomic Host release will be based on the RHEL 7.4 source code (https://seven.centos.org/2017/08/centos-linux-7-1708-based-on-rhel-7-4-sour…) and will include support for overlayfs container storage, among other enhancements. Outside of the Atomic Host itself, the SIG has updated its Kubernetes container images to be usable as system containers (http://www.projectatomic.io/blog/2016/09/intro-to-system-containers/) What's more, in addition to the Kubernetes 1.5.x-based containers that derive from RHEL, the Atomic SIG is now producing packages and containers that provide the current 1.7.x version of Kubernetes. ## Containerized Master The downstream release of CentOS Atomic Host ships without the kubernetes-master package built into the image. You can install the master kubernetes components (apiserver, scheduler, and controller-manager) as system containers, using the following commands: # atomic install --system --system-package=no --name kube-apiserver registry.centos.org/centos/kubernetes-apiserver:latest # atomic install --system --system-package=no --name kube-scheduler registry.centos.org/centos/kubernetes-scheduler:latest # atomic install --system --system-package=no --name kube-controller-manager registry.centos.org/centos/kubernetes-controller-manager:latest ## Kubernetes 1.7.x The CentOS Virt SIG is now producing Kubernetes 1.7.x rpms, available through this yum repo (https://github.com/CentOS/CentOS-Dockerfiles/blob/master/kubernetes-sig/mas…) The Atomic SIG is maintaining system containers based on these rpms that can be installed as as follows: ### on your master # atomic install --system --system-package=no --name kube-apiserver registry.centos.org/centos/kubernetes-sig-apiserver:latest # atomic install --system --system-package=no --name kube-scheduler registry.centos.org/centos/kubernetes-sig-scheduler:latest # atomic install --system --system-package=no --name kube-controller-manager registry.centos.org/centos/kubernetes-sig-controller-manager:latest ### on your node(s) # atomic install --system --system-package=no --name kubelet registry.centos.org/centos/kubernetes-sig-kubelet:latest # atomic install --system --system-package=no --name kube-proxy registry.centos.org/centos/kubernetes-sig-proxy:latest Both the 1.5.x and 1.7.x sets of containers have been tested with the kubernetes ansible scripts (https://github.com/kubernetes/contrib/tree/master/ansible) provided in the upstream contrib repository, and function as drop-in replacements for the installed rpms. If you prefer to run Kubernetes from installed rpms, you can layer the master components onto your Atomic Host image using rpm-ostree package layering with the command: `atomic host install kubernetes-master`. The containers referenced in these systemd service files are built in and hosted from the CentOS Community Container Pipeline (https://wiki.centos.org/ContainerPipeline) based on Dockerfiles from the CentOS-Dockerfiles repository (https://github.com/CentOS/CentOS-Dockerfiles/tree/master/kubernetes) ## Download CentOS Atomic Host CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the CentOS wiki (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) ## Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: $ sudo atomic host upgrade ## Release Cycle The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them. ## Getting Involved CentOS Atomic Host is produced by the CentOS Atomic SIG (http://wiki.centos.org/SpecialInterestGroup/Atomic) based on upstream work from Project Atomic (http://www.projectatomic.io/) If you'd like to work on testing images, help with packaging, documentation -- join us! The SIG meets weekly on Thursdays at 16:00 UTC in the #centos-devel channel, and you'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel (https://lists.projectatomic.io/mailman/listinfo/atomic-devel) mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions. ## Getting Help If you run into any problems with the images or components, feel free to ask on the centos-devel (http://lists.centos.org/mailman/listinfo/centos-devel) mailing list. Have questions about using Atomic? See the atomic (https://lists.projectatomic.io/mailman/listinfo/atomic) mailing list or find us in the #atomic channel on Freenode. ------------------------------ Message: 2 Date: Tue, 15 Aug 2017 20:20:53 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2456 Critical CentOS 6 firefox Security Update Message-ID: <20170815202053.GA55144(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2456 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2017:2456 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f29636840b84fd6d5a4a102d02a19c569a3c8e5bb122fffab931a57fdaf87ae8 firefox-52.3.0-3.el6.centos.i686.rpm x86_64: f29636840b84fd6d5a4a102d02a19c569a3c8e5bb122fffab931a57fdaf87ae8 firefox-52.3.0-3.el6.centos.i686.rpm fa94722eb61a41e0c0c12c31dab803aeb3387e9ba83ad52a305dc1880d5764b8 firefox-52.3.0-3.el6.centos.x86_64.rpm Source: 85eb85c49ccac809e5eb899b3680735e5ba1521c378866ccfa98982462801152 firefox-52.3.0-3.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 15 Aug 2017 20:23:35 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2424 Critical CentOS 6 java-1.7.0-openjdk Security Update Message-ID: <20170815202335.GA55418(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2424 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2017:2424 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 53a24f4fed4dffa5d60f5f6f5aae09cae0d5aa675aae5c89bc89568f150c375b java-1.7.0-openjdk-1.7.0.151-2.6.11.0.el6_9.i686.rpm 87ed44696e8f5d9f3a409e48e8e45c9963ee8bd5d66d85432f99fde5fe700fc6 java-1.7.0-openjdk-demo-1.7.0.151-2.6.11.0.el6_9.i686.rpm a22a1605fd7fd61c1edff42b837d048263c9ed3d62ddc6cb057df9db9b8488d3 java-1.7.0-openjdk-devel-1.7.0.151-2.6.11.0.el6_9.i686.rpm ab1fa5c00fc66e895c699909ba6f7a033359a2cb6c853b45db77bac414f83faa java-1.7.0-openjdk-javadoc-1.7.0.151-2.6.11.0.el6_9.noarch.rpm ddc41007c6b80e937826f9b08adb8529537e45224b7d9c77e88a5137333dec08 java-1.7.0-openjdk-src-1.7.0.151-2.6.11.0.el6_9.i686.rpm x86_64: bd3d2e33f5f05c97acdb4463ee838e1ac990de77704401a13cbee82d6359c93b java-1.7.0-openjdk-1.7.0.151-2.6.11.0.el6_9.x86_64.rpm 077188b99553fa5323ce61ae133048b4a3fbf12bb6feeb494734af627cf5fb62 java-1.7.0-openjdk-demo-1.7.0.151-2.6.11.0.el6_9.x86_64.rpm aa5efd1300c3240590bf4ecaaf00040eb1a3ae3674279de2c768c734921eef85 java-1.7.0-openjdk-devel-1.7.0.151-2.6.11.0.el6_9.x86_64.rpm ab1fa5c00fc66e895c699909ba6f7a033359a2cb6c853b45db77bac414f83faa java-1.7.0-openjdk-javadoc-1.7.0.151-2.6.11.0.el6_9.noarch.rpm 51f85429d7fb4aebb500b6ba73e717f7dbc6597191db9dd8c0b108d9f1e7aac4 java-1.7.0-openjdk-src-1.7.0.151-2.6.11.0.el6_9.x86_64.rpm Source: f7fea14d8c97e7251cb3129c2c0bc23485ed534d36f80a9e1feb6d301abbe207 java-1.7.0-openjdk-1.7.0.151-2.6.11.0.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 15 Aug 2017 20:25:39 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2478 Critical CentOS 6 httpd Security Update Message-ID: <20170815202539.GA55716(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2478 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2017:2478 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 68b712bfb3b1a08748f4bdac924dc30fa5683977333c9ff052a525d2e9347259 httpd-2.2.15-60.el6.centos.5.i686.rpm aeff46346d66dcb687524a05882f21b6c7596f433859c2a443354af33bc3deed httpd-devel-2.2.15-60.el6.centos.5.i686.rpm ae7886ff13fef00ae7272ccced1ec6e3d4cdd0db02a3e9ba37a37d7b7548d087 httpd-manual-2.2.15-60.el6.centos.5.noarch.rpm 30d1a73a78e580d5314b7140799e23af42c0023560c863ceab681eae175e815b httpd-tools-2.2.15-60.el6.centos.5.i686.rpm c6ee5b709d021faaa9abd61f8316948ed2043ce53d935b9063285bf3d41994f8 mod_ssl-2.2.15-60.el6.centos.5.i686.rpm x86_64: 6c4577f55b8b3f40a1223be39a61ee1185ce7b9a0588ef4ad60fbf45d5e431e7 httpd-2.2.15-60.el6.centos.5.x86_64.rpm aeff46346d66dcb687524a05882f21b6c7596f433859c2a443354af33bc3deed httpd-devel-2.2.15-60.el6.centos.5.i686.rpm 4c9cc089ac1d30b9b50bd1ff2a2a3eaf0c09cc969b0b543f6a7d9ffd01f5cf4f httpd-devel-2.2.15-60.el6.centos.5.x86_64.rpm ae7886ff13fef00ae7272ccced1ec6e3d4cdd0db02a3e9ba37a37d7b7548d087 httpd-manual-2.2.15-60.el6.centos.5.noarch.rpm 5cc5dfdd78d76f2c020cfab998363aa8345cdc477d48af3a1c1cd48dd364098f httpd-tools-2.2.15-60.el6.centos.5.x86_64.rpm b2f9c90fc09cb85894f20ead9cbf4405cf92ac1748860aa280e7af96c21e17fb mod_ssl-2.2.15-60.el6.centos.5.x86_64.rpm Source: ee426ab362997f52fcfd19d7e5610359d47a3a5439cbba2ecff7455c35bd9b85 httpd-2.2.15-60.el6.centos.5.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 150, Issue 1 ***********************************************

1 0

Power Fail Protection
by Chris Olson 15 Aug '17

15 Aug '17

Some of our largest systems run Windows because it supports engineering applications that we use regularly. These applications have unattended runs that often take between ten and fifteen hours to complete. We have taken the recommendation of the application supplier and equipped these Windows machines with UPS protection for 30 minutes at full load. The UPSs are Ethernet connected. A support application on the Windows engineering machine communicates with the UPS to detect and address any facility power failure. The long run engineering application is then suspended at a restart point and the system is shut down. We initiate job completion manually from the suspension restart point after the system has reliable power and is rebooted. If we wanted to protect our CentOS systems from facility power failure in a similar way, is there operating system or other standard support that we might employ? Most of the Linux-based applications are not as critical as the engineering applications on the Windows machines. There is a significant amount of processor idle time on several of the CentOS systems during non-work hours when the systems are unattended. Several CentOS systems are supported currently with UPSs, but they run out and the system loses power if it is unattended.

4 5

Custom kickstart post section on usb thumbdrive
by Jerry Geis 14 Aug '17

14 Aug '17

Hi All, I am attempting to create a custom USB drive for kickstart install. I found this: 1. get the ISO file of CentOS 7 2. mount -o loop CentOS-7.0*.iso /mnt/ 3. mkdir -p /CentOS-7-ISO-respin/{CentOS-7-unpacked,CentOS-7-iso} 4. rsync -avz /mnt/ /CentOS-7-ISO-respin/RHEL-7-unpacked 5. put your kickstart file into /CentOS-7-ISO-respin/RHEL-7-unpacked 6. add a new line to /CentOS-7-ISO-respin/RHEL-7-unpacked/isolinux/isolinux.cfg (this way you can use the ISO also from a DVD) label linux_ks menu label ^Install CentOS 7 with Kickstart kernel vmlinuz append initrd=initrd.img inst.stage2=hd:sdb2:/ ks=hd:sdb1:/ks.cfg 7. create the ISO with: /usr/bin/genisoimage -untranslated-filenames -volid 'CentOS-7.0-KS-x86_64' -J -joliet-long -rational-rock -translation-table -input-charset utf-8 -x ./lost+found -b isolinux/isolinux.bin -c isolinux/ boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table 8. dd if=/CentOS-7-ISO-respin/CentOS-7-CSB-iso/CentOS-7.0-KS-x86_64-DVD.iso of=/dev/XXX (where XXX is the Device Name of your USB drive without the partition number e.g. /dev/sdb) (Careful, that command destroys all data on the Stick) But I would also like to create a custom directory on the ISO and put some files in there for a custom POST section. I was not able to find an example with a custom POST section on the ISO. Anyone have any examples? Thanks, Jerry

2 1

Centos 7 specific cure for Spamassassin DNS lookup problem
by Gary Stainburn 14 Aug '17

14 Aug '17

I have the following error message in my /var/log/spamd spf: lookup failed: available_nameservers: No DNS servers available! Having Googled the error message I've found a number of responses which involve patching Perl or Spamassassin or other cures. Before I start changing things I was wondering if there was a Centos 7 specific resolution. Where possible, on production machines I prefer to stay with RPM's rather than amending software directly. Also, many of these responses are over 10 years old, so I'm a little sceptical about their success today. Gary

4 7

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