[CentOS] Centos7 update: epel no route to host
Hello All, I' have a laptop who's not booting to graphical screen today. Actualy I had several the last few days, related to cr repo. This one won't update, EM: updates | 3.4 kB 00:00:00 epel/x86_64/updateinfo FAILED https://mirror.ynet.sk/epel/7/x86_64/repodata/3ada5bcbccaa9772074a773b15bd01dd48e753a184ebecfed590de6c389ada03-updateinfo.xml.bz2: [Errno 14] curl#7 - "Failed connect to mirror.ynet.sk:443; No route to host" I reinstalled epel-release package, same issue remains. I guess I could update without epel, but maybe this will make things worse. Any advise would be appreciated. Greetings, J ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [Marketing Mail] Centos7 update: epel no route to host
Hi, there seem to be some problems with the epel. I'm not sure if your problem (have the same on my systems) relate to this, however see epel- devel Mailinglist [1] for more information on current epel problems. Best regards Markus [1] https://lists.fedoraproject.org/archives/list/epel-de...@lists.fedo raproject.org/thread/WC7T2SOTX2LDC2X3FKSBLZQR3LB2PUDP/ On Fri, 2018-05-11 at 12:35 +0200, johan.vermeul...@telenet.be wrote: > Hello All, > > I' have a laptop who's not booting to graphical screen today. > Actualy I had several the last few days, related to cr repo. > > This one won't update, EM: > > updates | 3.4 kB 00:00:00 > epel/x86_64/updateinfo FAILED > https://mirror.ynet.sk/epel/7/x86_64/repodata/3ada5bcbccaa9772074a773 > b15bd01dd48e753a184ebecfed590de6c389ada03-updateinfo.xml.bz2: [Errno > 14] curl#7 - "Failed connect to mirror.ynet.sk:443; No route to > host" > > I reinstalled epel-release package, same issue remains. > > I guess I could update without epel, but maybe this will make things > worse. > > Any advise would be appreciated. > > Greetings, J > ___ > 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] Yum-cron
Ok, I've just had issues this morning, and went and *looked*. I can see a yum-cron running monthly, sure. Running weekly, I guess. Running daily? Why? And there is *NO* reason whatever for a "yum-hourly*. None. This is CentOS, not ubuntu-snapshot-of-the-moment. I don't know if this is from upstream or not, but it's wrong. I mean, even Redmond only pushes out patches once or twice a month, except for critical fixes.,,,. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Yum-cron
On Fri, May 11, 2018 at 10:36 AM, wrote: > > And there is *NO* reason whatever for a "yum-hourly*. None. This is > CentOS, not ubuntu-snapshot-of-the-moment. > > I don't know if this is from upstream or not, but it's wrong. I mean, even > Redmond only pushes out patches once or twice a month, except for critical > fixes.,,,. > Are willing to wait up to 24 hours for new security patches, or only an hour? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Yum-cron
On Fri, 11 May 2018, m.r...@5-cent.us wrote: And there is *NO* reason whatever for a "yum-hourly*. None. This is CentOS, not ubuntu-snapshot-of-the-moment. Did you have a look at what the hourly run does by default? jh ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Yum-cron
Jon Pruente wrote: > On Fri, May 11, 2018 at 10:36 AM, wrote: >> >> And there is *NO* reason whatever for a "yum-hourly*. None. This is >> CentOS, not ubuntu-snapshot-of-the-moment. >> >> I don't know if this is from upstream or not, but it's wrong. I mean, >> even Redmond only pushes out patches once or twice a month, except for >> critical fixes.,,,. > > Are willing to wait up to 24 hours for new security patches, or only an > hour? In a work environment? Or production? No way is there going to be an instant update. In most cases, you need to test whether that update is going to break things, and that will get you a ton more grief from users and management. Even if it's rated "critical", it needs to be tested one predetermined systems before rolling it out to everyone. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Yum-cron
On Fri, 11 May 2018, m.r...@5-cent.us wrote: In a work environment? Or production? No way is there going to be an instant update. In most cases, you need to test whether that update is going to break things, and that will get you a ton more grief from users and management. Even if it's rated "critical", it needs to be tested one predetermined systems before rolling it out to everyone. But you might be pointing at yum repos where you've only pushed tested updates. jh ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Yum-cron
John Hodrien wrote: > On Fri, 11 May 2018, m.r...@5-cent.us wrote: > >> And there is *NO* reason whatever for a "yum-hourly*. None. This is >> CentOS, not ubuntu-snapshot-of-the-moment. > > Did you have a look at what the hourly run does by default? > Ok, I just did, and I see in the configuration file for yum-cron-hourly that it won't do anything by default, so my aggro level is subsiding. Still, I literally do not see any need whatever for an hourly check. As I noted, this isn't ubuntu current (as opposed to LTS) mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Yum-cron
On 11 May 2018 at 11:36, wrote: > Ok, I've just had issues this morning, and went and *looked*. I can see a > yum-cron running monthly, sure. Running weekly, I guess. Running daily? > Why? > > And there is *NO* reason whatever for a "yum-hourly*. None. This is > CentOS, not ubuntu-snapshot-of-the-moment. > > I don't know if this is from upstream or not, but it's wrong. I mean, even > Redmond only pushes out patches once or twice a month, except for critical > fixes.,,,. > So first off I am not seeing this installed by default on my EL-7 systems so something/someone installed yum-cron . Now if someone has installed this package, they also have to have edited the configuration file /etc/yum/yum-cron.conf # Whether updates should be applied when they are available. Note # that download_updates must also be yes for the update to be applied. apply_updates = no If that is not set to no.. someone has changed it from the defaults. In that case.. you need to find out who made the changes. All yum-cron is meant to do is make the cache updated to the latest so various other tools can alert a user that updates are needed. Otherwise you end up with someone keeping a box months out of date and then complaining that no one told them that they needed to update 4000 packages. If you need more control over testing before release, then you need to set up your own internal mirror which you can gate updates to. At that point you get the yum repos pointed to that mirror versus the world and you control your destiny. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1804) on x86_64 aarch64 i386 ppc64 ppc64le
On 05/10/2018 09:10 AM, Warren Young wrote: > On May 10, 2018, at 1:33 AM, Karanbir Singh wrote: >> >> I am pleased to announce the general availability of CentOS Linux 7 >> (1804) for across all architectures. > > I’ve checked about a dozen of the mirrors, and see no *.torrent files yet. > Any idea how long they’ll take to appear? I ask because we’re building a > system today, so if it’s going to be more than a few hours, I’ll grab the ISO > file directly, but otherwise, I’d prefer to spread the load. > OK .. the torrent files are on mirror.centos.org and the torrent server has seeds, so the torrents can now be downloaded. Special thanks for the torrents go to Anssi Johansson (avji on freenode/IRC), who also manages our external mirror database and the ipv6 mirrorlist server. Anssi is always key to us getting out release as a valued member of the QA team .. but for this release he was even more so. While thanking people .. The entire QA team help tremendously (as always) .. Specifically very helpful were these non CentOS core team members: Akemi Yagi Anssi Johansson Manuel Wolfshant Pablo Greco John Dennison Trevor Hemsley Christoph Galuschka James O'Connor And keeping the Community Build System going: Thomas Oulevey And someone who always helps me figure out all the build issues: Tuomo Soini (Foobar Linux team) And the rest of the CentOS Core team: Karanbir Singh Jim Perrin Fabian Arrotin Brian Stinson There is no way would could have got this release out the door without each of these people. (Obviously, if I forgot anyone, feel free to slap me next time you seem me :D ) Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] OT: hardware: sanitizing a dead SSD?
On Thu, May 10, 2018 12:00, m.r...@5-cent.us wrote: > > > On the other hand... static, and unchanging, right, and how many > minutes of Amazon S3 will it take to break the encryption? None. If it is NSA certified there will be a backdoor. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1804) on x86_64 aarch64 i386 ppc64 ppc64le
On 05/11/2018 12:08 PM, Johnny Hughes wrote: > On 05/10/2018 09:10 AM, Warren Young wrote: >> On May 10, 2018, at 1:33 AM, Karanbir Singh wrote: > Akemi Yagi > Anssi Johansson > Manuel Wolfshant > Pablo Greco > John Dennison > Trevor Hemsley > Christoph Galuschka > James O'Connor > > And keeping the Community Build System going: > Thomas Oulevey > > And someone who always helps me figure out all the build issues: > Tuomo Soini (Foobar Linux team) > > And the rest of the CentOS Core team: > Karanbir Singh > Jim Perrin > Fabian Arrotin > Brian Stinson > > There is no way would could have got this release out the door without > each of these people. (Obviously, if I forgot anyone, feel free to slap > me next time you seem me :D ) I did forget a couple of key contributors, For backporting code for our CentOS 7 i386 kernel (which becomes harder and harder every release), I would like to specifically thank: The Springdale Linux Team Akemi Yagi Taketo Kabe Pablo Greco Also, all of the volunteers who help translate our release notes: Hajime Taira Timothy Lee Inyong Hwang Hao Lee Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Latest CentOS does not boot, Proliant ML330 G6
Hello all. I just upgraded to the latest and tried to reboot: kernel panic and dead as a brick. Luckily GRUB still works and booting the to the next option in boot menu succeeds. How can this be? This OS is assumed to be solid as a brick :) br. jarif signature.asc Description: Message signed with OpenPGP ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Latest CentOS does not boot, Proliant ML330 G6
On 11 May 2018 at 15:34, Jari Fredriksson wrote: > Hello all. > > I just upgraded to the latest and tried to reboot: kernel panic and dead as a > brick. > > Luckily GRUB still works and booting the to the next option in boot menu > succeeds. > > How can this be? This OS is assumed to be solid as a brick :) So to diagnose this problem there needs to be a lot more information supplied: CPU type Memory Additional cards? Where does it kernel panic? [Starting up network? Starting up disk drives? Video?] That can help determine what went borked. > br. jarif > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Latest CentOS does not boot, Proliant ML330 G6
On Fri, May 11, 2018 at 10:34:41PM +0300, Jari Fredriksson wrote: > I just upgraded to the latest and tried to reboot: kernel panic and > dead as a brick. > > Luckily GRUB still works and booting the to the next option in boot > menu succeeds. > > How can this be? This OS is assumed to be solid as a brick :) It's hard to diagnose if the only thing you say is that it panicked. If it's panicking because it can't find the root disk, then that's a completely different issue than it panicking when it loads a particular driver. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Latest CentOS does not boot, Proliant ML330 G6
On Fri, May 11, 2018 at 03:49:23PM -0400, Jonathan Billings wrote: > > It's hard to diagnose if the only thing you say is that it panicked. I'd loan you my magic mind reading cap but it's at the cleaners. John -- Don't mistake my kindness for weakness. I am kind to everyone, but when someone is unkind to me, weak is not what you are going to remember about me. -- Alphonse Gabriel Capone (1899-1947), American gangster pgpJzaGbFd_Jp.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Latest CentOS does not boot, Proliant ML330 G6
Jari Fredriksson wrote: > Hello all. > > I just upgraded to the latest and tried to reboot: kernel panic and dead > as a brick. > > Luckily GRUB still works and booting the to the next option in boot menu > succeeds. > > How can this be? This OS is assumed to be solid as a brick :) > Do you have any excludes in /etc/yum.conf? We had an issue about a year ago, where, in spite of exclude kernel, someone other than me ran an update, or there was some auto-update, I don't remember, and it appeared to *partly* install the kernel... and did not appear to do any post-install actions (like building the ramdisk). I reinstalled the kernel, with my usual disableexcludes=all, and the upgrade succeeded, and all was good. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos