January 2021 - devel - lists.centos.org

CPE Weekly: 2021-01-15
by Aoife Moloney 15 Jan '21

15 Jan '21

Hi Everyone, New Year, same CPE weekly(ish) :) If you would like to see this report and toggle to the section you are most interested in, I would suggest visiting this link https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view and use the header bar on your left to skip to where you want to go! ## General Project Updates We are kicking off Q1 this year with some familiar project faces, namely Noggin, the replacement of the current FAS system and continuing our development of CentOS Stream. Most of our initiatives live here https://pagure.io/cpe/initiatives-proposal and you can use the new issue button to submit your own proposal. Our updated initative timetable can be viewed here for 2021 https://docs.fedoraproject.org/en-US/cpe/time_tables/ so you know when I need it in by to review it. We also have updated our docs section on the initiative process we follow as we cannot accept everything so please do check it out if you want to understand our process more https://docs.fedoraproject.org/en-US/cpe/initiatives/ ### Misc #### GitLab Being very honest, I've found myself a little bit strapped for time to give this project its due diligence over the last few months, but please bear with us/me and expect a more concentrated effort on this coming into Q2 (April, May, June) of this year. I apologise for the time a resolution is taking and I really do appreciate all of your patience. ## Project Updates *The below updates are pulled directly from our CPE team call we have every week.* ## CentOS Updates ### CentOS * Community newsletter can be read here https://blog.centos.org/2021/01/centos-community-newsletter-january-2020-21… ### CentOS Stream * Continuing to work on Stream 8 pushes and builds * Investigating how to automate some module pushes * Reviewing documentation that is available on Stream currently to identify gaps and where needs improvement ### Fedora * OSBS is building for aarm64 & x86_64 in production since December! * All of the projects under the fedora-infra and releng namespaces on pagure have had their default branch migrated from “master” to “main”. * F34 mass rebuild due to start next week ### Noggin/AAA * New sprint started focusing on testing correct access has been given per user/account * Last remaining apps being configured & tested with fasjson API * Work will be tracked here https://github.com/fedora-infra/aaa-tracker/issues/4 * Our open issues board can be found here https://github.com/orgs/fedora-infra/projects/6 ### Fedora Messaging Schemas * We are working through supybot and greenwave applications currently * There is a list of applications that require messaging schemas can be found here https://hackmd.io/@nilsph/H1i8CAbkP/edit * There is a readme which contains documentation on messaging schemas, a cookie-cutter template to create the schema and a definition of Done for writing a schemas https://github.com/fedora-infra/fedora-messaging-schemas-issues * The board they are working from can be viewed here https://github.com/orgs/fedora-infra/projects/7 ## Team Info ### Background: The Community Platform Engineering group, or CPE for short, is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. See our wiki page here for more information:https://docs.fedoraproject.org/en-US/cpe/ As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great weekend! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

[CloudSIG] RDO plans to move to CentOS Stream
by Alfredo Moralejo Alonso 14 Jan '21

14 Jan '21

Hi, As you know, CentOS announced recently that they will be focusing on CentOS Stream [1] and that CentOS Linux 8 will be EOL at the end of 2021 [2]. In order to align with this change, the RDO project is adapting the roadmap for the current and upcoming releases: - RDO Wallaby (ETA is end of April 2021 [3]) will be built, tested and released only for CentOS 8 Stream. - RDO CloudSIG repos for Victoria and Ussuri will be updated and tested for both CentOS Stream and CentOS Linux 8 until end of 2021 and then continue on CentOS Stream. - In the upcoming weeks, we will create new RDO CloudSIG repos for Victoria and Ussuri for CentOS Stream 8. - RDO Trunk repositories (aka DLRN repos) will be built and tested using CentOS 8 Stream for all releases currently using CentOS Linux 8 (starting with Train). If you are interested in the details about these plans and how we plan to implement it, we've created a blog post [4]. Don't hesitate to ask us in the ML or in the #rdo channel on freenode if you have questions or suggestions about this. We are also organizing a video AMA about RDO and CentOS Stream on Thursday Jan 21 1600 UTC in the RDO Meet room https://meet.google.com/uzo-tfkt-top On behalf of RDO, Alfredo [1] https://centos.org/distro-faq/ [2] https://blog.centos.org/2020/12/future-is-centos-stream/ [3] https://releases.openstack.org/ [4] https://blogs.rdoproject.org/2021/01/rdo-plans-to-move-to-centos-stream/

1 0

Re: [CentOS-devel] Upgrade to Stream wants to downgrade e.g. httpd
by Yedidyah Bar David 14 Jan '21

14 Jan '21

On Thu, Jan 14, 2021 at 3:23 PM orkcu via CentOS-devel <centos-devel(a)centos.org> wrote: > > Considering that CentOS 8.5 will never be, a year from now (6 month only?) you will not have this issue, as Baron said, with new packages coming to Stream the issue will go away naturally unless you want to move from RHEL to CentOS I can definitely see myself wanting to move from RHEL (or a rebuild) to Stream in the future, for specific uses/machines. And I do not think this is a unique/strange/corner case. I agree it's probably not the most common one. -- Didi

1 0

Upgrade to Stream wants to downgrade e.g. httpd
by Yedidyah Bar David 14 Jan '21

14 Jan '21

Hi all, I have a CentOS 8.3 machine I want to upgrade to Stream following [1]. After fighting with it a bit due to oVirt-specific issues [2], I reached the current point: doing 'dnf update' updated everything nicely, but now doing 'dnf distro-sync' wants to downgrade these packages: Downgrading: httpd x86_64 2.4.37-30.module_el8.3.0+462+ba287492.0.1 appstream 1.7 M httpd-filesystem noarch 2.4.37-30.module_el8.3.0+462+ba287492.0.1 appstream 37 k httpd-tools x86_64 2.4.37-30.module_el8.3.0+462+ba287492.0.1 appstream 104 k mod_ssl x86_64 1:2.4.37-30.module_el8.3.0+462+ba287492.0.1 appstream 133 k python3-docutils noarch 0.14-12.module_el8.3.0+389+6a62c88d appstream 1.6 M python36 x86_64 3.6.8-2.module_el8.3.0+389+6a62c88d appstream 19 k I specifically mention httpd in Subject because that's the one I spent some time looking at, but the issue is general. I currently have httpd-2.4.37-30.module_el8.3.0+561+97fdbbcc.x86_64 . It seems to be the result of [3], which says it was built from: git+https://git.centos.org/rpms/httpd#2f74eecf85362e67c403b7b1386a729da3e5c… . distro-sync wants to downgrade to 2.4.37-30.module_el8.3.0+462+ba287492.0.1 , which seems to be the result of [4], which says it was built from: git+https://git.centos.org/rpms/httpd#fcb5444a5c0aefcd065e6c4a805a454e4988b… . cloning the git repo, and then checking the difference between them, I get: $ git diff 2f74eecf fcb5444a diff --git a/SPECS/httpd.spec b/SPECS/httpd.spec index 8322bd8..7d66f2e 100644 --- a/SPECS/httpd.spec +++ b/SPECS/httpd.spec @@ -13,7 +13,7 @@ Summary: Apache HTTP Server Name: httpd Version: 2.4.37 -Release: 30%{?dist} +Release: 30%{?dist}.0.1 URL: https://httpd.apache.org/ Source0: https://www.apache.org/dist/httpd/httpd-%{version}.tar.bz2 Source1: centos-noindex-8.0.tar.gz So: 1. The sources seem to be identical, right now, with the only difference being the 'Release:'. 2. I failed to find where '462+ba287492' and '561+97fdbbcc' are coming from. I assume they are automatically-generated during the build process, but not saved in the dist-git repo. These seem to be what's causing the "newer" version in Stream to be considered a "Downgrade" - 462 < 561. Perhaps they are some kind of timestamps, or increasing counters, etc., and '462' was built earlier than '561', even if in all other regards it should be considered "newer". 3. Perhaps the intention was to have the release in Stream: Release: 30.0.1%{?dist} ? I think this would have caused this to not be considered a downgrade. I might be missing something. 4. IMO this is a bit confusing/discouraging. Can/Do we do anything so that 8-Stream packages are always >= 8.3 ones? Perhaps a fix should be manually applied to each and every package (if at all), but just generating a report somewhere, perhaps with a place to a link to a bug per package as applicable, can be done in batch, more-or-less, if I got it right. Do we have something like this? Do we want something like this? 5. Perhaps (alternatively?), Stream's version should just be rebuilt, e.g. with 'Release: 30%{?dist}.0.2'. Thanks and best regards, [1] https://www.centos.org/centos-stream/ [2] https://github.com/oVirt/ovirt-cockpit-sso/pull/30 [3] https://koji.mbox.centos.org/koji/buildinfo?buildID=14516 [4] https://koji.mbox.centos.org/koji/buildinfo?buildID=12971 -- Didi

6 8

[CloudSIG] Questions about adopting CentOS 8 Stream
by Alfredo Moralejo Alonso 14 Jan '21

14 Jan '21

Hi, In Cloud SIG, we are planning adoption to CentOS 8 Stream. I'd like to clarify what will be the workflow and get some info about open questions and issues before starting to request stuff. IIUC, the intended workflow to build, ship and consume packages for c8s should be pretty similar to the current one: Build: 1. Request new tags which will use C8S buildroot, something like cloud8s-openstack-victoria-*. 2. Build from srpm on those new tags. Ship: 3. Tagging into cloud8s-openstack-victoria-testing will trigger automatically shipping a package under https://buildlogs.centos.org/centos/8-stream/cloud/x86_64/openstack-victori… (note 8-stream in url). 4. Tagging into cloud8s-openstack-victoria-release will trigger automatically shipping a package under http://mirror.centos.org/centos/8/cloud/x86_64/openstack-victoria/ (note 8-stream in url) Consume: 5. Users in a C8S box, install the release rpm from extras centos-release-openstack-victoria and repos are configured to use from 8-stream URLs. Please confirm this is the intended workflow or if there is any change. I assume we can maintain separated repos for C8 and C8S with different or same (cross-tagged) packages in the SIG. Now, some questions: - The release RPMs will be the same for C8 and C8S (as it is currently) or can be different?, we may have a new release only for C8S and not for C8 so we may need different release rpms. - Do we need to adjust somehow the .repo to point to the right URLs in C8 or C8S (i thing $releasever points to 8 in centos-stream). - Is the infra already ready to build and push packages for C8S or are there open issues that we should be aware of?, is the automated push and ship based on tagging/untagging ready for C8S builds? - Is there any change in naming convention for tags, repos, etc... (i assumed <signame>8s- instead of <signame>8- ). - Should we use a different disttag for C8S buildroots?, (I'd prefer to stay with regular .el8). Best regards, Alfredo

2 2

NFV SIG meeting minutes - 2021-Jan-13
by Thomas F Herbert 13 Jan '21

13 Jan '21

1 0

CentOS Dojo @ FOSDEM
by Rich Bowen 11 Jan '21

11 Jan '21

We are pleased to announce a preliminary schedule for the online CentOS Dojo prior to FOSDEM. Details are available here: https://wiki.centos.org/Events/Dojo/FOSDEM2021 Registration will be free, and the link to registration is at the above page.

1 0

Queries on CentOS Stream
by Chan, Catherine [ITS] 09 Jan '21

09 Jan '21

Hi, I'm working in a University and we have a no. of servers running CentOS Linux. We chose CentOS Linux because it is free of charge. Recently we learned that CentOS is shifting focus from CentOS Linux to CentOS Stream. We are very concerned if CentOS Stream requires subscription and if updates/patches for CentOS Stream requires subscription. Can you help on my queries below: Question 1 Referring to 'FAQ - CentOS Project shifts focus to CentOS Stream' (https://centos.org/distro-faq/<https://secure-web.cisco.com/12vidbGo4KDeMy7BxwP79RXZ8adFilOrBfFEAuqwSj1E2G…>): Q2: What about the other releases of CentOS Linux? A: * Updates for the CentOS Linux 6 distribution ended November 30, 2020<https://secure-web.cisco.com/1AFEn0WSozOLnX5KWTyqLb81hqQsytVdWyuFXdazPwmDg4…>. * Updates for the CentOS Linux 7 distribution continue as before until the end of support for RHEL7<https://secure-web.cisco.com/1Vjg5-b7gAc7XPdTp009SgavZ85rt-79Y60WEjKdZHhQl-…>. * Updates for the CentOS Linux 8 distribution continue until the end of 2021; users can choose to switch over directly to CentOS Stream 8 * Updates for the CentOS Stream 8 distribution continue through the full RHEL support phase<https://secure-web.cisco.com/1Vjg5-b7gAc7XPdTp009SgavZ85rt-79Y60WEjKdZHhQl-…>. We will not be producing a CentOS Linux 9, as a rebuild of RHEL 9. Instead CentOS Stream 9 fulfills this role. (See Q6 below regarding the overlap between concurrent streams.) I don't quite understand the 4th point, 'Updates for the CentOS Stream 8 distribution continue through the full RHEL support phase<https://secure-web.cisco.com/1Vjg5-b7gAc7XPdTp009SgavZ85rt-79Y60WEjKdZHhQl-…>'. Can you further elaborate it? Does it mean that users will receive updates/patches for CentOS Stream 8 ONLY if they subscribe full RHEL support? Question 2 In the announcement, it states 'If you are using CentOS Linux 8 in a production environment, and are concerned that CentOS Stream will not meet your needs, we encourage you to contact Red Hat about options.' Can you highlight what are the drawbacks of CentOS Stream causing not encouraged to run on a production environment? Thanks very much in advance. Regards, Catherine Chan [https://www.polyu.edu.hk/emaildisclaimer/PolyU_Email_Signature.jpg] Disclaimer: This message (including any attachments) contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and notify the sender and The Hong Kong Polytechnic University (the University) immediately. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited and may be unlawful. The University specifically denies any responsibility for the accuracy or quality of information obtained through University E-mail Facilities. Any views and opinions expressed are only those of the author(s) and do not necessarily represent those of the University and the University accepts no liability whatsoever for any losses or damages incurred or caused to any party as a result of the use of such information.

6 8

Re: [CentOS-devel] [Gluster-devel] Multiple Geo Rep issues due to SELINUX on CentOS 8.3
by Strahil Nikolov 08 Jan '21

08 Jan '21

Hi Srijan, I will redeploy the scenario and I will check if the steps include that package. Shouldn't glusterfs-selinux a dependency ? Best Regards, Strahil Nikolov В сряда, 6 януари 2021 г., 07:29:27 Гринуич+2, Srijan Sivakumar <ssivakum(a)redhat.com> написа: Hi Strahil, Selinux policies and rules have to be added for gluster processes to work as intended when selinux is in enforced mode. Could you confirm if you've installed the glusterfs-selinux package in the nodes ? If not then you can check out the repo at https://github.com/gluster/glusterfs-selinux. Regards, Srijan On Wed, Jan 6, 2021 at 2:15 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > Did anyone receive that e-mail ? > Any hints ? > > Best Regards, > Strahil Nikolov > > В 19:05 +0000 на 30.12.2020 (ср), Strahil Nikolov написа: >> Hello All, >> >> I have been testing Geo Replication on Gluster v 8.3 ontop CentOS >> 8.3. >> It seems that everything works untill SELINUX is added to the >> equasion. >> >> So far I have identified several issues on the Master Volume's nodes: >> - /usr/lib/ld-linux-x86-64.so.2 has a different SELINUX Context than >> the target that it is pointing to. For details check >> https://bugzilla.redhat.com/show_bug.cgi?id=1911133 >> >> - SELINUX prevents /usr/bin/ssh from search access to >> /var/lib/glusterd/geo-replication/secret.pem >> >> - SELinux is preventing /usr/bin/ssh from search access to .ssh >> >> - SELinux is preventing /usr/bin/ssh from search access to >> /tmp/gsyncd-aux-ssh-tnwpw5tx/274d5d142b02f84644d658beaf86edae.sock >> >> Note: Using 'semanage fcontext' doesn't work due to the fact that >> files created are inheriting the SELINUX context of the parent dir >> and you need to restorecon after every file creation by the geo- >> replication process. >> >> - SELinux is preventing /usr/bin/rsync from search access on >> .gfid/00000000-0000-0000-0000-000000000001 >> >> Obviously, those needs fixing before anyone is able to use Geo- >> Replication with SELINUX enabled on the "master" volume nodes. >> >> Should I open a bugzilla at bugzilla.redhat.com for the selinux >> policy? >> >> Further details: >> [root@glustera ~]# cat /etc/centos-release >> CentOS Linux release 8.3.2011 >> >> [root@glustera ~]# rpm -qa | grep selinux | sort >> libselinux-2.9-4.el8_3.x86_64 >> libselinux-utils-2.9-4.el8_3.x86_64 >> python3-libselinux-2.9-4.el8_3.x86_64 >> rpm-plugin-selinux-4.14.3-4.el8.x86_64 >> selinux-policy-3.14.3-54.el8.noarch >> selinux-policy-devel-3.14.3-54.el8.noarch >> selinux-policy-doc-3.14.3-54.el8.noarch >> selinux-policy-targeted-3.14.3-54.el8.noarch >> >> [root@glustera ~]# rpm -qa | grep gluster | sort >> centos-release-gluster8-1.0-1.el8.noarch >> glusterfs-8.3-1.el8.x86_64 >> glusterfs-cli-8.3-1.el8.x86_64 >> glusterfs-client-xlators-8.3-1.el8.x86_64 >> glusterfs-fuse-8.3-1.el8.x86_64 >> glusterfs-geo-replication-8.3-1.el8.x86_64 >> glusterfs-server-8.3-1.el8.x86_64 >> libglusterd0-8.3-1.el8.x86_64 >> libglusterfs0-8.3-1.el8.x86_64 >> python3-gluster-8.3-1.el8.x86_64 >> >> >> [root@glustera ~]# gluster volume info primary >> >> Volume Name: primary >> Type: Distributed-Replicate >> Volume ID: 89903ca4-9817-4c6f-99de-5fb3e6fd10e7 >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 5 x 3 = 15 >> Transport-type: tcp >> Bricks: >> Brick1: glustera:/bricks/brick-a1/brick >> Brick2: glusterb:/bricks/brick-b1/brick >> Brick3: glusterc:/bricks/brick-c1/brick >> Brick4: glustera:/bricks/brick-a2/brick >> Brick5: glusterb:/bricks/brick-b2/brick >> Brick6: glusterc:/bricks/brick-c2/brick >> Brick7: glustera:/bricks/brick-a3/brick >> Brick8: glusterb:/bricks/brick-b3/brick >> Brick9: glusterc:/bricks/brick-c3/brick >> Brick10: glustera:/bricks/brick-a4/brick >> Brick11: glusterb:/bricks/brick-b4/brick >> Brick12: glusterc:/bricks/brick-c4/brick >> Brick13: glustera:/bricks/brick-a5/brick >> Brick14: glusterb:/bricks/brick-b5/brick >> Brick15: glusterc:/bricks/brick-c5/brick >> Options Reconfigured: >> changelog.changelog: on >> geo-replication.ignore-pid-check: on >> geo-replication.indexing: on >> storage.fips-mode-rchecksum: on >> transport.address-family: inet >> nfs.disable: on >> performance.client-io-threads: off >> cluster.enable-shared-storage: enable >> >> I'm attaching the audit log and sealert analysis from glustera (one >> of the 3 nodes consisting of the 'master' volume). >> >> >> Best Regards, >> Strahil Nikolov > >> > > ------- > > Community Meeting Calendar: > Schedule - > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC > Bridge: https://meet.google.com/cpu-eiue-hvk > > Gluster-devel mailing list > Gluster-devel(a)gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-devel > > >

1 2

glibc-2.28-145.el8 with glibc-hwcaps support is coming to CentOS Stream 8
by Florian Weimer 08 Jan '21

08 Jan '21

We have rebased a large part of the glibc dynamic loader and the x86 CPU detection infrastructure to the current upstream version. These changes are going to land in CentOS Stream soon. These glibc changes mean that going forward, run-time selection of optimized shared object implementations is possible for all x86 processors (e.g., generic AVX2-optimized code that gets loaded on EPYC and Xeon Scalable processors). This is primarily being done to allow user application code to leverage this functionality. At this time, we are not adjusting or optimizing CentOS Stream packages themselves. Convenient developer support depends on GCC Toolset 11 and LLVM Toolset 12, which are yet to be released (even in their upstream versions). I’m working on some form of documentation on how to produce builds that are compatible with this feature for earlier toolchain versions. Other changes in the new glibc version include: * Backwards-compatible ld.so cache format changes to support glibc-hwcaps * --argv0 support in ld.so * DT_AUDIT support: The --audit option in binutils ld finally works as expected. * Enhanced --help output in ld.so: “/lib64/ld-linux-x86-64.so.2 --help” shows library search path information. * TLS allocation improvements: dlopen is able to load shared objects that use initial-exec TLS in more cases. There is a new glibc.rtld.optional_static_tls tunable to support exceptionally large initial-exec TLS usage after dlopen. * The CPU tunable namespace has been renamed from “glibc.tune” to “glibc.cpu”. If you have any questions, please feel free to ask on-list. Thanks, Florian -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

3 5

TLS issues koji.mbox.centos.org
by Leon Fauster 07 Jan '21

07 Jan '21

On a C8 station: LANG=C curl -I https://koji.mbox.centos.org curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.haxx.se/docs/sslcerts.html this worked a couple of days ago. Any hints? -- Leon

3 5

Hyperscale SIG (Proposed)
by Rich Bowen 06 Jan '21

06 Jan '21

FYI: A Hyperscale SIG has been proposed, and will be considered in next week's board meeting. Details may be found here: https://wiki.centos.org/SpecialInterestGroup/Hyperscale --Rich

1 0

Why gnutls update was built for c8 but not c8s?
by Igor Raits 06 Jan '21

06 Jan '21

Hello, The https://git.centos.org/rpms/gnutls/c/3ec527a2c4ad3bad520b1004a50c075d94cc80… has been imported month ago, but there was just build for c8 from today and none for c8s. Is the process of building automated, or who is responsible for building the updates for c8s? Thanks in advance for your help!

1 0

should we expect to close CentOS Stream bugs as dups of RHEL?
by Ken Dreyer 06 Jan '21

06 Jan '21

Hi folks, This RHBZ tracks a problem in CentOS Stream: https://bugzilla.redhat.com/show_bug.cgi?id=1901449 Today someone closed it as a duplicate of RHEL 8.4: https://bugzilla.redhat.com/show_bug.cgi?id=1901449 When is it appropriate to track a bug against RHEL 8.4 vs CentOS Stream? What do we expect community members (inside and outside RH) to do in these cases? - Ken

11 14

Re: [CentOS-devel] Multiple Geo Rep issues due to SELINUX on CentOS 8.3
by Strahil Nikolov 05 Jan '21

05 Jan '21

Did anyone receive that e-mail ? Any hints ? Best Regards, Strahil Nikolov В 19:05 +0000 на 30.12.2020 (ср), Strahil Nikolov написа: > Hello All, > > I have been testing Geo Replication on Gluster v 8.3 ontop CentOS > 8.3. > It seems that everything works untill SELINUX is added to the > equasion. > > So far I have identified several issues on the Master Volume's nodes: > - /usr/lib/ld-linux-x86-64.so.2 has a different SELINUX Context than > the target that it is pointing to. For details check > https://bugzilla.redhat.com/show_bug.cgi?id=1911133 > > - SELINUX prevents /usr/bin/ssh from search access to > /var/lib/glusterd/geo-replication/secret.pem > > - SELinux is preventing /usr/bin/ssh from search access to .ssh > > - SELinux is preventing /usr/bin/ssh from search access to > /tmp/gsyncd-aux-ssh-tnwpw5tx/274d5d142b02f84644d658beaf86edae.sock > > Note: Using 'semanage fcontext' doesn't work due to the fact that > files created are inheriting the SELINUX context of the parent dir > and you need to restorecon after every file creation by the geo- > replication process. > > - SELinux is preventing /usr/bin/rsync from search access on > .gfid/00000000-0000-0000-0000-000000000001 > > Obviously, those needs fixing before anyone is able to use Geo- > Replication with SELINUX enabled on the "master" volume nodes. > > Should I open a bugzilla at bugzilla.redhat.com for the selinux > policy? > > Further details: > [root@glustera ~]# cat /etc/centos-release > CentOS Linux release 8.3.2011 > > [root@glustera ~]# rpm -qa | grep selinux | sort > libselinux-2.9-4.el8_3.x86_64 > libselinux-utils-2.9-4.el8_3.x86_64 > python3-libselinux-2.9-4.el8_3.x86_64 > rpm-plugin-selinux-4.14.3-4.el8.x86_64 > selinux-policy-3.14.3-54.el8.noarch > selinux-policy-devel-3.14.3-54.el8.noarch > selinux-policy-doc-3.14.3-54.el8.noarch > selinux-policy-targeted-3.14.3-54.el8.noarch > > [root@glustera ~]# rpm -qa | grep gluster | sort > centos-release-gluster8-1.0-1.el8.noarch > glusterfs-8.3-1.el8.x86_64 > glusterfs-cli-8.3-1.el8.x86_64 > glusterfs-client-xlators-8.3-1.el8.x86_64 > glusterfs-fuse-8.3-1.el8.x86_64 > glusterfs-geo-replication-8.3-1.el8.x86_64 > glusterfs-server-8.3-1.el8.x86_64 > libglusterd0-8.3-1.el8.x86_64 > libglusterfs0-8.3-1.el8.x86_64 > python3-gluster-8.3-1.el8.x86_64 > > > [root@glustera ~]# gluster volume info primary > > Volume Name: primary > Type: Distributed-Replicate > Volume ID: 89903ca4-9817-4c6f-99de-5fb3e6fd10e7 > Status: Started > Snapshot Count: 0 > Number of Bricks: 5 x 3 = 15 > Transport-type: tcp > Bricks: > Brick1: glustera:/bricks/brick-a1/brick > Brick2: glusterb:/bricks/brick-b1/brick > Brick3: glusterc:/bricks/brick-c1/brick > Brick4: glustera:/bricks/brick-a2/brick > Brick5: glusterb:/bricks/brick-b2/brick > Brick6: glusterc:/bricks/brick-c2/brick > Brick7: glustera:/bricks/brick-a3/brick > Brick8: glusterb:/bricks/brick-b3/brick > Brick9: glusterc:/bricks/brick-c3/brick > Brick10: glustera:/bricks/brick-a4/brick > Brick11: glusterb:/bricks/brick-b4/brick > Brick12: glusterc:/bricks/brick-c4/brick > Brick13: glustera:/bricks/brick-a5/brick > Brick14: glusterb:/bricks/brick-b5/brick > Brick15: glusterc:/bricks/brick-c5/brick > Options Reconfigured: > changelog.changelog: on > geo-replication.ignore-pid-check: on > geo-replication.indexing: on > storage.fips-mode-rchecksum: on > transport.address-family: inet > nfs.disable: on > performance.client-io-threads: off > cluster.enable-shared-storage: enable > > I'm attaching the audit log and sealert analysis from glustera (one > of the 3 nodes consisting of the 'master' volume). > > > Best Regards, > Strahil Nikolov >

1 0

RFC: CentOS 8 SIG
by redbaronbrowser 05 Jan '21

05 Jan '21

This is an introductory Request For Comment to purpose a community SIG to run CentOS 8 from Jan 1, 2022 to June 30, 2024. The responsiblity of the SIG members will be to maintain a repository of Stream 8 packages which have been accepted for publication into RHEL 8 The benefit to the CentOS community should be two fold: (1) Hopefully smooth the transistion from CentOS 8 to either Stream or Elephant (2) Provide a repository for Stream 8 members to perform a dnf downgrade as needed The purposed SIG is also seeking a CentOS Governing board member as a sponsor.

4 4

SIG representatives for January Board meeting
by Rich Bowen 05 Jan '21

05 Jan '21

In our attempt to increase the openness of the board meeting process, the board has asked for a phased approach, with SIG leaders attending the meetings, before we open them entirely to the project, so that we can assess whether we're still able to complete business in the allotted time with more attendees. We appreciate your patience. To that end, I ask that each SIG let me know who they would like to send as a representative to the January board meeting (Wednesday, January 13th, 21:00 UTC) so that they can be added to the invite list for the meeting. You may send this info to me, or to Thomas Oulevey, board secretary. Thanks.

1 0

what uses the messages on mqtt.git.centos.org?
by Ken Dreyer 05 Jan '21

05 Jan '21

Hi folks, I was reading about the MQTT broker at mqtt.git.centos.org? (https://wiki.centos.org/Sources) Does anything in CentOS infrastructure consume those messages (for example, to automatically build packages in Koji based on Pagure pushes)? I was also wondering about https://github.com/CentOS/ansible-role-kojihub/commits/master/files/plugins… , does any other tool consume those messages? - Ken

4 3

Re: [CentOS-devel] Vote of Confidence
by Mark Mielke 04 Jan '21

04 Jan '21

On Sat, Jan 2, 2021 at 8:50 AM orkcu via CentOS-devel <centos-devel(a)centos.org> wrote: > I don't think CentOS (or any other clone/rebuild) was ever a Bazaar, it can not be if the goal is to be a good clone/rebuild. > Since the very beginning the control was in a handful of people, very tight, and I remember one crisis when the founder didn't want (was unable/unavailable) to release control of dns domain, sign keys and few other main components that now you complain RedHat don't want to release I think you are right. The original intent, and the announcements and documentation for the project suggested something greater, but the reality turned out to be difficulty in delegation and scale. This is a common problem for volunteer or non-profit organizations. It doesn't matter if you have 3000 people willing to work on your project for free, if you can't effectively assign them work to do. It's worse if you can't even scale beyond a small number like "3", as these 3 eventually move on, and there is no succession plan, resulting in the project failing. For many of us - I think we had a naive trust that this would be figured out, and we would be invited when the time came to invite us. However, it didn't happen, and in 2014, Red Hat offered to take the reins. It's not that Red Hat set out to destroy the community - it is only that Red Hat has a conflict of interest, and it is really difficult for this conflict of interest to not eventually result in favouring certain self-interest outcomes over other non self-interest outcomes, and this is exactly what is happening in 2021. In effect, it was an inevitable conclusion. It was even predicted by several people in 2014. A similar thing is playing out in Rocky right now, however, there is a great deal of accumulated know-how, access to resources, and sober reflection on what went wrong leading up to 2014 and 2020. 3000+ people willing to work for free, but probably only 70 will be able to directly contribute, and initially the number will be a lot fewer as the initial setup takes place. This is why I say that Rocky is what CentOS should have been in 2014. We all know it wasn't. Now there is a chance to fix this. It could be a very good thing. > I don't like CentOS to evolve to Stream, I agree there is a need of a cheap RHEL's quality distribution, and I think all the arguments given so far at the end (in the very bottom) it is about cost (money), from the people complaining about the end because we are losing a very good distro that was free/gratis, from RedHat it is about moving the money to a direction that might provide better benefits for the company. > If RedHat would offer its RHEL with a minimum price (20? 50? 100?) for self support and then charge for a ticket a good amount of money ( like 200? 500?), that might work for a lot of people who are complaining now, I think we all understand that everyone need to have an income to feed its needs, even the small shops that are trying to save in (software) costs as much as possible. If Red Hat had agreed to this in 2016 and 2017 when I was asking for a reasonable solution to our problem, the company I work for would still be a Red Hat only shop. This was an opportunity missed then, and I believe it will be an opportunity missed when the new plans are announced. I don't believe the new subscription plans will be enough to make them an attractive option, and after the stumble with CentOS, even a good subscription plan that might meet some use cases will be frowned upon as a result of this debacle. > Bottom line, I don't think we ever had a community built OS in CentOS, we had people of the community assisting in testing and QA, but not even that was open to the public. I might be wrong but I think even before 2014 we had builders that were not (much) active in mailing list or IRC, and that is OK, each person have different strengths. I don't think you are wrong. Healthy communities need to prioritize delegation and scalability. It means investing specific effort in ensuring that people of different skills and capabilities can successfully contribute to the project. -- Mark Mielke <mark.mielke(a)gmail.com>

7 9

Package AppStreams variants in CentOS Stream?
by Leon Fauster 04 Jan '21

04 Jan '21

Hey, corresponding to CentOS 8 Stream: will ALL package/module versions for the different AppStreams be available? Some appstreams are only available as latest version (maven, nginx, perl, php). Wish you all some nice and healthy Christmas days, Leon

3 4

Vote of Confidence
by redbaronbrowser 03 Jan '21

03 Jan '21

This is an *UNOFFICIAL* non-binding vote to help provide an assessment of the state of the CentOS community and provoke further discussion. On November 11th (7 weeks ago), the CentOS governance board voted to reduce the life span of CentOS 8 from 10 years to 2 years. One board member, Karsten Wade, this is part of Red Hat effort to close the openness gap. He also explained that there is an elephant of which the community has only been shown parts with a flashlight. The CentOS governance page describe the governing board as being like a greenhouse. Why is the greenhouse so darken that it can hide an elephant such that over the last 7 weeks it has never been fully shown in the brightness of day? Part of the problem is the governance board is packed with people that are not active members of the CentOS community and have made no effort to explain the board's actions to the community. Please vote on each of the following items with +1 (in favor), 0 (sustain), -1 (reject). If you vote to reject an item, please explain why. Should Brian Exelbierd be asked to resign from the CentOS governance board? Should Mike McLean be asked to resign from the CentOS governance board? Should Carl Trieloff be asked to resign from the CentOS governance board? Should Rich Bowen be asked to resign from the CentOS governance board? Is obfuscating the CentOS kernel patches consistent with Red Hat attempting to close the openness gap? Are you likely to ever assist with Stream if the CentOS 8 End of Life is December 31, 2021? Would you be more likely to help with Stream if the CentOS 8 End of Life was set to June 30, 2024? Please keep in mind this vote is *UNOFFICIAL* and only for the purpose of promoting discussion. Template for responding: BE resign: [+1|0|-1] [-1 reason] MM resign: [+1|0|-1] [-1 reason] CT resign: [+1|0|-1] [-1 reason] RB resign: [+1|0|-1] [-1 reason] Obfuscation = Openness: [+1|0|-1] [-1 reason] EOL 2021: [+1|0|-1] [-1 reason] EOL 2024: [+1|0|-1] [-1 reason]

7 10

rare but repeating system crash in C7
by Fred 02 Jan '21

02 Jan '21

Hi all, I'm hoping someone can help me figure this out. every now and then (less than monthly, maybe every 2-4 months, or so, I'll walk up to my C7 box (my home PC) in the morning, wiggle the mouse to wake up the screen, and after a second or so, instead of a live screen, the keyboard shift-lock and scroll-lock keys light up. if I wait a few (tens of) second(s) I find it is rebooting, as the BIOS splash screen appears. it boots normally and comes up with everything apparently working fine. Note that I tend to leave myself logged in 24/7/365 since there's nobody here except my wife and myself, and she has her own Linux box. as it happened again this morning, I grabbed some lines from /var/log/messages that show the last few minutes before it rebooted and the first 3 or four statements as it began to reboot: Jan 2 08:50:12 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cb10 trb-start 00000000a9f2cb20 trb-end 00000000a9f2cb20 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 08:50:13 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:50:13 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164858d0 trb-start 00000000164858e0 trb-end 00000000164858e0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 08:51:12 fcshome dbus[1192]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Jan 2 08:51:13 fcshome dbus[1192]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Jan 2 08:51:14 fcshome setroubleshoot: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock. For complete SELinux messages run: sealert -l e4620dcc-6cdc-460d-a8a4-db9ce9624646 Jan 2 08:51:14 fcshome python: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that smbd should be allowed read access on the cups.sock sock_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'lpqd' --raw | audit2allow -M my-lpqd#012# semodule -i my-lpqd.pp#012 Jan 2 08:55:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:55:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485d20 trb-start 0000000016485d30 trb-end 0000000016485d30 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 08:55:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:55:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cae0 trb-start 00000000a9f2caf0 trb-end 00000000a9f2caf0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 08:58:00 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:58:00 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c530 trb-start 00000000a9f2c540 trb-end 00000000a9f2c540 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 08:59:51 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:59:51 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c340 trb-start 00000000a9f2c350 trb-end 00000000a9f2c350 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 08:59:51 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:59:51 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cfb0 trb-start 00000000a9f2cfc0 trb-end 00000000a9f2cfc0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:00:02 fcshome systemd: Created slice User Slice of root. Jan 2 09:00:02 fcshome systemd: Started Session 7364 of user root. Jan 2 09:00:02 fcshome systemd: Removed slice User Slice of root. Jan 2 09:00:06 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:00:06 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cd20 trb-start 00000000a9f2cd30 trb-end 00000000a9f2cd30 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485400 trb-start 0000000016485410 trb-end 0000000016485410 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cbc0 trb-start 00000000a9f2cbd0 trb-end 00000000a9f2cbd0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:00:59 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485c00 trb-start 0000000016485c10 trb-end 0000000016485c10 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:01:01 fcshome systemd: Created slice User Slice of root. Jan 2 09:01:01 fcshome systemd: Started Session 7365 of user root. Jan 2 09:01:01 fcshome systemd: Removed slice User Slice of root. Jan 2 09:03:45 fcshome dbus[1192]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Jan 2 09:03:46 fcshome dbus[1192]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Jan 2 09:03:47 fcshome setroubleshoot: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock. For complete SELinux messages run: sealert -l e4620dcc-6cdc-460d-a8a4-db9ce9624646 Jan 2 09:03:47 fcshome python: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that smbd should be allowed read access on the cups.sock sock_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'lpqd' --raw | audit2allow -M my-lpqd#012# semodule -i my-lpqd.pp#012 Jan 2 09:04:31 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:04:31 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2ca60 trb-start 00000000a9f2ca70 trb-end 00000000a9f2ca70 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:04:58 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:04:58 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cd70 trb-start 00000000a9f2cd80 trb-end 00000000a9f2cd80 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:04:59 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:04:59 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485b30 trb-start 0000000016485b40 trb-end 0000000016485b40 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:04:59 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:04:59 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164856c0 trb-start 00000000164856d0 trb-end 00000000164856d0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:05:03 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:05:03 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164851b0 trb-start 00000000164851c0 trb-end 00000000164851c0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:10:01 fcshome systemd: Created slice User Slice of root. Jan 2 09:10:01 fcshome systemd: Started Session 7366 of user root. Jan 2 09:10:01 fcshome systemd: Removed slice User Slice of root. Jan 2 09:10:30 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:10:30 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164854c0 trb-start 00000000164854d0 trb-end 00000000164854d0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:10:30 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:10:30 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485eb0 trb-start 0000000016485ec0 trb-end 0000000016485ec0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:11:55 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:11:55 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164852c0 trb-start 00000000164852d0 trb-end 00000000164852d0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:11:55 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:11:55 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485b70 trb-start 0000000016485b80 trb-end 0000000016485b80 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cbb0 trb-start 00000000a9f2cbc0 trb-end 00000000a9f2cbc0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164858d0 trb-start 00000000164858e0 trb-end 00000000164858e0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:11:56 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485a00 trb-start 0000000016485a10 trb-end 0000000016485a10 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:14:46 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:14:46 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485450 trb-start 0000000016485460 trb-end 0000000016485460 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:09 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:09 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c170 trb-start 00000000a9f2c180 trb-end 00000000a9f2c180 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:09 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:09 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c7a0 trb-start 00000000a9f2c7b0 trb-end 00000000a9f2c7b0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:10 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:10 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485560 trb-start 0000000016485570 trb-end 0000000016485570 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:21 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:21 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485b90 trb-start 0000000016485ba0 trb-end 0000000016485ba0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:21 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:21 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cf90 trb-start 00000000a9f2cfa0 trb-end 00000000a9f2cfa0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:22 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:22 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c9e0 trb-start 00000000a9f2c9f0 trb-end 00000000a9f2c9f0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:22 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:22 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485660 trb-start 0000000016485670 trb-end 0000000016485670 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:23 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:23 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485330 trb-start 0000000016485340 trb-end 0000000016485340 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:24 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:24 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485500 trb-start 0000000016485510 trb-end 0000000016485510 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:25 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:25 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c400 trb-start 00000000a9f2c410 trb-end 00000000a9f2c410 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:25 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:25 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000164851c0 trb-start 00000000164851d0 trb-end 00000000164851d0 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485e30 trb-start 0000000016485e40 trb-end 0000000016485e40 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cbf0 trb-start 00000000a9f2cc00 trb-end 00000000a9f2cc00 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:26 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c000 trb-start 00000000a9f2c010 trb-end 00000000a9f2c010 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:27 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:27 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2ce50 trb-start 00000000a9f2ce60 trb-end 00000000a9f2ce60 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:31 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:31 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c4e0 trb-start 00000000a9f2c4f0 trb-end 00000000a9f2c4f0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:15:47 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:15:47 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cbb0 trb-start 00000000a9f2cbc0 trb-end 00000000a9f2cbc0 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:16:15 fcshome dbus[1192]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Jan 2 09:16:16 fcshome dbus[1192]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Jan 2 09:16:17 fcshome setroubleshoot: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock. For complete SELinux messages run: sealert -l e4620dcc-6cdc-460d-a8a4-db9ce9624646 Jan 2 09:16:17 fcshome python: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that smbd should be allowed read access on the cups.sock sock_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'lpqd' --raw | audit2allow -M my-lpqd#012# semodule -i my-lpqd.pp#012 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 0000000016485b50 trb-start 0000000016485b60 trb-end 0000000016485b60 seg-start 0000000016485000 seg-end 0000000016485ff0 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c050 trb-start 00000000a9f2c060 trb-end 00000000a9f2c060 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c680 trb-start 00000000a9f2c690 trb-end 00000000a9f2c690 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:11 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2cb70 trb-start 00000000a9f2cb80 trb-end 00000000a9f2cb80 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:17:21 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:21 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2c520 trb-start 00000000a9f2c530 trb-end 00000000a9f2c530 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:17:21 fcshome kernel: xhci_hcd 0000:03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:17:21 fcshome kernel: xhci_hcd 0000:03:00.0: Looking for event-dma 00000000a9f2ca10 trb-start 00000000a9f2ca20 trb-end 00000000a9f2ca20 seg-start 00000000a9f2c000 seg-end 00000000a9f2cff0 Jan 2 09:20:11 fcshome kernel: Initializing cgroup subsys cpuset Jan 2 09:20:11 fcshome kernel: Initializing cgroup subsys cpu Jan 2 09:20:11 fcshome kernel: Initializing cgroup subsys cpuacct Jan 2 09:20:11 fcshome kernel: Linux version 3.10.0-1160.6.1.el7.x86_64 The last four events are the start of reboot and everything above is leading up to the crash. I note that there was a selinux event early in this list of events, but I see those frequently and they normally don't cause a crash. if I scroll upward from this list, I find more of the same above what is shown here. The selinux event seems to be related to a SMB mount. since I have a Synology box on the LAN, and it stays mounted nearly all the time, I suspect the selinux event has something to do with that, but I have no idea why it would cause a crash once every few months. Is that selinux event something I need to fix? I'm further guessing that "xhci_hcd" has something to do with USB, am I right? If so I don't know what it would be... Clues would be greatly appreciated! Thanks in advance! Fred

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2021