yes , me too, that works now thanks # date dim. juin 23 19:51:34 CEST 2019
De: "Jonathan Wright" <jonat...@knownhost.com> À: "OpenVZ users" <users@openvz.org> Envoyé: Dimanche 23 Juin 2019 19:11:34 Objet: Re: [Users] OpenVZ/Virtuozzo 7 Repos Broken Yep I can confirm it's working here. On 6/23/2019 12:04 PM, jjs - mainphrame wrote: Seems to be fixed this morning - Jake On Sat, Jun 22, 2019 at 8:24 AM Jonathan Wright < [ mailto:jonat...@knownhost.com | jonat...@knownhost.com ] > wrote: BQ_BEGIN The repos are still dead. It would be great if someone from VZ could weigh in and let us know what's going on and when to expect a fix. On 6/21/19 3:43 PM, Jehan Procaccia wrote: BQ_BEGIN I confirm , I cannot yum update on mine # cat /etc/openvz-release OpenVZ release 7.0.10 (254) # uname -a Linux [ http://olbia.int-evry.fr/ | olbia.int-evry.fr ] 3.10.0-957.12.2.vz7.86.2 #1 SMP Wed May 15 09:45:34 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux # yum update Modules complémentaires chargés : fastestmirror, langpacks, openvz, priorities, product-id, refresh-packagekit, rhsm-auto-add-pools, : search-disabled-repos, vzlinux Loading mirror speeds from cached hostfile One of the configured repositories failed (Inconnu), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: virtuozzolinux-base # yum repolist Modules complémentaires chargés : fastestmirror, langpacks, openvz, priorities, product-id, refresh-packagekit, rhsm-auto-add-pools, : search-disabled-repos, vzlinux Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile id du dépôt nom du dépôt statut openvz-os OpenVZ 0 openvz-updates OpenVZ Updates 0 virtuozzolinux-base VirtuozzoLinux Base 0 virtuozzolinux-updates VirtuozzoLinux Updates 0 repolist: 0 Le 21/06/2019 à 20:07, jjs - mainphrame a écrit : BQ_BEGIN Seeing the same here. I suspect it may be related to the package signing issue I saw yesterday. I suspect it will be cleared up before too long. Jake On Fri, Jun 21, 2019 at 9:22 AM Jonathan Wright < [ mailto:jonat...@knownhost.com | jonat...@knownhost.com ] > wrote: BQ_BEGIN Something has broken the vz7 repos: # yum upgrade Loaded plugins: fastestmirror, langpacks, openvz, priorities, vzlinux Determining fastest mirrors * openvz-os: [ http://mirrors.evowise.com/ | mirrors.evowise.com ] * openvz-updates: [ http://mirrors.evowise.com/ | mirrors.evowise.com ] openvz-os | 3.9 kB 00:00:00 openvz-updates | 3.1 kB 00:00:00 virtuozzolinux-base | 785 B 00:00:00 virtuozzolinux-updates | 2.9 kB 00:00:00 (1/4): virtuozzolinux-updates/primary_db | 1.1 kB 00:00:00 (2/4): openvz-os/group_gz | 18 kB 00:00:00 (3/4): openvz-updates/primary_db | 882 kB 00:00:00 (4/4): openvz-os/primary_db | 987 kB 00:00:00 Error: requested datatype primary not available Seeing this across all of my ovz/vz7 servers. -- Jonathan Wright KnownHost, LLC [ https://www.knownhost.com/ | https://www.knownhost.com ] _______________________________________________ Users mailing list [ mailto:Users@openvz.org | Users@openvz.org ] [ https://lists.openvz.org/mailman/listinfo/users | https://lists.openvz.org/mailman/listinfo/users ] _______________________________________________ Users mailing list [ mailto:Users@openvz.org | Users@openvz.org ] [ https://lists.openvz.org/mailman/listinfo/users | https://lists.openvz.org/mailman/listinfo/users ] BQ_END _______________________________________________ Users mailing list [ mailto:Users@openvz.org | Users@openvz.org ] [ https://lists.openvz.org/mailman/listinfo/users | https://lists.openvz.org/mailman/listinfo/users ] BQ_END -- Jonathan Wright KnownHost, LLC [ https://www.knownhost.com/ | https://www.knownhost.com ] _______________________________________________ Users mailing list [ mailto:Users@openvz.org | Users@openvz.org ] [ https://lists.openvz.org/mailman/listinfo/users | https://lists.openvz.org/mailman/listinfo/users ] BQ_END _______________________________________________ Users mailing list [ mailto:Users@openvz.org | Users@openvz.org ] [ https://lists.openvz.org/mailman/listinfo/users | https://lists.openvz.org/mailman/listinfo/users ] BQ_END _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
