Re: [CentOS] what's the advantage of NetworkManager for server?
Lamar Owen > > On 6/29/20 11:20 AM, Gordon Messmer wrote: > > ... > > In the event of a power loss, many servers will boot faster than the > > managed Ethernet switch they are attached to. Systems managed by > > network-scripts may not set up their network because there is no > > carrier at the time that networks-scripts start up. > > > > Network-manager, on the other hand, will set up networking whenever > > the interface becomes ready. > > Prior to the NetworkManager intelligence, I would have to manually reset > the host in the Bladecenter after the EMC was up and after the 7609 was > up. Not any more. Nice. (Clariion can take 15-20 minutes to come all > the way back up on a hard power fail; 7609 can take 10 minutes if not > longer. Bladecenter takes 5 at most.) our switches also take long time to be up. and our servers are booting fast. I don't know what's the problem with the situation. with network-scripts, the network settings is ready early. when physical network goes up, the related service is up too. maybe your situation need dynamic logic like dhcp or some kind of timeout so can not wait for long time? our servers may have team,bridge,vlan and complex routing. with static configuration they work fine. I don't want them up/down with network cable. I want them always setup and ready. I don't know if NetworkManager can handle these correctly with dynamic logic now. in early EL7 days, I have a teamd dependency problem. with network-scrips it can be fixed immediately . but with NetworkManager it is hard to fix. I am afraid these kind of bugs. https://bugzilla.redhat.com/show_bug.cgi?id=1264175 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-docs] Documentation SIG: Participation wanted
Count me in. wolfy On June 30, 2020 9:20:55 PM GMT+03:00, Rich Bowen wrote: >Hi, folks, > >I've been working through the CentOS wiki for more than a year now, >trying to identify and fix outdated/wrong/obsolete content. It's a >daunting task, and I'm losing. > >I would very much like to gather a group of people who are: > >* Knowledgeable about CentOS >* Good with words >* Have a little time > >who would be willing and able to review the content of the wiki, and >fix >the bits that are incorrect. > >The CentOS Documentation SIG (which doesn't actually exist in any >meaningful way) is, according to the wiki: > >responsible for the content of the Wiki, and other public sources of >documentation. This includes, but is not limited to: > >* Determining, and imposing, a hierarchy/architecture of content in the >wiki >* Editing/pruning existing content when it is >incorrect/outdated/obsolete >* Recruiting subject matter experts to do some of that editing >* Recruiting translators to keep our various translations in sync > >[Ref: https://wiki.centos.org/SpecialInterestGroup/Documentation ] > >If any of the above appeals to you, I would ask you to let me know. I >would like to create a SIG around the wiki. Please let me know if >you're >interested. I know that there are a number of you who are consistently >active on this list. I would like to find a way to give us a little >more >power/authority over the wiki to make higher-level editorial decisions >about information architecture. Also, having a formal SIG might be a >way >to engage more people to join the effort and dedicate some time to it. > >___ >CentOS-docs mailing list >CentOS-docs@centos.org >https://lists.centos.org/mailman/listinfo/centos-docs ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS] what's the advantage of NetworkManager for server?
On 6/29/20 11:20 AM, Gordon Messmer wrote: ... In the event of a power loss, many servers will boot faster than the managed Ethernet switch they are attached to. Systems managed by network-scripts may not set up their network because there is no carrier at the time that networks-scripts start up. Network-manager, on the other hand, will set up networking whenever the interface becomes ready. At $dayjob we got to see the advantages of this up close and personal a few days ago when we had a hard failure in the voltage regulator/exciter loop of one of our three primary generators during a utility power failure. First failure of this kind since that datacenter was placed online in 2008, and only the second power out event since 2008. (While critical systems have dual generator backup, and all systems have UPS with a few minutes run time, the systems affected by this weren't previously classed as 'critical' enough to have dual feeds, although that might change in the next few weeks). So, we have a virtualization host in an IBM Bladecenter with iSCSI shared storage on some EMC Clariion LUNs through a Cisco 7609 switch/router with RSP720. Anyone who has ever dealt with these items in a cold boot situation probably knows how the litany goes at this point. Prior to the NetworkManager intelligence, I would have to manually reset the host in the Bladecenter after the EMC was up and after the 7609 was up. Not any more. Nice. (Clariion can take 15-20 minutes to come all the way back up on a hard power fail; 7609 can take 10 minutes if not longer. Bladecenter takes 5 at most.) ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] fdisk boot partition
On Tue, Jun 30, 2020 at 12:12 PM Jerry Geis wrote: > I am trying to use CentOS 8 host to boot an image (OS X) that I created > using dd. > > First I tried fdisk -l image_file.img ... fdisk has been deprecated for quite a long time, I think parted is the preferred command line tool now. -- -john r pierce recycling used bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] fdisk boot partition
I am trying to use CentOS 8 host to boot an image (OS X) that I created using dd. First I tried fdisk -l image_file.img - all looks good so I did fdisk image_file.img - this works - but seems in CentOS 8 fdisk there is no longer a toggle bootable flag option. How do I do that ? Thanks, Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS-docs] Documentation SIG: Participation wanted
Hi, folks, I've been working through the CentOS wiki for more than a year now, trying to identify and fix outdated/wrong/obsolete content. It's a daunting task, and I'm losing. I would very much like to gather a group of people who are: * Knowledgeable about CentOS * Good with words * Have a little time who would be willing and able to review the content of the wiki, and fix the bits that are incorrect. The CentOS Documentation SIG (which doesn't actually exist in any meaningful way) is, according to the wiki: responsible for the content of the Wiki, and other public sources of documentation. This includes, but is not limited to: * Determining, and imposing, a hierarchy/architecture of content in the wiki * Editing/pruning existing content when it is incorrect/outdated/obsolete * Recruiting subject matter experts to do some of that editing * Recruiting translators to keep our various translations in sync [Ref: https://wiki.centos.org/SpecialInterestGroup/Documentation ] If any of the above appeals to you, I would ask you to let me know. I would like to create a SIG around the wiki. Please let me know if you're interested. I know that there are a number of you who are consistently active on this list. I would like to find a way to give us a little more power/authority over the wiki to make higher-level editorial decisions about information architecture. Also, having a formal SIG might be a way to engage more people to join the effort and dedicate some time to it. ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS] RPMFusion and NVIDIA driver problem
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
[CentOS-docs] [centos/centos.org] branch master updated (dec3e29 -> 43807c1)
This is an automated email from the git hooks/post-receive script. rbowen pushed a change to branch master in repository centos/centos.org. from dec3e29 Removed mirror .csv files and ignored through .gitignore. These files will come from other sources each time real site need to be rendered and pushed add 43807c1 Added some doc in README.md for contribution workflow No new revisions were added by this update. Summary of changes: README.md | 58 +- 1 file changed, 45 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository. ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
[CentOS] krb5 update => Database module does not match KDC version
Hi everybody As a word of caution - make sure you are prepared for some trouble when upgrading krb5 packages to version 1.18.2-2.el8. FreeIPA brakes with: ...krb5kdc[554972](Error): Database module does not match KDC version - while initializing database for realm XX.YY ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Unable to find the used space
Peter Kjellström wrote: As an addition to what others have already said. You'll also miss things "hidden under mounts". That is, if you had 5G in /var/log on the root file system and then mounted a different device on /var/log, then that 5G would still be there but invisible. What I usually do in cases like this, is to bind mount root to somewhere else - and then run 'du' or whatever using the bind mount point - this will show up any 'hidden under mounts' data - something like: mkdir /var/run/mnt mount --bind / /var/run/mnt du -sh /var/run/mnt/* James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 system running out of available memory, then unusable, network interfaces probably involved
Hello John, On Mon, 29 Jun 2020 12:54:58 -0700 John Pierce wrote: > On Mon, Jun 29, 2020 at 12:47 PM wwp wrote: > > > > > Nothing jumps to my eyes looking at /var/log/messages but this, many > > occurrences: > > kernel: nf_conntrack: falling back to vmalloc. > > > > nf_conntrack is only involved if you are doing some form of NAT routing on > this system and/or fairly complex iptables kind of rules On this machine I do not do anything at iptables or firewall level but opening ports for SSHD. > you mentioned two different network interfaces, one wired, one > wireless, how are you using these, what sort of routing between the > two networks ? The wired interface is directly bound to a 4G router (dhcp). The wireless one is connected to a LAN (wifi -> wifi AP -> wire -> switch -> wire -> router with iptables+dhcp -> wire -> xDSL box). Regards, -- wwp https://useplaintext.email/ pgp0Zr0fScsXK.pgp Description: OpenPGP digital signature ___ 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
