- Discuss - lists.centos.org

Re: [CentOS] Understanding VDO vs ZFS
by david 03 May '20

03 May '20

0At 08:07 PM 5/2/2020, you wrote: >My two cents: >1- Do you have an encrypted filesystem on top of VDO? If yes, you will see >no benefit from dedupe. >2- can you post the stats of vdostats verbose /dev/mapper/xxxxx (replace >with your device) > >you can do something like: "vdostats -verbose /dev/mapper/xxxxxxxx | grep >-B6 'save percentage' > > > > >On Sat, May 2, 2020 at 9:54 PM david <david(a)daku.org> wrote: > > > Folks > > > > I'm looking for a solution for backups because ZFS has failed on me > > too many times. In my environment, I have a large amount of data > > <snip> BTW: I think the 'saving percent' of 13 is consistent with my computation of 1.16 if one takes into account the overhead blocks. Is that true?

1 0

systemctl restart changes permission.
by Kaushal Shriyan 02 May '20

02 May '20

Hi, I am running CentOS Linux release 7.8.2003 (Core) with php72u-fpm-7.2.30-1.el7.ius.x86_64 version. I am facing the below permission denied issue. I also did the below steps #cd /run #chown -Rc nginx.nginx php-fpm changed ownership of ‘php-fpm/php-fpm.pid’ from root:root to nginx:nginx changed ownership of ‘php-fpm’ from root:root to nginx:nginx #systemctl restart php-fpm again changes it from nginx.nginx to root.root user. nginx error logs > 2020/04/30 03:09:28 [crit] 17175#0: *154570 connect() to > unix:/run/php-fpm/www.sock failed (13: *Permission denied*) while > connecting to upstream, client: 49.207.54.161, server: _, request: "GET / > HTTP/1.1", upstream: "fastcgi://unix:/run/php-fpm/www.sock:", host: > "35.128.212.112" > 2020/04/30 03:09:28 [error] 17175#0: *154570 open() > "/var/www/drupal/web/50x.html" failed (2: No such file or directory), > client: 49.207.54.161, server: _, request: "GET / HTTP/1.1", upstream: > "fastcgi://unix:/run/php-fpm/www.sock", host: "35.128.212.112" > 2020/04/30 03:09:35 [crit] 17176#0: *154573 connect() to > unix:/run/php-fpm/www.sock failed (13: Permission denied) while connecting > to upstream, client: 49.207.54.161, server: _, request: "GET / HTTP/1.1", > upstream: "fastcgi://unix:/run/php-fpm/www.sock:", host: "35.128.212.112" > 2020/04/30 03:09:35 [error] 17176#0: *154573 open() > "/var/www/drupal/web/50x.html" failed (2: No such file or directory), > client: 49.207.54.161, server: _, request: "GET / HTTP/1.1", upstream: > "fastcgi://unix:/run/php-fpm/www.sock", host: "35.128.212.112" > 2020/04/30 03:09:49 [crit] 17175#0: *154575 connect() to > unix:/run/php-fpm/www.sock failed (13: Permission denied) while connecting > to upstream, client: 14.98.153.6, server: _, request: "GET / HTTP/1.1", > upstream: "fastcgi://unix:/run/php-fpm/www.sock:", host: "35.128.212.112" > 2020/04/30 03:09:49 [error] 17175#0: *154575 open() > "/var/www/drupal/web/50x.html" failed (2: No such file or directory), > client: 14.98.153.6, server: _, request: "GET / HTTP/1.1", upstream: > "fastcgi://unix:/run/php-fpm/www.sock", host: "35.128.212.112" > 2020/04/30 03:09:50 [crit] 17175#0: *154575 connect() to > unix:/run/php-fpm/www.sock failed (13: Permission denied) while connecting > to upstream, client: 14.98.153.6, server: _, request: "GET / HTTP/1.1", > upstream: "fastcgi://unix:/run/php-fpm/www.sock:", host: "35.128.212.112" > 2020/04/30 03:09:50 [error] 17175#0: *154575 open() > "/var/www/drupal/web/50x.html" failed (2: No such file or directory), > client: 14.98.153.6, server: _, request: "GET / HTTP/1.1", upstream: > "fastcgi://unix:/run/php-fpm/www.sock", host: "35.128.212.112" > 2020/04/30 03:10:46 [crit] 17176#0: *154578 connect() to > unix:/run/php-fpm/www.sock failed (13: Permission denied) while connecting > to upstream, client: 184.22.107.148, server: _, request: "GET / HTTP/1.1", > upstream: "fastcgi://unix:/run/php-fpm/www.sock:", host: "35.128.212.112" > 2020/04/30 03:10:46 [error] 17176#0: *154578 open() > "/var/www/drupal/web/50x.html" failed (2: No such file or directory), > client: 184.22.107.148, server: _, request: "GET / HTTP/1.1", upstream: > "fastcgi://unix:/run/php-fpm/www.sock", host: "35.128.212.112" Please let me know if you need any additional information. Thanks in Advance. Best Regards, Kaushal

2 2

fcitx and switching between keyboards
by H 01 May '20

01 May '20

This is an old issue for me running CentOS 7, latest update. I am using fcitx to switch between keyboards, two western ones and Chinese pinyin keyboard. Ever since I installed CentOS 7 over two years ago, I have been unable to resolve issues where I can maintain keyboard setting within one application, notably chromium, and/or between applications. fcitx has a setting for allowing the keyboard choice to remain across applications but it does not work - so far. Further, in chromium, even when within an IME, every time I hit ENTER, the keyboard resets back to the default (EN_US). Needless to say, this makes for some very tedious typing using an alternative keyboard. I do not have this problem remaining within a single IME in Thunderbird, nor in Firefox, nor in LibreOffice. I can switch back and forth between one of these apps and the keyboard switches back to what I last used in that app when switching back to the app - /provided I have used Chinese/. It does not work when I use different western keyboards in the various apps. Is anyone using fcitx switching between different keyboards and can confirm the above - or refute it?

1 0

dhcpd: Not searching LDAP
by Frank Cox 01 May '20

01 May '20

Whenever my dhcp server is restarted it always puts this entry into /var/log/messages: dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file This isn't earth-shattering news since I don't have a ldap server and there's no mention of ldap in /etc/dhcp/dhcpd.conf either. So is this an error message? If it's just an informational message then that's one thing, but if it's an error message then what's the problem that it's telling me about and how do I solve it? -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

2 1

GNS3 installation docs for CentOS 8
by System Administrator 01 May '20

01 May '20

Hi, Does anyone have GNS3 installation guide for CentOS 8? Would be grateful if you could give me. Thank you. Sonam ****************************************************************************************************************************** Information contained in this message maybe confidential in nature and is meant for the intended recipient(s) of the message only. Tashi InfoComm Limited has the sole right to such information and any copying/redistribution of the information contained in the message, without the prior written consent of Tashi InfoComm Limited, is Prohibited. ******************************************************************************************************************************

3 4

CentOS-announce Digest, Vol 183, Issue 1
by centos-announce-request＠centos.org 01 May '20

01 May '20

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. CEBA-2020:1982 CentOS 7 tzdata BugFix Update (Johnny Hughes) 2. CESA-2020:1509 Important CentOS 7 java-11-openjdk Security Update (Johnny Hughes) 3. CESA-2020:1512 Important CentOS 7 java-1.8.0-openjdk Security Update (Johnny Hughes) 4. CESA-2020:1507 Important CentOS 7 java-1.7.0-openjdk Security Update (Johnny Hughes) 5. CESA-2020:1511 Important CentOS 7 git Security Update (Johnny Hughes) 6. CESA-2020:1561 Important CentOS 7 python-twisted-web Security Update (Johnny Hughes) 7. CESA-2020:1489 Important CentOS 7 thunderbird Security Update (Johnny Hughes) 8. CESA-2020:1962 Important CentOS 6 python-twisted-web Security Update (Johnny Hughes) 9. CEBA-2020:1982 CentOS 6 tzdata BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 30 Apr 2020 19:51:35 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:1982 CentOS 7 tzdata BugFix Update Message-ID: <20200430195135.GA23919(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:1982 Upstream details at : https://access.redhat.com/errata/RHBA-2020:1982 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: bc5c790c0a346bb20abbbd866e0c1cf664cec9c3e4d4e21dbfe32b32616257ba tzdata-2020a-1.el7.noarch.rpm df284a4379294602228b360243cb0fc0498371278b702354b9de2cc38ffbc09f tzdata-java-2020a-1.el7.noarch.rpm Source: d348bae19f293c56bb60b0f65b3d3dcf4523128a36ee356f0c7231da1219d2f4 tzdata-2020a-1.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 30 Apr 2020 19:52:43 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1509 Important CentOS 7 java-11-openjdk Security Update Message-ID: <20200430195243.GA24198(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1509 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:1509 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: feeefc6681aaa3bf69fdb9374e1dc13ed6e964b6545502f0bd14eaf7ce53f06d java-11-openjdk-11.0.7.10-4.el7_8.i686.rpm 7c4c37c0ea48f84107b282a1575f63a84f6f9cfbbc50708f77309afb46629be2 java-11-openjdk-11.0.7.10-4.el7_8.x86_64.rpm 5b7b7ad1f6a47aaaf64e78b1c3eaa439bc3d1fa487d4cf6d645f3e5f7f82aa1d java-11-openjdk-demo-11.0.7.10-4.el7_8.i686.rpm 0df0679e7cf1b5f15fda6bdd7d47f52bb042dd934055d93db063eba057f71d72 java-11-openjdk-demo-11.0.7.10-4.el7_8.x86_64.rpm 9ce3611a75397516fd6eac15d6b7e740ed3a497fdd49c77d03593701ad6f5bed java-11-openjdk-devel-11.0.7.10-4.el7_8.i686.rpm 7c16d75034f8b5af29f29368f9d6b6f0f96d206124bcede20b987cae23a8fc2b java-11-openjdk-devel-11.0.7.10-4.el7_8.x86_64.rpm ad579f5f54185a849e2c2f49818206dabd254d5b4a9f6a56eaaf828f8035d7ed java-11-openjdk-headless-11.0.7.10-4.el7_8.i686.rpm d59a5715f41d0cc42740ea8bbf254fee0729fe95f7783887470ac54e0028a645 java-11-openjdk-headless-11.0.7.10-4.el7_8.x86_64.rpm b8b135c555c96cb85f1b78394507e880cb3a0623d07f378b5ac2aee7ea0ceb2b java-11-openjdk-javadoc-11.0.7.10-4.el7_8.i686.rpm f8c301dd37d12af525a3f9515c8f316be1b0b45a896aff4aadbd54695c0202f3 java-11-openjdk-javadoc-11.0.7.10-4.el7_8.x86_64.rpm b65eaa6b5bbfc4d7f1c740a8b26fbe50a5a5fe48fd4d4cf6c418ad3245af136d java-11-openjdk-javadoc-zip-11.0.7.10-4.el7_8.i686.rpm e540cd84f0994771b455a98ad485737a20f0e818edbb3dc3c091e2679986872f java-11-openjdk-javadoc-zip-11.0.7.10-4.el7_8.x86_64.rpm 12b56a59045d9e0c7877d2cde5d82ff665bd0b98fc0fc87afca228ccd37f8be6 java-11-openjdk-jmods-11.0.7.10-4.el7_8.i686.rpm f7b5a8b2b137469210929ce36c6e37f56a328316f1424f3d4d004ec707e0f2ad java-11-openjdk-jmods-11.0.7.10-4.el7_8.x86_64.rpm bd5baed650742e2df7417aaf0faf09a3e1faa3d08ec1eab2b9ef618ffbb5b177 java-11-openjdk-src-11.0.7.10-4.el7_8.i686.rpm d0934f29f7538e5e971ebcc6b0f43f707af2699c32ac38f43aa18cdcb773cdfb java-11-openjdk-src-11.0.7.10-4.el7_8.x86_64.rpm Source: 987ea04496423b636a57918b0a1c49edb1ee626eff745721ea99c0877e64dc67 java-11-openjdk-11.0.7.10-4.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Thu, 30 Apr 2020 19:53:37 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1512 Important CentOS 7 java-1.8.0-openjdk Security Update Message-ID: <20200430195337.GA24470(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1512 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:1512 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ec734e220ac9e35c12a75bfd57bc8edac97facd2df5a1d03ce683d802b4c9fdd java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.i686.rpm f86917a54210c13a63bce8bb807947cdbc7cacc994acdd4c47b7d54e4b891104 java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64.rpm 45ee7e0f2042f58c6053003c233b795f0ad2c8ca26c2035d9332728c85f7341c java-1.8.0-openjdk-accessibility-1.8.0.252.b09-2.el7_8.i686.rpm dcac59f243f853c1da4e105b7c29f1eeb7ce15b9f271a6b36409660fd933be60 java-1.8.0-openjdk-accessibility-1.8.0.252.b09-2.el7_8.x86_64.rpm a9f65a8ea5f82e7465326d90fc08da7bba5e0a22da7a13503afbb430bb9e2634 java-1.8.0-openjdk-demo-1.8.0.252.b09-2.el7_8.i686.rpm 2e644a6a5b06af473181b288624993d4a0d2e821068d437e38da73cfcb5520ad java-1.8.0-openjdk-demo-1.8.0.252.b09-2.el7_8.x86_64.rpm bfe0e5a6ea3a1bc7dfdb62dbd19ba20a3eb4e531c416dd75ec01594ecd71b5d2 java-1.8.0-openjdk-devel-1.8.0.252.b09-2.el7_8.i686.rpm ecfa046985366a978f782b0e252d1b0b8027e231d3a1e89a72e6ad44e2d3d430 java-1.8.0-openjdk-devel-1.8.0.252.b09-2.el7_8.x86_64.rpm ddb19ff50033bc8f749c6974221b072059a020fdd393639f3c97d7b12fb17679 java-1.8.0-openjdk-headless-1.8.0.252.b09-2.el7_8.i686.rpm b21dace04c6c4fb78b7b3109d628f8719909d8bac028d312bfd124d393cbdfb7 java-1.8.0-openjdk-headless-1.8.0.252.b09-2.el7_8.x86_64.rpm 3d2dd4a1793923c8e0ccbf5a99a67d90fafa11076a69860dc3b88897867762eb java-1.8.0-openjdk-javadoc-1.8.0.252.b09-2.el7_8.noarch.rpm 06bb8b6b228e02cfa5c7686b98df704b16779b6fcda71a801d5acb409024228c java-1.8.0-openjdk-javadoc-zip-1.8.0.252.b09-2.el7_8.noarch.rpm 4dd4b147197c43a217f0a1e10ac10ce53346f5419e24476355e6f5dbdbaa63ba java-1.8.0-openjdk-src-1.8.0.252.b09-2.el7_8.i686.rpm 6f8df4b9604f4ec97936c1dbd04b99ede0e209670aac6e34cc4714888a470d29 java-1.8.0-openjdk-src-1.8.0.252.b09-2.el7_8.x86_64.rpm Source: 0482dd5996a91af5de3b7cbad8c1c22db6c3c1c4087e06a125bc13bb8bb824f7 java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Thu, 30 Apr 2020 19:54:04 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1507 Important CentOS 7 java-1.7.0-openjdk Security Update Message-ID: <20200430195404.GA24629(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1507 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:1507 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: fabe67fc9df555934da2d72279096fd3c24b3e2ff47850f5896505890f38a0a4 java-1.7.0-openjdk-1.7.0.261-2.6.22.2.el7_8.x86_64.rpm 03c15876c6039d9417ee91cd8c126e85728890c0197caf2eabe8ead3f490ede3 java-1.7.0-openjdk-accessibility-1.7.0.261-2.6.22.2.el7_8.x86_64.rpm 7575efaca8e9a5cf4f0a1e2248ccae845d3e59aaf7ae927486d923a3546dd141 java-1.7.0-openjdk-demo-1.7.0.261-2.6.22.2.el7_8.x86_64.rpm 2cbb801428afc2eb0a923e443936b9a998896d3b6b34a69344eafd09c4d900af java-1.7.0-openjdk-devel-1.7.0.261-2.6.22.2.el7_8.x86_64.rpm 91d7ddde31bd7f6dee89c8e4c710bf889e2f6e0dadb253de44f76a18c71fbd65 java-1.7.0-openjdk-headless-1.7.0.261-2.6.22.2.el7_8.x86_64.rpm 4116eb9fadf6555249e648b54b721e40488fd224f7f2c3c1ff3a97124b66a2fe java-1.7.0-openjdk-javadoc-1.7.0.261-2.6.22.2.el7_8.noarch.rpm 7b6b6a78638df33409453224096ef0e0201774bc67bdd1d5016f52b034f97e19 java-1.7.0-openjdk-src-1.7.0.261-2.6.22.2.el7_8.x86_64.rpm Source: 13bcf8e890d357b8d0963724df486217403817c19c2ac0c424513440296a4b99 java-1.7.0-openjdk-1.7.0.261-2.6.22.2.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Thu, 30 Apr 2020 19:55:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1511 Important CentOS 7 git Security Update Message-ID: <20200430195506.GA24985(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1511 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:1511 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b051121e45e0afb64ee88bcc0ac8571ff447ddce874c3d1a3fdf0f32c16967bf emacs-git-1.8.3.1-22.el7_8.noarch.rpm c6dd608f4399755307cbebe7a60524042017d162d3d58c7a9cbdf313917a09f7 emacs-git-el-1.8.3.1-22.el7_8.noarch.rpm 15f56ffd76f82179e50c87cdd6be86df7b86092748048012af41bd50848a4a34 git-1.8.3.1-22.el7_8.x86_64.rpm f3fc0ec55423631c0fa8458a3008ed09380b9c5deee9b3e930c32213376d6227 git-all-1.8.3.1-22.el7_8.noarch.rpm e442411450eb36b331314e705343178cfd4d00d3b65d86ceeb47b2b2a7695f8a git-bzr-1.8.3.1-22.el7_8.noarch.rpm 0c17dfb9729fc289765911713f403406c570032f053e439c510b1e0b08291732 git-cvs-1.8.3.1-22.el7_8.noarch.rpm b3d2535112b577451f3bd143e7f7bdf309b44a9d569f6391da00c0ef2ba9a37b git-daemon-1.8.3.1-22.el7_8.x86_64.rpm d49c9b174bd2b055533cbe4f0d552dff471663a2cb2e1d8d49c505083e326109 git-email-1.8.3.1-22.el7_8.noarch.rpm 298ad8b5602c5d19fe31a1ce894f086a3791109c72e8639696d1f86764844948 git-gnome-keyring-1.8.3.1-22.el7_8.x86_64.rpm 7d3e2c231fd82b2391c02dcc67fbfbecb2611fff1ff71d8ee4afcfc754c77581 git-gui-1.8.3.1-22.el7_8.noarch.rpm e2564d303ab9591bf676e2b648962b129494d6cde44fc07cbf35876f7bae6cbc git-hg-1.8.3.1-22.el7_8.noarch.rpm 937e2b3ae022aa61e8f940621deada7b91acab68b8a5d8cf110ab7db2627b168 git-instaweb-1.8.3.1-22.el7_8.noarch.rpm 06e30621b84c138fb4526ab8db767cfbd2a0e27347d31dff51de282b2e28c0f7 gitk-1.8.3.1-22.el7_8.noarch.rpm 002b73881adce7c1097c6eacae3126bbc5a8291bcae3287bfd5c6ebd54d3df8a git-p4-1.8.3.1-22.el7_8.noarch.rpm 06e66cad08604adc984297c26d16efdcdcf5eb24681f34617e602fcdf7d73f42 git-svn-1.8.3.1-22.el7_8.x86_64.rpm 017ae64401d8a4f4feafa909d3272c0c7b56f3985c433ce57983d646bd395e24 gitweb-1.8.3.1-22.el7_8.noarch.rpm d0f32f152e8d5c3f34d79a3eeda56968f86bf1b1cc988434d38f2850aed31cc7 perl-Git-1.8.3.1-22.el7_8.noarch.rpm 5c84268f2a7aa825566a1384008c11015782982fc09c403544758a6334021196 perl-Git-SVN-1.8.3.1-22.el7_8.noarch.rpm Source: a422d7a3c2620fbcde288f89eb7a7ef0f85d16355766e5914648ce75372f3cb9 git-1.8.3.1-22.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 6 Date: Thu, 30 Apr 2020 19:55:14 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1561 Important CentOS 7 python-twisted-web Security Update Message-ID: <20200430195514.GA25077(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1561 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:1561 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c934c963bfda9541fb295807dd5b3491516e30ddca030f9994b16aaf5abf586a python-twisted-web-12.1.0-7.el7_8.x86_64.rpm Source: 1fc7a67cae437978a930e1430f7fd6723180dfe327b2c173719b352e471804ab python-twisted-web-12.1.0-7.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Thu, 30 Apr 2020 19:57:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1489 Important CentOS 7 thunderbird Security Update Message-ID: <20200430195702.GA25220(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1489 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:1489 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c1f729bd646d786b455ced02fdef3ba707209d19abbe2e9248afe1d5a9d619e4 thunderbird-68.7.0-1.el7.centos.x86_64.rpm Source: 089d5be107c79b4090a94a85a7eb10266faa859fe4a4cac0ef4dbd418f1946f8 thunderbird-68.7.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 8 Date: Thu, 30 Apr 2020 19:58:15 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1962 Important CentOS 6 python-twisted-web Security Update Message-ID: <20200430195815.GA25401(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1962 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:1962 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e5325be26650ca5a0802a3b95cb74026f32994e65aa2bd47c8d2ee33f639012d python-twisted-web-8.2.0-6.el6_10.i686.rpm x86_64: d9ae88251c4f8c24ce973b48536a2a12fe5cc447f2fdf868255072bf0f444014 python-twisted-web-8.2.0-6.el6_10.x86_64.rpm Source: 79f6182719d97f904c01fc56312ed76942e6a487e4d255854d8d8a4bcd07ec86 python-twisted-web-8.2.0-6.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 9 Date: Thu, 30 Apr 2020 19:58:47 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:1982 CentOS 6 tzdata BugFix Update Message-ID: <20200430195847.GA25560(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:1982 Upstream details at : https://access.redhat.com/errata/RHBA-2020:1982 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 40bd5ea9365a4b62cf62983819ffbfc0b3cf796bb73c84738476457e3dc9ca8c tzdata-2020a-1.el6.noarch.rpm 35cc464cff218e7bd57f1f0583ec6f5f6228348d5dfa8cf319f2965b86685499 tzdata-java-2020a-1.el6.noarch.rpm x86_64: 40bd5ea9365a4b62cf62983819ffbfc0b3cf796bb73c84738476457e3dc9ca8c tzdata-2020a-1.el6.noarch.rpm 35cc464cff218e7bd57f1f0583ec6f5f6228348d5dfa8cf319f2965b86685499 tzdata-java-2020a-1.el6.noarch.rpm Source: 4e839c9ed8072332b875d17f7d54305a938996f3304808adafb0f455627adf13 tzdata-2020a-1.el6.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 183, Issue 1 ***********************************************

1 0

Diagnosing IPv6 routing
by Kenneth Porter 30 Apr '20

30 Apr '20

I just got 50 Mbps symmetric fiber from AT&T and it includes a /56 of IPv6 addresses, replacing a much slower ADSL line. I never tried to get IPv6 working on the old connection. I'm using CentOS 7 as a gateway and it's worked great for several versions for IPv4. I'm not seeing any IPv6 default route on the WAN interface. I suspect I'm not getting route announcements. I think I have all the IPv6 variables in ifcfg-em2 set right. But I do notice that the accept_ra file in proc for that interface has value 1, not 2. Changing it to 2 doesn't change anything, though. No route appears. While I wait for an answer to my trouble ticket, is there some way to verify that I'm not receiving any RA packets? Is there a way to force a solicitation for one? Is there a tcpdump invocation I can use to watch for them? Are there log messages that will tell me when an RA has been seen and added to the routing table or ignored?

3 11

INITRD_MODULES
by Jerry Geis 29 Apr '20

29 Apr '20

I am trying to take a CentOS 7 img and get hyperv to boot. First step. qemu-img convert "CentOS7.img" -O vhdx -o subformat=dynamic "CentOS7.vhdx" after adding new hyper-v I get dracut-timeout... So doing some searching it says add hv_vmbus hv_netvsc hv_storvsc to INITRD_MODULES. which doesnt really exist any more in CentOS 7. I did find /etc/dracut.conf and add_drivers... I uncommented the line for '#add_drivers += "" ' added the above modules and then ran: grub2-mkconfig -o /boot/grub2/grub.cfg Then redid the convert above... Hyper-V still gives me dracut-timeout errors. Thoughts ? Did I miss something ? Thanks Jerry

2 5

Tomcat or what on CentOS 8?
by Simon Matter 29 Apr '20

29 Apr '20

Hi, We're running some web apps on CentOS 6 on Tomcat 6 shipped by the distribution. As time goes by we'd like to move on to CentOS 8 and Tomcat 9 or whatever is appropriate. My question is, what do others use now that Tomcat is not shipped anymore with CentOS? Do you run some JBoss/WildFly instead or still running Tomcat? And, how do you install/manage those installations. Do you have RPM packaged versions or fiddle with tarballs? Since this is a quite standard setup for web apps I'm really wondering how everybody is doing it these days? Thanks, Simon

5 7

Checksums in Distribution Directories
by david 29 Apr '20

29 Apr '20

Folks While trying to automate a download of the ISO files, I ran into inconsistencies with the method of checksums. I was trying to use the checksum values to validate my download. At least in one mirror (mirrors.sonic.net) Centos 7 uses a file called sha256sum.txt containing: 087a5743dc6fd6706d9b961b8147423ddc029451b938364c760d75440eb7be14 CentOS-7-x86_64-DVD-2003.iso 4120aff542c2f9a30bcf90d4d79e39511e5d9eabdf202566a94ff24ea7f0974c CentOS-7-x86_64-Everything-2003.iso 659691c28a0e672558b003d223f83938f254b39875ee7559d1a4a14c79173193 CentOS-7-x86_64-Minimal-2003.iso 101bc813d2af9ccf534d112cbe8670e6d900425b297d1a4d2529c5ad5f226372 CentOS-7-x86_64-NetInstall-2003.iso 3febddab1498f940e3127f2f5e1056d6fef57fcd559d5b70ff1bfa55a444f176 CentOS-7-x86_64-LiveGNOME-2003.iso 92be566a5b1d2aa62acf2e4ab01ba91420e7170cdb21e2e190dd1dafcb6a8c94 CentOS-7-x86_64-LiveKDE-2003.iso Centos 8 uses a file called CHECKSUM containing: # CentOS-8.1.1911-x86_64-boot.iso: 625999872 bytes SHA256 (CentOS-8.1.1911-x86_64-boot.iso) = 7fea13202bf2f26989df4175aace8fdc16e1137f7961c33512cbfad844008948 # CentOS-8.1.1911-x86_64-dvd1.iso: 7554990080 bytes SHA256 (CentOS-8.1.1911-x86_64-dvd1.iso) = 3ee3f4ea1538e026fff763e2b284a6f20b259d91d1ad5688f5783a67d279423b While these are fairly easy to understand as a human, a script is burdened with the job of guessing the file name of the checksum file, and then decoding the format. I don't know if this method is used on all mirrors. Would it be too much to ask that there be one format across the distributions. I suspect that SHA256 is going to be an acceptable digest for a few years. David

1 0

Network Interfaces Issue
by Jared Jacob 28 Apr '20

28 Apr '20

I have two network interfaces configured on a server. I would like both of them to be configured to start on boot, but when I enable the second interface to start on boot I do not have access to the first network interface. The second interface is a private network and does not allow any communication our or in from any other interfaces. I can start the server with the first network interface being the only one enabled to start at boot and go in and activate the second interface which allows communication on both interfaces, but when they are both enabled to start on boot only the private interface can communicate. I am running Centos 7.7. Thanks in advance for any assistance you can provide. Jared Jacob

2 1

Understanding modularity
by Simon Matter 28 Apr '20

28 Apr '20

Hi, I've read the Fedora modularity docs but am still missing the big picture somehow. Hope someone can clarify things for me. What I'm most wondering: does modularity have any influence on the RPM packages at all. I mean, is there anything inside a RPM package which says it belongs to a module or it has a special function in a module? >From what I understand the RPMs are just completely normal packages and only YUM/DNF knows from some metadata that an RPM belongs to a module. Is that corrent? Thanks for any insights, Simon

3 5

CentOS-announce Digest, Vol 182, Issue 3
by centos-announce-request＠centos.org 28 Apr '20

28 Apr '20

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 (2003) on the x86_64 Architecture (Johnny Hughes) 2. Release for CentOS Linux 7 (2003) on armhfp aarch64 i386 ppc64 ppc64le and power9 (Pablo Sebasti?n Greco) 3. CESA-2020:1488 Important CentOS 6 thunderbird Security Update (Johnny Hughes) 4. CESA-2020:1429 Important CentOS 6 firefox Security Update (Johnny Hughes) 5. CESA-2020:1403 Important CentOS 6 qemu-kvm Security Update (Johnny Hughes) 6. CESA-2020:1508 Important CentOS 6 java-1.7.0-openjdk Security Update (Johnny Hughes) 7. CESA-2020:1506 Important CentOS 6 java-1.8.0-openjdk Security Update (Johnny Hughes) 8. CESA-2020:1524 Important CentOS 6 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 27 Apr 2020 05:04:53 -0500 From: Johnny Hughes <johnny(a)centos.org> To: CentOS-Announce <centos-announce(a)centos.org> Subject: [CentOS-announce] Release for CentOS Linux 7 (2003) on the x86_64 Architecture Message-ID: <e9ae4414-edb9-7ac0-06fa-9013e6777dfd(a)centos.org> Content-Type: text/plain; charset="utf-8" Release for CentOS Linux 7 (2003) 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.8 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: 087a5743dc6fd6706d9b961b8147423ddc029451b938364c760d75440eb7be14 CentOS-7-x86_64-DVD-2003.iso 4120aff542c2f9a30bcf90d4d79e39511e5d9eabdf202566a94ff24ea7f0974c CentOS-7-x86_64-Everything-2003.iso 659691c28a0e672558b003d223f83938f254b39875ee7559d1a4a14c79173193 CentOS-7-x86_64-Minimal-2003.iso 101bc813d2af9ccf534d112cbe8670e6d900425b297d1a4d2529c5ad5f226372 CentOS-7-x86_64-NetInstall-2003.iso 3febddab1498f940e3127f2f5e1056d6fef57fcd559d5b70ff1bfa55a444f176 CentOS-7-x86_64-LiveGNOME-2003.iso 92be566a5b1d2aa62acf2e4ab01ba91420e7170cdb21e2e190dd1dafcb6a8c94 CentOS-7-x86_64-LiveKDE-2003.iso Information for the torrent files and sums are available at http://mirror.centos.org/centos/7/isos/x86_64 -------- Additional Images The Cloud images are posted here: https://cloud.centos.org/centos/7/images/ The container, Vagrant, 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 _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce

1 0

RHEL 8.2
by Thomas Stephen Lee 28 Apr '20

28 Apr '20

Got RHEL 8.2 today. https://www.redhat.com/en/about/press-releases/red-hat-delivers-force-multi… . thanks -- Lee

1 0

Weird problem with my app and blocked ports
by david allan finch 27 Apr '20

27 Apr '20

Hi, Not sure where to look for my issue. I hope someone can point me in the correct place. I have been working on a bespoke server package for more than twenty years. It was originally developed on Solaris (Unix), was ported to windows and now ported to Linux for the last five years. This system is in live production under heavy usage everyday. The servers are all written in C++ and use a version of encoded ONC RPC (without bind) to communicate server to server and java for the client displays. Since about six months ago, I have been experiencing a weird issue with the sockets on my test system. My dev env is on CentsOS 7.7 running on Virtualbox 6 on a Windows 10 machine. The VM has bridge networks interface to my lan using a static IP. Our servers talk on the interface on Virtualbox to other servers possibly on other hosts via my real network. All works well until I do a massive relability and soak test of one of our servers. I send a series of large data message every 15 second or so to one of our servers (say Y), expecting that I might see a lockup and bugs to fix etc in that server Y. But instead of Y server failing what I see is the well know port that our system uses (ie 2323) for name lookup requests, block and I then see timouts of on that socket (this is a different server say Z). All the others servers (A..Y) get timeouts communicating to Z from then on. This effect I don't see on other OSs with similar tests. If I systemctl stop our service and then restart the servers A-Y start but continue to fail with timeouts to Z. Reboot does the same. I have change the well know port to 23232 and it still fails. I have run the servers in the systemctl as a new user and it still fails. As a mad idea I change the interface so the servers talk on the virtual box internal network and the system returns to operation. Also if I run the servers manually on the command line as my user account they work. It kind of looks like a firewall/anti-virus/tojan block rule on our well known port 2323 or Z server. As far as I can see the CentOS firewall is not running. The Norton firewall on my PC does not seam to have an rules or warning about my virtualbox ips or ports. Our servers don't cache any ip data. The first time this happened I was too busy to look at it and just restored the VM from a backup. It then happened a second time a month ago and spend a day looking at the issue found nothing and restored from backup again, putting it down to the centos security update I have just done earlier that day. It happen for a third time on Friday (24th). This time I have done no updates since the last restore so I can be sure its not a centos update. I checked again could find nothing wrong, did all the updates and still nothing worked. Investigated all the firewall and interfaces and it works. I need the system to work on the external bridge network interface and I can't think of anything else todo. The socket error messages are just Timeout, there is nothing in dmesg, or journal that suggests anything. I am now a complete lost to what is happening and why. Regards David Finch

1 0

libGLU.so.1
by Art Edwards 27 Apr '20

27 Apr '20

I'm trying to download the rpm that will install this library. I do not see it on the CentOS site. Any help would be appreciated. Art Edwards

2 1

Weird bug in 389 Directory Server : no spaces in admin console (CentOS 7)
by Nicolas Kovacs 26 Apr '20

26 Apr '20

Hi, I'm currently setting up 389 Directory Server on a server running CentOS 7, and I have a weird and somehow showstopping bug. All the spaces are suddenly missing in the admin console. Here's a screenshot so you can get the idea : https://www.microlinux.fr/download/389-admin-console-2020.png So instead of "Standard branch for configuration information", I get "Standardbranchforconfigurationinformation", "Secure connection" reads "Secureconnection", etc. I tried to add a user in my directory, with "Nicolas Kovacs" in the "Common Name" field, but instead of "Nicolas Kovacs" I get "NicolasKovacs" and there is no way to add space between the first and the last name. Last year I made the same setup and even wrote a series of blog articles about 389 DS on CentOS 7, and everything worked perfectly. Here's the screenshot from last year's setup: https://www.microlinux.fr/download/389-admin-console-2019.png Any idea what's going on here ? Cheers, Niki -- 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 8

Open-source software to file IRS form 941 electronically
by H 24 Apr '20

24 Apr '20

Is there any such software available? Does not need to include paying payroll taxes but only the filing of form 941.

1 0

Looking for C8 AMD help
by Pete Geenhuizen 24 Apr '20

24 Apr '20

I'm migrating from C7 to C8. I'm currently using autofs, but alas autofs has been dropped in C8 for the AMD automounter. I have some very ancient knowledge of AMD, I used it when it was first introduced many years ago on Solaris and moved to Sun's automounter when it was introduced. So now it's back to square one. I used automount2amd to convert one of my existing maps, included it in the amd.conf file and tried it out. I don't get any syntax errors so I guess that the map syntax is correct, but amd fails to mount the remote filesystem and generates these errors in messages. Apr 23 16:04:29 localhost.my.domain amd[19389]: matched default selectors "type:=nfs;opts:=rw,grpid,nosuid,utimeout=600" Apr 23 16:04:29 localhost.my.domain amd[19389]: key new: map selector host (=localhost) did not match remotehost Apr 23 16:04:29 localhost.my.domain amd[19389]: merge rem/opts "rw,grpid,nosuid,utimeout=600" add "fstype=nfs,vers=4,soft,intr" => "rw,grpid,nosuid,utimeout=600,fstype=nfs,vers=4,soft,intr" Apr 23 16:04:29 localhost.my.domain amd[19389]: Map entry host==remotehost;type:=link;fs:=/export/data/& for /repo/new did not match Apr 23 16:04:29 localhost.my.domain amd[19389]: merge rem/opts "rw,grpid,nosuid,utimeout=600" add "fstype=nfs,vers=4,soft,intr" => "rw,grpid,nosuid,utimeout=600,fstype=nfs,vers=4,soft,intr" Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: returning NFS(4,tcp) on host remotehost.my.domain Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: NFS(4,udp) failed for remotehost.my.domain: RPC: Unable to receive Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: NFS(3,udp) failed for remotehost.my.domain: RPC: Unable to receive Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: NFS(2,udp) failed for remotehost.my.domain: RPC: Unable to receive Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: returning NFS(0,udp) on host remotehost.my.domain Apr 23 16:04:29 localhost.my.domain amd[19389]: Using NFS version 4, protocol tcp on host remotehost.my.domain Apr 23 16:04:29 localhost.my.domain amd[19389]: changing remotehost.my.domain's ping value from 30 to 30 Apr 23 16:04:29 localhost.my.domain amd[19389]: Trying mount of remotehost:/export/data/& on /.automount/remotehost/export/data/& fstype nfs mount_type non-autofs Apr 23 16:04:31 localhost.my.domain amd[19389]: Trying mount of remotehost:/export/data/& on /.automount/remotehost/export/data/& fstype nfs mount_type non-autofs Apr 23 16:04:32 localhost.my.domain amd[19389]: file server remotehost.my.domain, type nfs, state starts down Apr 23 16:04:49 localhost.my.domain amd[19389]: "/repo/new" on //nil// timed out (flags 0x20) I'm using firewalld on both hosts and allow these services mountd nfs rpc-bind and protocols 111/tcp and 111/udp all of which allow autofs to work flawlessly, I've tried turning firewalld off which made no difference. Here's my /etc/amd.remote file looks like new \ -addopts:=fstype=nfs,vers=4,soft,intr \ host==remotehost;type:=link;fs:=/export/data/& \ rhost:=remotehost;rfs:=/export/data/& Any assistance in pointing me in the right direction would be greatly appreciated. Pete -- Unencumbered by the thought process. -- Click and Clack the Tappet brothers -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 2

CentOS repo question
by Tony Molloy 23 Apr '20

23 Apr '20

Hi All, I've just installed a test laptop with CentOS Stream 8.1. I notice that the default install has both CentOS-Base and CentOS-Base-Appstream repos enabled. Is that necessary, or should I just have the Appstream repos enabled. The reason I'm asking is because I'm having trouble updating the installation. The problem seems to be some installed rpms seem to depend on updates from the CentOS-Base repos and others seem to depend on similar updates from the CentOS-Base-Appstream repos and you can't install both. A typical error looks like this. cannot install both qt5-qttools-common-5.12.5-1.el8.0.1.noarch and qt5-qttools-common-5.11.1-9.el8.noarch qt5-qttools-common-5.11.1-9.el8.noarch is from CentOS-Base qt5-qttools-common-5.12.5-1.el8.0.1.noarch is from CentOS-Base-Appstream So updating some installed rpm depends on updating to the Appstream version of qt5-qttools and some other installed rpm depends on the original CentOS-Base version of qt5-qttools. I've played around with --allowerasing --best and --nobest but still can't get a clean update. Thanks, Tony -- Tony Molloy <tony.molloy(a)ul.ie> Home

2 4

slow performance on company production server I need help
by Christopher Wensink 22 Apr '20

22 Apr '20

Hello Everyone, Since rebooting my Centos 6.10 Openvz server "daisy" yesterday, I am getting horrible system performance. /var/log/messages is full of HDIO_GET_IDENTITY failed for /dev/sdb. The latest entries look like this: Apr 22 08:51:32 daisy kernel: [141224.655699] CT: 1005: stopped Apr 22 08:55:04 daisy ata_id[21513]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22 09:00:05 daisy ata_id[21584]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22 09:05:02 daisy ata_id[21644]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22 09:10:01 daisy ata_id[22282]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22 09:11:49 daisy kernel: [142441.721065] INFO: task hdparm:22246 blocked for more than 120 seconds. Apr 22 09:11:49 daisy kernel: [142441.721083] Not tainted 2.6.32-042stab142.1 #1 Apr 22 09:11:49 daisy kernel: [142441.721093] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 22 09:11:49 daisy kernel: [142441.721109] hdparm D ffff88000c778300 0 22246 20845 0 0x00000080 Apr 22 09:11:49 daisy kernel: [142441.721115] ffff88006654bcb8 0000000000000086 ffffffff8114f130 ffff88002821fa40 Apr 22 09:11:49 daisy kernel: [142441.721121] ffff88000004d238 ffff88006654bd70 ffff88006654bc88 ffffea00016ab7c0 Apr 22 09:11:49 daisy kernel: [142441.721125] ffff88011a707000 ffff880028321168 000000000001b7ea 0000816be9b3faa2 Apr 22 09:11:49 daisy kernel: [142441.721130] Call Trace: Apr 22 09:11:49 daisy kernel: [142441.721139] [<ffffffff8114f130>] ? sync_page+0x0/0x50 Apr 22 09:11:49 daisy kernel: [142441.721144] [<ffffffff8107c851>] ? update_curr+0xe1/0x1f0 Apr 22 09:11:49 daisy kernel: [142441.721149] [<ffffffff81566c55>] schedule_timeout+0x215/0x2f0 Apr 22 09:11:49 daisy kernel: [142441.721155] [<ffffffff81067432>] ? check_preempt_curr+0x82/0xa0 Apr 22 09:11:49 daisy kernel: [142441.721159] [<ffffffff815669b4>] wait_for_completion+0xe4/0x120 Apr 22 09:11:49 daisy kernel: [142441.721162] [<ffffffff81071ce0>] ? default_wake_function+0x0/0x20 Apr 22 09:11:49 daisy kernel: [142441.721167] [<ffffffff815694db>] ? _spin_unlock_bh+0x1b/0x20 Apr 22 09:11:49 daisy kernel: [142441.721172] [<ffffffff811f98d8>] sync_inodes_sb_ub+0xa8/0x1d0 Apr 22 09:11:49 daisy kernel: [142441.721176] [<ffffffff8114fa6f>] ? filemap_fdatawait+0x2f/0x40 Apr 22 09:11:49 daisy kernel: [142441.721181] [<ffffffff81200f85>] __sync_filesystem+0x95/0xa0 Apr 22 09:11:49 daisy kernel: [142441.721184] [<ffffffff8120151d>] sync_filesystems+0x30d/0x350 Apr 22 09:11:49 daisy kernel: [142441.721188] [<ffffffff812016e5>] sys_sync+0x155/0x1a0 Apr 22 09:11:49 daisy kernel: [142441.721192] [<ffffffff81571424>] system_call_fastpath+0x22/0x3a Apr 22 09:13:49 daisy kernel: [142561.721069] INFO: task hdparm:22246 blocked for more than 120 seconds. Apr 22 09:13:49 daisy kernel: [142561.721087] Not tainted 2.6.32-042stab142.1 #1 Apr 22 09:13:49 daisy kernel: [142561.721096] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 22 09:13:49 daisy kernel: [142561.721112] hdparm D ffff88000c778300 0 22246 20845 0 0x00000080 Apr 22 09:13:49 daisy kernel: [142561.721118] ffff88006654bcb8 0000000000000086 ffffffff8114f130 ffff88002821fa40 Apr 22 09:13:49 daisy kernel: [142561.721123] ffff88000004d238 ffff88006654bd70 ffff88006654bc88 ffffea00016ab7c0 Apr 22 09:13:49 daisy kernel: [142561.721128] ffff88011a707000 ffff880028321168 000000000001b7ea 0000816be9b3faa2 Apr 22 09:13:49 daisy kernel: [142561.721133] Call Trace: Apr 22 09:13:49 daisy kernel: [142561.721142] [<ffffffff8114f130>] ? sync_page+0x0/0x50 Apr 22 09:13:49 daisy kernel: [142561.721148] [<ffffffff8107c851>] ? update_curr+0xe1/0x1f0 Apr 22 09:13:49 daisy kernel: [142561.721153] [<ffffffff81566c55>] schedule_timeout+0x215/0x2f0 Apr 22 09:13:49 daisy kernel: [142561.721158] [<ffffffff81067432>] ? check_preempt_curr+0x82/0xa0 Apr 22 09:13:49 daisy kernel: [142561.721162] [<ffffffff815669b4>] wait_for_completion+0xe4/0x120 Apr 22 09:13:49 daisy kernel: [142561.721166] [<ffffffff81071ce0>] ? default_wake_function+0x0/0x20 Apr 22 09:13:49 daisy kernel: [142561.721170] [<ffffffff815694db>] ? _spin_unlock_bh+0x1b/0x20 Apr 22 09:13:49 daisy kernel: [142561.721176] [<ffffffff811f98d8>] sync_inodes_sb_ub+0xa8/0x1d0 Apr 22 09:13:49 daisy kernel: [142561.721180] [<ffffffff8114fa6f>] ? filemap_fdatawait+0x2f/0x40 Apr 22 09:13:49 daisy kernel: [142561.721184] [<ffffffff81200f85>] __sync_filesystem+0x95/0xa0 Apr 22 09:13:49 daisy kernel: [142561.721188] [<ffffffff8120151d>] sync_filesystems+0x30d/0x350 Apr 22 09:13:49 daisy kernel: [142561.721192] [<ffffffff812016e5>] sys_sync+0x155/0x1a0 Apr 22 09:13:49 daisy kernel: [142561.721196] [<ffffffff81571424>] system_call_fastpath+0x22/0x3a Apr 22 09:15:06 daisy ata_id[22299]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22 09:15:49 daisy kernel: [142681.721085] INFO: task hdparm:22246 blocked for more than 120 seconds. Apr 22 09:15:49 daisy kernel: [142681.721104] Not tainted 2.6.32-042stab142.1 #1 Apr 22 09:15:49 daisy kernel: [142681.721113] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 22 09:15:49 daisy kernel: [142681.721129] hdparm D ffff88000c778300 0 22246 20845 0 0x00000080 Apr 22 09:15:49 daisy kernel: [142681.721136] ffff88006654bcb8 0000000000000086 ffffffff8114f130 ffff88002821fa40 Apr 22 09:15:49 daisy kernel: [142681.721141] ffff88000004d238 ffff88006654bd70 ffff88006654bc88 ffffea00016ab7c0 Apr 22 09:15:49 daisy kernel: [142681.721146] ffff88011a707000 ffff880028321168 000000000001b7ea 0000816be9b3faa2 Apr 22 09:15:49 daisy kernel: [142681.721150] Call Trace: Apr 22 09:15:49 daisy kernel: [142681.721160] [<ffffffff8114f130>] ? sync_page+0x0/0x50 Apr 22 09:15:49 daisy kernel: [142681.721166] [<ffffffff8107c851>] ? update_curr+0xe1/0x1f0 Apr 22 09:15:49 daisy kernel: [142681.721172] [<ffffffff81566c55>] schedule_timeout+0x215/0x2f0 Apr 22 09:15:49 daisy kernel: [142681.721178] [<ffffffff81067432>] ? check_preempt_curr+0x82/0xa0 Apr 22 09:15:49 daisy kernel: [142681.721182] [<ffffffff815669b4>] wait_for_completion+0xe4/0x120 Apr 22 09:15:49 daisy kernel: [142681.721185] [<ffffffff81071ce0>] ? default_wake_function+0x0/0x20 Apr 22 09:15:49 daisy kernel: [142681.721190] [<ffffffff815694db>] ? _spin_unlock_bh+0x1b/0x20 Apr 22 09:15:49 daisy kernel: [142681.721196] [<ffffffff811f98d8>] sync_inodes_sb_ub+0xa8/0x1d0 Apr 22 09:15:49 daisy kernel: [142681.721200] [<ffffffff8114fa6f>] ? filemap_fdatawait+0x2f/0x40 Apr 22 09:15:49 daisy kernel: [142681.721204] [<ffffffff81200f85>] __sync_filesystem+0x95/0xa0 Apr 22 09:15:49 daisy kernel: [142681.721208] [<ffffffff8120151d>] sync_filesystems+0x30d/0x350 Apr 22 09:15:49 daisy kernel: [142681.721212] [<ffffffff812016e5>] sys_sync+0x155/0x1a0 Apr 22 09:15:49 daisy kernel: [142681.721217] [<ffffffff81571424>] system_call_fastpath+0x22/0x3a Apr 22 09:17:49 daisy kernel: [142801.721064] INFO: task hdparm:22246 blocked for more than 120 seconds. Apr 22 09:17:49 daisy kernel: [142801.721082] Not tainted 2.6.32-042stab142.1 #1 Apr 22 09:17:49 daisy kernel: [142801.721091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 22 09:17:49 daisy kernel: [142801.721107] hdparm D ffff88000c778300 0 22246 20845 0 0x00000080 Apr 22 09:17:49 daisy kernel: [142801.721114] ffff88006654bcb8 0000000000000086 ffffffff8114f130 ffff88002821fa40 Apr 22 09:17:49 daisy kernel: [142801.721119] ffff88000004d238 ffff88006654bd70 ffff88006654bc88 ffffea00016ab7c0 Apr 22 09:17:49 daisy kernel: [142801.721124] ffff88011a707000 ffff880028321168 000000000001b7ea 0000816be9b3faa2 Apr 22 09:17:49 daisy kernel: [142801.721128] Call Trace: Apr 22 09:17:49 daisy kernel: [142801.721137] [<ffffffff8114f130>] ? sync_page+0x0/0x50 Apr 22 09:17:49 daisy kernel: [142801.721143] [<ffffffff8107c851>] ? update_curr+0xe1/0x1f0 Apr 22 09:17:49 daisy kernel: [142801.721149] [<ffffffff81566c55>] schedule_timeout+0x215/0x2f0 Apr 22 09:17:49 daisy kernel: [142801.721154] [<ffffffff81067432>] ? check_preempt_curr+0x82/0xa0 Apr 22 09:17:49 daisy kernel: [142801.721158] [<ffffffff815669b4>] wait_for_completion+0xe4/0x120 Apr 22 09:17:49 daisy kernel: [142801.721162] [<ffffffff81071ce0>] ? default_wake_function+0x0/0x20 Apr 22 09:17:49 daisy kernel: [142801.721166] [<ffffffff815694db>] ? _spin_unlock_bh+0x1b/0x20 Apr 22 09:17:49 daisy kernel: [142801.721172] [<ffffffff811f98d8>] sync_inodes_sb_ub+0xa8/0x1d0 Apr 22 09:17:49 daisy kernel: [142801.721176] [<ffffffff8114fa6f>] ? filemap_fdatawait+0x2f/0x40 Apr 22 09:17:49 daisy kernel: [142801.721180] [<ffffffff81200f85>] __sync_filesystem+0x95/0xa0 Apr 22 09:17:49 daisy kernel: [142801.721184] [<ffffffff8120151d>] sync_filesystems+0x30d/0x350 Apr 22 09:17:49 daisy kernel: [142801.721188] [<ffffffff812016e5>] sys_sync+0x155/0x1a0 Apr 22 09:17:49 daisy kernel: [142801.721192] [<ffffffff81571424>] system_call_fastpath+0x22/0x3a Apr 22 09:20:01 daisy ata_id[22405]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22 09:21:49 daisy kernel: [143041.721494] INFO: task hdparm:22246 blocked for more than 120 seconds. Apr 22 09:21:49 daisy kernel: [143041.721512] Not tainted 2.6.32-042stab142.1 #1 Apr 22 09:21:49 daisy kernel: [143041.721522] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 22 09:21:49 daisy kernel: [143041.721691] hdparm D ffff88000c778300 0 22246 20845 0 0x00000080 Apr 22 09:21:49 daisy kernel: [143041.721697] ffff88006654bcc8 0000000000000086 ffff88006654bc58 ffffffff810098af Apr 22 09:21:49 daisy kernel: [143041.721702] ffff880028200000 000000001a42f238 ffff8800110101c0 ffff88011a42f200 Apr 22 09:21:49 daisy kernel: [143041.721706] ffff88006654bc68 ffffffff8107bbfe ffff8800110101c0 0000000000000000 Apr 22 09:21:49 daisy kernel: [143041.721711] Call Trace: Apr 22 09:21:49 daisy kernel: [143041.721720] [<ffffffff810098af>] ? __switch_to+0x16f/0x470 Apr 22 09:21:49 daisy kernel: [143041.721726] [<ffffffff8107bbfe>] ? finish_task_switch+0xce/0x120 Apr 22 09:21:49 daisy kernel: [143041.721730] [<ffffffff8107c851>] ? update_curr+0xe1/0x1f0 Apr 22 09:21:49 daisy kernel: [143041.721735] [<ffffffff81566c55>] schedule_timeout+0x215/0x2f0 Apr 22 09:21:49 daisy kernel: [143041.721739] [<ffffffff815669b4>] wait_for_completion+0xe4/0x120 Apr 22 09:21:49 daisy kernel: [143041.721743] [<ffffffff81071ce0>] ? default_wake_function+0x0/0x20 Apr 22 09:21:49 daisy kernel: [143041.721747] [<ffffffff815694db>] ? _spin_unlock_bh+0x1b/0x20 Apr 22 09:21:49 daisy kernel: [143041.721753] [<ffffffff811f9773>] writeback_inodes_sb_nr_ub+0x83/0xb0 Apr 22 09:21:49 daisy kernel: [143041.721757] [<ffffffff811f9806>] writeback_inodes_sb_ub+0x46/0x50 Apr 22 09:21:49 daisy kernel: [143041.721762] [<ffffffff81200f38>] __sync_filesystem+0x48/0xa0 Apr 22 09:21:49 daisy kernel: [143041.721765] [<ffffffff8120151d>] sync_filesystems+0x30d/0x350 Apr 22 09:21:49 daisy kernel: [143041.721769] [<ffffffff812016d8>] sys_sync+0x148/0x1a0 Apr 22 09:21:49 daisy kernel: [143041.721773] [<ffffffff81571424>] system_call_fastpath+0x22/0x3a Apr 22 09:23:49 daisy kernel: [143161.721064] INFO: task hdparm:22246 blocked for more than 120 seconds. Apr 22 09:23:49 daisy kernel: [143161.721169] Not tainted 2.6.32-042stab142.1 #1 Apr 22 09:23:49 daisy kernel: [143161.721259] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 22 09:23:49 daisy kernel: [143161.721430] hdparm D ffff88000c778300 0 22246 20845 0 0x00000080 Apr 22 09:23:49 daisy kernel: [143161.721437] ffff88006654bcc8 0000000000000086 ffff88006654bc58 ffffffff810098af Apr 22 09:23:49 daisy kernel: [143161.721442] ffff880028200000 000000001a42f238 ffff8800110101c0 ffff88011a42f200 Apr 22 09:23:49 daisy kernel: [143161.721447] ffff88006654bc68 ffffffff8107bbfe ffff8800110101c0 0000000000000000 Apr 22 09:23:49 daisy kernel: [143161.721451] Call Trace: Apr 22 09:23:49 daisy kernel: [143161.721460] [<ffffffff810098af>] ? __switch_to+0x16f/0x470 Apr 22 09:23:49 daisy kernel: [143161.721466] [<ffffffff8107bbfe>] ? finish_task_switch+0xce/0x120 Apr 22 09:23:49 daisy kernel: [143161.721470] [<ffffffff8107c851>] ? update_curr+0xe1/0x1f0 Apr 22 09:23:49 daisy kernel: [143161.721475] [<ffffffff81566c55>] schedule_timeout+0x215/0x2f0 Apr 22 09:23:49 daisy kernel: [143161.721479] [<ffffffff815669b4>] wait_for_completion+0xe4/0x120 Apr 22 09:23:49 daisy kernel: [143161.721483] [<ffffffff81071ce0>] ? default_wake_function+0x0/0x20 Apr 22 09:23:49 daisy kernel: [143161.721487] [<ffffffff815694db>] ? _spin_unlock_bh+0x1b/0x20 Apr 22 09:23:49 daisy kernel: [143161.721493] [<ffffffff811f9773>] writeback_inodes_sb_nr_ub+0x83/0xb0 Apr 22 09:23:49 daisy kernel: [143161.721498] [<ffffffff811f9806>] writeback_inodes_sb_ub+0x46/0x50 Apr 22 09:23:49 daisy kernel: [143161.721502] [<ffffffff81200f38>] __sync_filesystem+0x48/0xa0 Apr 22 09:23:49 daisy kernel: [143161.721506] [<ffffffff8120151d>] sync_filesystems+0x30d/0x350 Apr 22 09:23:49 daisy kernel: [143161.721510] [<ffffffff812016d8>] sys_sync+0x148/0x1a0 Apr 22 09:23:49 daisy kernel: [143161.721514] [<ffffffff81571424>] system_call_fastpath+0x22/0x3a Apr 22 09:25:02 daisy ata_id[22445]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22 09:25:49 daisy kernel: [143281.721066] INFO: task hdparm:22246 blocked for more than 120 seconds. Apr 22 09:25:49 daisy kernel: [143281.721159] Not tainted 2.6.32-042stab142.1 #1 Apr 22 09:25:49 daisy kernel: [143281.721244] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 22 09:25:49 daisy kernel: [143281.721408] hdparm D ffff88000c778300 0 22246 20845 0 0x00000080 Apr 22 09:25:49 daisy kernel: [143281.721415] ffff88006654bcc8 0000000000000086 ffff88006654bc58 ffffffff810098af Apr 22 09:25:49 daisy kernel: [143281.721420] ffff880028200000 000000001a42f238 ffff8800110101c0 ffff88011a42f200 Apr 22 09:25:49 daisy kernel: [143281.721424] ffff88006654bc68 ffffffff8107bbfe ffff8800110101c0 0000000000000000 Apr 22 09:25:49 daisy kernel: [143281.721429] Call Trace: Apr 22 09:25:49 daisy kernel: [143281.721438] [<ffffffff810098af>] ? __switch_to+0x16f/0x470 Apr 22 09:25:49 daisy kernel: [143281.721444] [<ffffffff8107bbfe>] ? finish_task_switch+0xce/0x120 Apr 22 09:25:49 daisy kernel: [143281.721448] [<ffffffff8107c851>] ? update_curr+0xe1/0x1f0 Apr 22 09:25:49 daisy kernel: [143281.721453] [<ffffffff81566c55>] schedule_timeout+0x215/0x2f0 Apr 22 09:25:49 daisy kernel: [143281.721457] [<ffffffff815669b4>] wait_for_completion+0xe4/0x120 Apr 22 09:25:49 daisy kernel: [143281.721461] [<ffffffff81071ce0>] ? default_wake_function+0x0/0x20 Apr 22 09:25:49 daisy kernel: [143281.721465] [<ffffffff815694db>] ? _spin_unlock_bh+0x1b/0x20 Apr 22 09:25:49 daisy kernel: [143281.721471] [<ffffffff811f9773>] writeback_inodes_sb_nr_ub+0x83/0xb0 Apr 22 09:25:49 daisy kernel: [143281.721476] [<ffffffff811f9806>] writeback_inodes_sb_ub+0x46/0x50 Apr 22 09:25:49 daisy kernel: [143281.721480] [<ffffffff81200f38>] __sync_filesystem+0x48/0xa0 Apr 22 09:25:49 daisy kernel: [143281.721484] [<ffffffff8120151d>] sync_filesystems+0x30d/0x350 Apr 22 09:25:49 daisy kernel: [143281.721487] [<ffffffff812016d8>] sys_sync+0x148/0x1a0 Apr 22 09:25:49 daisy kernel: [143281.721492] [<ffffffff81571424>] system_call_fastpath+0x22/0x3a Apr 22 09:27:49 daisy kernel: [143401.721072] INFO: task hdparm:22246 blocked for more than 120 seconds. Apr 22 09:27:49 daisy kernel: [143401.721165] Not tainted 2.6.32-042stab142.1 #1 Apr 22 09:27:49 daisy kernel: [143401.721253] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 22 09:27:49 daisy kernel: [143401.721421] hdparm D ffff88000c778300 0 22246 20845 0 0x00000080 Apr 22 09:27:49 daisy kernel: [143401.721427] ffff88006654bcc8 0000000000000086 ffff88006654bc58 ffffffff810098af Apr 22 09:27:49 daisy kernel: [143401.721432] ffff880028200000 000000001a42f238 ffff8800110101c0 ffff88011a42f200 Apr 22 09:27:49 daisy kernel: [143401.721436] ffff88006654bc68 ffffffff8107bbfe ffff8800110101c0 0000000000000000 Apr 22 09:27:49 daisy kernel: [143401.721441] Call Trace: Apr 22 09:27:49 daisy kernel: [143401.721450] [<ffffffff810098af>] ? __switch_to+0x16f/0x470 Apr 22 09:27:49 daisy kernel: [143401.721456] [<ffffffff8107bbfe>] ? finish_task_switch+0xce/0x120 Apr 22 09:27:49 daisy kernel: [143401.721460] [<ffffffff8107c851>] ? update_curr+0xe1/0x1f0 Apr 22 09:27:49 daisy kernel: [143401.721465] [<ffffffff81566c55>] schedule_timeout+0x215/0x2f0 Apr 22 09:27:49 daisy kernel: [143401.721469] [<ffffffff815669b4>] wait_for_completion+0xe4/0x120 Apr 22 09:27:49 daisy kernel: [143401.721473] [<ffffffff81071ce0>] ? default_wake_function+0x0/0x20 Apr 22 09:27:49 daisy kernel: [143401.721477] [<ffffffff815694db>] ? _spin_unlock_bh+0x1b/0x20 Apr 22 09:27:49 daisy kernel: [143401.721483] [<ffffffff811f9773>] writeback_inodes_sb_nr_ub+0x83/0xb0 Apr 22 09:27:49 daisy kernel: [143401.721487] [<ffffffff811f9806>] writeback_inodes_sb_ub+0x46/0x50 Apr 22 09:27:49 daisy kernel: [143401.721492] [<ffffffff81200f38>] __sync_filesystem+0x48/0xa0 Apr 22 09:27:49 daisy kernel: [143401.721495] [<ffffffff8120151d>] sync_filesystems+0x30d/0x350 Apr 22 09:27:49 daisy kernel: [143401.721499] [<ffffffff812016d8>] sys_sync+0x148/0x1a0 Apr 22 09:27:49 daisy kernel: [143401.721503] [<ffffffff81571424>] system_call_fastpath+0x22/0x3a Apr 22 09:29:49 daisy kernel: [143521.721059] INFO: task hdparm:22246 blocked for more than 120 seconds. Apr 22 09:29:49 daisy kernel: [143521.721158] Not tainted 2.6.32-042stab142.1 #1 Apr 22 09:29:49 daisy kernel: [143521.721245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 22 09:29:49 daisy kernel: [143521.721415] hdparm D ffff88000c778300 0 22246 20845 0 0x00000084 Apr 22 09:29:49 daisy kernel: [143521.721421] ffff88006654bcc8 0000000000000086 ffff88006654bc58 ffffffff810098af Apr 22 09:29:49 daisy kernel: [143521.721426] ffff880028200000 000000001a42f238 ffff8800110101c0 ffff88011a42f200 Apr 22 09:29:49 daisy kernel: [143521.721431] ffff88006654bc68 ffffffff8107bbfe ffff8800110101c0 0000000000000000 Apr 22 09:29:49 daisy kernel: [143521.721436] Call Trace: Apr 22 09:29:49 daisy kernel: [143521.721445] [<ffffffff810098af>] ? __switch_to+0x16f/0x470 Apr 22 09:29:49 daisy kernel: [143521.721451] [<ffffffff8107bbfe>] ? finish_task_switch+0xce/0x120 Apr 22 09:29:49 daisy kernel: [143521.721455] [<ffffffff8107c851>] ? update_curr+0xe1/0x1f0 Apr 22 09:29:49 daisy kernel: [143521.721460] [<ffffffff81566c55>] schedule_timeout+0x215/0x2f0 Apr 22 09:29:49 daisy kernel: [143521.721465] [<ffffffff815669b4>] wait_for_completion+0xe4/0x120 Apr 22 09:29:49 daisy kernel: [143521.721469] [<ffffffff81071ce0>] ? default_wake_function+0x0/0x20 Apr 22 09:29:49 daisy kernel: [143521.721473] [<ffffffff815694db>] ? _spin_unlock_bh+0x1b/0x20 Apr 22 09:29:49 daisy kernel: [143521.721479] [<ffffffff811f9773>] writeback_inodes_sb_nr_ub+0x83/0xb0 Apr 22 09:29:49 daisy kernel: [143521.721483] [<ffffffff811f9806>] writeback_inodes_sb_ub+0x46/0x50 Apr 22 09:29:49 daisy kernel: [143521.721487] [<ffffffff81200f38>] __sync_filesystem+0x48/0xa0 Apr 22 09:29:49 daisy kernel: [143521.721491] [<ffffffff8120151d>] sync_filesystems+0x30d/0x350 Apr 22 09:29:49 daisy kernel: [143521.721495] [<ffffffff812016d8>] sys_sync+0x148/0x1a0 Apr 22 09:29:49 daisy kernel: [143521.721499] [<ffffffff81571424>] system_call_fastpath+0x22/0x3a Apr 22 09:30:04 daisy ata_id[22489]: HDIO_GET_IDENTITY failed for '/dev/sdb' ------------------ I tried running hdparm -tT /dev/sda, but after waiting 5+ minutes for any command output I cancelled it. I am rsyncing the data from this system over to another system now, clearly something is wrong, but I can't tell what. The system is an older AMD Opteron 180 processor (dual core) 4 GB ram, RAID controller with RAID 5 set up with 4x 4TB Western Digital Drives. I rebooted the system day before yesterday, and that's when the timeout messages started pouring into the log. when I run tw_cli /c8 show, all four drives say they are ok [root@daisy cron.daily]# tw_cli /c8 show Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy ------------------------------------------------------------------------------ u0 RAID-5 OK - - 256K 11175.8 Ri ON VPort Status Unit Size Type Phy Encl-Slot Model ------------------------------------------------------------------------------ p0 OK u0 3.63 TB SATA 0 - WDC WD4005FZBX-00K5 p1 OK u0 3.63 TB SATA 1 - WDC WD4005FZBX-00K5 p2 OK u0 3.63 TB SATA 2 - WDC WD4005FZBX-00K5 p3 OK u0 3.63 TB SATA 3 - WDC WD4005FZBX-00K5 Logical Volumes appear active: [root@daisy cron.daily]# lvscan ACTIVE '/dev/vg_daisy/lv_root' [10.89 TiB] inherit ACTIVE '/dev/vg_daisy/lv_swap' [3.88 GiB] inherit ACTIVE '/dev/vg_daisy/lv_home' [20.00 GiB] inherit [root@daisy cron.daily]# [root@daisy cron.daily]# lvmdiskscan /dev/ram0 [ 16.00 MiB] /dev/root [ 10.89 TiB] /dev/ram1 [ 16.00 MiB] /dev/sda1 [ 2.82 TiB] /dev/vg_daisy/lv_swap [ 3.88 GiB] /dev/ram2 [ 16.00 MiB] /dev/vg_daisy/lv_home [ 20.00 GiB] /dev/ram3 [ 16.00 MiB] /dev/sda3 [ 842.87 GiB] /dev/ram4 [ 16.00 MiB] /dev/ram5 [ 16.00 MiB] /dev/ram6 [ 16.00 MiB] /dev/ram7 [ 16.00 MiB] /dev/ram8 [ 16.00 MiB] /dev/ram9 [ 16.00 MiB] /dev/ram10 [ 16.00 MiB] /dev/ram11 [ 16.00 MiB] /dev/ram12 [ 16.00 MiB] /dev/ram13 [ 16.00 MiB] /dev/ram14 [ 16.00 MiB] /dev/ram15 [ 16.00 MiB] /dev/sdb1 [ 1.82 TiB] LVM physical volume /dev/sdc1 [ 500.00 MiB] /dev/sdc2 [ 4.00 TiB] LVM physical volume /dev/sdd1 [ 4.00 TiB] LVM physical volume /dev/sde1 [ 2.91 TiB] LVM physical volume 3 disks 19 partitions 0 LVM physical volume whole disks 4 LVM physical volumes [root@daisy cron.daily]# grub.conf: [root@daisy grub]# cat grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/mapper/vg_daisy-lv_root # initrd /initrd-[generic-]version.img #boot=/dev/sdb default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title OpenVZ (2.6.32-042stab142.1) root (hd0,0) kernel /vmlinuz-2.6.32-042stab142.1 ro root=/dev/mapper/vg_daisy-lv_root rd_NO_LUKS rd_LVM_LV=vg_daisy/lv_swap LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_daisy/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-042stab142.1.img title OpenVZ (2.6.32-042stab141.3) root (hd0,0) kernel /vmlinuz-2.6.32-042stab141.3 ro root=/dev/mapper/vg_daisy-lv_root rd_NO_LUKS rd_LVM_LV=vg_daisy/lv_swap LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_daisy/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-042stab141.3.img title OpenVZ (2.6.32-042stab140.4) root (hd0,0) kernel /vmlinuz-2.6.32-042stab140.4 ro root=/dev/mapper/vg_daisy-lv_root rd_NO_LUKS rd_LVM_LV=vg_daisy/lv_swap LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_daisy/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-042stab140.4.img title OpenVZ (2.6.32-042stab140.1) root (hd0,0) kernel /vmlinuz-2.6.32-042stab140.1 ro root=/dev/mapper/vg_daisy-lv_root rd_NO_LUKS rd_LVM_LV=vg_daisy/lv_swap LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_daisy/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-042stab140.1.img title OpenVZ (2.6.32-042stab139.1) root (hd0,0) kernel /vmlinuz-2.6.32-042stab139.1 ro root=/dev/mapper/vg_daisy-lv_root rd_NO_LUKS rd_LVM_LV=vg_daisy/lv_swap LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_daisy/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-042stab139.1.img title CentOS 6 (2.6.32-754.el6.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32-754.el6.x86_64 ro root=/dev/mapper/vg_daisy-lv_root rd_NO_LUKS rd_LVM_LV=vg_daisy/lv_swap LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_daisy/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-754.el6.x86_64.img ------------- Top is not showing anything out of the ordinary: ---------- [root@daisy grub]# top - 09:41:57 up 1 day, 16:04, 3 users, load average: 5.89, 5.83, 5.43 Tasks: 369 total, 1 running, 368 sleeping, 0 stopped, 0 zombie Cpu(s): 0.2%us, 1.2%sy, 0.0%ni, 25.0%id, 73.5%wa, 0.0%hi, 0.2%si, 0.0%st Mem: 3894628k total, 3861280k used, 33348k free, 95608k buffers Swap: 4063228k total, 34888k used, 4028340k free, 3139272k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1266 root 20 0 0 0 0 D 1.0 0.0 12:27.75 flush-253:0 21041 1153 20 0 3188 1840 1012 D 0.7 0.0 0:00.72 imap 21599 97 20 0 5160 1940 1568 S 0.7 0.0 0:01.06 imap-login 22636 root 20 0 15272 1524 964 R 0.7 0.0 0:00.06 top 1977 root 20 0 2096 644 360 S 0.3 0.0 0:27.92 dovecot 22528 97 20 0 5160 2044 1672 S 0.3 0.1 0:00.35 imap-login 22578 1155 20 0 2904 1528 940 D 0.3 0.0 0:00.22 imap 1 root 20 0 19236 268 136 S 0.0 0.0 0:00.68 init 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd 3 root RT 0 0 0 0 S 0.0 0.0 0:00.04 migration/0 4 root 20 0 0 0 0 S 0.0 0.0 0:01.88 ksoftirqd/0 5 root RT 0 0 0 0 S 0.0 0.0 0:00.00 stopper/0 6 root RT 0 0 0 0 S 0.0 0.0 0:00.19 watchdog/0 7 root RT 0 0 0 0 S 0.0 0.0 0:00.07 migration/1 8 root RT 0 0 0 0 S 0.0 0.0 0:00.00 stopper/1 9 root 20 0 0 0 0 S 0.0 0.0 0:03.17 ksoftirqd/1 10 root RT 0 0 0 0 S 0.0 0.0 0:00.20 watchdog/1 11 root 20 0 0 0 0 S 0.0 0.0 0:07.23 events/0 12 root 20 0 0 0 0 S 0.0 0.0 0:08.55 events/1 13 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events/0 14 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events/1 15 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events_long/0 16 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events_long/1 17 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events_power_ef 18 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events_power_ef 19 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cgroup 20 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper 21 root 20 0 0 0 0 S 0.0 0.0 0:00.01 netns 22 root 20 0 0 0 0 S 0.0 0.0 0:00.00 async/mgr 23 root 20 0 0 0 0 S 0.0 0.0 0:00.00 pm 24 root 20 0 0 0 0 S 0.0 0.0 0:00.29 sync_supers ------------ This is a company production mail server, and I can't find the solution, I need help, as soon as someone is able, thank you!

5 7

nodejs version 14
by Jerry Geis 22 Apr '20

22 Apr '20

Hi All, I was following the instructions for installing nodejs version 14. https://github.com/nodesource/distributions First thing was: curl -sL https://rpm.nodesource.com/setup_14.x | bash - After that : yum -y install nodejs ---> Package nodejs.x86_64 2:12.16.2-1nodesource will be installed --> Finished Dependency Resolution You can see its installing the OLD Version 12. not the 14. ??? Why ? (this errors actually) My repo looks correct for Version 14 not 12.. more /etc/yum.repos.d/nodesource-el7.repo [nodesource] name=Node.js Packages for Enterprise Linux 7 - $basearch baseurl=https://rpm.nodesource.com/pub_14.x/el/7/$basearch failovermethod=priority enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/NODESOURCE-GPG-SIGNING-KEY-EL [nodesource-source] name=Node.js for Enterprise Linux 7 - $basearch - Source baseurl=https://rpm.nodesource.com/pub_14.x/el/7/SRPMS failovermethod=priority enabled=0 gpgkey=file:///etc/pki/rpm-gpg/NODESOURCE-GPG-SIGNING-KEY-EL gpgcheck=1 Thoughts ? did I do something wrong ? Jerry

2 1

CentOOS 8 and libuv
by Adrian van Bloois 20 Apr '20

20 Apr '20

Hi all, Why is libuv-devel missing in CentOS-8? The rpm for libuv is preset but libuv-devel is not there. Adrian -- Adri P. van Bloois "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

3 2

running app panel overflows
by Michael Hennebry 19 Apr '20

19 Apr '20

I'm running Centos 7 with gnome. After 32 running applications, the panel at the bottom overflows. There seems to be no scrolling mechanism. How if at all can I see the overflow? -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

2 1

Re: [CentOS] [Off topic] sending mail from Comcast was: Sendmail not working
by Jason Pyeron 19 Apr '20

19 Apr '20

> -----Original Message----- > From: Tim Evans > Sent: Sunday, April 19, 2020 12:50 PM > > On 4/19/20 12:38 PM, S.Bob wrote: > > > > On 4/19/20 10:36 AM, Tim Evans wrote: > >> On 4/19/20 12:28 PM, S.Bob wrote: > >>> All; > >>> > >>> > >>> I installed sendmail via yum, but if I test it like this: > >>> > >>> > >> > >>> The original message was received at Sun, 19 Apr 2020 10:02:56 -0600 > >>> from localhost [127.0.0.1] > >>> > >>> ----- The following addresses had permanent fatal errors ----- > >>> <sbob(a)quadratum-braccas.com> > >>> (reason: 554 5.7.1 Service unavailable; Client host > >>> [50.243.150.81] blocked using xbl.spamhaus.org.rbl.local; > >>> https://www.spamhaus > >>> .org/query/ip/50.243.150.81) > >> > >> Is 50.243.150.81 your system's IP address? If so, as this shows, that > >> IP is on spamhaus' blacklist of addresses. Thus, your sendmail is > >> working fine. Problem is elsewhere. > >> > >> anything I can do to fix it? > > Assuming this is your IP address, visit https://www.spamhaus.org/lookup/ > and request that it be removed from the blacklisted IP's. > > However, looking at the headers from your message, it appears Comcast > may be your ISP, and this 50.243.150.81 IP address appears to be a > Comcast address, so you may need to contact Comcast tech support for > help in getting the blacklist designation removed. There are a few situations here. 1. You are a business customer with a static IP, and are entitled to send/receive SMTP by your ISP (Comcast) 2. You are a business/residential customer who is allowed to send (not likely allowed to receive) SMTP and you have a domain elsewhere to receive replies to your email 3. You are a business/residential customer who is NOT allowed to send SMTP except for your ISP (Comcast) provided email. Only you would know which on for sure is you, but it is very likely #3. The advice provided previously is for case #1 - contact Comcast and inform them that your contracted services are not working because of .... and you will need to beable to work with them on testing and suggesting fixes. They have a dedicated support phone number (which they provided you if you are actually a #1 type customer - e.g. gigabit pro, metro Ethernet, etc.) In case you are a #2 or #3 type customer, you may want to use a smart host configuration - e.g. define('SMART_HOST','[smtp.comcast.net]') . For postfix, use relayhost = [smtp.comcast.net] . Now when you send mail to that relay it will relay it. This is provided you are entitled to have your email relayed - contact Xfinity customer service for help there. If using this relay does not work, please post the exchange starting with the HELO (check your maillog or do it by hand with telnet). -- Jason Pyeron | Architect PD Inc | 10 w 24th St | Baltimore, MD | .com: jpyeron(a)pdinc.us tel : 202-741-9397

5 15

Sendmail not working
by S.Bob 19 Apr '20

19 Apr '20

All; I installed sendmail via yum, but if I test it like this: echo "Subject: sendmail test" | sendmail sbob(a)quadratum-braccas.com I get a local mail on the server with this every time: Message 1: From MAILER-DAEMON(a)kdb-bugs.example.com Sun Apr 19 10:15:00 2020 Return-Path: <MAILER-DAEMON(a)kdb-bugs.example.com> Date: Sun, 19 Apr 2020 10:15:00 -0600 From: Mail Delivery Subsystem <MAILER-DAEMON(a)kdb-bugs.example.com> To: <root(a)kdb-bugs.example.com> Content-Type: multipart/report; report-type=delivery-status; boundary="03JGF0ni013558.1587312900/kdb-bugs.example.com" Subject: Returned mail: see transcript for details Auto-Submitted: auto-generated (failure) Status: R Part 1: The original message was received at Sun, 19 Apr 2020 10:02:56 -0600 from localhost [127.0.0.1] ----- The following addresses had permanent fatal errors ----- <sbob(a)quadratum-braccas.com> (reason: 554 5.7.1 Service unavailable; Client host [50.243.150.81] blocked using xbl.spamhaus.org.rbl.local; https://www.spamhaus .org/query/ip/50.243.150.81) ----- Transcript of session follows ----- ... while talking to in1-smtp.messagingengine.com.: >>> RCPT To:<sbob(a)quadratum-braccas.com> <<< 554 5.7.1 Service unavailable; Client host [50.243.150.81] blocked using xbl.spamhaus.org.rbl.local; https://www.spamhaus.org/quer y/ip/50.243.150.81 554 5.0.0 Service unavailable >>> DATA <<< 421 4.4.2 mx5.messagingengine.com Error: timeout exceeded ... while talking to in2-smtp.messagingengine.com.: >>> DATA <<< 421 4.4.2 wmx2.messagingengine.com Error: timeout exceeded Thanks in advance If it helps, here is my sendmail.mc file: [root@kdb-bugs ~]# cat /etc/mail/sendmail.mc divert(-1)dnl dnl # dnl # This is the sendmail macro config file for m4. If you make changes to dnl # /etc/mail/sendmail.mc, you will need to regenerate the dnl # /etc/mail/sendmail.cf file by confirming that the sendmail-cf package is dnl # installed and then performing a dnl # dnl # /etc/mail/make dnl # include(`/usr/share/sendmail-cf/m4/cf.m4')dnl VERSIONID(`setup for linux')dnl OSTYPE(`linux')dnl dnl # dnl # Do not advertize sendmail version. dnl # dnl define(`confSMTP_LOGIN_MSG', `$j Sendmail; $b')dnl dnl # dnl # default logging level is 9, you might want to set it higher to dnl # debug the configuration dnl # dnl define(`confLOG_LEVEL', `9')dnl dnl # dnl # Uncomment and edit the following line if your outgoing mail needs to dnl # be sent out through an external mail server: dnl # dnl define(`SMART_HOST', `smtp.your.provider')dnl dnl # define(`confDEF_USER_ID', ``8:12'')dnl dnl define(`confAUTO_REBUILD')dnl define(`confTO_CONNECT', `1m')dnl define(`confTRY_NULL_MX_LIST', `True')dnl define(`confDONT_PROBE_INTERFACES', `True')dnl define(`PROCMAIL_MAILER_PATH', `/usr/bin/procmail')dnl define(`ALIAS_FILE', `/etc/aliases')dnl define(`STATUS_FILE', `/var/log/mail/statistics')dnl define(`UUCP_MAILER_MAX', `2000000')dnl define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl define(`confPRIVACY_FLAGS', `authwarnings,novrfy,noexpn,restrictqrun')dnl define(`confAUTH_OPTIONS', `A')dnl dnl # dnl # The following allows relaying if the user authenticates, and disallows dnl # plaintext authentication (PLAIN/LOGIN) on non-TLS links dnl # dnl define(`confAUTH_OPTIONS', `A p')dnl dnl # dnl # PLAIN is the preferred plaintext authentication method and used by dnl # Mozilla Mail and Evolution, though Outlook Express and other MUAs do dnl # use LOGIN. Other mechanisms should be used if the connection is not dnl # guaranteed secure. dnl # Please remember that saslauthd needs to be running for AUTH. dnl # dnl TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl dnl define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl dnl # dnl # Rudimentary information on creating certificates for sendmail TLS: dnl # cd /etc/pki/tls/certs; make sendmail.pem dnl # Complete usage: dnl # make -C /etc/pki/tls/certs usage dnl # dnl define(`confCACERT_PATH', `/etc/pki/tls/certs')dnl dnl define(`confCACERT', `/etc/pki/tls/certs/ca-bundle.crt')dnl dnl define(`confSERVER_CERT', `/etc/pki/tls/certs/sendmail.pem')dnl dnl define(`confSERVER_KEY', `/etc/pki/tls/certs/sendmail.pem')dnl dnl # dnl # This allows sendmail to use a keyfile that is shared with OpenLDAP's dnl # slapd, which requires the file to be readble by group ldap dnl # dnl define(`confDONT_BLAME_SENDMAIL', `groupreadablekeyfile')dnl dnl # dnl define(`confTO_QUEUEWARN', `4h')dnl dnl define(`confTO_QUEUERETURN', `5d')dnl dnl define(`confQUEUE_LA', `12')dnl dnl define(`confREFUSE_LA', `18')dnl define(`confTO_IDENT', `0')dnl dnl # If you're operating in a DSCP/RFC-4594 environment with QoS dnl define(`confINET_QOS', `AF11')dnl dnl FEATURE(delay_checks)dnl FEATURE(`no_default_msa', `dnl')dnl FEATURE(`smrsh', `/usr/sbin/smrsh')dnl FEATURE(`mailertable', `hash -o /etc/mail/mailertable.db')dnl FEATURE(`virtusertable', `hash -o /etc/mail/virtusertable.db')dnl FEATURE(redirect)dnl FEATURE(always_add_domain)dnl FEATURE(use_cw_file)dnl FEATURE(use_ct_file)dnl dnl # dnl # The following limits the number of processes sendmail can fork to accept dnl # incoming messages or process its message queues to 20.) sendmail refuses dnl # to accept connections once it has reached its quota of child processes. dnl # dnl define(`confMAX_DAEMON_CHILDREN', `20')dnl dnl # dnl # Limits the number of new connections per second. This caps the overhead dnl # incurred due to forking new sendmail processes. May be useful against dnl # DoS attacks or barrages of spam. (As mentioned below, a per-IP address dnl # limit would be useful but is not available as an option at this writing.) dnl # dnl define(`confCONNECTION_RATE_THROTTLE', `3')dnl dnl # dnl # The -t option will retry delivery if e.g. the user runs over his quota. dnl # FEATURE(local_procmail, `', `procmail -t -Y -a $h -d $u')dnl FEATURE(`access_db', `hash -T<TMPF> -o /etc/mail/access.db')dnl FEATURE(`blacklist_recipients')dnl EXPOSED_USER(`root')dnl dnl # dnl # For using Cyrus-IMAPd as POP3/IMAP server through LMTP delivery uncomment dnl # the following 2 definitions and activate below in the MAILER section the dnl # cyrusv2 mailer. dnl # dnl define(`confLOCAL_MAILER', `cyrusv2')dnl dnl define(`CYRUSV2_MAILER_ARGS', `FILE /var/lib/imap/socket/lmtp')dnl dnl # dnl # The following causes sendmail to only listen on the IPv4 loopback address dnl # 127.0.0.1 and not on any other network devices. Remove the loopback dnl # address restriction to accept email from the internet or intranet. dnl # DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl dnl # dnl # The following causes sendmail to additionally listen to port 587 for dnl # mail from MUAs that authenticate. Roaming users who can't reach their dnl # preferred sendmail daemon due to port 25 being blocked or redirected find dnl # this useful. dnl # dnl DAEMON_OPTIONS(`Port=submission, Name=MSA, M=Ea')dnl dnl # dnl # The following causes sendmail to additionally listen to port 465, but dnl # starting immediately in TLS mode upon connecting. Port 25 or 587 followed dnl # by STARTTLS is preferred, but roaming clients using Outlook Express can't dnl # do STARTTLS on ports other than 25. Mozilla Mail can ONLY use STARTTLS dnl # and doesn't support the deprecated smtps; Evolution <1.1.1 uses smtps dnl # when SSL is enabled-- STARTTLS support is available in version 1.1.1. dnl # dnl # For this to work your OpenSSL certificates must be configured. dnl # dnl DAEMON_OPTIONS(`Port=smtps, Name=TLSMTA, M=s')dnl dnl # dnl # The following causes sendmail to additionally listen on the IPv6 loopback dnl # device. Remove the loopback address restriction listen to the network. dnl # dnl DAEMON_OPTIONS(`port=smtp,Addr=::1, Name=MTA-v6, Family=inet6')dnl dnl # dnl # enable both ipv6 and ipv4 in sendmail: dnl # dnl DAEMON_OPTIONS(`Name=MTA-v4, Family=inet, Name=MTA-v6, Family=inet6') dnl # dnl # We strongly recommend not accepting unresolvable domains if you want to dnl # protect yourself from spam. However, the laptop and users on computers dnl # that do not have 24x7 DNS do need this. dnl # FEATURE(`accept_unresolvable_domains')dnl dnl # dnl FEATURE(`relay_based_on_MX')dnl dnl # dnl # Also accept email sent to "localhost.localdomain" as local email. dnl # LOCAL_DOMAIN(`localhost.localdomain')dnl dnl # dnl # The following example makes mail from this host and any additional dnl # specified domains appear to be sent from mydomain.com dnl # dnl MASQUERADE_AS(`mydomain.com')dnl dnl # dnl # masquerade not just the headers, but the envelope as well dnl # dnl FEATURE(masquerade_envelope)dnl dnl # dnl # masquerade not just @mydomainalias.com, but @*.mydomainalias.com as well dnl # dnl FEATURE(masquerade_entire_domain)dnl dnl # dnl MASQUERADE_DOMAIN(localhost)dnl dnl MASQUERADE_DOMAIN(localhost.localdomain)dnl dnl MASQUERADE_DOMAIN(mydomainalias.com)dnl dnl MASQUERADE_DOMAIN(mydomain.lan)dnl MAILER(smtp)dnl MAILER(procmail)dnl dnl MAILER(cyrusv2)dnl -- `When you say "I wrote a program that crashed Windows", people just stare at you blankly and say "Hey, I got those with the system, *for free*".' (By Linus Torvalds)

5 7

Netfilter fails to filter traffic from a netblock?
by Jeffrey Walton 19 Apr '20

19 Apr '20

Hi Everyone, We rent a CentOS 7 VM from GoDaddy. We received a warning about excessive cpu usage, and a threat to cancel our service. We tracked it down to Apache and someone hammering our web server. The offending host is 59.64.129.175. To err on the side of caution we attempted to block the entire netblock. According to whois data, that's 59.64.128.0-59.64.159.255. iptables -A INPUT -s 59.64.128.0/19 -p TCP -j DROP After reboot cpu usage is still high and access_log still shows useless requests from the host: 59.64.129.175 - - [19/Apr/2020:08:53:53 -0400] "GET /w/index.php?title=Special:WhatLinksHere&limit=50& printable=yes HTTP/1.1" 301 311 I seem to be missing something. That's not surprising since I am not a server administrator. How do I filter the unwanted traffic from the netblock? Thanks in advance.

6 11

CentO 8 and nftables default policy
by Alessandro Baggi 19 Apr '20

19 Apr '20

Hi list, I'm studying nftables. I'm using CentOS 8.1 (Gnome) and I disabled firewalld. I noticed that a default policy is created with tables and chains probably for firewalld. So I created a .nft script where I stored my rules with a flush for previous ruleset, then saved on /etc/sysconfig/nftables.conf and the enabled nftables service. Running the script with nft -f script.nft all work as expected but when rebooting, running nft list ruleset I find my rules and the default policy (chains and tables) that I would not have in my configuration. My nftables.conf contains only my ruleset. For example, running nft list tables I found several default tables like: table ip filter table ip6 filter table bridge filter table ip nat table ip mangle So probably there is something that is applying its policy but I ignore what is. Can someone point me in the right direction? Thank you in advance.

2 3

Strangeness on X11 screen capture
by Jerry Geis 19 Apr '20

19 Apr '20

Hi all, I am running CentOS 7 on a NUC5CPYB. Intel video: 00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35) When I take a screen shot I get "different" things. I use: export DISPLAY=:0.0 /usr/bin/xwd -silent -root -out screen; convert screen screen.png I tried import also for the screen capture and its the same random images. Granted the images are all things I have showing previously - but most times its not what is showing now. I have verified the Intel driver is loaded: [ 19.009] (II) LoadModule: "intel" [ 19.010] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 19.012] (II) Module intel: vendor="X.Org Foundation" [ 19.012] compiled for 1.20.1, module version = 2.99.917 [ 19.012] Module class: X.Org Video Driver [ 19.012] ABI class: X.Org Video Driver, version 24.0 [ 19.012] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 19.015] (II) intel: Driver for Intel(R) HD Graphics [ 19.015] (II) intel: Driver for Intel(R) Iris(TM) Graphics [ 19.015] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics [ 19.015] (++) using VT number 1 [ 19.016] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20181204 [ 19.018] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics [ 19.019] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2; using a maximum of 2 threads [ 19.019] (II) intel(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 19.019] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [ 19.019] (==) intel(0): RGB weight 888 [ 19.019] (==) intel(0): Default visual is TrueColor [ 19.023] (II) intel(0): Output DP1 has no monitor section [ 19.024] (II) intel(0): Enabled output DP1 [ 19.024] (II) intel(0): Output HDMI1 has no monitor section [ 19.025] (II) intel(0): Enabled output HDMI1 [ 19.025] (II) intel(0): Output DP2 has no monitor section [ 19.026] (II) intel(0): Enabled output DP2 [ 19.026] (II) intel(0): Output HDMI2 has no monitor section [ 19.027] (II) intel(0): Enabled output HDMI2 [ 19.027] (--) intel(0): Using a maximum size of 256x256 for hardware cursors [ 19.027] (II) intel(0): Output VIRTUAL1 has no monitor section [ 19.027] (II) intel(0): Enabled output VIRTUAL1 [ 19.028] (--) intel(0): Output HDMI2 using initial mode 1920x1080 on pipe 2 What can be doing this ? How do I track it down? Thanks, Jerry

2 2

CentOS 8 and xhost
by Jerry Geis 18 Apr '20

18 Apr '20

I am trying to run 'xhost +' on CentOS 8 (such that I can grab a screen shot) but its not letting me. On boot of X I run the "xhost +" then later with SSH into hte box - I run export DISPLAY=:0.0 gnome-screenshot -f jj.png and I get the cannot open display message. This works on the older CentOS 7. What is the magic for C8? Thanks, Jerry

3 4

phpMyAdmin for Centos 8
by Ranbir 18 Apr '20

18 Apr '20

Has anyone seen a phpMyAdmin rpm for Centos 8 out in the wild? I've been using the Centos 7 EPEL package for phpMyAdmin for many years. When I went there to look for the Centos 8 version of the rpm, I couldn't find one. O_O -- Ranbir

1 0

fail2ban firewalld problems with current CentOS 7
by Andreas Haumer 17 Apr '20

17 Apr '20

Hi! I have a server running CentOS 7.7 (1908) with all current patches installed. I think this server should be a quite standard installation with no specialities On this server I have fail2ban with an apache and openvpn configuration. I'm using firewalld to manage the firewall rules. Fail2an is configured to use firewalld: [root@server ~]# ll /etc/fail2ban/jail.d/ insgesamt 12 -rw-r--r--. 1 root root 356 21. Jan 05:12 00-firewalld.conf -rw-r--r--. 1 root root 610 15. Nov 19:55 apache.local -rw-r--r--. 1 root root 115 15. Nov 19:10 openvpn.local [root@server ~]# cat /etc/fail2ban/jail.d/00-firewalld.conf # This file is part of the fail2ban-firewalld package to configure the use of # the firewalld actions as the default actions. You can remove this package # (along with the empty fail2ban meta-package) if you do not use firewalld [DEFAULT] banaction = firewallcmd-ipset[actiontype=<multiport>] banaction_allports = firewallcmd-ipset[actiontype=<allports>] A few days ago I noticed that on restart firewalld complains about a missing ipset: [root@server ~]# systemctl restart firewalld [root@server ~]# systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled) Active: active (running) since Do 2020-04-09 09:25:28 CEST; 5s ago Docs: man:firewalld(1) Main PID: 8324 (firewalld) CGroup: /system.slice/firewalld.service └─8324 /usr/bin/python2 -Es /usr/sbin/firewalld --nofork --nopid Apr 09 09:25:28 server.my.domain systemd[1]: Starting firewalld - dynamic firewall daemon... Apr 09 09:25:28 server.my.domain systemd[1]: Started firewalld - dynamic firewall daemon. Apr 09 09:25:30 server.my.domain firewalld[8324]: ERROR: '/usr/sbin/iptables-restore -w -n' failed: iptables-restore v1.4.21: Set f2b-apache doesn't exist. Error occurred at line: 2... Apr 09 09:25:30 server.my.domain firewalld[8324]: ERROR: COMMAND_FAILED: Direct: '/usr/sbin/iptables-restore -w -n' failed: iptables-restore v1.4.21: Set f2b-apache doesn't exist. Error occurred at line: 2... Hint: Some lines were ellipsized, use -l to show in full. Indeed there is no ipset named "f2b-apache", there is no set configured at all: [root@server ~]# ipset list There is no error when restarting fail2ban: [root@server ~]# systemctl restart fail2ban [root@server ~]# systemctl status fail2ban ● fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; vendor preset: disabled) Active: active (running) since Do 2020-04-09 09:26:13 CEST; 4s ago Docs: man:fail2ban(1) Process: 8539 ExecStop=/usr/bin/fail2ban-client stop (code=exited, status=0/SUCCESS) Process: 8543 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS) Main PID: 8545 (f2b/server) CGroup: /system.slice/fail2ban.service └─8545 /usr/bin/python -s /usr/bin/fail2ban-server -xf start Apr 09 09:26:13 server.my.domain systemd[1]: Stopped Fail2Ban Service. Apr 09 09:26:13 server.my.domain systemd[1]: Starting Fail2Ban Service... Apr 09 09:26:13 server.my.domain systemd[1]: Started Fail2Ban Service. Apr 09 09:26:13 server.my.domain fail2ban-server[8545]: Server ready Fail2ban seems to be running fine: [root@server ~]# fail2ban-client status Status |- Number of jail: 6 `- Jail list: apache, apache-badbots, apache-nohome, apache-noscript, apache-overflows, openvpn No errors loged in fail2ban.log on restart: [...] 2020-04-09 09:26:13,773 fail2ban.server [8545]: INFO Starting Fail2ban v0.10.5 2020-04-09 09:26:13,799 fail2ban.database [8545]: INFO Connected to fail2ban persistent database '/var/lib/fail2ban/fail2ban.sqlite3' 2020-04-09 09:26:13,801 fail2ban.jail [8545]: INFO Creating new jail 'apache-badbots' 2020-04-09 09:26:13,805 fail2ban.jail [8545]: INFO Jail 'apache-badbots' uses poller {} 2020-04-09 09:26:13,805 fail2ban.jail [8545]: INFO Initiated 'polling' backend 2020-04-09 09:26:13,838 fail2ban.filter [8545]: INFO maxRetry: 1 2020-04-09 09:26:13,838 fail2ban.filter [8545]: INFO encoding: UTF-8 2020-04-09 09:26:13,839 fail2ban.actions [8545]: INFO banTime: 172800 2020-04-09 09:26:13,839 fail2ban.filter [8545]: INFO findtime: 3600 2020-04-09 09:26:13,840 fail2ban.filter [8545]: INFO Added logfile: '/var/log/httpd/ssl_error_log' (pos = 588859, hash = 755a00cfc09ef9b2f76d78cff61ea766) 2020-04-09 09:26:13,840 fail2ban.filter [8545]: INFO Added logfile: '/var/log/httpd/error_log' (pos = 27101, hash = 53ba5e7041d49628af3b86be05de6fa7) 2020-04-09 09:26:13,841 fail2ban.jail [8545]: INFO Creating new jail 'apache-noscript' 2020-04-09 09:26:13,843 fail2ban.jail [8545]: INFO Jail 'apache-noscript' uses poller {} 2020-04-09 09:26:13,843 fail2ban.jail [8545]: INFO Initiated 'polling' backend 2020-04-09 09:26:13,851 fail2ban.filter [8545]: INFO maxRetry: 3 2020-04-09 09:26:13,851 fail2ban.filter [8545]: INFO encoding: UTF-8 2020-04-09 09:26:13,851 fail2ban.actions [8545]: INFO banTime: 10800 2020-04-09 09:26:13,852 fail2ban.filter [8545]: INFO findtime: 3600 2020-04-09 09:26:13,853 fail2ban.filter [8545]: INFO Added logfile: '/var/log/httpd/ssl_error_log' (pos = 588859, hash = 755a00cfc09ef9b2f76d78cff61ea766) 2020-04-09 09:26:13,854 fail2ban.filter [8545]: INFO Added logfile: '/var/log/httpd/error_log' (pos = 27101, hash = 53ba5e7041d49628af3b86be05de6fa7) 2020-04-09 09:26:13,855 fail2ban.jail [8545]: INFO Creating new jail 'apache-overflows' 2020-04-09 09:26:13,857 fail2ban.jail [8545]: INFO Jail 'apache-overflows' uses poller {} 2020-04-09 09:26:13,857 fail2ban.jail [8545]: INFO Initiated 'polling' backend 2020-04-09 09:26:13,863 fail2ban.filter [8545]: INFO maxRetry: 2 2020-04-09 09:26:13,863 fail2ban.filter [8545]: INFO encoding: UTF-8 2020-04-09 09:26:13,864 fail2ban.actions [8545]: INFO banTime: 10800 2020-04-09 09:26:13,864 fail2ban.filter [8545]: INFO findtime: 3600 2020-04-09 09:26:13,865 fail2ban.filter [8545]: INFO Added logfile: '/var/log/httpd/ssl_error_log' (pos = 588859, hash = 755a00cfc09ef9b2f76d78cff61ea766) 2020-04-09 09:26:13,865 fail2ban.filter [8545]: INFO Added logfile: '/var/log/httpd/error_log' (pos = 27101, hash = 53ba5e7041d49628af3b86be05de6fa7) 2020-04-09 09:26:13,866 fail2ban.jail [8545]: INFO Creating new jail 'apache-nohome' 2020-04-09 09:26:13,867 fail2ban.jail [8545]: INFO Jail 'apache-nohome' uses poller {} 2020-04-09 09:26:13,868 fail2ban.jail [8545]: INFO Initiated 'polling' backend 2020-04-09 09:26:13,872 fail2ban.filter [8545]: INFO maxRetry: 2 2020-04-09 09:26:13,873 fail2ban.filter [8545]: INFO encoding: UTF-8 2020-04-09 09:26:13,873 fail2ban.actions [8545]: INFO banTime: 10800 2020-04-09 09:26:13,873 fail2ban.filter [8545]: INFO findtime: 3600 2020-04-09 09:26:13,874 fail2ban.filter [8545]: INFO Added logfile: '/var/log/httpd/ssl_error_log' (pos = 588859, hash = 755a00cfc09ef9b2f76d78cff61ea766) 2020-04-09 09:26:13,875 fail2ban.filter [8545]: INFO Added logfile: '/var/log/httpd/error_log' (pos = 27101, hash = 53ba5e7041d49628af3b86be05de6fa7) 2020-04-09 09:26:13,876 fail2ban.jail [8545]: INFO Creating new jail 'apache' 2020-04-09 09:26:13,878 fail2ban.jail [8545]: INFO Jail 'apache' uses poller {} 2020-04-09 09:26:13,879 fail2ban.jail [8545]: INFO Initiated 'polling' backend 2020-04-09 09:26:13,898 fail2ban.filter [8545]: INFO maxRetry: 3 2020-04-09 09:26:13,899 fail2ban.filter [8545]: INFO encoding: UTF-8 2020-04-09 09:26:13,899 fail2ban.actions [8545]: INFO banTime: 10800 2020-04-09 09:26:13,900 fail2ban.filter [8545]: INFO findtime: 3600 2020-04-09 09:26:13,900 fail2ban.filter [8545]: INFO Added logfile: '/var/log/httpd/ssl_error_log' (pos = 588859, hash = 755a00cfc09ef9b2f76d78cff61ea766) 2020-04-09 09:26:13,901 fail2ban.filter [8545]: INFO Added logfile: '/var/log/httpd/error_log' (pos = 27101, hash = 53ba5e7041d49628af3b86be05de6fa7) 2020-04-09 09:26:13,902 fail2ban.jail [8545]: INFO Creating new jail 'openvpn' 2020-04-09 09:26:13,931 fail2ban.jail [8545]: INFO Jail 'openvpn' uses systemd {} 2020-04-09 09:26:13,932 fail2ban.jail [8545]: INFO Initiated 'systemd' backend 2020-04-09 09:26:13,944 fail2ban.filtersystemd [8545]: INFO [openvpn] Added journal match for: '_SYSTEMD_UNIT=openvpn-server(a)xss.service + _COMM=openvpn' 2020-04-09 09:26:13,944 fail2ban.actions [8545]: INFO banTime: 10800 2020-04-09 09:26:13,944 fail2ban.filter [8545]: INFO maxRetry: 2 2020-04-09 09:26:13,944 fail2ban.filter [8545]: INFO encoding: UTF-8 2020-04-09 09:26:13,945 fail2ban.filter [8545]: INFO findtime: 3600 2020-04-09 09:26:13,949 fail2ban.jail [8545]: INFO Jail 'apache-badbots' started 2020-04-09 09:26:13,952 fail2ban.jail [8545]: INFO Jail 'apache-noscript' started 2020-04-09 09:26:13,954 fail2ban.jail [8545]: INFO Jail 'apache-overflows' started 2020-04-09 09:26:13,956 fail2ban.jail [8545]: INFO Jail 'apache-nohome' started 2020-04-09 09:26:13,961 fail2ban.jail [8545]: INFO Jail 'apache' started 2020-04-09 09:26:13,964 fail2ban.jail [8545]: INFO Jail 'openvpn' started [...] BUT: SELinux complains about fail2ban: type=AVC msg=audit(1586413496.76:53507): avc: denied { read } for pid=1324 comm="f2b/f.apache" name="disable" dev="sysfs" ino=1481 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:sysfs_t:s0 tclass=file permissive=0 So it seems somehow fail2ban does not add the required ip sets correctly. From what I see in firewalld logfile it seems these problems started after the last updates on April 2nd. On this day I did a "yum update" which executed without errors and installed: augeas-libs-1.4.0-9.el7_7.1.x86_64 Do 02 Apr 2020 20:14:27 CEST restic-0.9.6-1.el7.x86_64 Do 02 Apr 2020 20:14:25 CEST python-perf-3.10.0-1062.18.1.el7.x86_64 Do 02 Apr 2020 20:14:23 CEST python3-pip-9.0.3-7.el7_7.noarch Do 02 Apr 2020 20:14:23 CEST borgbackup-1.1.11-1.el7.x86_64 Do 02 Apr 2020 20:14:19 CEST libgudev1-219-67.el7_7.4.x86_64 Do 02 Apr 2020 20:14:18 CEST kernel-tools-3.10.0-1062.18.1.el7.x86_64 Do 02 Apr 2020 20:14:16 CEST pcp-4.3.2-5.el7_7.x86_64 Do 02 Apr 2020 20:14:01 CEST kernel-3.10.0-1062.18.1.el7.x86_64 Do 02 Apr 2020 20:13:44 CEST systemd-python-219-67.el7_7.4.x86_64 Do 02 Apr 2020 20:13:27 CEST systemd-sysv-219-67.el7_7.4.x86_64 Do 02 Apr 2020 20:13:26 CEST rsyslog-8.24.0-41.el7_7.4.x86_64 Do 02 Apr 2020 20:13:26 CEST python2-certbot-apache-1.3.0-1.el7.noarch Do 02 Apr 2020 20:13:25 CEST sssd-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:13:24 CEST firewalld-0.6.3-2.el7_7.4.noarch Do 02 Apr 2020 20:13:24 CEST sssd-proxy-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:13:23 CEST sssd-krb5-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:13:23 CEST sssd-ldap-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:13:22 CEST sssd-ipa-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:13:22 CEST sssd-ad-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:13:22 CEST sssd-krb5-common-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:13:21 CEST sssd-common-pac-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:13:21 CEST sssd-common-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:13:20 CEST http-parser-2.7.1-8.el7_7.2.x86_64 Do 02 Apr 2020 20:13:19 CEST python-firewall-0.6.3-2.el7_7.4.noarch Do 02 Apr 2020 20:13:18 CEST certbot-1.3.0-1.el7.noarch Do 02 Apr 2020 20:13:11 CEST python2-certbot-1.3.0-1.el7.noarch Do 02 Apr 2020 20:13:10 CEST python2-acme-1.3.0-1.el7.noarch Do 02 Apr 2020 20:13:09 CEST python-requests-2.6.0-9.el7_7.noarch Do 02 Apr 2020 20:13:08 CEST systemd-219-67.el7_7.4.x86_64 Do 02 Apr 2020 20:13:05 CEST kmod-20-25.el7_7.1.x86_64 Do 02 Apr 2020 20:13:02 CEST binutils-2.27-41.base.el7_7.3.x86_64 Do 02 Apr 2020 20:13:00 CEST pcp-selinux-4.3.2-5.el7_7.x86_64 Do 02 Apr 2020 20:12:48 CEST libsss_autofs-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:12:47 CEST kernel-tools-libs-3.10.0-1062.18.1.el7.x86_64 Do 02 Apr 2020 20:12:46 CEST python-sssdconfig-1.16.4-21.el7_7.3.noarch Do 02 Apr 2020 20:12:45 CEST libsss_sudo-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:12:45 CEST firewalld-filesystem-0.6.3-2.el7_7.4.noarch Do 02 Apr 2020 20:12:44 CEST sssd-client-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:12:43 CEST libsss_nss_idmap-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:12:42 CEST libipa_hbac-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:12:42 CEST pcp-libs-4.3.2-5.el7_7.x86_64 Do 02 Apr 2020 20:12:41 CEST pcp-conf-4.3.2-5.el7_7.x86_64 Do 02 Apr 2020 20:12:41 CEST kmod-libs-20-25.el7_7.1.x86_64 Do 02 Apr 2020 20:12:40 CEST libsss_idmap-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:12:39 CEST libsss_certmap-1.16.4-21.el7_7.3.x86_64 Do 02 Apr 2020 20:12:33 CEST systemd-libs-219-67.el7_7.4.x86_64 Do 02 Apr 2020 20:12:32 CEST The firewalld errors start exactly after the updates were installed. Does anyone else see similar problems since the last updates? I googled and found some older postings, but nothing matching the problems I see exactly. I have other CentOS 7 servers with fail2ban and firewalld which should be updated soon, but before I do this I first want to solve this issue. Any idea? Thanks! - andreas -- Andreas Haumer | mailto:andreas@xss.co.at *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0 A-1100 Vienna, Austria | Fax: +43-1-6060114-71

4 6

HPC question: torques replacement
by Valeri Galtsev 17 Apr '20

17 Apr '20

Dear Experts, I know there are many HPC (high performance computing) experts on this list. I'd like to ask your advise. Almost two decades ago I chose to go with OpenPBS (turned down condor and other alternatives for whatever reason) for clusters and number crunchers I support for the Department at the university. It turned out to be not bad, long lived choice. At some point I smoothly migrated to torque which was advertised as open source project (based on PBS, but it was much less hassle to compile...). Torque ceased to be open source two years ago, it is proprietary now. At some point I have to migrate away from torque for this reason. One of the ways would be to switch (back) to open source PBS Pro (pbspro.org) I wonder what other options experts would recommend. Hopefully, not too far from torque (or PBS) from user prospective. Thanks a lot for all your advises! Valeri -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

3 2

Re: [CentOS] Thank You
by david 17 Apr '20

17 Apr '20

At 07:59 PM 4/16/2020, you wrote: >Just reaching out to say thanks to all the folks that keep CentOS, >EPEL, this mailing list, etc running. It is probably partly due to >having used Red Hat for over two decades, but I always have a good >experience with CentOS. The recent servers that I have setup with >CentOS 8 are purring along. Thanks for the work and support. > >Cheers, >Ian Ian It is an absolute delight to see a posting like yours. No questions, no complaints, no "you shouldn't be doing that, and no non-answers. Thank you for confirming my belief that the open-source community is there to help. I, too, started with RedHat Linux when it was 'free', converted to WhiteHat, then Centos. I control servers of x86_64, Raspberry Pi, mostly on Centos 7, all for fun, not as a job. I'm working on the C8.... Now, ... I haven't had as good luck with C8 s you allege. There were several things I had to deal with: - new firewall - new mailer (sendmail -> postfix) - new system management (systemd) - new yum (introduction of software streams, whatever they are) But, it keeps me busy during this lockdown time. David San Francisco

2 1

Thank You
by Ian P. 17 Apr '20

17 Apr '20

Just reaching out to say thanks to all the folks that keep CentOS, EPEL, this mailing list, etc running. It is probably partly due to having used Red Hat for over two decades, but I always have a good experience with CentOS. The recent servers that I have setup with CentOS 8 are purring along. Thanks for the work and support. Cheers, Ian

1 0

A
by MOHD HOMAIDUR RAHMAN 16 Apr '20

16 Apr '20

-- ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' *M*d* H*omaidur* R**ahman *( Research Scholar ) Lab No. 510, Computational Biophysics Lab. Department of Biotechnology Indian Institute of Technology-Madras Chennai-600 036, India *Mobile No = +91- 7845991785* '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

1 0

Asking again: CentOS 7, KDE, logout needed twice
by mark 15 Apr '20

15 Apr '20

Every single time, no matter if I chose leave->logout from the start menu, or from ctrl-alt-delete, it does *not* log me out, but restarts KDE. The second time, doesn't matter which way I go, it *does* log me out. Anyone got a clue? Googling hasn't found anything.... mark

2 1

bcc tools and bpftrace packages misbuilt?
by Eric Zuck 15 Apr '20

15 Apr '20

After upgrading to 8.1.1911, bcc-tools and bpftrace seem to be broken. Current package versions I have: bpftrace-0.9-3.el8.x86_64 and bcc-tools-0.8.0-4.el8.x86_64 Both of these seem to be pulling in LLVM version 7, rather than the version 8 that is in 8.1.1911: [root@localhost ~]# bpftrace bpftrace: error while loading shared libraries: libclangFrontend.so.7: cannot open shared object file: No such file or directory [root@localhost ~]# /usr/share/bcc/tools/opensnoop Traceback (most recent call last): File "/usr/share/bcc/tools/opensnoop", line 19, in <module> from bcc import ArgString, BPF File "/usr/lib/python3.6/site-packages/bcc/__init__.py", line 27, in <module> from .libbcc import lib, bcc_symbol, bcc_symbol_option, _SYM_CB_TYPE File "/usr/lib/python3.6/site-packages/bcc/libbcc.py", line 17, in <module> lib = ct.CDLL("libbcc.so.0", use_errno=True) File "/usr/lib64/python3.6/ctypes/__init__.py", line 343, in __init__ self._handle = _dlopen(self._name, mode) OSError: libclangFrontend.so.7: cannot open shared object file: No such file or directory Looking through the CentosBug tracker, I see https://bugs.centos.org/view.php?id=16922: qt5-doctools-5.11.1-9.el8 from CentOS CR/8-stream is misbuilt https://bugs.centos.org/view.php?id=16930: rust-1.37.0-1.module_el8.1.0+246+1f1fd47e built against old libLLVM-7.so So, I gather that bcc-tools and bpftrace are not the only packages affected by an LLVM mismatch. Short of downloading and rebuilding the packages, does anyone have any suggestions about workarounds? Regards, -EricZ

1 1

Samba Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE SessSetup = -13
by Ralf Prengel 15 Apr '20

15 Apr '20

Hallo, perhaps someone hat a hint vor me. My centos 7 samba Server ist working fine using Win10 Clienst with Domaine-Integration. Shares are browseable and access is possible with a sepearte login. My problem: I want to mount this shares from a centos7 client. This fails with the following mesages. I tried several variations in my fstab found in the internet. Can anyone give me a hint to to access an samba-server that is working fine against a Win2016 Domain-Cotroller? Thanks Rakf Apr 15 05:37:47 6805ca01a270 kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE Apr 15 05:37:47 6805ca01a270 kernel: CIFS VFS: Send error in SessSetup = -13 Apr 15 05:37:47 6805ca01a270 kernel: CIFS VFS: cifs_mount failed w/return code = -13 Apr 15 05:37:52 6805ca01a270 kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE Apr 15 05:37:52 6805ca01a270 kernel: CIFS VFS: Send error in SessSetup = -13 Apr 15 05:37:52 6805ca01a270 kernel: CIFS VFS: cifs_mount failed w/return code = -13 smb.conf [global] Workgroup = COMLINE security = ads encrypt passwords = yes passdb backend = tdbsam realm = comline.de printing = cups printcap name = cups load printers = yes cups options = raw map to guest = bad user [share_gov_srvgovrcpbuild_clients] comment = share für gov projekt rcpbuild clients path = /mnt/raid01/share_volumes_gov_srvgovrcpbuild_clients_smb browseable = yes comment = Share für alle guest ok = yes writeable = yes read only = no force user = root create mask = 0777 directory mask = 0777 public = yes

3 5

Centos 7: cups-pdf Postprocessing prevented by selinux :(
by hw 15 Apr '20

15 Apr '20

Hi, how can I make it so that printing to a cups PDF printer can successfully run the postprocessing script I specified in /etc/cups/cups-pdf.conf? It does work with 'sentenforce permissve', and after creating and installing some selinux modules from audit.log entries, it still doesn't work, and there doesn't seem to be anything else that might prevent the postprocessing script from being run.

2 1

Red Hat Enterprise Linux 8.2 Beta now available
by Turritopsis Dohrnii Teo En Ming 14 Apr '20

14 Apr '20

Link: https://www.redhat.com/en/blog/red-hat-enterprise-linux-82-beta-now-availab… -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

1 0

SELinux denies login
by Gordon Messmer 13 Apr '20

13 Apr '20

We have a CentOS 7 workstation whose user has started reporting periodic login failures. This seems to be the result of the krb5 cache aging out, and sssd's krb5_child attempting and failing to remove the old cache file. The AVC follows: type=AVC msg=audit(1586670874.327:73041): avc: denied { unlink } for pid=28735 comm="krb5_child" name="krb5cc_1985100122_oxJnH7" dev="dm-0" ino=67978294 scontext=system_u:system_r:sssd_t:s0 tcontext=system_u:object_r:tmp_t:s0 tclass=file permissive=0 The policy allows sssd_t to unlink user_tmp_type: sesearch -s sssd_t --allow: allow sssd_t user_tmp_type : file { ioctl read write create getattr setattr lock relabelfrom relabelto append unlink link rename open } ; Is the problem that the credential cache files in /tmp are being created with the wrong label, or is there some other problem I'm not seeing?

1 0

CentOS 8 NIS
by Mark LaPierre 13 Apr '20

13 Apr '20

Hey all, Does anyone know where I can get NIS for CentOS 8? -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

8 14

Display system logs in chroot ?
by kikinovak 12 Apr '20

12 Apr '20

Hi, This morning my day began quite badly, since my main production server wasn't responsive anymore. For public hosting I'm using a "Dedibox Pro" server at the french provider Online that's recently been acquired by Scaleway. I'm currently managing half a dozen public servers at that provider, all running CentOS 7. For debugging purposes, Online's web console enables you to boot the machine into a live rescue system, in that case Ubuntu 18.04. Once I managed to connect via SSH to the live system, here's what I did. Mount the root partition : # mount /dev/sda2 /mnt Mount the /boot partition : # mount /dev/sda1 /mnt/boot Then : # mount --rbind /proc /mnt/proc # mount --rbind /dev /mnt/dev # mount --rbind /sys /mnt/sys And then I chroot into the system : # chroot /mnt /bin/bash I had networking in the chroot environment. I tried to disable a handful of services like fail2ban and firewalld to begin with, but systemctl won't run in a chroot. So what I did was simply remove everything related to fail2ban and firewalld. Next thing was to look at the system logs to know what went wrong on startup, but I don't know how to do that from within a chroot. Any suggestions? Cheers, Niki PS : sorry for bad formatting. Since the unresponsive server is also running all my mails, I had to setup a Protonmail account to post on this list. Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 2

Zoom?
by mark 11 Apr '20

11 Apr '20

Hi, folks, After I did a complete reinstall of current 7, with KDE instead of minimal, I'm mostly ok... except for Zoom. Has anyone gotten sound working with firefox? I get video, but it keeps claiming that my browser (the default firefox) can't access the system sound. Given that even as I type this, I'm streaming WUMB through its player.... I have noScript, but I enabled everything (except google-analytics), and no joy. I'd *really* rather use my browser than trust their app.... mark

11 15

CentOS 7 : broken dependencies
by Nicolas Kovacs 09 Apr '20

09 Apr '20

Hi, I got an alert from Yum-Cron this morning: Failed to check for updates with the following error message: Failed to build transaction: sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 requires libMagickCore.so.5()(64bit) sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 requires libMagickWand.so.5()(64bit) The CR repository is activated on this server, so I guess that's why. Which leads me to the more general question of: enable CR on a production server, yes or no? Pros : get security updates sooner Cons : expect breakage like the one above Any suggestions? Cheers, Niki -- 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 8

CentOS-announce Digest, Vol 182, Issue 2
by centos-announce-request＠centos.org 09 Apr '20

09 Apr '20

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. CESA-2020:1349 Important CentOS 6 krb5-appl Security Update (Johnny Hughes) 2. CESA-2020:1331 Important CentOS 6 ipmitool Security Update (Johnny Hughes) 3. CESA-2020:1335 Important CentOS 6 telnet Security Update (Johnny Hughes) 4. CESA-2020:1339 Critical CentOS 6 firefox Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 8 Apr 2020 15:29:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1349 Important CentOS 6 krb5-appl Security Update Message-ID: <20200408152938.GA12312(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1349 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:1349 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2cffa95c73d5b9662a971f9eddbd67ce1bf396911127e3d31b52caf60c90d984 krb5-appl-clients-1.0.1-10.el6_10.i686.rpm b7af46946a015ebf805991e9a9341163aec0ecbd1d9edb7cfc0234fbcc2b40cb krb5-appl-servers-1.0.1-10.el6_10.i686.rpm x86_64: 6309ea0347c159b5270abe84ad36d6e6d94c563c41ba107190a79a2a8210ccb6 krb5-appl-clients-1.0.1-10.el6_10.x86_64.rpm 3dced1fba4d6aa65537dedc85ef52ec6d7093edd165279e6284aac7e326f5579 krb5-appl-servers-1.0.1-10.el6_10.x86_64.rpm Source: 24b1ce1567946fff000259c1904aeb7b4736bbd067b6ca929d9869dcab4787e7 krb5-appl-1.0.1-10.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 8 Apr 2020 15:29:49 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1331 Important CentOS 6 ipmitool Security Update Message-ID: <20200408152949.GA12427(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1331 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:1331 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: fe098e08061bc5f26a3ccf7cf13727bcb81372ed1b075f8f6bb72760b554a839 ipmitool-1.8.15-3.el6_10.i686.rpm x86_64: 07ff5fac0cc78ed7bc23e72e668073b9ed878ecc9255021783e22d1f4fe3fcbb ipmitool-1.8.15-3.el6_10.x86_64.rpm Source: 00383fb3bf567a510f400d60bf8e8626bc350a00fbaeac9280db242b7f770bcb ipmitool-1.8.15-3.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 8 Apr 2020 15:30:05 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1335 Important CentOS 6 telnet Security Update Message-ID: <20200408153005.GA12627(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1335 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:1335 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 923d72923ba2cd24753cc70ac63cf25d24718d3c228f6f92d2254ec7d73ef590 telnet-0.17-49.el6_10.i686.rpm 63af65efc0cf601f982af8bc595e12980d43b3c4b9872a273b518d05057c07b6 telnet-server-0.17-49.el6_10.i686.rpm x86_64: 591ba5f1a15b7b68106ddd4021fb4ff5f9c405535efe3b72375fec756ac414c9 telnet-0.17-49.el6_10.x86_64.rpm 4fb370c991172abffe095b182b70b2ed7badea2ae9db89e33c28d66b5c9c339c telnet-server-0.17-49.el6_10.x86_64.rpm Source: 7aba1d5e792fe1bbf45000f404f712727a55724523c36c88f26abe3c0cd1e91b telnet-0.17-49.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Wed, 8 Apr 2020 15:31:17 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:1339 Critical CentOS 6 firefox Security Update Message-ID: <20200408153117.GA13046(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:1339 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2020:1339 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 459d53b5c53d356ac22b15f40bdb6d7c046d1ceb8bfda60a717325677780533f firefox-68.6.1-1.el6.centos.i686.rpm x86_64: 459d53b5c53d356ac22b15f40bdb6d7c046d1ceb8bfda60a717325677780533f firefox-68.6.1-1.el6.centos.i686.rpm e83b453b7ccedac2c51fe1c6885e7d93d94940bf9011bbba921b98e75b6d4bc7 firefox-68.6.1-1.el6.centos.x86_64.rpm Source: cb52c089eb51c556b126bca5243dfa28125152405f1e77de20dbc247c0288733 firefox-68.6.1-1.el6.centos.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 182, Issue 2 ***********************************************

1 0

Re: [CentOS] RHEL 7.8 is out
by Thomas Stephen Lee 08 Apr '20

08 Apr '20

On Wed, Apr 8, 2020 at 2:01 AM Kenneth Porter <shiva(a)sewingwitch.com> wrote: > Some useful info for the list. Release notes! ;) > > < > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… > > > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > Is this https://wiki.centos.org/About/Building_7 the place to look ? thanks. -- Lee

2 1

CentOS 7 and USB 3.1
by Jerry Geis 08 Apr '20

08 Apr '20

I am getting these errors on my machine for an external USB connection. Apr 8 13:23:55 devgeis kernel: xhci_hcd 0000:b3:00.0: ERROR Transfer event for unknown stream ring slot 4 ep 3 Apr 8 13:23:55 devgeis kernel: xhci_hcd 0000:b3:00.0: @00000020155b24c0 00000000 00000000 1a001000 04048001 Apr 8 13:23:55 devgeis kernel: sd 7:0:0:0: [sdd] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT Apr 8 13:23:55 devgeis kernel: sd 7:0:0:0: [sdd] tag#3 CDB: Write(10) 2a 00 35 b8 db ff 00 04 00 00 Apr 8 13:23:55 devgeis kernel: xhci_hcd 0000:b3:00.0: ERROR Transfer event for unknown stream ring slot 4 ep 3 Apr 8 13:23:55 devgeis kernel: xhci_hcd 0000:b3:00.0: @00000020155b24e0 00000000 00000000 1a001000 04048001 Apr 8 13:23:55 devgeis kernel: sd 7:0:0:0: [sdd] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT Apr 8 13:23:55 devgeis kernel: sd 7:0:0:0: [sdd] tag#2 CDB: Write(10) 2a 00 35 b8 d7 ff 00 04 00 00 Apr 8 13:23:55 devgeis kernel: xhci_hcd 0000:b3:00.0: ERROR Transfer event for unknown stream ring slot 4 ep 3 Apr 8 13:23:55 devgeis kernel: xhci_hcd 0000:b3:00.0: @00000020155b2500 00000000 00000000 1a001000 04048001 Apr 8 13:23:55 devgeis kernel: sd 7:0:0:0: [sdd] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT The device is a Crucial MX300 SSD 2T disk. I ran badblocks on it and nothing was reported. Why might I be getting errors ? Jerry

1 1

Upgrade from Centos 7 to Centos 8
by Stefano Simonucci 08 Apr '20

08 Apr '20

I don't understand how I can upgrade my CentOS 7. cat /etc/redhat-release CentOS Linux release 7.7.1908 (Core) I followed the directions found on the web (by installing dnf and so on), but when I tried to install centos-release I get dnf upgrade -y http://mirror.centos.org/centos/8/BaseOS/x86_64/os/Packages/centos-release-… Last metadata expiration check: 0:19:05 ago on Wed 08 Apr 2020 04:50:14 PM CEST. centos-release-8.1-1.1911.0.9.el8.x86_64.rpm 184 kB/s | 21 kB 00:00 Dependencies resolved. Problem: cannot install the best update candidate for package centos-release-7-7.1908.0.el7.centos.x86_64 - nothing provides centos-gpg-keys = 8.1-1.1911.0.9.el8 needed by centos-release-8.1-1.1911.0.9.el8.x86_64 - nothing provides centos-repos = 8.1-1.1911.0.9.el8 needed by centos-release-8.1-1.1911.0.9.el8.x86_64 ================================================================================================================================= Package Arch Version Repository Size ================================================================================================================================= Skipping packages with broken dependencies: centos-release x86_64 8.1-1.1911.0.9.el8 @commandline 21 k Transaction Summary ================================================================================================================================= Skip 1 Package Nothing to do. Complete! Does anyone know how to upgrade? Thanks Stefano

5 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss