Discuss

discuss@lists.centos.org

3 participants
34748 discussions

UEFI booting
by Jerry Geis 19 Sep '19

19 Sep '19

I installed my first UEFI disk yesterday. Seemed to go fine. CentOS 7.6 x86_64 I then took that disk "out" of that machine and put it another machine - it seems to not even boot. I put the original disk back in that machine and it boots fine. I put the UEFI disk back in the machine I built it on and it works fine. They are similar machines either and i3 and i7. Shouldn't that work? Build a UEFI disk on machine A - move it to machine B? Thanks Jerry

6 6

Postfix vs. Thunderbird on Mac OS
by Nicolas Kovacs 19 Sep '19

19 Sep '19

Hi, I'm running our local school's mail server on CentOS 7, Postfix and Dovecot. We get quite a lot of spam, so I have the following sender restrictions in my /etc/postfix/main.cf: --8<------------------------------------------------------ # Restrictions SMTP smtpd_helo_restrictions = reject_unknown_helo_hostname smtpd_sender_restrictions = reject_unknown_sender_domain, check_sender_access hash:/etc/postfix/sender_access smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_rbl_client zen.spamhaus.org, reject_rhsbl_reverse_client dbl.spamhaus.org, reject_rhsbl_helo dbl.spamhaus.org, reject_rhsbl_sender dbl.spamhaus.org smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_data_restrictions = reject_unauth_pipelining --8<------------------------------------------------------ Most folks are using Thunderbird on Linux, and everything works perfectly. One single user has a MacBook Air with Thunderbird on Mac OS Mojave, and her outgoing mails are rejected with the following error message in /var/log/maillog on the server: --8<------------------------------------------------------ Sep 16 14:22:32 sd-48011 postfix/smtps/smtpd[14434]: NOQUEUE: reject: RCPT from villa.figaret.pck.nerim.net[62.212.106.47]: 450 4.7.1 <Air-de-bea.scholae.lan>: Helo command rejected: Host not found; from=<xxxxx.yyyyyyyy(a)scholae.fr> to=<info(a)microlinux.fr> proto=ESMTP helo=<Air-de-bea.scholae.lan> --8<------------------------------------------------------ As far as I understand, it has to do with this MacBook's host configuration. Any suggestions? Cheers from the sunny South of France, Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

4 3

conflicts in updating to CR repo
by Fred Smith 19 Sep '19

19 Sep '19

Note, first of all I haven't actually updated, I'm just running "yum update" to see what conflicts, if any, I get so I can be prepared when the final 7.7 release happens. I've traditionally used the nvidia packages from elrepo, but recently enabled rpmfusion (back when I started using 7.x, I disabled rpmfusion because it took them a looooong time to get a EL7 repository up). I use the priority plugin in yum, and have elrepo at priority 50 and rpmfusion at priority 60, so the elrepo nvidia packages should "win", but yum seems to be confused about which packages to use. So now when doing yum update (with CR enabled) I get this long list of dependency issues regarding the nvidia packages. I don't see any reason to switch to the rpmfusion packages, elrepo seems to do a good job of packaging and keeping them up to date: --> Processing Dependency: xorg-x11-drv-nvidia-390xx-libs(x86-64) = 3:390.129-1.el7 for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64 --> Processing Dependency: nvidia-settings-390xx(x86-64) = 390.129 for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64 --> Processing Dependency: libnvidia-tls.so.390.129()(64bit) for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64 --> Processing Dependency: libnvidia-glcore.so.390.129()(64bit) for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64 --> Running transaction check ---> Package nvidia-settings-390xx.x86_64 0:390.129-1.el7 will be installed ---> Package xorg-x11-drv-nvidia-390xx-libs.x86_64 3:390.129-1.el7 will be installed --> Processing Conflict: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 conflicts xorg-x11-drv-nvidia-390xx Removing kmod-nvidia.x86_64 0:430.50-1.el7_7.elrepo - u due to obsoletes from kmod-nvidia-390xx.x86_64 3:390.129-3.el7 - u --> Restarting Dependency Resolution with new changes. --> Running transaction check ---> Package kmod-nvidia.x86_64 0:430.50-1.el7_7.elrepo will be an update --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 ---> Package nvidia-x11-drv.x86_64 0:430.40-1.el7_6.elrepo will be updated ---> Package nvidia-x11-drv.x86_64 0:430.40-1.el7_6.elrepo will be updated --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:3.10.0-957.21.2.el7 will be erased ---> Package kernel-devel.x86_64 0:3.10.0-957.21.2.el7 will be erased ---> Package kmod-nvidia.x86_64 0:430.50-1.el7_7.elrepo will be an update --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 --> Processing Conflict: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 conflicts xorg-x11-drv-nvidia-390xx --> Finished Dependency Resolution Error: nvidia-x11-drv conflicts with 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64 Error: Package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 (elrepo) Requires: nvidia-kmod = 430.50 Removing: kmod-nvidia-430.40-1.el7_6.elrepo.x86_64 (@elrepo) nvidia-kmod = 430.40-1.el7_6.elrepo Obsoleted By: 3:kmod-nvidia-390xx-390.129-3.el7.x86_64 (rpmfusion-nonfree-updates) Not found Updated By: kmod-nvidia-430.50-1.el7_7.elrepo.x86_64 (elrepo) nvidia-kmod = 430.50-1.el7_7.elrepo Available: 3:akmod-nvidia-430.40-2.el7.x86_64 (rpmfusion-nonfree-updates) nvidia-kmod = 3:430.40-2.el7 Available: kmod-nvidia-430.14-1.el7_6.elrepo.x86_64 (elrepo) nvidia-kmod = 430.14-1.el7_6.elrepo Available: kmod-nvidia-430.26-1.el7_6.elrepo.x86_64 (elrepo) nvidia-kmod = 430.26-1.el7_6.elrepo Available: kmod-nvidia-430.34-1.el7_6.elrepo.x86_64 (elrepo) nvidia-kmod = 430.34-1.el7_6.elrepo Available: kmod-nvidia-430.40-2.el7_7.elrepo.x86_64 (elrepo) nvidia-kmod = 430.40-2.el7_7.elrepo Available: 3:kmod-nvidia-430.40-2.el7.x86_64 (rpmfusion-nonfree-updates) nvidia-kmod = 3:430.40-2.el7 Available: 3:kmod-nvidia-3.10.0-1062.el7.x86_64-430.40-2.el7.x86_64 (rpmfusion-nonfree-updates) nvidia-kmod = 3:430.40-2.el7 You could try using --skip-broken to work around the problem Thanks in advance for advice! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- Show me your ways, O LORD, teach me your paths; Guide me in your truth and teach me, for you are God my Savior, And my hope is in you all day long. -------------------------- Psalm 25:4-5 (NIV) --------------------------------

3 4

Updates
by Jerry Geis 19 Sep '19

19 Sep '19

I did yum -y update --exclude=vulkan*; then rebooted When I do yum check-updates I get this: (which I expect) vulkan.x86_64 1.1.97.0-1.el7 base vulkan-filesystem.noarch 1.1.97.0-1.el7 base When I do the yum -y update I get this: Transaction check error: file /usr/lib64/libSPIRV-Tools-opt.so from install of vulkan-1.1.97.0-1.el7.x86_64 conflicts with file from package spirv-tools-libs-2019.1-1.el7.x86_64 file /usr/lib64/libSPIRV-Tools.so from install of vulkan-1.1.97.0-1.el7.x86_64 conflicts with file from package spirv-tools-libs-2019.1-1.el7.x86_64 How do I get past that ? Vulkan is used by "wine" I believe. THanks Jerry

3 2

What about Mate Desktop on Centos 8?
by Frank Cox 18 Sep '19

18 Sep '19

According to Twitter: https://mobile.twitter.com/CentOSProject/status/1173652996305170432 "The next version of #CentOS is being released September 24 and will be announced in all the usual places." I'm wondering about the status of the Mate Desktop. Looking under M here: https://mirror.csclub.uwaterloo.ca/fedora/epel/8/Everything/x86_64/Packages… I don't see anything about Mate. Which leads me to ask, what's its status then? I hope it hasn't died since that's what I use for all of my computers. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

6 8

CentOS-announce Digest, Vol 175, Issue 1
by centos-announce-request＠centos.org 18 Sep '19

18 Sep '19

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. Release for CentOS Linux 7 (1908) on the x86_64 Architecture (Johnny Hughes) 2. Release for CentOS Linux 7 (1810) on armhfp aarch64 i386 ppc64 ppc64le and power9 (Pablo Sebasti?n Greco) 3. Release for CentOS Linux 7 (1908) on armhfp aarch64 i386 ppc64 ppc64le and power9 (Johnny Hughes) 4. CESA-2019:2694 Critical CentOS 6 firefox Security Update (Johnny Hughes) 5. CESA-2019:2736 Important CentOS 6 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Sep 2019 08:01:36 -0500 From: Johnny Hughes <johnny(a)centos.org> To: CentOS-Announce <centos-announce(a)centos.org> Subject: [CentOS-announce] Release for CentOS Linux 7 (1908) on the x86_64 Architecture Message-ID: <da1896ff-3527-ccef-4c92-7f463c63f4ae(a)centos.org> Content-Type: text/plain; charset="utf-8" Release for CentOS Linux 7 (1908) on the x86_64 Architecture We are pleased to announce the general availability of CentOS Linux 7 (1908) for the x86_64 architecture. Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 1908, derived from Red Hat Enterprise Linux 7.7 Source Code. As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. ---------- Updates, Sources, and DebugInfos Updates released since the upstream release are all posted, across all architectures. We strongly recommend every user apply all updates, including the content released today, on your existing CentOS Linux 7 machine by just running 'yum update'. As with all CentOS Linux 7 components, this release was built from sources hosted at git.centos.org. In addition, SRPMs that are a byproduct of the build (and also considered critical in the code and buildsys process) are being published to match every binary RPM we release. Sources will be available from vault.centos.org in their own dedicated directories to match the corresponding binary RPMs. Since there is far less traffic to the CentOS source RPMs compared with the binary RPMs, we are not putting this content on the main mirror network. If users wish to mirror this content they can do so using the reposync command available in the yum-utils package. All CentOS source RPMs are signed with the same key used to sign their binary counterparts. Developers and end users looking at inspecting and contributing patches to the CentOS Linux distro will find the code hosted at git.centos.org far simpler to work against. Details on how to best consume those are documented along with a quick start at : http://wiki.centos.org/Sources Debuginfo packages are also being signed and pushed. Yum configs shipped in the new release file will have all the context required for debuginfo to be available on every CentOS Linux install. This release supersedes all previously released content for CentOS Linux 7, and therefore we highly encourage all users to upgrade their machines. Information on different upgrade strategies and how to handle stale content is included in the Release Notes. Note that older content, obsoleted by newer versions of the same applications are trim'd off from repos like Extras/ and Plus/ However this time we have also extended this to the SIG content hosted at mirror.centos.org, and some older End of Life content has been dropped. Everything we ever release, is always available on the vault service for people still looking for and have a real need for it. ---------- Download In order to conserve donor bandwidth, and to make it possible to get the mirror content sync'd out as soon as possible, we recommend using torrents to get your initial installer images: Details on the images are available on the mirrors at http://mirror.centos.org/centos/7/isos/x86_64/0_README.txt - that file clearly highlights the difference in the images, and when one might be more suitable than the others. sha256sum x86_64: ba827210d4eb9313fc19120b9b85e7baef234c7f81bc55847a336114ddac20cb CentOS-7-x86_64-LiveGNOME-1908.iso 9a2c47d97b9975452f7d582264e9fc16d108ed8252ac6816239a3b58cef5c53d CentOS-7-x86_64-Minimal-1908.iso 9bba3da2876cb9fcf6c28fb636bcbd01832fe6d84cd7445fa58e44e569b3b4fe CentOS-7-x86_64-DVD-1908.iso 0ef3310d13f7fc140ec5180dc05369d2f473e802577466825205d17e46ef5a9b CentOS-7-x86_64-LiveKDE-1908.iso bd5e6ca18386e8a8e0b5a9e906297b5610095e375e4d02342f07f32022b13acf CentOS-7-x86_64-Everything-1908.iso 6ffa7ad44e8716e4cd6a5c3a85ba5675a935fc0448c260f43b12311356ba85ad CentOS-7-x86_64-NetInstall-1908.iso Information for the torrent files and sums are available at http://mirror.centos.org/centos/7/isos/x86_64 -------- Additional Images The container, Vagrant, Cloud and Atomic Host images are being prepared and will be released in the next few days. Look for an announcement posted to the centos-announce list for more information on availability for these in the coming days. ---------- Getting Help The CentOS ecosystem is sustained by community driven help and guidance. The best place to start for new users is at http://wiki.centos.org/GettingHelp We are also on social media, you can find the project: on Twitter at? : http://twitter.com/CentOSProject on Facebook at : https://www.facebook.com/groups/centosproject/ on LinkedIn at : https://www.linkedin.com/groups/22405 And you will find the core team and a majority of the contributors on irc, on freenode.net in #centos ; talking about the finer points of distribution engineering and platform enablement. ---------- Contributors This release was made possible due to the hard work of many people, foremost on that list are the Red Hat Engineers for producing a great distribution and the CentOS QA team, without them CentOS Linux would look very different. Many of the team went further and beyond expectations to bring this release to you, and I would like to thank everyone for their help. We are also looking for people to get involved with the QA process in CentOS, if you would like to join this please introduce yourself on the centos-devel list (http://lists.centos.org/mailman/listinfo/centos-devel ). Finally, please join me in thanking the donors who all make this possible for us. Enjoy the fresh new release! Thanks, Johnny Hughes

1 0

OT: DMARC / DKIM Failure Reports
by Miroslav Geisselreiter 17 Sep '19

17 Sep '19

Hi guys, when I send e-mails to CentOS mailing list <centos(a)centos.org>, I received DMARC / DKIM failure reports. Is it possible to solve this problem and if so how? This is the first report: This is an email abuse report for an email message received from IP 208.100.23.70 on Tue, 17 Sep 2019 15:56:25 +0200. The message below did not meet the sending domain's DMARC policy. For more information about this format please seehttp://tools.ietf.org/html/rfc6591 . Feedback-Type: auth-failure User-Agent: Lua/1.0 Version: 1.0 Original-Mail-From:centos-bounces@centos.org Original-Rcpt-To:obodor@vub.sk Arrival-Date: Tue, 17 Sep 2019 15:56:25 +0200 Message-ID:<5502e8ac-6b01-18dd-e028-7d2dd666063b(a)intar.cz> Authentication-Results: dmarc=fail (p=none, dis=none) header.from=intar.cz Source-IP: 208.100.23.70 Delivery-Result: smg-policy-action Auth-Failure: dmarc Reported-Domain: intar.cz ------------ This is the seconf report: This is an authentication failure report for an email message received from IP 208.100.23.70 on Tue, 17 Sep 2019 15:56:32 +0200 (CEST). Feedback-Type: auth-failure Version: 1 User-Agent: OpenDMARC-Filter/1.3.2 Auth-Failure: dmarc Authentication-Results: mx.bitactive.com; dmarc=fail header.from=intar.cz Original-Envelope-Id: 46Xl5X0Ss6z1ltXM Original-Mail-From:centos-bounces@centos.org Source-IP: 208.100.23.70 (mail.centos.org) Reported-Domain: intar.cz Authentication-Results: mx.bitactive.com; dkim=fail reason="signature verification failed" (1024-bit key) header.d=intar.czheader.i=(a)intar.cz header.b="rSnG4eyi" Received: from mail.centos.org (mail.centos.org [208.100.23.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.bitactive.com (Postfix) with ESMTPS id 46Xl5X0Ss6z1ltXM for<mwanat(a)forall.pl>; Tue, 17 Sep 2019 15:56:32 +0200 (CEST) Received: from mail.centos.org (localhost [IPv6:::1]) by mail.centos.org (Postfix) with ESMTP id 011EE3C1F16; Tue, 17 Sep 2019 13:56:03 +0000 (UTC) X-Original-To:centos@centos.org Delivered-To:centos@centos.org Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=81.19.4.73; helo=nirvana.intar.cz;envelope-from=mg(a)intar.cz; receiver=centos(a)centos.org Received: from nirvana.intar.cz (nirvana.intar.cz [81.19.4.73]) by mail.centos.org (Postfix) with ESMTPS id 640643C1F0F for<centos(a)centos.org>; Tue, 17 Sep 2019 13:55:59 +0000 (UTC) Received: from larix.intarnet.cz (larix.intarnet.cz [192.168.1.53]) by nirvana.intar.cz (Postfix) with ESMTPS id 74992C045CD1; Tue, 17 Sep 2019 15:55:57 +0200 (CEST) Received: from [192.168.1.176] (nirvana.intar.cz [81.19.4.73]) by larix.intarnet.cz (Postfix) with ESMTPSA id 5EB62104F460; Tue, 17 Sep 2019 15:55:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intar.cz; s=larix; t=1568728557; bh=ezgga1YmsO9WxPgAc+7ouaZ9HJlG9XkA8LJjbiJd0yA=; h=Subject:To:References:From:Date:In-Reply-To; b=rSnG4eyiHg6tTDdBdCJyp1/ACUczgG+9usycftG3BMz1EwN0zPMPyo0gSkpvxwJUf aM/jvd/gzFJVz7Z6MEw1A9iCE0ZzJy931WvXG+rIJR+Set5hb3fMpu1PgaOz1MIYTF 7Z24H3X1KwUPof1RaKHrFQLYFbr011IbEwz613Xo= To: CentOS mailing list<centos(a)centos.org>, Mauricio Tavares<raubvogel(a)gmail.com> References:<b3f926b0-711f-4a32-4a61-644e707a8db8(a)intar.cz> <CAHEKYV42BVbAiPmCPnDPhQm53=+t6PVpjheXvjEY535kHFttSg(a)mail.gmail.com> <ea092741-5941-c49d-7fe2-b4e8df9944ed(a)intar.cz> <CAHEKYV5T8UJNB-PVoj=Aujje3MjN-HiAxKp9kcB24ZK6z8d2Kg(a)mail.gmail.com> From: Miroslav Geisselreiter<mg(a)intar.cz> Organization: INTAR a.s. Message-ID:<5502e8ac-6b01-18dd-e028-7d2dd666063b(a)intar.cz> Date: Tue, 17 Sep 2019 15:55:57 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To:<CAHEKYV5T8UJNB-PVoj=Aujje3MjN-HiAxKp9kcB24ZK6z8d2Kg(a)mail.gmail.com> Subject: Re: [CentOS] CentOS7 sometimes don't detect NIC after reboot X-BeenThere:centos@centos.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe:<https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive:<http://lists.centos.org/pipermail/centos/> List-Post:<mailto:centos@centos.org> List-Help:<mailto:centos-request@centos.org?subject=help> List-Subscribe:<https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> Reply-To: CentOS mailing list<centos(a)centos.org> Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To:centos-bounces@centos.org Sender: "CentOS"<centos-bounces(a)centos.org>

3 2

Release for CentOS Linux 7 (1908) on armhfp aarch64 i386 ppc64 ppc64le and power9
by Johnny Hughes 17 Sep '19

17 Sep '19

On 9/17/19 8:23 AM, Pablo Sebastián Greco wrote: <snip> Should be .. CentOS 7 (1908)

1 0

audit freeing multiple contexts (when running certbot)
by tony＠softins.co.uk 17 Sep '19

17 Sep '19

Apologies if it's considered off-topic, but I'm not sure in what part of the system the issue lies. So I am giving as much info as possible, not knowing which is most relevant. I have two VMs hosted on ESX, running CentOS 6.10 One has kernel 2.6.32-754.11.1.el6.i686 and the other has 2.6.32-754.18.2.el6.i686 Both have selinux, currently in permissive mode. On both machines we have noticed messages like the following appear in /var/log/messages from time to time: Sep 17 10:32:28 merlin kernel: audit(:0): major=252 name_count=0: freeing multiple contexts (1) Sep 17 10:32:28 merlin kernel: audit(:0): major=355 name_count=0: freeing multiple contexts (2) Sep 17 10:32:29 merlin kernel: audit(:0): major=252 name_count=0: freeing multiple contexts (1) Sep 17 10:32:29 merlin kernel: audit(:0): major=355 name_count=0: freeing multiple contexts (2) On further investigation, this only happens when certbot-auto runs (under python 3.4), whether or not it renews the certificate. The above instance was created by running the following command: [root@merlin ~]# date ; cd /opt/letsencrypt && ./certbot-auto renew ; date Tue Sep 17 10:32:24 BST 2019 /opt/eff.org/certbot/venv/lib/python3.4/site-packages/cryptography/hazmat/bindings/openssl/binding.py:163: CryptographyDeprecationWarning: OpenSSL version 1.0.1 is no longer supported by the OpenSSL project, please upgrade. A future version of cryptography will drop support for it. utils.CryptographyDeprecationWarning Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/xxxx.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert not yet due for renewal - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The following certs are not due for renewal yet: /etc/letsencrypt/live/xxxx/fullchain.pem expires on 2019-11-15 (skipped) No renewals were attempted. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Tue Sep 17 10:32:30 BST 2019 [root@merlin letsencrypt]# Has anyone else seen anything similar? Is it something that can be fixed, or should be ignored? Cheers Tony -- Tony Mountifield Work: tony(a)softins.co.uk - http://www.softins.co.uk Play: tony(a)mountifield.org - http://tony.mountifield.org

1 0

reconfigure centos-6.9 host to ignore missing nic
by James B. Byrne 16 Sep '19

16 Sep '19

I need to work on a host which has been offline and powered down for some time. I has CentOS-6.9 installed. At some point it had two nics, one on the motherboard (still present and working) and one as an expansion card. When booted the console displays: pciehp 0000:00:1c:0:pcie04: Failed to check link status repeatedly. How do I tell the host to ignore the missing nic or remove it from the system configuration so that the error is removed. -- *** 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

2 1

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