Unter Berücksichtigung deines Kenntnisstandes und im Interesse deiner Webshopkunden kann man eigentlich nur zu Folgendem raten:
- Beiß in den sauren Apfel, mach ein paar Euro locker und hol dir einen professionellen Admin an die Seite, der deine Daten sichert.
- Ziehe deinen Webshop auf einen vernünftigen Webspace oder auf einen managed Server (wenn es denn unbedingt ein eigener Server sein muß) um.
Ja die paar Euro mach ich gerne locker das alles wieder klappt.
Aber wo finde ich den Profi Admin ?
Nun habe ich es geschafft das mit dem Key zu klären bekomme aber jetzt das :-(
One of the configured repositories failed (Unknown),
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: base/$releasever/x86_64
