Re: [CentOS] KVM virsh console to physical console?
Il 12/02/22 00:33, Lists ha scritto: I'm preparing to virtualize a Windows server onto a Linux system under virsh. Initial results are looking good, but an issue that's come up is the need to log into the Linux system prior to being able to access the Windows system for updates. Is there a way to "connect" the virsh console directly to a physical Linux terminal? EG: Ctl+Alt+F8 to access the Windows virsh console for Windows Server Thank you Ben Smith ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi, I'm in late. If you are using virsh, you are using libvirt. From what I know you can connect a virt-manager (and probably cockpit) to te libvirtd of the host system (where the Guest runs) from another workstation using virt-manager or cockpit via browser. Hope that helps ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] The conclusio: CentOS is dead
Il 14/12/20 23:47, Ruslanas Gžibovskis ha scritto: your suggestions? It is the debian family time man. I'm converting many stuff to debian buster and some on Ubuntu LTS 20.04. Would be great if FreeBSD will be largely adopted now. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] I'm looking forward to the future of CentOS Stream
Il 11/12/20 12:59, Konstantin Boyandin via CentOS ha scritto: On 11.12.2020 17:41, Alessandro Baggi wrote: Il 11/12/20 10:24, Konstantin Boyandin via CentOS ha scritto: My primary objection is breach of trust. RH shouldn't have lied at least to CentOS community. Other bug-to-bug compatible RHEL clones will replace the CentOS, so this is the part I am less worried about. If someone is happy with CentOS Stream, that's fine. I am not, but that's (not only) my problem. This. Centos Stream is NOT a REPLACEMENT of CentOS, it is a different "product" used as a rhel preview (and testing platform for next rhel releases [minor/major]). This is a simple direction change for a corporation. I accept this without any problem, they have not any legal duty with CentOS community. Ethically, wow...they should ask itself WTF did they done. But no problem..many of us have imagined this since IBM ops (also if this is a centos board decision), today it is reality. Really there is nothing new for me (This is why I started to find alternatives for my case usage since 8 was released waiting the switch to see if direction was good) The days you install CentOS as server distro for stability and compatibility are gone. I always used centos and not rhel because I don't need support. I don't need CentOS Stream so I will not use it. CentOS 8, with its all defects, was enough for me and I think I will not use rhel until forced. So for me (and many) there is not an alternative then to change ship and switch to Debian/Ubuntu LTS that are not bad systems. Intended, there are other alternatives like SUSE/OpenSUSE, OL and other... I started intensively using Debian, Ubuntu and Kali 3+ years ago. So far, they are solid enough (talking of LTS) and quite reliable, as CentOS 6 was. I read many times that Debian/Ubuntu LTS are not centos/rhel, this is true (they are different products) but please, stop saying this, them are not shitty distro..but when I read that many users use fedora as server distro I laugh. I'm not in enterprise so I don't need this type of "support" and can change the distro without any problem but I will stay away from CentOS/RH products due to 0 trust in them. For the past years, for CentOS 6,7 and 8 thank you Johnny, Rich and all other maintainers. You did a great job. I agree, I think I leave this thread on a good line. The maintainers did great job (and I hope they will keep doing it). But "tempora mutantur, and nos mutamus in illis". Good luck to all of us. "tempora mutantur, and nos mutamus in illis" +1 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] I'm looking forward to the future of CentOS Stream
Il 11/12/20 10:24, Konstantin Boyandin via CentOS ha scritto: My primary objection is breach of trust. RH shouldn't have lied at least to CentOS community. Other bug-to-bug compatible RHEL clones will replace the CentOS, so this is the part I am less worried about. If someone is happy with CentOS Stream, that's fine. I am not, but that's (not only) my problem. This. Centos Stream is NOT a REPLACEMENT of CentOS, it is a different "product" used as a rhel preview (and testing platform for next rhel releases [minor/major]). This is a simple direction change for a corporation. I accept this without any problem, they have not any legal duty with CentOS community. Ethically, wow...they should ask itself WTF did they done. But no problem..many of us have imagined this since IBM ops (also if this is a centos board decision), today it is reality. Really there is nothing new for me (This is why I started to find alternatives for my case usage since 8 was released waiting the switch to see if direction was good) The days you install CentOS as server distro for stability and compatibility are gone. I always used centos and not rhel because I don't need support. I don't need CentOS Stream so I will not use it. CentOS 8, with its all defects, was enough for me and I think I will not use rhel until forced. So for me (and many) there is not an alternative then to change ship and switch to Debian/Ubuntu LTS that are not bad systems. Intended, there are other alternatives like SUSE/OpenSUSE, OL and other... I read many times that Debian/Ubuntu LTS are not centos/rhel, this is true (they are different products) but please, stop saying this, them are not shitty distro..but when I read that many users use fedora as server distro I laugh. I'm not in enterprise so I don't need this type of "support" and can change the distro without any problem but I will stay away from CentOS/RH products due to 0 trust in them. For the past years, for CentOS 6,7 and 8 thank you Johnny, Rich and all other maintainers. You did a great job. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [CentOS-devel] https://blog.centos.org/2020/12/future-is-centos-stream/
Il 08/12/20 18:19, Marc Balmer via CentOS ha scritto: Am I the only one to perceive CentOS/RedHat team members responses as quite arrogant? No and this is not started with the current discussion. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [CentOS-devel] https://blog.centos.org/2020/12/future-is-centos-stream/
Il 08/12/20 17:17, Marc Balmer via CentOS ha scritto: But we, the users, trusted you. No we don't anymore. This! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] https://blog.centos.org/2020/12/future-is-centos-stream/
Il 08/12/20 22:12, Nicolas Kovacs ha scritto: Le 08/12/2020 à 21:56, Johnny Hughes a écrit : And, it will likely be sometime mid to late 1st quarter 2021 before CentOS Stream is in its 'Fully Functional' state with community pull requests and the RHEL package maintainer doing all the work in CentOS Stream, etc . CentOS Linux 8 will still be available and updated until the end of December 2021. I've spent the last couple hours reading through various reactions to this sudden paradigm shift, and they're overwhelmingly negative. Even the brazen professionals and the hardcore guru admins who have seen it all add a little "RIP CentOS" to their tweets, blog articles and other publications. Only last month I held my yearly 101 class about Linux and Open Source at our local university here in South France. We were talking about enterprise class Linux - which isn't necessarily commercial Linux - and I remember explaining to my students the choice of CentOS and the benefits of low-risk updates over an extended period of ten years. A colleague of mine - the most proficient admin I personally know - already decided to move to Oracle Linux. And I'm currently considering it as an option. Cheers from the sunny South of France, Niki Hi Niki, I'm migrating away from centos since 8 released. The possibility of centos drop was enabled since IBM acquired RH. Johnny says that this is not an IBM decision, that a RH decision? Then it's worst. My new ship (that was my old ship) will be debian and Ubuntu. Thank you Johnny for the hard work. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] https://blog.centos.org/2020/12/future-is-centos-stream/
Il 08/12/20 17:04, John Thomas ha scritto: I'll probably switch to Debian over the new year. On Tue, Dec 8, 2020 at 8:01 AM Phelps, Matthew wrote: I'm exactly planning this today. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Plasma problem with numeric keypad
Il 08/09/20 10:58, Alessandro Baggi ha scritto: Hi list, I'm running CentOS 8.2 with Plasma from EPEL and I noticed that I have problem using numeric keypad of my keyboard when using plasma application like Konsole, Kcalc, Konqueror and all application of Plasma. Using Firefox, Thunderbird, xterm, Libreoffice all works as expected. So this problem is related to Plasma application. I noticed the same problem on sddm login. I noticed that to make the numeric keypad to work I need to press SHIFT+NUMKEY. I tried to manage Plasma keyboard configuration but nothing worked. I tried my keyboard on other PC and distro but the problem does not occour. I should try this using GNOME or XFCE but being a KDE user I would avoid to install the others. There is a way to solve this problem? Thank you in advance. Alessandro. I found this: https://bugzilla.redhat.com/show_bug.cgi?id=1868371 This is a known bug. I will wait. Thanks to all ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Plasma problem with numeric keypad
Hi list, I'm running CentOS 8.2 with Plasma from EPEL and I noticed that I have problem using numeric keypad of my keyboard when using plasma application like Konsole, Kcalc, Konqueror and all application of Plasma. Using Firefox, Thunderbird, xterm, Libreoffice all works as expected. So this problem is related to Plasma application. I noticed the same problem on sddm login. I noticed that to make the numeric keypad to work I need to press SHIFT+NUMKEY. I tried to manage Plasma keyboard configuration but nothing worked. I tried my keyboard on other PC and distro but the problem does not occour. I should try this using GNOME or XFCE but being a KDE user I would avoid to install the others. There is a way to solve this problem? Thank you in advance. Alessandro. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
Il 09/08/20 10:40, Johnny Hughes ha scritto: On 8/9/20 2:49 AM, Alessandro Baggi wrote: Il 07/08/20 17:39, Leon Fauster via CentOS ha scritto: Am 07.08.20 um 17:17 schrieb Alessandro Baggi: Hi Johnny, what is the current status of the notification tool for security updates on C8? There are possibilities to get soon announces on ML for EL8? Would be great have the tool working. As I understand some kind of mapping must be implemented for indexcode+gitcommitid beetween CentOS and RH ... https://lists.centos.org/pipermail/centos/2020-August/351263.html -- Leon Hi Leon, so we won't have announces soon. Until this happen why not push them on list manually? Push what to the list .. i don't have anything to push? We have this: https://feeds.centos.org/ Hi Johnny, thank you for the resource. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
Il 07/08/20 17:39, Leon Fauster via CentOS ha scritto: Am 07.08.20 um 17:17 schrieb Alessandro Baggi: Hi Johnny, what is the current status of the notification tool for security updates on C8? There are possibilities to get soon announces on ML for EL8? Would be great have the tool working. As I understand some kind of mapping must be implemented for indexcode+gitcommitid beetween CentOS and RH ... https://lists.centos.org/pipermail/centos/2020-August/351263.html -- Leon Hi Leon, so we won't have announces soon. Until this happen why not push them on list manually? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS advisories for 8 release
Il 07/08/20 23:05, Olivier Bonhomme ha scritto: Hello dear CentOS community, I'm writing on this mailing list because I'm discovering CentOS 8 after several years of practice on CentOS 7. One of my main concern about a distribution is Bug Fixes and Security Fixes. For CentOS 7, all fixes where identified on CentOS-Announces lists with CESA, CEBA and CEEA which is a good thing in order to identify how a distribution can be broken, vulnerable. However, I didn't find any announcement for CentOS 8. I tried to investigate about any changes about announcement policies but I didn't find anything reliable. So I'm asking here what is exactly the status about announcements for CentOS 8 ? Is it a thing who totally disappeared replaced by Red Hat advisories or is it something different ? Or maybe it is just not planned yet ? Explanations would be very welcomed. Thanks for your answer Regards, Olivier Bonhomme Hi Olivier, this question got several answers. Since C8 was release updates on announces ML are not available because the tool that provides notification does not work with the new tool that is used to build packages. Actually I use RHEL advisory, but this require a RH account (not subscription). I asked some days ago and I got this answer: Start Quote: As I understand some kind of mapping must be implemented for indexcode+gitcommitid beetween CentOS and RH ... https://lists.centos.org/pipermail/centos/2020-August/351263.html End Quote: So seems that something boils in the pot. We must only wait. My 2 Cents ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
Il 07/08/20 15:46, Stephen John Smoogen ha scritto: On Fri, 7 Aug 2020 at 09:15, Chris Adams wrote: Once upon a time, Alessandro Baggi said: you are right but is not UEFI a standard and it shouldn't work the same on several vendors? I ask this because this patch broken all my uefi workstations. The great thing about standards is there's so many to choose from! Also relevant: https://xkcd.com/927/ UEFI has gone through a number of revisions over the years, and has optional bits like Secure Boot (which itself has gone through revisions). Almost any set of standards has undefined corners where vendors interpret things differently. Vendors also have bugs in weird places sometimes. I go with the lines from Pirates of the Carribean movie.. it is less of a rigid code and more a set of guidelines. Computer programmers are a surly lot, and most take any MUST/SHALL in a standard a personal challenge on how to make it pass a test but do so in an interesting way. +1 Jack :D ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
Il 07/08/20 14:53, Johnny Hughes ha scritto: On 8/7/20 5:30 AM, Phil Perry wrote: On 07/08/2020 10:01, Johnny Hughes wrote: On 8/7/20 3:46 AM, Nicolas Kovacs wrote: Le 07/08/2020 à 09:40, Alessandro Baggi a écrit : Probably many users have not updated their machines between the bug release and the resolution (thanks to your fast apply in the weekend, thank you) and many update their centos machines on a 2 months base (if not worst). I think also that many users of CentOS user base have not proclamed their disappointement/the issue on this list or in other channels. For example I simply updated in the wrong time. I'm using yum-cron to keep all my server updated on a daily basis. And my question "How could this have passed Q & A" was obviously directed at Red Hat... and *not* at Johnny Hughes and the CentOS team who do their best to deliver the best possible downstream system. I raise my morning coffee mug to your health, guys. Cheers, Niki I can assure you .. a BUNCH of testing was done. Because of the scope of this udpate, the CentOS team was looped in during the embargo stage (we normally are not .. Red Hat Engineering got permission to make this happen for this issue). Normally we see things that are open source only .. not embargoed content. Once the embargo gets lifted, the items become open source. Kudos to the RH team for making this happen. The CentOS team worked with the RHEL team on this update for several days (more than a week, for sure, maybe 2 weeks) I gained MUCH respect for all those guys .. especially Peter Jones. He is Mr.Secure Boot. I personally tested both the c8 and c7 solutions on several machines (All i have access to actually, including several personal machines that have secureboot). I saw some of the testing that happened on the RHEL side. It was extensive. I'll just add to Johnny's already comprehensive reply. As a member of the CentOS QA team, I personally tested the update on 3 physical machines and all worked fine. Moreover, the QA team was not able to replicate the issue on a single physical machine available to them - the first indication of a problem came from public reports. We give up a huge amount of our personal time and resources to ensure CentOS (and RHEL) are the very best products they can be. I'm unsure what more could have been done. Thanks Phil, I very much appreciate all you and the rest of the QA team do. I know it is a knee jerk reaction to say .. how did that not get caught. I actually said it MYSELF for this very issue. But looking back, I am not sure how we could have caught it. "Stuff Happens" :) There are just a huge number of possible combinations. Hi Johnny, what is the current status of the notification tool for security updates on C8? There are possibilities to get soon announces on ML for EL8? Would be great have the tool working. Thank you. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
Il 07/08/20 10:47, Johnny Hughes ha scritto: On 8/7/20 2:40 AM, Alessandro Baggi wrote: Il 07/08/20 08:22, Johnny Hughes ha scritto: "How on earth could this have passed Q & A ?" Hi Johnny, Niki's question is spread, legit, in the thoughts in many and many users so don't see this as an attack. Many and many users,though really "if this was tested before release" and I think that many of us are incredulous at what happened on CentOS and in the upstream (specially in the upstream) but as you said CentOS inherits RHEL bugs. I'm reading about many users that lost their trust in RH with the last 2 problem (microcode and shim). This is bad for CentOS. Well, I mean that would be a valid point if it happened for every install. The issue did not happen on every install. There is no way to test every single hardware and firmware combination for every single computer ever built :) It would be great if things like this did not happen, but with the universe of possible combinations, i am surprised it does not happen more often. Probably many users have not updated their machines between the bug release and the resolution (thanks to your fast apply in the weekend, thank you) and many update their centos machines on a 2 months base (if not worst). I think also that many users of CentOS user base have not proclamed their disappointement/the issue on this list or in other channels. For example I simply updated in the wrong time. We do run boot tests of every single kernel for CentOS. The RHEL team runs many more tests for RHEL. But every possible combination from every vendor can't possibly be tested. Right? you are right but is not UEFI a standard and it shouldn't work the same on several vendors? I ask this because this patch broken all my uefi workstations. It would be nice if it did .. however, this worked on many UEFI/Secureboot machines. It did not work on a small subset of machines. While CentOS team could not have so much resources to run this type of tests would be great to know what happened to RHEL QA (being RH giant) for this release and given the partenership between CentOS and RH if you know something more on this. I have not seen the full post event account if what actually happened. I do know that many Red Hatters worked many hours over the last weekend to fix it. I am sure a public post will be made (if not already there) .. if someone knows where it is, post a link. If I don't see it posted soon, I'll look for it and post here. Thank you Johnny. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
Il 07/08/20 10:46, Nicolas Kovacs ha scritto: Le 07/08/2020 à 09:40, Alessandro Baggi a écrit : Probably many users have not updated their machines between the bug release and the resolution (thanks to your fast apply in the weekend, thank you) and many update their centos machines on a 2 months base (if not worst). I think also that many users of CentOS user base have not proclamed their disappointement/the issue on this list or in other channels. For example I simply updated in the wrong time. I'm using yum-cron to keep all my server updated on a daily basis. And my question "How could this have passed Q & A" was obviously directed at Red Hat... and *not* at Johnny Hughes and the CentOS team who do their best to deliver the best possible downstream system. I raise my morning coffee mug to your health, guys. Cheers, Niki Hi Niki, I intended what you mean. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
Il 07/08/20 08:22, Johnny Hughes ha scritto: "How on earth could this have passed Q & A ?" Hi Johnny, Niki's question is spread, legit, in the thoughts in many and many users so don't see this as an attack. Many and many users,though really "if this was tested before release" and I think that many of us are incredulous at what happened on CentOS and in the upstream (specially in the upstream) but as you said CentOS inherits RHEL bugs. I'm reading about many users that lost their trust in RH with the last 2 problem (microcode and shim). This is bad for CentOS. Well, I mean that would be a valid point if it happened for every install. The issue did not happen on every install. There is no way to test every single hardware and firmware combination for every single computer ever built :) It would be great if things like this did not happen, but with the universe of possible combinations, i am surprised it does not happen more often. Probably many users have not updated their machines between the bug release and the resolution (thanks to your fast apply in the weekend, thank you) and many update their centos machines on a 2 months base (if not worst). I think also that many users of CentOS user base have not proclamed their disappointement/the issue on this list or in other channels. For example I simply updated in the wrong time. We do run boot tests of every single kernel for CentOS. The RHEL team runs many more tests for RHEL. But every possible combination from every vendor can't possibly be tested. Right? you are right but is not UEFI a standard and it shouldn't work the same on several vendors? I ask this because this patch broken all my uefi workstations. While CentOS team could not have so much resources to run this type of tests would be great to know what happened to RHEL QA (being RH giant) for this release and given the partenership between CentOS and RH if you know something more on this. Thank you. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Boot failed on latest CentOS 7 update
Il 02/08/20 19:22, Valeri Galtsev ha scritto: On 8/2/20 12:09 PM, Alessandro Baggi wrote: Il 02/08/20 18:54, Stephen John Smoogen ha scritto: On a side note, you keep emphasizing you aren't expecting an SLA.. but all your questions are what someone asks to have in a defined SLA. I have done the same thing in the past when things have gone badly, but couching it in 'I am not asking' just makes the people being asked grumpy. Better to be open and say 'Look I would like to know what my expectations should be for CentOS' and be done with it. Sorry, but you are wrong about this. If I want SLA and QA I will use RHEL. Now permit me to say one thing: the update on my machines, failed in a so bad way that my first thought was "WTF? they tested this fix?" and I'm not the only one that And this complaint has to fall onto RedHat. Slightly underestimating the job CentOS team is doing, one could say: CentOS in just a binary replica of RedHat Enterprise. Hi Valeri, Yes you are right. And again, we use distributions for what benefit they give us, and any trouble we may encounter, we have just ourselves to blame for the choice we had made. And I here am not restricting the choices we could have made to variety of Linux flavors, but include in general anything one could use: a bunch of BSD descendants, MacOS (which server administration wise I excluded from chain BSD --> Darwin --> MacOS 10, or rather ignore that to be a chain), MS Windows (no, I am not asking for shots at me, I for one use FreeBSD for servers, not MS Windows), etc. I use CentOS on workstation (except for my own_ and numbercrunchers. And once again, thanks a lot to the whole CentOS team for the great job, you, guys are doing! Just my abstract view of this. Valeri the previous message was sent incomplete. I appreciate very much the great job done by the CentOS team with so low resource. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Boot failed on latest CentOS 7 update
Il 02/08/20 19:09, Alessandro Baggi ha scritto: Il 02/08/20 18:54, Stephen John Smoogen ha scritto: On a side note, you keep emphasizing you aren't expecting an SLA.. but all your questions are what someone asks to have in a defined SLA. I have done the same thing in the past when things have gone badly, but couching it in 'I am not asking' just makes the people being asked grumpy. Better to be open and say 'Look I would like to know what my expectations should be for CentOS' and be done with it. I press send wrongly. Sorry, but you are wrong about this. If I want SLA and QA I will use RHEL. Now permit me to say one thing: the update on my machines, failed in a so BAD way that my first thought was "WTF? they tested this fix?" and I'm not the only one that who thought about this. I expect that a package is tested to not break a machine/service like for other distro like debian, opensuse, ubuntu and this is DIFFERENT than expect a defined SLA or QA level. How I can expect SLA from CentOS for personal usage and free? But if this happen on CentOS I read "Eh, you want SLA and you should use RHEL", ifthis happen on Ubuntu "Ah, don't use Ubuntu, I abondoned it for this type of problems"... I need only that the update does not destroy the entire installation. Now, if expect that a distro, with a strong reputation like centos, make test on a package that could break the boot process of a system, for a good number of usage case is not requiring SLA or QA, is only expect a good practice like I would expect for other distro. When I release a patch/fix to a script or an RPM package or php page or python script, before I apply the change I ensure that this change does not break anything. I'm not sure about this? Good I'll wait to push it and test it again ( this not imply that bugs are not present) but this is not a SLA request man because I know that centos can't offer it. Probably this is a my misconception, but hey I'm really and very surprised that this happend in a bad way (specially on the upstream). As I said, I will use again centos and won't expect any type of SLA, QA, fast release in a different way like for the previous version, I can only send a thank you to the CentOS team. As Johnny explained this happened and will happen in the future, this problem is not related to CentOS directly and the great job that Johnny done today is amazing. My 2 cent. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Boot failed on latest CentOS 7 update
Il 02/08/20 18:54, Stephen John Smoogen ha scritto: On a side note, you keep emphasizing you aren't expecting an SLA.. but all your questions are what someone asks to have in a defined SLA. I have done the same thing in the past when things have gone badly, but couching it in 'I am not asking' just makes the people being asked grumpy. Better to be open and say 'Look I would like to know what my expectations should be for CentOS' and be done with it. Sorry, but you are wrong about this. If I want SLA and QA I will use RHEL. Now permit me to say one thing: the update on my machines, failed in a so bad way that my first thought was "WTF? they tested this fix?" and I'm not the only one that ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
Il 02/08/20 15:10, Marc Balmer via CentOS ha scritto: Thanks for acting quickly, especially on a weekend. This. +1 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Boot failed on latest CentOS 7 update
Hi Johnny, thank you for your answer. I always accepted release cycle of CentOS without any problem (maybe with EL8 but it is ok). I don't need SLA and I don't blame anyone for this, errors can occour. For example in this story, I applied blindly updates without check what and how so really I ran the command that brake my installation...and as I said no problem for this. You said:" We TRY to validate all fixes, but if something is broken in the source code, it will likely be borken in CentOS Linux as well". This means that if a rhel package break something, the centos team releases it with the bug anyway also if the bug is already known? The update cannot be delayed until the correct version is released if the package bug is already known? Is it not possible by policy or other? Validate is equal to "test if nothing get breakage"? I repeat, I don't need SLA or QA or faster update/release. What sound strange to me is that the testing procedure for a released update to see if all works has failed and has not revealed the problem when the bug showed up right away to me on a workstation and on a fresh install with minimal and on a personal "server" with mdadm raid devices? In all my cases, when updating shim I got several and clear messages of failed update without the need to perform a reboot and see that grub was broken. I have another question. I know that the gear that provides notification for el8 updates does not work due to koji. How is the current status for notification of updates for centos 8? We can see update notifications soon re-enabled? Thank you for your time. I appreciate your work. Il Dom 2 Ago 2020, 14:42 Johnny Hughes ha scritto: > On 8/2/20 2:47 AM, Alessandro Baggi wrote: > > > > Il 02/08/20 00:42, Mike McCarthy, W1NR ha scritto: > >> It appears that it is affecting multiple distributions including Debian > >> and Ubuntu so it looks like the grub2 team messed up. See > >> > >> > https://www.zdnet.com/article/boothole-fixes-causing-boot-problems-across-multiple-linux-distros/ > >> > >> > >> Mike > >> > >> On 8/1/2020 6:11 PM, Marc Balmer via CentOS wrote: > >>> > >>>> Am 01.08.2020 um 23:52 schrieb Leon Fauster via CentOS > >>>> : > >>>> > >>>> Am 01.08.20 um 23:41 schrieb Kay Schenk: > >>>>> Well misery loves company but still...just truly unfathomable! > >>>>> Time for a change. > >>>> > >>>> I can only express my incomprehension for such statements! > >>>> > >>>> Stay and help. Instead running away or should I say out of the > >>>> frying pan and into the fire? :-) > >>> The thing, RHEL and CentOS not properly testing updates, cost me at > >>> minimum 3-4 full working days, plus losses at customer sites. > >>> > >>> This is really a huge failure of RHEL and CentOS. > >>> > >>> A lot of trust has been destroyed. > > > > Hi Mike, > > > > I'm not interested that the issue is present on Debian, Ubuntu and the > > others. Currently I'm using CentOS, I'm a CentOS user and currently I'm > > interested what is happening on CentOS because I have machines that runs > > CentOS. If the "wrong" patch was not pushed as update so fast (maybe > > waiting more time before release with more testing to get all cases [yes > > because when you update grub and depending on the fix you can break a > > system easily]) there would have been no problem, by the way I prefer > > wait some days (consider that I can accept the release delay of > > minor/major release) then break my systems...and without messages on ML > > announces about this type of problem does not help. Sorry I can't know > > what and when a packages is updated, why it is updated, what type of > > problem (CVE) it suffers and do my reasoning for an update process. This > > is a missing for me but I still use centos and I should not need a RHEL > > account to access to get advisories and see what applies on CentOS > > (6,7,8 and Stream). > > > > Many of us, choose CentOS due to its stability and enteprise-ready > > feature (and because is partially/enterely backed by RH). Due to actual > > problem, many server and workstation died and it's normal that some user > > said "A lot of trust has been destroyed." because they placed a lot of > > trust on the pro-redhat support. On the other side, all of us can fall > > in error and this is the case (like me that I updated blindy, so its > > also my fault not only the broken update). > > > > Only one error in many years could not
Re: [CentOS] Boot failed on latest CentOS 7 update
Hi Paride, I also have a debian 10 on a workstation and some VMs for test purpose. Probably you updated after the grub-regression update but I noticed several stories about debian breakage. Il 02/08/20 01:13, paride desimone ha scritto: I use debian buster on my old notebook, an asus f3ja and I have not grub throuble. I try a virtual mschine with testing and unstable, and both boot regularly Il dom 2 ago 2020, 00:42 Mike McCarthy, W1NR ha scritto: It appears that it is affecting multiple distributions including Debian and Ubuntu so it looks like the grub2 team messed up. See https://www.zdnet.com/article/boothole-fixes-causing-boot-problems-across-multiple-linux-distros/ Mike On 8/1/2020 6:11 PM, Marc Balmer via CentOS wrote: Am 01.08.2020 um 23:52 schrieb Leon Fauster via CentOS < centos@centos.org>: Am 01.08.20 um 23:41 schrieb Kay Schenk: Well misery loves company but still...just truly unfathomable! Time for a change. I can only express my incomprehension for such statements! Stay and help. Instead running away or should I say out of the frying pan and into the fire? :-) The thing, RHEL and CentOS not properly testing updates, cost me at minimum 3-4 full working days, plus losses at customer sites. This is really a huge failure of RHEL and CentOS. A lot of trust has been destroyed. -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Boot failed on latest CentOS 7 update
Il 02/08/20 00:42, Mike McCarthy, W1NR ha scritto: It appears that it is affecting multiple distributions including Debian and Ubuntu so it looks like the grub2 team messed up. See https://www.zdnet.com/article/boothole-fixes-causing-boot-problems-across-multiple-linux-distros/ Mike On 8/1/2020 6:11 PM, Marc Balmer via CentOS wrote: Am 01.08.2020 um 23:52 schrieb Leon Fauster via CentOS : Am 01.08.20 um 23:41 schrieb Kay Schenk: Well misery loves company but still...just truly unfathomable! Time for a change. I can only express my incomprehension for such statements! Stay and help. Instead running away or should I say out of the frying pan and into the fire? :-) The thing, RHEL and CentOS not properly testing updates, cost me at minimum 3-4 full working days, plus losses at customer sites. This is really a huge failure of RHEL and CentOS. A lot of trust has been destroyed. Hi Mike, I'm not interested that the issue is present on Debian, Ubuntu and the others. Currently I'm using CentOS, I'm a CentOS user and currently I'm interested what is happening on CentOS because I have machines that runs CentOS. If the "wrong" patch was not pushed as update so fast (maybe waiting more time before release with more testing to get all cases [yes because when you update grub and depending on the fix you can break a system easily]) there would have been no problem, by the way I prefer wait some days (consider that I can accept the release delay of minor/major release) then break my systems...and without messages on ML announces about this type of problem does not help. Sorry I can't know what and when a packages is updated, why it is updated, what type of problem (CVE) it suffers and do my reasoning for an update process. This is a missing for me but I still use centos and I should not need a RHEL account to access to get advisories and see what applies on CentOS (6,7,8 and Stream). Many of us, choose CentOS due to its stability and enteprise-ready feature (and because is partially/enterely backed by RH). Due to actual problem, many server and workstation died and it's normal that some user said "A lot of trust has been destroyed." because they placed a lot of trust on the pro-redhat support. On the other side, all of us can fall in error and this is the case (like me that I updated blindy, so its also my fault not only the broken update). Only one error in many years could not destroy a distro and its stability reputation (I think and correct me if I'm wrong) and I hope it won't happen again. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
Il 01/08/20 22:03, Greg Bailey ha scritto: On 8/1/20 6:56 AM, david wrote: At 02:54 AM 8/1/2020, Alessandro Baggi wrote: Hi Johnny, thank you very much for clarification. You said that in the centos infrastructure only one server got the problem. What are the conditions that permit the breakage? There is a particular configuration (hw/sw) case that match always the problem or it is random? Thank you I have two servers running Centos 7 on apple hardware (one mac-mini and one mac server). They both failed to reboot a few days ago. So perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7. I can't tell what version got updated since the system simply fails to boot. I don't even get a grub screen. I'll have to rebuild the systems from scratch. You should be able to boot off of installation media into rescue mode, and downgrade the grub2* and/or shim* RPMs. -Greg I did the downgrade on a fresh install of c8.2 but yum said that all selected packages (grub2,shim...) are already to the lowest version and the downgrade is not possibile, ending with "nothing to do". ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
Hi Johnny, thank you very much for clarification. You said that in the centos infrastructure only one server got the problem. What are the conditions that permit the breakage? There is a particular configuration (hw/sw) case that match always the problem or it is random? Thank you Il Sab 1 Ago 2020, 05:20 Johnny Hughes ha scritto: > On 7/31/20 11:24 AM, Alessandro Baggi wrote: > > > > Il 31/07/20 13:08, ja ha scritto: > >> On Fri, 2020-07-31 at 22:35 +1200, Alan McRae via CentOS wrote: > >>> I am running an Intel x64 machine using UEFI to boot an SSD. > >>> > >>> Installing the latest yum update which includes grub2 and kernel > >>> 4.18.0-193.14.2.el8_2.x86_64 renders the machine unbootable, blank > >>> screen where grub should be, no error messages, just hangs. > >>> > >>> After some hours I managed to modify another bootable partition > >>> (containing older software) and boot it from there. > >>> > >>> After that, I found out it is a known problem. > >>> > >>> The main point of this message is to make people aware of the problem > >>> and suggest admins don't run 'yum update' until they understand the > >>> problem and have a fix at hand. > >>> > >>> See 'UEFI boot blank screen post update' for a solution and directions > >>> to the redhat article. > >>> > >>> Regards > >>> > >>> Alan > >>> > >> I have been punished by this bug - it is/was very nasty. > >> > > Me too. Luckily it happened on a test machine. > > > > Sorry but seems that those packages were not tested before pushing them > > in the update repo. Would be great to know what happened to the > > mainstream chains and how a package like grub reached the update repo > > when it has serious problem (genuine curiosity but not to blame them). > > Of course it was tested before it was pushed. Obviously this is not a > problem with every install. Surely you don't think we push items > without doing any testing. Certainly not items as important as this > update. > > The CentOS infrastructure has hundreds of servers, most of them were > not impacted (as an example). In fact, we seem to have had this happen > on only one machine in those hundreds so far. It is a problem, obviously. > > The issue seems to be with the shim package (not the grub or kernel > packages) and we are currently working with Red Hat on a fix. This > issue happened in many Linux OSes and even Windows, not just RHEL and > CentOS. > > We will push a fix as soon as one is available. > > I would hold off on installing this until we release the new fixes. > > > > > In my case, the restore procedure reported by RH in case of reboot does > > not work and reports that the packages are already at the lowest version > > and that the downgrade is not possibile. I don't know why. > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
I would add,
RedHat is recomending also to blacklist grub, shim and mokutil in
yum.conf until the problem is resolved.
Il 31/07/20 18:26, Laack, Andrea P ha scritto:
RedHat is recommending not to patch.
https://access.redhat.com/solutions/5272311
Andrea
-Original Message-
From: CentOS On Behalf Of Alessandro Baggi
Sent: Friday, July 31, 2020 11:25 AM
To: centos@centos.org
Subject: {EXTERNAL} Re: [CentOS] 8.2.2004 Latest yum update renders machine
unbootable
CAUTION: This email originated outside of BSWH; avoid action unless you know
the content is safe. Send suspicious emails as attachments to
badem...@bswhealth.org.
Il 31/07/20 13:08, ja ha scritto:
On Fri, 2020-07-31 at 22:35 +1200, Alan McRae via CentOS wrote:
I am running an Intel x64 machine using UEFI to boot an SSD.
Installing the latest yum update which includes grub2 and kernel
4.18.0-193.14.2.el8_2.x86_64 renders the machine unbootable, blank
screen where grub should be, no error messages, just hangs.
After some hours I managed to modify another bootable partition
(containing older software) and boot it from there.
After that, I found out it is a known problem.
The main point of this message is to make people aware of the problem
and suggest admins don't run 'yum update' until they understand the
problem and have a fix at hand.
See 'UEFI boot blank screen post update' for a solution and
directions to the redhat article.
Regards
Alan
I have been punished by this bug - it is/was very nasty.
Me too. Luckily it happened on a test machine.
Sorry but seems that those packages were not tested before pushing them in the
update repo. Would be great to know what happened to the mainstream chains and
how a package like grub reached the update repo when it has serious problem
(genuine curiosity but not to blame them).
In my case, the restore procedure reported by RH in case of reboot does not
work and reports that the packages are already at the lowest version and that
the downgrade is not possibile. I don't know why.
___
CentOS mailing list
CentOS@centos.org
https://urldefense.com/v3/__https://lists.centos.org/mailman/listinfo/centos__;!!JA_k2roV-A!TZ0vdQBvu-4qe6spakWlZ8WocsAa0gEznp4zChtxB-6LsI9T5wEvaXV3KZzeSmSp4Q$
**
The information contained in this e-mail may be privileged and/or confidential, and
protected from disclosure, and no waiver of any attorney-client, work product, or other
privilege is intended. If you are the intended recipient, further disclosures are
prohibited without proper authorization. If you are not the intended recipient (or have
received this e-mail in error) please notify the sender immediately and destroy this
e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail
is strictly forbidden and possibly a violation of federal or state law and regulations. The
sender and Baylor Scott & White Health, and its affiliated entities, hereby expressly
reserve all privileges and confidentiality that might otherwise be waived as a result of an
erroneous or misdirected e-mail transmission. No employee or agent is authorized to
conclude any binding agreement on behalf of Baylor Scott & White Health, or any
affiliated entity, by e-mail without express written confirmation by the CEO, the Senior
Vice President of Supply Chain Services or other duly authorized representative of Baylor
Scott & White Health.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
Il 31/07/20 13:08, ja ha scritto: On Fri, 2020-07-31 at 22:35 +1200, Alan McRae via CentOS wrote: I am running an Intel x64 machine using UEFI to boot an SSD. Installing the latest yum update which includes grub2 and kernel 4.18.0-193.14.2.el8_2.x86_64 renders the machine unbootable, blank screen where grub should be, no error messages, just hangs. After some hours I managed to modify another bootable partition (containing older software) and boot it from there. After that, I found out it is a known problem. The main point of this message is to make people aware of the problem and suggest admins don't run 'yum update' until they understand the problem and have a fix at hand. See 'UEFI boot blank screen post update' for a solution and directions to the redhat article. Regards Alan I have been punished by this bug - it is/was very nasty. Me too. Luckily it happened on a test machine. Sorry but seems that those packages were not tested before pushing them in the update repo. Would be great to know what happened to the mainstream chains and how a package like grub reached the update repo when it has serious problem (genuine curiosity but not to blame them). In my case, the restore procedure reported by RH in case of reboot does not work and reports that the packages are already at the lowest version and that the downgrade is not possibile. I don't know why. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] hardlinks
Hi Martin, thank you very much for your explanation. +1 Il Ven 17 Lug 2020, 12:14 J Martin Rushton via CentOS ha scritto: > On 17/07/2020 10:30, Alessandro Baggi wrote: > > > > Il 17/07/20 10:54, Karl Vogel ha scritto: > >> It depends on the size of the variables in the structure used by the > >> stat() call. In ext4, the "links" variable is an unsigned 16-bit > >> integer, > >> so you have your limit of 64k or so. I've worked with systems where > >> the limit was a signed 16-bit integer, so it maxed out at 32k. > >> > >> XFS may be a full 32-bit integer, so your test script could be running > >> for quite some time. Or it may just allocate space as it needs. It > >> sounds > >> like you have plenty of room for links, so I wouldn't worry. > >> > >> -- > >> Karl Vogel / voge...@pobox.com / I don't speak for the USAF or my > company > >> > >> Don't accept your dog's admiration as > >> conclusive evidence that you are wonderful. --Ann Landers > > > > Hi Karl, > > > > thank you for your clarification. I will try to rearch this limit (by > > curiosity) > > > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos > > Have a look at > > https://mirrors.edge.kernel.org/pub/linux/utils/fs/xfs/docs/xfs_filesystem_structure.pdf > > On page 105 the inode structure is given: > > __uint16_t di_onlink; > ... > __uint32_t di_nlink > > Page 107 gives more detail: > > di_onlink: > In v1 inodes, this specifies the number of links to the inode from > directories. When the number exceeds 65535,the inode is converted to v2 > and the link count is stored in di_nlink. > > di_nlink: > Specifies the number of links to the inode from directories. This is > maintained for both inode versions for current versions of XFS. Prior to > v2 inodes, this field was part of di_pad. > > So, the effect is that whatever version you start with, adding more than > 65535 links will force it to version 2 and give you up to 4,294,967,295 > links! > > -- > J Martin Rushton MBCS > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] hardlinks
Il 17/07/20 10:54, Karl Vogel ha scritto: It depends on the size of the variables in the structure used by the stat() call. In ext4, the "links" variable is an unsigned 16-bit integer, so you have your limit of 64k or so. I've worked with systems where the limit was a signed 16-bit integer, so it maxed out at 32k. XFS may be a full 32-bit integer, so your test script could be running for quite some time. Or it may just allocate space as it needs. It sounds like you have plenty of room for links, so I wouldn't worry. -- Karl Vogel / voge...@pobox.com / I don't speak for the USAF or my company Don't accept your dog's admiration as conclusive evidence that you are wonderful. --Ann Landers Hi Karl, thank you for your clarification. I will try to rearch this limit (by curiosity) ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] [OT] What is the max hardlink number for a single file on XFS
Hi list, I have a little script that uses rysnc and hardlink to perform backups. Some days ago a friend told me that rsync could crash if the hardlink limit is reached. I know (and tested) that for ext4 the max number of hardlink for a single file is 65000 but I can't get a limit on XFS. Due to the fact that I can't get good resources from google search, I tried to reach its limit with a script creating a regular file and create in another dir many hardlinks. Currently I have: -rw-r--r-- 8730476 root root 12 16 lug 12.13 hlink/1 My scripts is trying to reach 20 mln of hardlink so need time to finish but 8730476 of hardlinks is an huge number. Someone know this limit? Thank you in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [OT] Bacula offsite replication
Il 02/07/20 16:39, Valeri Galtsev ha scritto: On 2020-07-02 08:28, Alessandro Baggi wrote: Il 02/07/20 15:02, Valeri Galtsev ha scritto: On 7/2/20 3:22 AM, Alessandro Baggi wrote: Il 01/07/20 17:13, Leroy Tennison ha scritto: I realize this shouldn't happen, the file is a tgz and isn't being modified while being transmitted. This has happened maybe three times this year and unfortunately I've just had to deal with it rather than invest the time to do the research. Harriscomputer Leroy Tennison Network Information/Cyber Security Sp Hi Leroy, I think that in my case I could not use a tgz archive. I'm speaking about full backups that reach 600/700GiB, compressing them and then rsync them could take so much time that it will be useless. unless you use tape (of that high capacity), it is advantageous to restrict volume size to, say, 50GB. Then when you restore, search for specific files will be faster. And it will help your backup volumes transfers as well. Valeri Hi Valeri, thank you for your suggestion. Is bacula the right backup system when I need to replicate data offsite? There are other backup solution that simplify this process? Bacula is great enterprise level open source backup system. I switched to its fork bareos at some point; I use bacula/bareos for at least a decade. And with this your extra requirement I still would stay with bareos (or bacula). If I were to have two sets of backup: on site and off site, I would just set up separate bacula/bareos director and storage daemon(s) off site. Add to FDs (file daemons) extra instances of director - offsite one with different passwords for the sake of security. Then there will be a set of everything off site, not only a set of volumes. Of course, if you only have a set of volumes, but everything else has evaporated, you still will be able to restore everything, including database records by scanning set of volumes. Which will take forever. I would alternate dates of backups in offsite/onsite schedules, or define times of backups so that they do not overlap. Another good news of this vs just rsyncing volumes is: bacula/bareos verifies checksum of every backed up file after receiving it. This will ensure consistency of files in remote volumes, for rsync you will have to at least verify checksum of each volume transferred to destination (unless I miss my wits and rsync does verify checksums of files transferred, I just re-read rsync man and don't see verification - hopefully rsync expert will chime in and correct me if I'm wrong about rsync). Anyway, that is what I would do. Valeri Hi Valeri, I'm in late but thank you for your suggestion. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [OT] Bacula offsite replication
Il 02/07/20 15:02, Valeri Galtsev ha scritto: On 7/2/20 3:22 AM, Alessandro Baggi wrote: Il 01/07/20 17:13, Leroy Tennison ha scritto: I realize this shouldn't happen, the file is a tgz and isn't being modified while being transmitted. This has happened maybe three times this year and unfortunately I've just had to deal with it rather than invest the time to do the research. Harriscomputer Leroy Tennison Network Information/Cyber Security Sp Hi Leroy, I think that in my case I could not use a tgz archive. I'm speaking about full backups that reach 600/700GiB, compressing them and then rsync them could take so much time that it will be useless. unless you use tape (of that high capacity), it is advantageous to restrict volume size to, say, 50GB. Then when you restore, search for specific files will be faster. And it will help your backup volumes transfers as well. Valeri Hi Valeri, thank you for your suggestion. Is bacula the right backup system when I need to replicate data offsite? There are other backup solution that simplify this process? Thank you in advance ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [OT] Bacula offsite replication
Hi John, thank you for your answer, I already take in consideration DRBD but I need some test before start. Reading you seems that this solution is not anymore available. What do you use for this? Thank you in advance. Il 02/07/20 10:43, John Pierce ha scritto: I setup drbd to replicate a ~50TB backuppc hive to the DR copy, an identical box in a different DC on the same campus, with approximately gigE speeds, and ran this for a year or two. It worked well enough but required babysitting from time to time. Both nodes were mdraid lvm logical volumes formatted as a single huge xfs on centos. I never automated the failover as it never failed, and as a dev/test backup, 8 hour response seemed adequate On Thu, Jul 2, 2020, 1:22 AM Alessandro Baggi wrote: Il 01/07/20 17:13, Leroy Tennison ha scritto: I realize this shouldn't happen, the file is a tgz and isn't being modified while being transmitted. This has happened maybe three times this year and unfortunately I've just had to deal with it rather than invest the time to do the research. Harriscomputer Leroy Tennison Network Information/Cyber Security Sp Hi Leroy, I think that in my case I could not use a tgz archive. I'm speaking about full backups that reach 600/700GiB, compressing them and then rsync them could take so much time that it will be useless. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [OT] Bacula offsite replication
Il 01/07/20 17:13, Leroy Tennison ha scritto: I realize this shouldn't happen, the file is a tgz and isn't being modified while being transmitted. This has happened maybe three times this year and unfortunately I've just had to deal with it rather than invest the time to do the research. Harriscomputer Leroy Tennison Network Information/Cyber Security Sp Hi Leroy, I think that in my case I could not use a tgz archive. I'm speaking about full backups that reach 600/700GiB, compressing them and then rsync them could take so much time that it will be useless. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [OT] Bacula offsite replication
Hi Leroy, How I can confirm that during rsync transfer corruption are not encountered? Thank you in advance. Il 01/07/20 16:04, Leroy Tennison ha scritto: I've used rsync (but probably not for the size you're referring to), it works and has enough features to meet most needs. I have had a single situation where corruption occurred during transfer (a few times, have no idea why), might want to independently confirm the integrity of the transfer. From: CentOS on behalf of Alessandro Baggi Sent: Wednesday, July 1, 2020 5:26 AM To: centos@centos.org Subject: [EXTERNAL] [CentOS] [OT] Bacula offsite replication CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi everyone, I have updated my backup server to CentOS 8.2. It runs bacula performing backup on disks. I would like to replicate backups on another offsite machine. I read about the ability to configure a new storage daemon in the offsite location and create a Migration/Copy Jobs. If I'm not wrong, it replicates only volumes but not replicate the catalog. I will try this. Another way to replicate the volumes on another server is using rsync. What is your suggestion about this topic? Thank you in advance. Alessandro. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Harriscomputer Leroy Tennison Network Information/Cyber Security Specialist E: le...@datavoiceint.com [cid:Data-Voice-International-LOGO_aa3d1c6e-5cfb-451f-ba2c-af8059e69609.PNG] 2220 Bush Dr McKinney, Texas 75070 www.datavoiceint.com<http://www..com> This message has been sent on behalf of a company that is part of the Harris Operating Group of Constellation Software Inc. If you prefer not to be contacted by Harris Operating Group please notify us<http://subscribe.harriscomputer.com/>. This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] [OT] Bacula offsite replication
Hi everyone, I have updated my backup server to CentOS 8.2. It runs bacula performing backup on disks. I would like to replicate backups on another offsite machine. I read about the ability to configure a new storage daemon in the offsite location and create a Migration/Copy Jobs. If I'm not wrong, it replicates only volumes but not replicate the catalog. I will try this. Another way to replicate the volumes on another server is using rsync. What is your suggestion about this topic? Thank you in advance. Alessandro. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RPMFusion and NVIDIA driver problem
Il 30/06/20 17:41, Phil Perry ha scritto: On 30/06/2020 08:33, Alessandro Baggi wrote: Il 29/06/20 16:02, Phil Perry ha scritto: On 29/06/2020 07:36, Alessandro Baggi wrote: Hi list, I'm on C8.1 and I'm trying to install NVIDIA driver from rpmfusion-nonfree repository but it returns: package kmod-nvidia-3:440.82-2.el8.x86_64 requires kmod-nvidia-4.18.0-147.el8.x86_64 >= 3:440.82-2.el8, but none of the providers can be installed - conflicting requests - nothing provides kernel < 4.18.0-148.el8 needed by The package is looking for an el8.1 kernel to meet it's dependencies and can not find one. C8.2 has now been released, and as a result all 8.1 packages got moved to vault. If you enable the vault repo, yum will be able to find the kernel package it is looking for to meet the dependencies. However, if you do that you will have to boot to an old C8.1 series kernel for your nvidia drivers to work. kmod-nvidia-4.18.0-147.el8.x86_64-3:440.82-2.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) and uname -r returns: 4.18.0-193.6.3.el8_2.x86_64 Yes, you are running the latest 8.2 series kernel. Seems that RPMFusion needs an update. Waiting for this there is a way to install this package without fall in problems? Thank you in advance. Yes, seems that repo is stale. They need to release packages built against el8.2, which at least for RHEL have been out for 2 months now. A newer stable nvidia driver (440.100) was also released recently. The (not ideal) workaround is as stated above - enable CentOS vault repo and boot into an older el8.1 series kernel for now until they update packages. I would normally recommend you try the nvidia drivers from elrepo, but I have a vested interest as I maintain them Phil Hi Phil, thank you for your answer. I tried with this after installing ELrepo repository: yum --enablerepo=elrepo install kmod-nvidia but I get the same result for different version. Hi Alessandro, You will need to provide more information for me to be able to help, like the errors you received. As a general rule, try not to mix elrepo and rpmfusion repos, or if you have to, do so carefully and manage any conflicts manually. You can usually tell which point release kernel series a kmod is built for by the tag in their release (e.g, el8.2 packages will have the elrepo.el8_2 release tag), so you can ensure you are installing / updating the correct package for your system. Regards, Phil ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi Phil, thank you for your answer. Currently I need RPMFusion for some packages so I cannot remove it. About my previous error about the command with --enablerepo=elrepo it gives me errors because it tries to install again rpmfusion packages so adding --disablerepo=rpmfusion-nonfree-updated will permit to install the driver but currently I remain with nouveau to avoid conflicts between elrepo and RPMFusion. Thank you for your help. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RPMFusion and NVIDIA driver problem
Il 29/06/20 16:02, Phil Perry ha scritto: On 29/06/2020 07:36, Alessandro Baggi wrote: Hi list, I'm on C8.1 and I'm trying to install NVIDIA driver from rpmfusion-nonfree repository but it returns: package kmod-nvidia-3:440.82-2.el8.x86_64 requires kmod-nvidia-4.18.0-147.el8.x86_64 >= 3:440.82-2.el8, but none of the providers can be installed - conflicting requests - nothing provides kernel < 4.18.0-148.el8 needed by The package is looking for an el8.1 kernel to meet it's dependencies and can not find one. C8.2 has now been released, and as a result all 8.1 packages got moved to vault. If you enable the vault repo, yum will be able to find the kernel package it is looking for to meet the dependencies. However, if you do that you will have to boot to an old C8.1 series kernel for your nvidia drivers to work. kmod-nvidia-4.18.0-147.el8.x86_64-3:440.82-2.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) and uname -r returns: 4.18.0-193.6.3.el8_2.x86_64 Yes, you are running the latest 8.2 series kernel. Seems that RPMFusion needs an update. Waiting for this there is a way to install this package without fall in problems? Thank you in advance. Yes, seems that repo is stale. They need to release packages built against el8.2, which at least for RHEL have been out for 2 months now. A newer stable nvidia driver (440.100) was also released recently. The (not ideal) workaround is as stated above - enable CentOS vault repo and boot into an older el8.1 series kernel for now until they update packages. I would normally recommend you try the nvidia drivers from elrepo, but I have a vested interest as I maintain them Phil Hi Phil, thank you for your answer. I tried with this after installing ELrepo repository: yum --enablerepo=elrepo install kmod-nvidia but I get the same result for different version. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] RPMFusion and NVIDIA driver problem
Hi list, I'm on C8.1 and I'm trying to install NVIDIA driver from rpmfusion-nonfree repository but it returns: package kmod-nvidia-3:440.82-2.el8.x86_64 requires kmod-nvidia-4.18.0-147.el8.x86_64 >= 3:440.82-2.el8, but none of the providers can be installed - conflicting requests - nothing provides kernel < 4.18.0-148.el8 needed by kmod-nvidia-4.18.0-147.el8.x86_64-3:440.82-2.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) and uname -r returns: 4.18.0-193.6.3.el8_2.x86_64 Seems that RPMFusion needs an update. Waiting for this there is a way to install this package without fall in problems? Thank you in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Blog article about the state of CentOS
Il 21/06/20 03:28, Peter ha scritto: On 21/06/20 1:23 pm, John Pierce wrote: but the build process should be the same, no? I can't believe RH would use a completely different build process for the release than for the beta/development stuff. The packages still have to be built as a whole, they need to go through QA testing, isos need to be built and tested. The only thing that I can think of that Stream benefits this process is to help Red Hat find the odd bug here and there before their final release (after which CentOS still has to do everything listed above). Peter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos I have a question. Why CentOS Stream is needed and what problem it solves? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Blog article about the state of CentOS
Il 19/06/20 17:15, Johnny Hughes ha scritto: On 6/17/20 12:11 PM, Alessandro Baggi wrote: Hi Johnny, thank you for your and all centos team works. Many of us know how much work is needed for building new releases and maintaining C6 and C7, plus CentOS Stream and modules (Appstream). This is a huge work for a small team. Again thank you. For me OL is not an alternative. As reported in my previous message I'm not worried about how much time is required to build the new (major/minor) release, it will be ready when it will be. My major concern is about the "security update blackout" that take long as the build process. I would ask to you: 1. Why all security fix are stopped when a new release building process is started? There is a way or possibility to run the two process in parallel? So .. when a point release happens .. say 7.8 to 7.9 (just an example .. could be 6.10 to 6.11 or 8.1 to 8.2, etc) Those packages are built against EACH other, one at a time. Once we build the new gcc, new kernel, and new glibc (if they are reqruies) .. then all the OTHER updated packages are built against those new libraries.. they therefore need those NEW shared libraries to run. So the new files have to be released as a set, not individually. 2. When a build process is started and a security fix released there is a way for your team to "suspend" the building process, release security updates (for 6/7.x or 8.1) and resume the builing process? I think that many users (included me) will have less disappointment having security updates instead of receiving a "signal lost" when building process takes its way. It makes no difference if the update is a bugfix update or a security update. If 500 packages get released at the same time, they have to be built in a specific order in order to match how they were built in RHEL. We have to build them, one at a time, then individually test them to make sure they LINK against the proper new libraries and not older libraries. Also any UPDATES released to the new version , after RHEL does the point release (so updates FOR 7.9 after the 7.9 release) need to wait until the 7.9 release is done and tested to be built .. as they were built against RHEL 7.9 and not RHEL 7.8 So, you can't just build items out of order at point release time. We have to build the 500 packages , in a specific order. We then have to test the packages, and usually rebuild several of them again for bad links, etc. This is the process that takes time .. testing and getting the proper links to the proper shared libraries. If we quickly release bad files .. then we have to rebuild them and re-release them with different versions that RHEL has (because they have to replace our previuosly BAD release). That is not good for anyone. Hopefully this answers your question. Hi Johnny, thank you for your answer. This is more clear to me now. Alessandro. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Blog article about the state of CentOS
Hi Johnny,
thank you for your and all centos team works.
Many of us know how much work is needed for building new releases and
maintaining C6 and C7, plus CentOS Stream and modules (Appstream). This is
a huge work for a small team. Again thank you.
For me OL is not an alternative.
As reported in my previous message I'm not worried about how much time is
required to build the new (major/minor) release, it will be ready when it
will be. My major concern is about the "security update blackout" that take
long as the build process.
I would ask to you:
1. Why all security fix are stopped when a new release building process is
started? There is a way or possibility to run the two process in parallel?
2. When a build process is started and a security fix released there is a
way for your team to "suspend" the building process, release security
updates (for 6/7.x or 8.1) and resume the builing process? I think that
many users (included me) will have less disappointment having security
updates instead of receiving a "signal lost" when building process takes
its way.
Thank you for your time.
Alessandro.
Il Mer 17 Giu 2020, 16:15 Johnny Hughes ha scritto:
> On 6/17/20 8:06 AM, Simon Matter via CentOS wrote:
> >> Hi,
> >>
> >> I just read this blog article from austrian Linux expert Michael Kofler.
> >> For
> >> those among you who don't know the guy, he's my home country's number
> one
> >> Linux
> >> expert (known as "der Kofler") and most notably the author of a series
> of
> >> excellent books about Linux over the last 25 years.
> >>
> >> https://kofler.info/centos-8-wertlose-langzeitunterstuetzung/
> >>
> >> Disclaimer : I've been a CentOS user (and fan) since 4.x, I'm using it
> on
> >> all
> >> my servers, and yes, I know the difference between upstream RHEL and
> >> CentOS.
> >>
> >> The article is in german, but the statistics graph is eloquent enough
> for
> >> the
> >> non-german-speaking users. It focuses on updates for CentOS 8, and more
> >> exactly
> >> the extended periods of time where there have been no updates available.
> >>
> >> The author's theory ("unspoken truth"): while it's a positive thing that
> >> Red
> >> Hat is sponsoring CentOS, the amount of sponsoring is just insufficient
> >> enough
> >> so that the product is "starved to death" by Red Hat (e. g. IBM) to
> >> encourage
> >> users to move to RHEL.
> >
> > I think if Red Hat really wanted to improve the situation, they could
> > integrate the building of CentOS into the EL build system to produce both
> > versions, RHEL and CentOS, at the same time. In the end 99% of the bits
> > are the same anyway. If the delay of CentOS builds is really wanted by
> Red
> > Hat, it would be nice of them to speak it out - and change the name to
> > COS, because the ent is not true anymore :-)
> >
> > Up to now I thought the big delay with 8 is more an accident than wanted.
> > Would be nice to hear what Red Hat says about it. Maybe the problem is
> not
> > known well enough in the Red Hat universe.
> >
>
>
> No one is trynig to make anything slower.
>
> And CentOS Stream 'is' going to be how RHEL is developed in the future.
> So, all this is happening.
>
> But modules introduced in RHEL 8 requires a who new build system (as
> koji set up) and a whole new module build back end (MBS).
>
> If you would rather use Oracle for your open source needs .. well, that
> is a decision you can make and be responsible for.
>
> If you would instead have feedback directly into the RHEL development
> process as a community .. then CentOS is where you want to be.
>
> This stuff is open source, and you are all gown ups who can make your
> own decisions.
>
> I can assure you .. I am working my butt off everyday to make CentOS
> Linux the best it can be. If you want to compare what the CentOS team
> (a small team) can do compared to Oracle (a tmulti billin dollar
> corporation who bought Sun Microsystems .. took over Java and Open
> Office, etc) .. well, we can not provide the resources they can provide.
>
> But Red hat heard the community .. that the community and Red Hat
> customers want more direct input into RHEL development. And Red Hat is
> taking action to open up RHEL development in CentOS Stream.
>
> You get to decide who you trust.
>
> Thanks,
> Johnny hUghes
>
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Blog article about the state of CentOS
Il 17/06/20 15:42, Scott Robbins ha scritto: On Wed, Jun 17, 2020 at 02:23:36PM +0100, Pete Biggs wrote: About Oracle as alternative. Oracle Linux is not an alternative to CentOS but for RHEL and if I will force to pay for enteprise system currently I will pay RHEL, not OL. Over this, OL is not the only enterprise distro that a "user" could choose. If support is needed there are SUSE (SLES) and Ubuntu. For who that don't need support there are Debian, Ubuntu, OpenSUSE (I'm talking about the most used but you know that slackware,FreeBSD are in that list), so many alternatives are in place. I think it's particularly disappointing *if* this is a "policy" from RH since the other major RHEL clone, Scientific Linux, has not produced an EL8 offering in favour of using CentOS. Keep in mind that as soon as Scientific Linux started taking off, IIRC, because CentOS was late with a release, RH quickly hired its main developer. I don't think we can really expect RH to act differently than most corporations. Yes but today Scientific Linux is out of games and CERN made CentOS CERN based on C8 so there is no more a valid competitor for this target (in the RH family based distro) CentOS at the current status (third 8 release) is not suitable for production with the current issues and we are forced to buy rhel license (and every needed extension). I would to know what think all ISPs that offer centos 8 on their VPS, Dedicated Server, Shared Hosting and how they handle this problem (probably they don't because the choice is on the customer but maybe...) As you said, probably nothing will change for the corporation "limit" concept but at this point, probably, many users will migrate to another platform with less limitation. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Blog article about the state of CentOS
Il 17/06/20 09:16, Nicolas Kovacs ha scritto:
Hi,
I just read this blog article from austrian Linux expert Michael Kofler. For
those among you who don't know the guy, he's my home country's number one Linux
expert (known as "der Kofler") and most notably the author of a series of
excellent books about Linux over the last 25 years.
https://kofler.info/centos-8-wertlose-langzeitunterstuetzung/
Disclaimer : I've been a CentOS user (and fan) since 4.x, I'm using it on all
my servers, and yes, I know the difference between upstream RHEL and CentOS.
The article is in german, but the statistics graph is eloquent enough for the
non-german-speaking users. It focuses on updates for CentOS 8, and more exactly
the extended periods of time where there have been no updates available.
The author's theory ("unspoken truth"): while it's a positive thing that Red
Hat is sponsoring CentOS, the amount of sponsoring is just insufficient enough
so that the product is "starved to death" by Red Hat (e. g. IBM) to encourage
users to move to RHEL.
The author's conclusion is quite severe: in the current state of things, CentOS
8 is not recommendable for production as updates are lagging too much behind.
While CentOS 7 may be usable, CentOS 8 has been "degraded to teaching and
testing purposes".
Still according to Mister Kofler, this "sorry state of things" will probably
encourage users to move to Oracle Linux, the other big RHEL clone.
After some hesitation, I decided to share this on the mailing list. Since this
raises some concerns, I'd be curious to have your take on this.
Cheers from the sunny South of France,
Niki
Hi Niki,
this is a sad thing but I'm not surprised by this and this is what I'm
thinking about CentOS since 8 was released. The CentOS team does a huge
work to release CentOS8, CentOS Stream and maintaining 7 and 6. Thank
you so much for this CentOS Team.
But since the core team is composed by 6(?) member is obvious that they
can't maintain all this versions without being in late and because it is
supported (but maybe supported is the wrong word in the current case) by
RH, if RH really interest about CentOS release they should put more
effort on CentOS Development. This is not what is happening and since 8
is released, it seems a try and buy distro.
I walked through 6.5 to 7 and 8. In 6.5 I was new, in 7 I really
appreciated CentOS but with 8 I noticed that it is not supported like
CentOS 7.
I use (like you) centos on all my server, some are anchored to the old
stable and other on 8 (but not production). I liked it very much that I
use it also on my workstation.
About update blackout, this is a great problem for production system
faced on Internet. SELinux can mitigate the risk (but also selinux got
security fix) but this is always an issue. Many report that the gap
between RHEL release and CentOS release is too much but I'm not
interested in how much time centos releases get through the build
process but I'm interested that, when a new centos release (major/minor)
are on the way, all others releases (current stable inside) will get
security updates during the build process and not left alone. Another
minor issue about updates are relative announces on ml that works for C7
but not for C8 (I read in a reddit AMA why this happens). This is
annoying because I need to follow every RHBA to see what happened and
why a package is updated or blindly install updates. This is another
thing that is not so good for a server.
If the theory "unspoken truth" is real I don't like how RH is trying to
encourage me to switch to RHEL and this is a bad way to do this.
About Oracle as alternative. Oracle Linux is not an alternative to
CentOS but for RHEL and if I will force to pay for enteprise system
currently I will pay RHEL, not OL. Over this, OL is not the only
enterprise distro that a "user" could choose. If support is needed there
are SUSE (SLES) and Ubuntu. For who that don't need support there are
Debian, Ubuntu, OpenSUSE (I'm talking about the most used but you know
that slackware,FreeBSD are in that list), so many alternatives are in place.
I hope that things will be better but in case of "failure" I will
evaluate other alternatives to CentOS for this "sorry state of things".
Thank you for sharing, I found it interesting.
My 2 Cent
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Apache (httpd) fails to start at boot - Centos 8.1
Il 16/06/20 08:11, Alessandro Baggi ha scritto: Il 16/06/20 06:21, Gordon Messmer ha scritto: On 6/15/20 7:06 PM, Jay Hart wrote: If I do 'systemctl start httpd', apache will start right up. But during boot, it doesn't and I get the resulting errors below. Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address 10.20.30.11:80 httpd is starting before an interface has been configured with 10.20.30.11. The default configuration starts httpd after "network.target" but you want to start it after "network-online.target". IIRC: run "systemctl edit httpd.service" and insert: [Unit] After=network-online.target ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos +1 This happened to me with ssh. Note: when you will get update for httpd package all could be reverted to the original status, so to avoid that your modified httpd.service will get an overwrite, create an alternative httpd.service in /etc/systemd/system (if I'm not wrong). Probably there is a new way to do this. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Apache (httpd) fails to start at boot - Centos 8.1
Il 16/06/20 06:21, Gordon Messmer ha scritto: On 6/15/20 7:06 PM, Jay Hart wrote: If I do 'systemctl start httpd', apache will start right up. But during boot, it doesn't and I get the resulting errors below. Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address 10.20.30.11:80 httpd is starting before an interface has been configured with 10.20.30.11. The default configuration starts httpd after "network.target" but you want to start it after "network-online.target". IIRC: run "systemctl edit httpd.service" and insert: [Unit] After=network-online.target ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos +1 This happened to me with ssh. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS runs on six cores.
Il 12/06/20 18:59, Gordon Messmer ha scritto: On 6/12/20 2:16 AM, Thomas Stephen Lee wrote: Do we need an upgrade ? Can you restate your question so that it's clear what version you are running, what hardware you are running it on, what you expect to happen, and what is happening instead? Hi, I think that Stephen is referring about the number of developer of the core team that is of 6 members (from this "Do we need an upgrade?"). My first question for Stephen is: why do you think that the core team needs more dev? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Understanding VDO vs ZFS
Il 03/05/20 04:50, david ha scritto: 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 (around 2tb) that I periodically back up. I keep the last 5 "snapshots". I use rsync so that when I overwrite the oldest backup, most of the data is already there and the backup completes quickly, because only a small number of files have actually changed. Because of this low change rate, I have used ZFS with its deduplication feature to store the data. I started using a Centos-6 installation, and upgraded years ago to Centos7. Centos 8 is on my agenda. However, I've had several data-loss events with ZFS where because of a combination of errors and/or mistakes, the entire store was lost. I've also noticed that ZFS is maintained separately from Centos. At this moment, the Centos 8 update causes ZFS to fail. Looking for an alternate, I'm trying VDO. In the VDO installation, I created a logical volume containing two hard-drives, and defined VDO on top of that logical volume. It appears to be running, yet I find the deduplication numbers don't pass the smell test. I would expect that if the logical volume contains three copies of essentially identical data, I should see deduplication numbers close to 3.00, but instead I'm seeing numbers like 1.15. I compute the compression number as follows: Use df and extract the value for "1k blocks used" from the third column use vdostats --verbose and extract the number titled "1K-blocks used" Divide the first by the second. Can you provide any advice on my use of ZFS or VDO without telling me that I should be doing backups differently? Thanks David Hi David, I'm not an expert about vdo but I will try it for backup purpose with rsync + hardlink. I know that this is not an answer you asked, sorry for this. Many user said me to use more specific tool for running backup using deduplication (borg in my case). I'm testing it and I'm not sure if I will adopt it in the long term. As you reported, you are using rsync solution so I would ask: why not use a more specific tool? What are benefits to stay with rsync for you? Thank you in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentO 8 and nftables default policy
Hi, the problem is that I'm using libvirtd for my vms. I think currently the best solution is remove this policies from .xml files. Il 18/04/20 22:22, Alan McRae via CentOS ha scritto: I had the same problem. If you are not using virtual machines then # systemctl disable libvirtd works and is easily reversible. Alan On 18/04/2020 23:03, Alessandro Baggi wrote: Il 17/04/20 11:01, Alessandro Baggi ha scritto: 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. Hi have not received any replies but I tried to investigate. After checking configuration files in my system I supposed that this could caused by a daemon, so I found that libvirtd push some rules. running virsh nwfilter-list I get: UUID Nome -- 34fe8cba-af99-4438-8efc-b135143425e2 allow-arp dc110112-3824-4cf3-946f-ba6e15cd29c3 allow-dhcp fecc383a-bab5-465d-a5be-98834fb626ce allow-dhcp-server 761e7132-8738-47c2-8101-275d6fd6a347 allow-incoming-ipv4 d37b017f-8f21-4ad0-9fa6-052a5cb1ed2e allow-ipv4 a8c740d5-328c-452e-bae7-9828c54f95b7 clean-traffic 296bdfad-11d9-4aa0-9817-4656ef2be6e5 clean-traffic-gateway 69215a61-bff5-482a-b913-589bb1ce18f2 no-arp-ip-spoofing 70c61f0a-c005-407f-843d-d13c2495f05d no-arp-mac-spoofing 386cd2f4-7272-43e2-ba1f-80cb3518649c no-arp-spoofing 9117fa21-e3d6-4c32-9cdf-af97ebd6599e no-ip-multicast 7a964470-4f74-4eef-9fec-a0e9a79e168d no-ip-spoofing 8c9e45a3-5d44-4641-b23d-eded5c1f1632 no-mac-broadcast 82dcd4f0-f55a-43ad-b520-d4c8d4bf37cd no-mac-spoofing bdd0ba54-7ce0-4a2c-9c25-c24072d364ba no-other-l2-traffic fc50783e-d32b-42ba-8380-7576c4388244 no-other-rarp-traffic edfc1bb3-b325-4f8d-8c5b-423e55da66eb qemu-announce-self 8556bd82-dc97-47b0-b573-5986ebbad3b2 qemu-announce-self-rarp If I will remove these libvirt filters I will get errors? Thank you in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentO 8 and nftables default policy
Il 17/04/20 11:01, Alessandro Baggi ha scritto: 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. Hi have not received any replies but I tried to investigate. After checking configuration files in my system I supposed that this could caused by a daemon, so I found that libvirtd push some rules. running virsh nwfilter-list I get: UUID Nome -- 34fe8cba-af99-4438-8efc-b135143425e2 allow-arp dc110112-3824-4cf3-946f-ba6e15cd29c3 allow-dhcp fecc383a-bab5-465d-a5be-98834fb626ce allow-dhcp-server 761e7132-8738-47c2-8101-275d6fd6a347 allow-incoming-ipv4 d37b017f-8f21-4ad0-9fa6-052a5cb1ed2e allow-ipv4 a8c740d5-328c-452e-bae7-9828c54f95b7 clean-traffic 296bdfad-11d9-4aa0-9817-4656ef2be6e5 clean-traffic-gateway 69215a61-bff5-482a-b913-589bb1ce18f2 no-arp-ip-spoofing 70c61f0a-c005-407f-843d-d13c2495f05d no-arp-mac-spoofing 386cd2f4-7272-43e2-ba1f-80cb3518649c no-arp-spoofing 9117fa21-e3d6-4c32-9cdf-af97ebd6599e no-ip-multicast 7a964470-4f74-4eef-9fec-a0e9a79e168d no-ip-spoofing 8c9e45a3-5d44-4641-b23d-eded5c1f1632 no-mac-broadcast 82dcd4f0-f55a-43ad-b520-d4c8d4bf37cd no-mac-spoofing bdd0ba54-7ce0-4a2c-9c25-c24072d364ba no-other-l2-traffic fc50783e-d32b-42ba-8380-7576c4388244 no-other-rarp-traffic edfc1bb3-b325-4f8d-8c5b-423e55da66eb qemu-announce-self 8556bd82-dc97-47b0-b573-5986ebbad3b2 qemu-announce-self-rarp If I will remove these libvirt filters I will get errors? Thank you in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentO 8 and nftables default policy
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. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8.1 Grub problem
Il 08/04/20 13:40, Jonathan Billings ha scritto: On Apr 8, 2020, at 04:01, Alessandro Baggi wrote: Il 08/04/20 01:46, Jonathan Billings ha scritto: grubby only alters the existing configuration. It never regenerates the grub.cfg in EFI. You can’t use “grub2-mkconfig” to create individual boot spec entries. -- Jonathan Billings Please explain how the process work, it is not so clear for me. I'm confused. In C7 when I need to modify grub menu kernel option I modify /etc/default/grub and run grub2-mkconfig and thats all. It always worked for me. On C8 this does not work anymore, grub2-mkconfig is not enough, it generates only the grub.cfg but it does not update the menu entries and need to modify each entry using grubby. At this point what grub.cfg is used for if directives are not loaded by it and need grubby to modify entries? I'm missing something Don’t use grub2-mkconfig, it is really only for initial grub configuration. It has a problematic past in CentOS 7 too. Disabling blscfg is possible but it isn’t the default setup and not the recommended way of updating kernel entries. If you need to update kernel parameters, use grubby. That’s what is run in the kernel package install scripts (via new-kernel-package). That’s what is run in packages like the nvidia 3rd party packages. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Ok thank you for your suggestion. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8.1 Grub problem
Il 08/04/20 01:46, Jonathan Billings ha scritto: On Apr 7, 2020, at 04:14, Alessandro Baggi wrote: thank you for your explanation. So in el8 grubby should be used to update kernel opts and grub2-mkconfig is used to generate an initial config. If I'm not wrong, grubby updates every single (sperated) entries on /boot/loader/entries and then generate the /boot/efi/EFI/centos/grub.cfg? Suppose that I want use only grub2-mkconfig to generate the grub.cfg what other operation are needed to make it working? grubby only alters the existing configuration. It never regenerates the grub.cfg in EFI. You can’t use “grub2-mkconfig” to create individual boot spec entries. -- Jonathan Billings Please explain how the process work, it is not so clear for me. I'm confused. In C7 when I need to modify grub menu kernel option I modify /etc/default/grub and run grub2-mkconfig and thats all. It always worked for me. On C8 this does not work anymore, grub2-mkconfig is not enough, it generates only the grub.cfg but it does not update the menu entries and need to modify each entry using grubby. At this point what grub.cfg is used for if directives are not loaded by it and need grubby to modify entries? I'm missing something ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8.1 Grub problem
Il 06/04/20 20:51, Jonathan Billings ha scritto: On Mon, Apr 06, 2020 at 04:03:53PM +0200, Alessandro Baggi wrote: I'm on 8.1. I'm searching help to see if this is a bug or error by me but can't find nothing. Currently I used grubby but it does not write any file that I know like /boot/efi/EFI/centos/grub.cfg (I tried to remove and add arg but nothing changed on files), so I don't know where it make update. I never got a problem using grub2-mkconfig -o file on C7 (last used was 7.5) It always worked as expected to me (for example when I installed nvidia driver using NVIDIA package to blacklist nouveau manually). In CentOS 8, GRUB2 uses 'blscfg' to store bootloader-independent boot entries in /boot/loader/entries (by default). grub2-mkconfig generates an initial configuration but grubby modifies the individual bootloader spec files in the entries directory. After It's updated the kernel arguments, it overrides the kernelopts in the grub.cfg and hard-codes them per-spec file. In addition to providing a bootloader-agnostic config file, another benefit of blscfg is that the EFI volume is usually a FAT32 filesystem and can't recover easily from filesystem errors. We want to avoid writing to the EFI volume repeatedly, so we write a single configuration once and it should remain static. New kernel entries create new bootloader spec files in /boot/loader/entries/, which is on the /boot filesystem, which is normally a journaled EXT4 or XFS filesystem, which can recover better from failures. Hi Jonathan, thank you for your explanation. So in el8 grubby should be used to update kernel opts and grub2-mkconfig is used to generate an initial config. If I'm not wrong, grubby updates every single (sperated) entries on /boot/loader/entries and then generate the /boot/efi/EFI/centos/grub.cfg? Suppose that I want use only grub2-mkconfig to generate the grub.cfg what other operation are needed to make it working? Thank you in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8.1 Grub problem
Il 06/04/20 15:21, Simon Matter via CentOS ha scritto: Il 06/04/20 11:54, Georgios ha scritto: Hi there! I had a similar problem recently with grub. No idea why it doesnt work. Try using grubby instead of grub2-mkconfig if you want the system to keep your kernel parameters between boots. Something like: sudo grubby --args="i915.modeset=0 rd.driver.blacklist=i915" --update- kernel=ALL Hope it helps! Have a nice day! On Mon, 2020-04-06 at 11:42 +0200, Alessandro Baggi wrote: Hi list, I reinstalled on my workstation CentOS 8.1. I explain: I'm a KDE user but packages shipped from EPEL currently are buggy so I prefer a stable and functioning system to work with. So I tried to remove KDE workgroup and installed group "Workstation" but the system bricked so I reinstalled with GNOME. I've an nvidia gtx 1050ti GPU so I installed kmod-driver from rpmfusion. After the installation of Nvidia driver, I rebooted, gdm start and after I perform the login the system freeze. So this problem happened to me with C7.5 and nvidia driver. In my case I need to blacklist i915 module and system works. Also in this case I tried to boot centos changing grub kernel parameters pressing 'e' in the grub menu and adding "i915.modeset=0 rd.driver.blacklist=i915", booted and system works. So I tried to make this permanent updating grub configuration adding the previous directives (and removed rhgb and quiet) to /etc/default/grub and run grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg. Reboot the system and checked again kernel parameters on grub menu and seen that nothing changed. Booted and freezed. I checked /boot/efi/EFI/centos/grub.cfg and kernelops has the new directives. Seems that grub configuration does not take effect. I made another test inside a VM installed with minimal selection and remove rhgb and quiet parameters and worked fine. The vm is BIOS and my workstation UEFI. How I can solve this problem? Currently to boot my system I need always to add this params. Thank you in advance ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi, I tried as suggested, parameters will be updated but I get already crash. So I tried to remove also rhgb and quiet and works well. Would be good to know what is wrong with grub2-mkconfig. Where start to investigate? Just to be sure, your subject line says this is on CentOS 8.1, right? Because IIRC grub2-mkconfig was broken in CentOS 7 despite the head of every grub cfg file telling us "It is automatically generated by grub2-mkconfig using templates". Really weird that you see the same with CentOS 8.1. Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi Simon, I'm on 8.1. I'm searching help to see if this is a bug or error by me but can't find nothing. Currently I used grubby but it does not write any file that I know like /boot/efi/EFI/centos/grub.cfg (I tried to remove and add arg but nothing changed on files), so I don't know where it make update. I never got a problem using grub2-mkconfig -o file on C7 (last used was 7.5) It always worked as expected to me (for example when I installed nvidia driver using NVIDIA package to blacklist nouveau manually). ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8.1 Grub problem
Il 06/04/20 14:42, Georgios ha scritto: Hi, I tried as suggested, parameters will be updated but I get already crash. So I tried to remove also rhgb and quiet and works well. Would be good to know what is wrong with grub2-mkconfig. Where start to investigate? No idea. I stop looking after I manage to pass the arguments I wanted to the kernel. If you find the problem send an email on the list. It would be good to know what is wrong. Hi, I noticed that running grub2-mkconfig the output file is modified. Using simply grubby grub.cfg seems not to be modified. So seems that something changed but I don't know where to search ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8.1 Grub problem
Il 06/04/20 11:54, Georgios ha scritto: Hi there! I had a similar problem recently with grub. No idea why it doesnt work. Try using grubby instead of grub2-mkconfig if you want the system to keep your kernel parameters between boots. Something like: sudo grubby --args="i915.modeset=0 rd.driver.blacklist=i915" --update- kernel=ALL Hope it helps! Have a nice day! On Mon, 2020-04-06 at 11:42 +0200, Alessandro Baggi wrote: Hi list, I reinstalled on my workstation CentOS 8.1. I explain: I'm a KDE user but packages shipped from EPEL currently are buggy so I prefer a stable and functioning system to work with. So I tried to remove KDE workgroup and installed group "Workstation" but the system bricked so I reinstalled with GNOME. I've an nvidia gtx 1050ti GPU so I installed kmod-driver from rpmfusion. After the installation of Nvidia driver, I rebooted, gdm start and after I perform the login the system freeze. So this problem happened to me with C7.5 and nvidia driver. In my case I need to blacklist i915 module and system works. Also in this case I tried to boot centos changing grub kernel parameters pressing 'e' in the grub menu and adding "i915.modeset=0 rd.driver.blacklist=i915", booted and system works. So I tried to make this permanent updating grub configuration adding the previous directives (and removed rhgb and quiet) to /etc/default/grub and run grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg. Reboot the system and checked again kernel parameters on grub menu and seen that nothing changed. Booted and freezed. I checked /boot/efi/EFI/centos/grub.cfg and kernelops has the new directives. Seems that grub configuration does not take effect. I made another test inside a VM installed with minimal selection and remove rhgb and quiet parameters and worked fine. The vm is BIOS and my workstation UEFI. How I can solve this problem? Currently to boot my system I need always to add this params. Thank you in advance ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi, I tried as suggested, parameters will be updated but I get already crash. So I tried to remove also rhgb and quiet and works well. Would be good to know what is wrong with grub2-mkconfig. Where start to investigate? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] C8.1 Grub problem
Hi list, I reinstalled on my workstation CentOS 8.1. I explain: I'm a KDE user but packages shipped from EPEL currently are buggy so I prefer a stable and functioning system to work with. So I tried to remove KDE workgroup and installed group "Workstation" but the system bricked so I reinstalled with GNOME. I've an nvidia gtx 1050ti GPU so I installed kmod-driver from rpmfusion. After the installation of Nvidia driver, I rebooted, gdm start and after I perform the login the system freeze. So this problem happened to me with C7.5 and nvidia driver. In my case I need to blacklist i915 module and system works. Also in this case I tried to boot centos changing grub kernel parameters pressing 'e' in the grub menu and adding "i915.modeset=0 rd.driver.blacklist=i915", booted and system works. So I tried to make this permanent updating grub configuration adding the previous directives (and removed rhgb and quiet) to /etc/default/grub and run grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg. Reboot the system and checked again kernel parameters on grub menu and seen that nothing changed. Booted and freezed. I checked /boot/efi/EFI/centos/grub.cfg and kernelops has the new directives. Seems that grub configuration does not take effect. I made another test inside a VM installed with minimal selection and remove rhgb and quiet parameters and worked fine. The vm is BIOS and my workstation UEFI. How I can solve this problem? Currently to boot my system I need always to add this params. Thank you in advance ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Trying again: KDE fails with a gray screen after login, can't reinstall
Il 03/04/20 17:54, mark ha scritto: On 2020-04-03 11:46, Simon Matter via CentOS wrote: I set for graphical mode, I get the login screen, I change to KDE, and the screen goes black, then after minutes, gray with a cursor, and that's it - I left it overnight, no change. Brand new install (as of yesterday). Missed any "agree to license", and missed choosing software. Manually groupinstalled Installed Environment Groups: KDE Plasma Workspaces Development and Creative Workstation Tried to reinstall: No group named KDE Plasma Workspaces exists I'm assuming I need to install something else, but does anyone have a clue? I really do NOT want gnome. I don't know how the situation is with C8 but I always liked XFCE to get work done. It has less dependencies and is therefore a bit easier to install. Doesn't address my problem. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi mark, I suppose that you are using C8.1. This are my steps to install Plasma 5 from EPEL starting from a minimal centos installation. # dnf install epel-release # dnf config-manager --set-enabled PowerTools # dnf grouplist "KDE" # dnf install sddm # systemctl set-default graphical # systemctl enable sddm # reboot It worked on first shot. Now, I'm using an old Nvidia GTX 1050ti and it works with any problem using nouveau and nvidia driver. If it does not start as normal, try to install xfce group and see if you can run it. If not there is something missing or a video driver problem Other this I can't help anymore, maybe some logs could be usefull. Hope that helps. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 and backup solution
Il 02/04/20 21:14, Karl Vogel ha scritto: [Replying privately because my messages aren't making it to the list] In a previous message, Alessandro Baggi said: A> Bacula works without any problem, well tested, solid but complex to A> configure. Tested on a single server (with volumes on disk) and a A> full backup of 810gb (~15 files) took 6,30 hours (too much). For a full backup, I'd use something like "scp -rp". Anything else has overhead you don't need for the first copy. Also, pick a good cipher (-c) for the ssh/scp commands -- it can improve your speed by an order of magnitude. Here's an example where I copy my current directory to /tmp/bkup on my backup server: Running on: Linux x86_64 Thu Apr 2 14:48:45 2020 me% scp -rp -c aes128-...@openssh.com -i $HOME/.ssh/bkuphost_ecdsa \ . bkuphost:/tmp/bkup Authenticated to remote-host ([remote-ip]:22). ansible-intro 100% 16KB 11.3MB/s 00:00 ETA nextgov.xml 100% 27KB 21.9MB/s 00:00 ETA building-VM-images 100% 1087 1.6MB/s 00:00 ETA sort-array-of-hashes 100% 1660 2.5MB/s 00:00 ETA ... ex1 100% 910 1.9MB/s 00:00 ETA sitemap.m4 100% 1241 2.3MB/s 00:00 ETA contents 100% 3585 5.5MB/s 00:00 ETA ini2site 100% 489 926.1KB/s 00:00 ETA mkcontents 100% 1485 2.2MB/s 00:00 ETA Transferred: sent 6465548, received 11724 bytes, in 0.4 seconds Bytes per second: sent 18002613.2, received 32644.2 Thu Apr 02 14:48:54 2020 A> scripted rsync. Simple, through ssh protocol and private key. No agent A> required on target. I use file level deduplication using hardlinks. I avoid block-level deduplication as a general rule -- ZFS memory use goes through the roof if you turn that on. rsync can do the hardlinks, but for me it's been much faster to create a list of SHA1 hashes and use a perl script to link the duplicates. I can send you the script if you're interested. This way, you're not relying on the network for anything other than the copies; everything else takes place on the local or backup system. A> Using a scripted rsync is the simpler way but there is something that A> could be leaved out by me (or undiscovered error). Simple to restore. I've never had a problem with rsync, and I've used it to back up Linux workstations with ~600Gb or so. One caveat -- if you give it a really big directory tree, it can get lost in the weeds. You might want to do something like this: 1. Make your original backup using scp. 2. Get a complete list of file hashes on your production systems using SHA1 or whatever you like. 3. Whenever you do a backup, get a (smaller) list of modified files using something like "find ./something -newer /some/timestamp/file" or just making a new list of file hashes and comparing that to the original list. 4. Pass the list of modified files to rsync using the "--files-from" option so it doesn't have to walk the entire tree again. Good luck! -- Karl Vogel / voge...@pobox.com / I don't speak for the USAF or my company The best setup is having a wife and a mistress. Each of them will assume you're with the other, leaving you free to get some work done. --programmer with serious work-life balance issues Hi Karl, thank you for your answer. I'm trying ssh scripted rsync using a faster cypher like you suggested and seems that transfer on 10GB is better of default selected cypher (129 sec vs 116 using aes128-gcm, I tested this multiple times). Now I will try to check on the entire dataset and see how much benefit I gain. Waiting that, what do you think about bacula as backup solution? Thank you in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 and backup solution
Yes you are right. I meant that I don't need an real agent like with bacula that need to be configured completely Il Gio 2 Apr 2020, 19:52 Jonathan Billings ha scritto: > On Thu, Apr 02, 2020 at 05:32:35PM +0200, Alessandro Baggi wrote: > > scripted rsync. Simple, through ssh protocol and private key. No agent > > required on target. > > Just a point of clarification -- you need an rsync binary on both > sides of the ssh session, so 'rsync' would be the agent needed on the > target. > > -- > Jonathan Billings > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 and backup solution
Il 02/04/20 17:49, Nicolas Kovacs ha scritto: Le 02/04/2020 à 17:32, Alessandro Baggi a écrit : I have not so much experiences on backups and choosing the bad tool could be dangerous so I need some suggestion. What backup solution do you suggest for my scenario? I'm using Rsnapshot on all my CentOS 7 servers. It's a very elegant solution that follows the KISS principle. I've written a little blog article about it. It's in French, but the Unix bits are universal. :o) https://blog.microlinux.fr/rsnapshot-centos-7/ It's basically scripted rsync with ssh on steroids. Been using it for the last five years or so. It just works. Cheers, Niki Hi Niki, thank you for your answer. I remember you when I used Slackware and I think your KISS is inherited by there but sometimes more complex things are needed. Rsnapshot is a great tool but I need catalog, jobs info, pre/post job script on remote target, mailing, compression and possibly store data off-site (no on a public cloud). ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] C8 and backup solution
Hi list, I'm searching a valid backup system to perform backups of 3 server, one local and 2 remote, and 2 linux workstation. (this number could be higher in future). Currently I'm testing bacula, scripted rsync with hardlink and borgbackup on C8.1. Bacula works without any problem, well tested, solid but complex to configure. Tested on a single server (with volumes on disk) and a full backup of 810gb (~15 files) took 6,30 hours (too much). I would run deduplication but 1. bacula on C8 is not compiled with aligned 2. bacula put attention on some possibile bad scenario where deduplication could be a problem in losing one block that could break many files with the same shared block. So deduplication is secure or I should be away from it? scripted rsync. Simple, through ssh protocol and private key. No agent required on target. I use file level deduplication using hardlinks. To perform compression and block deduplication I could use fs like zfs (not available from epel) or use something like stratis (I don't checked if it offer deduplication in this moment). Encryption could be performed on fs level. Using a scripted rsync is the simpler way but there is something that could be leaved out by me (or undiscovered error). Simple to restore. BorgBackup is another solution similar to rsync in some way. It works like rsync through ssh but while rsync simply sends data, borg run deduplication, compression and encryption on place. Why is similar rsync? Because I need another script to run borg. It is not a complete solution and it works on push method and not pull like with bacula or rsync. If I would manage all my server from a central backup server is a problem, so to accomplish this I should run the borg command from the central server on the target server that point back to the remote repository (located on the central server). There is another solution with borg: using sshfs but is 4 time slower (too much solwer). I have not so much experiences on backups and choosing the bad tool could be dangerous so I need some suggestion. What backup solution do you suggest for my scenario? Thank you in advance. Alessandro. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 and Plasma5 error
Il 12/03/20 00:58, Ian Mortimer ha scritto: On Wed, 2020-03-11 at 09:19 +0100, Alessandro Baggi wrote: Seems that kde5init is not present on the system and inside repositories. I think you mean kdeinit5 (as in your original post). That's provided by the package: kf5-kinit If you have mlocate installed you can find files with: locate _file_name_ If the file is installed by a package and is an executable you can find which package with: rpm -qf $(which kdeinit5) If it's not an executable but you know the path to the file: rpm -qf /path/to/file Thank you for your answer ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 and Plasma5 error
Il 11/03/20 04:13, Ian Mortimer ha scritto: On Tue, 2020-03-10 at 09:46 +0100, Alessandro Baggi wrote: How I can communicate the bug with the maintainer? Open an account at https://bugzilla.redhat.com/ Select "File a Bug" Go to "Fedora" then "Fedora EPEL" In "Component" select the relevant plasma package File the bug report Sorry, I'm here again. I have created a bugzilla account and done what you said. Reading select list of which component give the error, I tried to locate what packages has kde5init but nothing contains it. I run also "find / | grep "kde5init" but I don't get any results. Seems that kde5init is not present on the system and inside repositories. How I can proceed? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 and Plasma5 error
On Tue, 2020-03-10 at 09:46 +0100, Alessandro Baggi wrote: How I can communicate the bug with the maintainer? Open an account at https://bugzilla.redhat.com/ Select "File a Bug" Go to "Fedora" then "Fedora EPEL" In "Component" select the relevant plasma package File the bug report Thank you. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] C8 and Plasma5 error
Hi list, I have installed plasma5 on my c8 workstation but I'm getting (random) error for kdeinit5 and cannot see any information about the segmentation fault because there are not available information. Anyone that use Plasma5 from EPEL get this error? How I can communicate the bug with the maintainer? Thanks in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] C8 and bacula messages
Hi list, I'm updating my backup server using C8 and bacula 9.0.6. I have problem when I run a full backup with a pool that has Maximum Volume Jobs = 1 as in the configuration used on C7. The problem is that I get this message: JobId 11: Max Volume jobs=1 exceeded. Marking Volume "Full-0009" as Used. multiple time inside bacula messages when backup is performing? Is this a bug or is a misconfiguration? Thanks in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Borgbackup question
Il 02/03/20 13:50, Tobias Kirchhofer ha scritto: On 2 Mar 2020, at 13:35, Alessandro Baggi wrote: Il 02/03/20 13:18, Tobias Kirchhofer ha scritto: On 2 Mar 2020, at 12:58, Alessandro Baggi wrote: Il 01/03/20 20:18, Tobias Kirchhofer ha scritto: On 1 Mar 2020, at 20:00, Gordon Messmer wrote: On 3/1/20 12:40 AM, Alessandro Baggi wrote: borgbackup is a very interesting backup tool with a lot of features. It is ready for "production" or I should expect some bad surprise? I don't know the answer to that, but to me that implies two questions: 1) Are there failure conditions that it doesn't handle, especially with an interrupted backup, and 2) Does it perform poorly under any specific circumstances. If anyone has experience with those questions, or is familiar enough with the implementation to explain why those should not be an issue, I'd be interested in their input as well. I use borgbackup for several laptops backing up to a local file server with sshfs, and that's been good so far. We have around 50 linux clients with borg backups to two different backup server, provisioned with Ansible. A new host is in the backup in around 30 seconds :) One backup server is internal for DMZ and LAN and one is for external hosts. The internal backup server syncs its backup to the external server. Storage is made with ZFS summed up to 16 TB each server. This runs nicely for around two years without interruption. We learned a bit her e and there about some side effects with borg cache in the beginning and invested some time in hardening and Ansible role. Before we choosed borg restic was on the list. Looks good too. Do not now anymore why we decided for borg. Maybe the name :) We startet here https://borgbackup.readthedocs.io/en/stable/deployment/central-backup-server.html Tobias Hi Tobias, How do you secure the process? Plain ssh: authorized_keys on the backup server: ``` … command="borg serve --restrict-to-path /borgbackup/vm/host-name-of-backup-client --append-only" ssh-ed25519 C3NzaC1… root@host-name-of-backup-client … ``` Ok thank you but how do you run prune command if append-only is enabled? Prune is startet on the client after each backup. Before we did it on the backup server at once. But borg recreated the whole index per repo each time. The mailing list was helpful with this. borg prune must run on the machine where the backup is created. append-only is not involved in borg prune. Thank you for your answer. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Borgbackup question
Il 02/03/20 13:18, Tobias Kirchhofer ha scritto: On 2 Mar 2020, at 12:58, Alessandro Baggi wrote: Il 01/03/20 20:18, Tobias Kirchhofer ha scritto: On 1 Mar 2020, at 20:00, Gordon Messmer wrote: On 3/1/20 12:40 AM, Alessandro Baggi wrote: borgbackup is a very interesting backup tool with a lot of features. It is ready for "production" or I should expect some bad surprise? I don't know the answer to that, but to me that implies two questions: 1) Are there failure conditions that it doesn't handle, especially with an interrupted backup, and 2) Does it perform poorly under any specific circumstances. If anyone has experience with those questions, or is familiar enough with the implementation to explain why those should not be an issue, I'd be interested in their input as well. I use borgbackup for several laptops backing up to a local file server with sshfs, and that's been good so far. We have around 50 linux clients with borg backups to two different backup server, provisioned with Ansible. A new host is in the backup in around 30 seconds :) One backup server is internal for DMZ and LAN and one is for external hosts. The internal backup server syncs its backup to the external server. Storage is made with ZFS summed up to 16 TB each server. This runs nicely for around two years without interruption. We learned a bit her e and there about some side effects with borg cache in the beginning and invested some time in hardening and Ansible role. Before we choosed borg restic was on the list. Looks good too. Do not now anymore why we decided for borg. Maybe the name :) We startet here https://borgbackup.readthedocs.io/en/stable/deployment/central-backup-server.html Tobias Hi Tobias, How do you secure the process? Plain ssh: authorized_keys on the backup server: ``` … command="borg serve --restrict-to-path /borgbackup/vm/host-name-of-backup-client --append-only" ssh-ed25519 C3NzaC1… root@host-name-of-backup-client … ``` Ok thank you but how do you run prune command if append-only is enabled? Thanks in advance ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Borgbackup question
Il 01/03/20 20:18, Tobias Kirchhofer ha scritto: On 1 Mar 2020, at 20:00, Gordon Messmer wrote: On 3/1/20 12:40 AM, Alessandro Baggi wrote: borgbackup is a very interesting backup tool with a lot of features. It is ready for "production" or I should expect some bad surprise? I don't know the answer to that, but to me that implies two questions: 1) Are there failure conditions that it doesn't handle, especially with an interrupted backup, and 2) Does it perform poorly under any specific circumstances. If anyone has experience with those questions, or is familiar enough with the implementation to explain why those should not be an issue, I'd be interested in their input as well. I use borgbackup for several laptops backing up to a local file server with sshfs, and that's been good so far. We have around 50 linux clients with borg backups to two different backup server, provisioned with Ansible. A new host is in the backup in around 30 seconds :) One backup server is internal for DMZ and LAN and one is for external hosts. The internal backup server syncs its backup to the external server. Storage is made with ZFS summed up to 16 TB each server. This runs nicely for around two years without interruption. We learned a bit her e and there about some side effects with borg cache in the beginning and invested some time in hardening and Ansible role. Before we choosed borg restic was on the list. Looks good too. Do not now anymore why we decided for borg. Maybe the name :) We startet here https://borgbackup.readthedocs.io/en/stable/deployment/central-backup-server.html Tobias Hi Tobias, How do you secure the process? Thanks in advance ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Borgbackup question
Hi all, borgbackup is a very interesting backup tool with a lot of features. It is ready for "production" or I should expect some bad surprise? Anyone use it for work purpose? Thanks in advance. Alessandro. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8.1 and NVIDIA support
Il 02/02/20 01:11, Jerry Geis ha scritto: Does CentOS 8.1 support OLDER generate NVIDIA ? Like NVIDIA Corporation GF119M [GeForce GT 520M] I'm looking for hardware acceleration H264 type support. Thanks, Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi Jerry, I don't know if your card is supported natively considering it an old model. The default module for NVIDIA GPU is nouveau but I remove it due to low performances. I have a 1050ti and currently using rpmfusion-nonfree for NVIDIA driver to avoid problem every kernel update using NVIDIA "package". Try to install rpmfusion packages and try. Hope that helps. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 Question
Il 24/01/20 23:00, Orion Poplawski ha scritto: On 1/24/20 4:38 AM, Alessandro Baggi wrote: Hi list, I installed on my workstation C8.1 (1911) and performed a minimal install and then installed XFCE from EPEL. I noticed a strange behaviour (don't know if this is the wanted default). If I try ,from normal user shell, to run command like "reboot" or "shutdown -h now" system will reboot/shutdown. This happens on tty console, on xfce terminal and ssh session. My user is not in wheel and during install I have not enabled checkbox to give that user administration permission. I tried to create a new user with adduser but got the same problem. To solve this I modified polkit login1 policy on /usr/share/polkit-1/actions/org.freedesktop.login1.policy setting no for statement that concern reboot and shutdown/poweroff. Why on CentOS a normal user can shutdown the system without root privileges? I think that on any server normal user should not be able to shutdown the system without privileges. This is a bug or a wanted default? So, as you figured out from the polkit setting - "active" user's (i.e. with a "seat") have access to shut a machine down. Now to figure out who has a seat - and you use "loginctl" to see that. For e.g. from my non-privileged user logged into my CentOS 8.1 VM via ssh: $ loginctl SESSION UID USER SEAT TTY 1 # user it shows that I don't have a "seat" and so: $ shutdown -h now Failed to set wall message, ignoring: Connection timed out Failed to power off system via logind: Interactive authentication required. Failed to open initctl fifo: Permission denied Failed to talk to init daemon. as expected. Perhaps you can start tracking down with loginctl who has a seat and why. Hi, thank you very much for your suggestion, loginctl did help me to understand this "problem". I tried to run loginctl on my VM logging in with ssh and I get this: [testuser@localhost ~]$ loginctl SESSION UID USER SEAT TTY 3 1000 testuser 1 sessions listed. and try to run reboot give me the expected behaviour. If I try from tty console I have a seat for testuser and can reboot the system. I don't know what I done in the other test... Thank you very much, I'm happy this is my mistake and not a centos bug. Thank you to all user that helped me. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 Question
Il 24/01/20 15:44, Pete Biggs ha scritto: I noticed a strange behaviour (don't know if this is the wanted default). If I try ,from normal user shell, to run command like "reboot" or "shutdown -h now" system will reboot/shutdown. This happens on tty console, on xfce terminal and ssh session. I've just created a normal user on my test system and when I try to reboot or halt the system when logged in via ssh I get: $ reboot Failed to set wall message, ignoring: Interactive authentication required. Failed to reboot system via logind: Interactive authentication required. Failed to open initctl fifo: Permission denied Failed to talk to init daemon. Which is correct behaviour. Hi Pete, Yes this is what I expect, but I'm trying to understand why on a fresh installation on a VM, this happens on ssh without user logged in or from console as normal user? I tried the installation several times and with several ISO but nothing changed. On every fresh installation I have not installed other packages and not enabled networking. If you have the time, please can you try to install from 8.1 iso using minimal installation and try again? I know that you struggle to believe my problem but I don't know how to prove this. However, a user logged in at the machine as GUI console session has always been able to halt or reboot the system. This does not happen only on my xfce system but on system on VM without a GUI. Why on CentOS a normal user can shutdown the system without root privileges? I think that on any server normal user should not be able to shutdown the system without privileges. If it's a desktop machine, then the console logged in user should be able to shutdown the machine - at least then it means they don't resort to pulling the plug. ... Presumably you don't allow users physically near a server? No, but this happen also in ssh session. Thank you for your help. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 Question
Il 24/01/20 15:47, Simon Matter via CentOS ha scritto: Il 24/01/20 15:11, Simon Matter via CentOS ha scritto: Hi list, I installed on my workstation C8.1 (1911) and performed a minimal install and then installed XFCE from EPEL. I noticed a strange behaviour (don't know if this is the wanted default). If I try ,from normal user shell, to run command like "reboot" or "shutdown -h now" system will reboot/shutdown. This happens on tty console, on xfce terminal and ssh session. But can you describe exactly in which situation user x can shutdown? I mean, if you say via ssh connection, is it that user x is at the same time also logged in into XFCE desktop on the same system? Or is it also true if the only login to the system at this time is via the ssh connection and then user x is still able to shutdown? I mean if user x runs the XFCE session remote on the system using ssh X11 forwarding, NX or whatever, then user x should really NOT be able to shutdown without providing the root password. That would be a nightmare for multi user systems :-) Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi Simon, I tried on my system using XFCE, I tried with a fresh installation on vm without X (using minimal and server installation), inside ssh with/without user logged and from tty console. Try to reproduce it. Install C8 on a VM using minimal installation, login in as normal user an type reboot. Well, I didn't install C8 yet but do you say that if do a fresh server type install of C8 on a host, add an unprivileged user, login via ssh to the user account on the host, you can reboot then? This is what is happening to my C8 installation on VM or physical server. If you can confirm this, the only thing that remains to understand is if this is a bug or a default policy. If not, there is something wrong in my fresh installation but I cannot identify what. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 Question
Il 24/01/20 15:11, Simon Matter via CentOS ha scritto: Hi list, I installed on my workstation C8.1 (1911) and performed a minimal install and then installed XFCE from EPEL. I noticed a strange behaviour (don't know if this is the wanted default). If I try ,from normal user shell, to run command like "reboot" or "shutdown -h now" system will reboot/shutdown. This happens on tty console, on xfce terminal and ssh session. But can you describe exactly in which situation user x can shutdown? I mean, if you say via ssh connection, is it that user x is at the same time also logged in into XFCE desktop on the same system? Or is it also true if the only login to the system at this time is via the ssh connection and then user x is still able to shutdown? I mean if user x runs the XFCE session remote on the system using ssh X11 forwarding, NX or whatever, then user x should really NOT be able to shutdown without providing the root password. That would be a nightmare for multi user systems :-) Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi Simon, I tried on my system using XFCE, I tried with a fresh installation on vm without X (using minimal and server installation), inside ssh with/without user logged and from tty console. Try to reproduce it. Install C8 on a VM using minimal installation, login in as normal user an type reboot. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] C8 Question
Hi list, I installed on my workstation C8.1 (1911) and performed a minimal install and then installed XFCE from EPEL. I noticed a strange behaviour (don't know if this is the wanted default). If I try ,from normal user shell, to run command like "reboot" or "shutdown -h now" system will reboot/shutdown. This happens on tty console, on xfce terminal and ssh session. My user is not in wheel and during install I have not enabled checkbox to give that user administration permission. I tried to create a new user with adduser but got the same problem. To solve this I modified polkit login1 policy on /usr/share/polkit-1/actions/org.freedesktop.login1.policy setting no for statement that concern reboot and shutdown/poweroff. Why on CentOS a normal user can shutdown the system without root privileges? I think that on any server normal user should not be able to shutdown the system without privileges. This is a bug or a wanted default? Thanks in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem
Il 16/01/20 02:21, Gordon Messmer ha scritto: On 1/15/20 8:18 AM, Alessandro Baggi wrote: Then I sync src/ to dest/ using "rsync -avS src/ dest/", all ok but when I run "du -h dest/testfile" I get 0 and if I run "du -b dest/testfile" I get the correct size in bytes. That's not a bug, that's what sparse files are. In POSIX systems, it's possible to treat a regular file like memory, and one of the things you might do with such a feature is use a file to keep track of the last time a user logged in. The simplest way to so that is to save the time value at the offset of the user's UID. My uid is 55665, so if the file weren't sparse, that one entry would create an enormous file, but with sparse files, the system only needs to allocate one block to store that value. If a process reads that file, it will get all zeros from the OS until it reaches the date stored at my uid offset. Applications can't tell whether a given set of zeros in a file are actual zeros on disk, or if they're simply parts of the file that haven't been written to, so when you tell rsync to create sparse files, it will do its best to identify blocks that are all zeros and simply not write to those on the destination. Thus, if you use /dev/zero to create a file on the source and then rsync it with -S, the destination file will use zero blocks of storage. Naturally, that can only be true with files whose contents are null bytes, as you get from /dev/zero. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Thank you for your answer. I appreciated it. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem
Il 15/01/20 18:54, Jon Pruente ha scritto: On Wed, Jan 15, 2020 at 11:38 AM Alessandro Baggi < alessandro.ba...@gmail.com> wrote: Hi Jon, I wrote in the first mail the script with the current order of command that I used. Try to run in a bash script and you will see the result. If not my sequence is: dd if=/dev/zero of=src/testfile bs=1M count=100 rsync -avS src/ dest/ du -h dest/testfile du -b dest/testfile for urandom: dd if=/dev/urandom of=src/testfile bs=1M count=100 rsync -avS src/ dest/ du -h dest/testfile du -b dest/testfile without --sparse the same as first sequence without -S option. But why du reports 0M when with -b reports correct bytes and why this happens only with zeroed file? Ah, I misunderstood what you meant. I had thought you might have created a file with urandom first and then overwrote it with zeros. This is behaving as expected with sparse files. You can create a sparse file with dd by using seek: https://www.thegeekdiary.com/how-to-create-sparse-files-in-linux-using-dd-command/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Thank you for the suggestion. I meant -S of rsync to use disk space efficiently but this is a (great) misunderstood. Now I read again rsync man page (and your link) and this means "treat sparse files efficiently to save space on disk". My question is: is rsync capable to detect sparse files from "regular" files? If -S is invoked and no sparse files are not in dataset, it treats those files as sparse files or "regular" files? Why I get different behaviour using urandom and /dev/zero? This is casual/accidental? Thank you again for your help. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem
Il 15/01/20 17:51, Jon Pruente ha scritto: On Wed, Jan 15, 2020 at 10:18 AM Alessandro Baggi < alessandro.ba...@gmail.com> wrote: I made several test to see what happens and noticed that removing -S (--sparse) from rsync command problem does not occour. In another test, thinking about a problem on 0ed file, I tried file generation using /dev/urandom then /dev/zero and running rsync -avS the problem is disappeared. https://wiki.archlinux.org/index.php/Sparse_file#Creating_sparse_files In short, rsync is being told to create sparse files with the -S flag, so it does. Could you share what you did with the urandom then zero test you mentioned? I'm curious what exact sequence of commands you used. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi Jon, I wrote in the first mail the script with the current order of command that I used. Try to run in a bash script and you will see the result. If not my sequence is: dd if=/dev/zero of=src/testfile bs=1M count=100 rsync -avS src/ dest/ du -h dest/testfile du -b dest/testfile for urandom: dd if=/dev/urandom of=src/testfile bs=1M count=100 rsync -avS src/ dest/ du -h dest/testfile du -b dest/testfile without --sparse the same as first sequence without -S option. But why du reports 0M when with -b reports correct bytes and why this happens only with zeroed file? I don't know if in the original post mail script ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] [semi-OT] C7 Possible bug but I can't determine what tool has the problem
Hi all, I'm writing a script that uses rsync to sync 2 dirs on C7. I noticed a strange behaviour. I have 2 dir: src and dest. In src dir I generate a testfile with "dd if=/dev/zero of=testfile bs=1M count=100" and when I run "du -h testfile" I get the correct result. Then I sync src/ to dest/ using "rsync -avS src/ dest/", all ok but when I run "du -h dest/testfile" I get 0 and if I run "du -b dest/testfile" I get the correct size in bytes. I made several test to see what happens and noticed that removing -S (--sparse) from rsync command problem does not occour. In another test, thinking about a problem on 0ed file, I tried file generation using /dev/urandom then /dev/zero and running rsync -avS the problem is disappeared. This not seems to be a CentOS 7 related problem. I tried also on Fedora 31 and get the same problem. I wrote a simple bash script to replicate the problem: #!/bin/bash mkdir src mkdir dest cd src #dd if=/dev/urandom of=testfile bs=1M count=100 dd if=/dev/zero of=testfile bs=1M count=100 echo "src/testfile size:" du -h testfile du -b testfile cd .. rsync -avS src/ dest/ > /dev/null echo "dest/testfile size after rsync --sparse:" du -h dest/testfile du -b dest/testfile rm -f dest/testfile echo "dest/testfile size after rsync:" rsync -av src/ dest/ > /dev/null du -h dest/testfile du -b dest/testfile There is a bug in rsync or in du or something else? Thanks in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] External HD partitioning & formatting considerations
On 30/11/19 21:50, John Pierce wrote: I strongly dislike moving removable disks between computers, especially with differing operating systems. I would instead recommend getting/building a NAS aka file server and using the network to share files, or make backups, or whatever. On Sat, Nov 30, 2019 at 11:38 AM Pierre Emerald wrote: +1 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 and NetworkManager problem
Il 20/11/19 14:46, Chris Adams ha scritto: Once upon a time, Alessandro Baggi said: 3) I noticed that with NetworkManager a bridge must have an address. If I don't specify an address for the bridge, NM will try to assign some address, enable the connection forever (reporting errors in messages and on notification bar). Do you have the device configured to not configure IP? From the CLI, do "nmcli con mod ipv4.method disabled ipv6.method ignore". I have only configured br1 to have a manual method for ipv4.address. This is different from having method disabled? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 and NetworkManager problem
Il 20/11/19 14:44, Chris Adams ha scritto: Once upon a time, Alessandro Baggi said: Really I don't know, I can say that they have an entry in fstab and I have several mnt-share.mount unit as generated. Are the fstab entries marked "_netdev"? No ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 and NetworkManager problem
Il 20/11/19 12:29, Kenneth Porter ha scritto: --On Wednesday, November 20, 2019 10:37 AM +0100 Alessandro Baggi wrote: 2) Due to the problem 1, It cannot mount samba shares on boot saying "Not suitable address found". After the network is available I can mount samba shares. Are the shares mounted as systemd mount or automount units that wait for networking? <https://www.freedesktop.org/software/systemd/man/systemd.automount.html> Really I don't know, I can say that they have an entry in fstab and I have several mnt-share.mount unit as generated. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] C8 and NetworkManager problem
Hi list, I've installed C8 on my workstation. I configured my network devices (two bridges, two nics) using nmcli. Now that NM is the default I tried it. On C7 I always disabled it. I noticed some problem: 1) During the boot, also if NetworkManager-wait-online.service status is OK, I noticed that opening a terminal and ping some address it needs some time to perform ping and any operation on a network connection. So seems that in the first 30sec/1min there isn't an available network connection. After this time if I run a ping or whatever network is available. 2) Due to the problem 1, It cannot mount samba shares on boot saying "Not suitable address found". After the network is available I can mount samba shares. 3) I noticed that with NetworkManager a bridge must have an address. If I don't specify an address for the bridge, NM will try to assign some address, enable the connection forever (reporting errors in messages and on notification bar). 4) NetworkManager-wait-online slow down boot time and network availability. To solve this problem I installed network-scripts and disabled NetworkManager but I don't understand why NetworkManager need so much time to enable a connection. Can someone point me in the right direction? Thanks in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 Questions
On 16/11/19 04:52, Steffan Cline wrote: I have all my issues posted on the forum - https://centos.org/forums/viewtopic.php?f=54=71934 I'm using Xen and it seems to be an issue with pvgrub and grub2. No matter what I do, it always boots into the grubdom> prompt. I made the changes suggested in the thread but can't get past that. HVM is fine but slow. PV just won't work. Thank you, Steffan Cline stef...@hldns.com 602-793-0014 On 11/15/19, 1:48 PM, "CentOS on behalf of Alessandro Baggi" wrote: Hi Steffan, I run my VMs on c7 using qemu-kvm + libvirt + virt-manager and the same on a slackware 14.2 without any problem. What error/problem do you receive? Il Ven 15 Nov 2019, 19:01 Steffan Cline ha scritto: > I'm really curious how you were able to virtualize CentOS 8. > > What platform are you using? Xen, KVM or VMWare? PV or HVM? > > I started a thread here and was referred to a project page for > development. There was a thread on the forums for this which I replied to > but it's been dead too so when I saw your opening sentence I'm really > interested in, how'd you do it? > > > Thank you, > Steffan Cline > stef...@hldns.com > 602-793-0014 > > > On 11/15/19, 9:12 AM, "CentOS on behalf of Alessandro Baggi" < > centos-boun...@centos.org on behalf of alessandro.ba...@gmail.com> wrote: > > Hi all, > I've several questions about C8. I'm using 8 on my personal NAS and > works very well. I'm running several VMs with centos 8 and noticed > something: > > 1) Why corosync, pacemaker and pcs are missing on C8? They are only > available on rhel with payments( rhel ha addons)? > 2) Why there is only Gnome as available DE? I use centos on my > workstation and I'm a kde-plasma user. XFCE is ok but not gnome. I > tried > fedora, it has all software that I need and it is a very good distro > but > I don't like too much update and its EOL (upgrade/reinstall every 13 > months on a workstation is not so good for me). I don't want to be > forced to install another stable distro like debian (This not means > that > debian is bad but I prefer centos). > 3) I have a VM with C8 installed. I got several updates but I don't > receive any update for 8 on centos-announce like for previous versions > (6 & 7). Something has changed? > 4) EPEL. I know that EPEL is a Fedora SIG but I use several packages > from EPEL. There is a place to see what packages will be included in > EPEL? For example, I tried to install audacious from epel but got > errors > for missing deps. Seems that EPEL8 is released but not ready. There is > a > ETA for this? > 5) It's my impression or there are less packages in this release? > 6) Why cockpit installed by default? > 7) Why repo PowerTools was created? What is the main purpose? > 8) Why NetworkManager is the default method to configure interfaces? I > know that I can install network-scripts but I don't understand this > change. > > > > Best regards, Alessandro. > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > > > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos I'm sorry but I can't help you. I have not any experiences with XEN. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 Questions
So for HA tool a SIG is needed? Il Ven 15 Nov 2019, 18:14 Valeri Galtsev ha scritto: > > > On 2019-11-15 10:52, Stephen John Smoogen wrote: > > On Fri, 15 Nov 2019 at 11:12, Alessandro Baggi > > wrote: > >> > >> Hi all, > >> I've several questions about C8. I'm using 8 on my personal NAS and > >> works very well. I'm running several VMs with centos 8 and noticed > >> something: > >> > > > > OK most of these questions are going to be answered by the fact that > > CentOS is a rebuild of Red Hat Enterprise Linux. If Red Hat Enterprise > > Linux does not have something in it's base packages, it isn't going to > > be in the CentOS package set. > > > >> 1) Why corosync, pacemaker and pcs are missing on C8? They are only > >> available on rhel with payments( rhel ha addons)? > > RedHat was diligent in following License Requirements. For the most part > the software they use is GNU licensed, and GNU requires: > > 1. all code derived from original be also GNU licensed, > 2. and as such, whatever [GNU licensed] is provided to customer, should > be published and available for everybody. > > The above prompted me to check what is the license for corosync. It > turns out to be BSD license. The last does not subject everyone to the > requirement of publishing [derived if any[] source code, and RedHat does > not publish srpms (as Alessandro mentioned), and there is no violation > of License on RedHat side. > > I just satisfied my curiosity, I hope, this helps others. > > Valeri > > > > > Because Red Hat put them in a package set which is not shipped as > > source to CentOS to rebuild. > > > >> 2) Why there is only Gnome as available DE? I use centos on my > >> workstation and I'm a kde-plasma user. XFCE is ok but not gnome. I tried > >> fedora, it has all software that I need and it is a very good distro but > >> I don't like too much update and its EOL (upgrade/reinstall every 13 > >> months on a workstation is not so good for me). I don't want to be > >> forced to install another stable distro like debian (This not means that > >> debian is bad but I prefer centos). > > > > Because Red Hat only did a build of GNOME for RHEL-8. > > > >> 3) I have a VM with C8 installed. I got several updates but I don't > >> receive any update for 8 on centos-announce like for previous versions > >> (6 & 7). Something has changed? > > > > The way modules and other layout changes come with RHEL-8, the old > > tools which are used for announcing updates do not work. Please see > > other threads on this for the request for help on this. > > > > > >> 4) EPEL. I know that EPEL is a Fedora SIG but I use several packages > >> from EPEL. There is a place to see what packages will be included in > >> EPEL? For example, I tried to install audacious from epel but got errors > >> for missing deps. Seems that EPEL8 is released but not ready. There is a > >> ETA for this? > > > > EPEL is a volunteer project and there is no ETA because it is up to > > the volunteers time and effort to build things. > > > >> 5) It's my impression or there are less packages in this release? > > > > You are probably looking for packages in PowerTools. Please enable > > this as this will also fix your audacious problem. > > > >> 6) Why cockpit installed by default? > > > > Because RHEL shipped with it that way. > > > >> 7) Why repo PowerTools was created? What is the main purpose? > > > > PowerTools is a set of packages which Red Hat ships as > > CodeReadyBuilder channel fo RHEL-8. It contains packages which are not > > part of the main distribution and would not have 'technical support'. > > [AKA if lynx were shipped in RHEL appstream it would have certain > > support levels for security and application fixes... it has few of > > those in Code Ready Builder.] For CentOS it is meant to communicate > > that CentOS is a rebuild of RHEL and certain problems may not get > > upstream fixes. > > > >> 8) Why NetworkManager is the default method to configure interfaces? I > >> know that I can install network-scripts but I don't understand this > change. > > > > Because RHEL shipped that way. > > > >> > >> > >> > >> Best regards, Alessandro. > >> > >> ___ > >> CentOS mailing list > >> CentOS@centos.org > >> https://lists.centos.org/mailman/listinfo/centos > > > > > > > > -- > > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C8 Questions
Hi Steffan, I run my VMs on c7 using qemu-kvm + libvirt + virt-manager and the same on a slackware 14.2 without any problem. What error/problem do you receive? Il Ven 15 Nov 2019, 19:01 Steffan Cline ha scritto: > I'm really curious how you were able to virtualize CentOS 8. > > What platform are you using? Xen, KVM or VMWare? PV or HVM? > > I started a thread here and was referred to a project page for > development. There was a thread on the forums for this which I replied to > but it's been dead too so when I saw your opening sentence I'm really > interested in, how'd you do it? > > > Thank you, > Steffan Cline > stef...@hldns.com > 602-793-0014 > > > On 11/15/19, 9:12 AM, "CentOS on behalf of Alessandro Baggi" < > centos-boun...@centos.org on behalf of alessandro.ba...@gmail.com> wrote: > > Hi all, > I've several questions about C8. I'm using 8 on my personal NAS and > works very well. I'm running several VMs with centos 8 and noticed > something: > > 1) Why corosync, pacemaker and pcs are missing on C8? They are only > available on rhel with payments( rhel ha addons)? > 2) Why there is only Gnome as available DE? I use centos on my > workstation and I'm a kde-plasma user. XFCE is ok but not gnome. I > tried > fedora, it has all software that I need and it is a very good distro > but > I don't like too much update and its EOL (upgrade/reinstall every 13 > months on a workstation is not so good for me). I don't want to be > forced to install another stable distro like debian (This not means > that > debian is bad but I prefer centos). > 3) I have a VM with C8 installed. I got several updates but I don't > receive any update for 8 on centos-announce like for previous versions > (6 & 7). Something has changed? > 4) EPEL. I know that EPEL is a Fedora SIG but I use several packages > from EPEL. There is a place to see what packages will be included in > EPEL? For example, I tried to install audacious from epel but got > errors > for missing deps. Seems that EPEL8 is released but not ready. There is > a > ETA for this? > 5) It's my impression or there are less packages in this release? > 6) Why cockpit installed by default? > 7) Why repo PowerTools was created? What is the main purpose? > 8) Why NetworkManager is the default method to configure interfaces? I > know that I can install network-scripts but I don't understand this > change. > > > > Best regards, Alessandro. > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > > > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] C8 Questions
Hi all, I've several questions about C8. I'm using 8 on my personal NAS and works very well. I'm running several VMs with centos 8 and noticed something: 1) Why corosync, pacemaker and pcs are missing on C8? They are only available on rhel with payments( rhel ha addons)? 2) Why there is only Gnome as available DE? I use centos on my workstation and I'm a kde-plasma user. XFCE is ok but not gnome. I tried fedora, it has all software that I need and it is a very good distro but I don't like too much update and its EOL (upgrade/reinstall every 13 months on a workstation is not so good for me). I don't want to be forced to install another stable distro like debian (This not means that debian is bad but I prefer centos). 3) I have a VM with C8 installed. I got several updates but I don't receive any update for 8 on centos-announce like for previous versions (6 & 7). Something has changed? 4) EPEL. I know that EPEL is a Fedora SIG but I use several packages from EPEL. There is a place to see what packages will be included in EPEL? For example, I tried to install audacious from epel but got errors for missing deps. Seems that EPEL8 is released but not ready. There is a ETA for this? 5) It's my impression or there are less packages in this release? 6) Why cockpit installed by default? 7) Why repo PowerTools was created? What is the main purpose? 8) Why NetworkManager is the default method to configure interfaces? I know that I can install network-scripts but I don't understand this change. Best regards, Alessandro. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] smart card auth
On 10/25/19 1:27 PM, Stephen Berg (Code 7309) via CentOS wrote: I updated my work desktop to kernel-3.10.0-1062.4.1.el7.x86_64 yesterday as I was leaving. This morning booted into that new kernel I was unable to login using my common access card. Rebooted in the previous kernel (3.10.0-1062.1.2.el7.x86_64) and smart card login works fine. Anyone else seeing any similar problems? I haven't had time to dig deeply into the logs yet but I did a bunch of pcscd restarts overnight, about once per hour according to monit. Hi Stephen, I never used pcscd and card login and I don't know how it works. Without any type of error/message/warning from system logs I cannot help much but I will try. I would ask: 1) You need a kernel module to use your drive? 2) If yes to the previous, this modules was compiled manually(a) or is shipped by centos(b)? 2a) if compiled manually, you need to compile it again because kernel local version is changed to -1062.1.2.el7.x86_64 so the previous module will not load (you can try to load using --force-modversion). This happens to me when I update the kernel and the module that manage my waterblock led does not work anymore. 2b) Check if you module is loaded and if not try to load it and check again. 3) Can you boot your workstation and make the login without the card reader? If yes you could check what differs from the previous and the new kernel when running pcscd (maybe using strace or similar tool). 5) What report logs? This is the first thing that I will check before try actions and before ask in ML and if I can't solve then ask help reporting errors found. Maybe someone could help you with more detailed informations. My 2 Cent(O)s. Alessandro. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 Mate?
On 17/10/19 22:24, Nicolas Kovacs wrote: I decided to switch the desktop clients to OpenSUSE Leap KDE Hi Niki, why you choosed OpenSUSE Leap and not a distro like Fedora or Debian/Ubuntu? Best regards. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] BackupPC v4 from epel
On 16/10/19 02:31, Ranbir wrote: Hello Everyone, Has anyone tried to install BackupPC v4 on CentOS 8 from epel? I just did and this happened: [root@resurrect ~]# dnf --enablerepo epel install BackupPC Last metadata expiration check: 0:18:41 ago on Tue 15 Oct 2019 08:03:59 PM EDT. Error: Problem: conflicting requests - nothing provides par2cmdline needed by BackupPC-4.3.1-2.el8.x86_64 - nothing provides perl(Net::FTP::AutoReconnect) needed by BackupPC-4.3.1-2.el8.x86_64 - nothing provides perl(Net::FTP::RetrHandle) needed by BackupPC-4.3.1-2.el8.x86_64 - nothing provides perl(Time::ParseDate) needed by BackupPC-4.3.1-2.el8.x86_64 - nothing provides perl(XML::RSS) needed by BackupPC-4.3.1-2.el8.x86_64 - nothing provides perl-Time-modules needed by BackupPC-4.3.1-2.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) If that didn't come out too nice, here's a pastebin link: https://pastebin.com/HgjAQmvV I've checked all the disabled repos on my system and none of them have those packages. Is this just a case of the dependencies not being built yet? Hi Ranbir, as you said this could be a list of deps not yet released. If your machine is a "testing machine" you can try to enable epel-testing and epel-playground and check if those deps are in those supplementary repos. Caution because they are testing repos so if you need to use on production wait releases. Hope that helps. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] qeum on centos 8 with nvme disk
On 13/10/19 20:56, Jerry Geis wrote: 6 hours are too much. First of all you need to check your nvme performace (dd can help? dd if=/dev/zero of=/test bs=1M count=1 andd see results. If you want results more benchmark oriented you could try bonnie++ as suggested by Jerry). Other this, have you got kvm module loaded and enabled cpu virtualization option in the BIOS? If yes, have you got created the VM using --accelerate? Have you tried another distro on VM? I mounted the partition under C7.7 and ran the nvme test. Pretty much came back in seconds for 10G test. dd if=/dev/zero of=test bs=1M count=1 1+0 records in 1+0 records out 1048576 bytes (10 GB) copied, 5.45451 s, 1.9 GB/s Yes kvm_intel is loaded as a module. I am using the "-hda /dev/nvme0n1" when I run qemu I'm thinking this works find for my other "img" files - but does not work for "well" for my physical NVME. What is the correct argument perhaps to use for running a physical NVME disk as a qemu guest ?? Thanks, Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi Jerry, I never used a block device as disk devices on my vms. From virt-install (I use it) man pages from --disk section: path A path to some storage media to use, existing or not. Existing media can be a file or block device. Specifying a non-existent path implies attempting to create the new storage, and will require specifying a 'size' value. Even for remote hosts, virt-install will try to use libvirt storage APIs to automatically create the given path. If the hypervisor supports it, path can also be a network URL, like http://example.com/some-disk.img . For network paths, they hypervisor will directly access the storage, nothing is downloaded locally. So you can try like: virt-install -n NAME -r mem --vcpus=N --accelerate --os-type=X --os-variant=X --disk path=/dev/nvme0n1[pN] ...and so on. It should run without problem. I added [pN] because you can use also a partition other than entire nvme0n1. I don't know if any type of option would be needed for a particular type of device like nvme. hope that helps. Alessandro. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] qeum on centos 8 with nvme disk
On 13/10/19 00:57, Jerry Geis wrote: How do you measure the slowness? Use fio or bonnie++ to share some number. By it taking more than 6 hours to "install" CentOS 8 in the guest :) Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos Hi Jerry, 6 hours are too much. First of all you need to check your nvme performace (dd can help? dd if=/dev/zero of=/test bs=1M count=1 andd see results. If you want results more benchmark oriented you could try bonnie++ as suggested by Jerry). Other this, have you got kvm module loaded and enabled cpu virtualization option in the BIOS? If yes, have you got created the VM using --accelerate? Have you tried another distro on VM? Actually I can't install C8 on my nmve drive. It powers this workstation and is still 7.7, at the moment I don't install C8 because it is unusable. Hope that helps. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Missing per-Filesys--Df in CentOS-8
On 06/10/19 19:23, Adrian van Bloois wrote:
Hi,
I'm missing perl-Filesys-Df ins CentOS-8, I need it because of Df.pm
which is in it.
Any suggestiosn?
Adrian
Hi Adrian,
To solve this you can:
1. Install using CPAN
2. Wait and EPEL release (if any)
3. Create your own rpm using F28 (if present) source from
https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/28/Everything/source/tree/
You can use also F30 repository.
A little example:
(commands are runned by simple user, not root)
$ rpmdev-setuptree
$ mkdir src && cd src
$ wget
https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/28/Everything/source/tree/Packages/p/perl-Filesys-Df-0.92-30.fc28.src.rpm
$ rpm -Uvh perl-Filesys-Df-0.92-30.fc28.src.rpm
$ cd ../rpmbuild/SPECS
$ rpmbuild -bb perl...spec
At this point rpmbuild will check BuildRequire and will print any deps
required for build (if any). Once you have solved all deps and
compilation is OK you will have your rpm in ~/rpmbuild/RPMS/{noarch/x86_64}
(from root)
# yum localinstall your.rpm
(at this point yum will try to solve required deps. If yum can't find
anything I suppose that you need to install other packages)
I know that this is very simplicistic way to do this but it's a start point.
Many user, could suggest to install f28 packages but I don't encourage this.
Hope that helps.
Alessandro.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS] C8 and KDE
Goog morning to the list, for all users that are interested about KDE Plasma on Centos 8 you can install KDE from epel. All packages are get from epel-playground and epel-testing and some packages seems need to be build. I run "yum grouplist" and see kde workspace available. I tried to install it, reboot my machine and running startx a KDE plasma session was correctly launched. I think that this is a testing release and not ready for production but if you want play you can try. Maybe you will find bug and can help EPEL to fix. Best regards. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
