Hallo zusammen,
ich wollte heute EDOMI mit CentOS 7 auf meinem Intel NUK installieren.
Die Installation von CentOS7 hat ohne probleme funktioniert.
Nur bei der Installation von EDOMI_201 komme ich nicht weiter. Mit dem LAN bin ich verbunden.
Beim installieren bekomme ich immer die folgenden Fehler:
Leider weis ich jetzt nicht mehr weiter.
Kann mir jemand helfen, wie ich EDOMI wieder zum laufen bekomme.
Vorab schonmal Vielen Dank für eure Hilfe!
Liebe Grüße
Michael
ich wollte heute EDOMI mit CentOS 7 auf meinem Intel NUK installieren.
Die Installation von CentOS7 hat ohne probleme funktioniert.
Nur bei der Installation von EDOMI_201 komme ich nicht weiter. Mit dem LAN bin ich verbunden.
Beim installieren bekomme ich immer die folgenden Fehler:
Leider weis ich jetzt nicht mehr weiter.
Kann mir jemand helfen, wie ich EDOMI wieder zum laufen bekomme.
Vorab schonmal Vielen Dank für eure Hilfe!
Liebe Grüße
Michael
>>> EDOMI und Systemdienste für CentOS 7 installieren...
>>> Firewall deaktivieren
>>> Packete installieren
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Konnte nicht geöffnet werden: https://dl.fedoraproject.org/pub/epe...t-7.noarch.rpm. Wird übersprungen.
Fehler: Nichts zu tun
Geladene Plugins: fastestmirror
remi-release-7.rpm | 28 kB 00:00:00
/var/tmp/yum-root-qXCRR2/remi-release-7.rpm wird untersucht: remi-release-7.9-6.el7.remi.noarch
/var/tmp/yum-root-qXCRR2/remi-release-7.rpm wird zum Installieren markiert
Abhängigkeiten werden aufgelöst
--> Transaktionsprüfung wird ausgeführt
---> Paket remi-release.noarch 0:7.9-6.el7.remi markiert, um installiert zu werden
--> Abhängigkeit epel-release = 7 wird für Paket remi-release-7.9-6.el7.remi.noarch verarbeitet
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
install.sh: Zeile 180: yum-config-manager: Kommando nicht gefunden.
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
>>> Dienste konfigurieren
Failed to execute operation: No such file or directory
Failed to execute operation: No such file or directory
Failed to execute operation: No such file or directory
Failed to execute operation: No such file or directory
>>> SELinux deaktivieren
>>> FTP konfigurieren
sed: kann /etc/vsftpd/vsftpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/vsftpd/vsftpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/vsftpd/vsftpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
>>> Apache konfigurieren
sed: kann /etc/httpd/conf/httpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/httpd/conf/httpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/httpd/conf/httpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/httpd/conf/httpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
>>> mySQL/MariaDB konfigurieren
Failed to start mariadb.service: Unit not found.
install.sh: Zeile 215: /usr/bin/mysqladmin: Datei oder Verzeichnis nicht gefunden
install.sh: Zeile 216: mysql: Kommando nicht gefunden.
install.sh: Zeile 217: mysql: Kommando nicht gefunden.
install.sh: Zeile 218: mysql: Kommando nicht gefunden.
install.sh: Zeile 219: mysql: Kommando nicht gefunden.
sed: kann /usr/lib/systemd/system/mariadb.service nicht lesen: Datei oder Verzeichnis nicht gefunden
ln: die symbolische Verknüpfung „/etc/systemd/system/mysqld.service“ konnte nicht angelegt werden: Die Datei existiert bereits
>>> PHP konfigurieren
sed: kann /etc/php.ini nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/php.ini nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/php.ini nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/php.ini nicht lesen: Datei oder Verzeichnis nicht gefunden
>>> Bootvorgang konfigurieren
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.10.0-957.el7.x86_64
Found initrd image: /boot/initramfs-3.10.0-957.el7.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-7413c115a2f546a5a99c64f250926a2d
Found initrd image: /boot/initramfs-0-rescue-7413c115a2f546a5a99c64f250926a2d.img
done
>>> EDOMI installieren
Redirecting to /bin/systemctl stop mysqld.service
Failed to stop mysqld.service: Unit mysqld.service not loaded.
tar: edomi.edomiinstall: Kann open nicht ausführen: Datei oder Verzeichnis nicht gefunden
tar: Error is not recoverable: exiting now
>>> Firewall deaktivieren
>>> Packete installieren
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Konnte nicht geöffnet werden: https://dl.fedoraproject.org/pub/epe...t-7.noarch.rpm. Wird übersprungen.
Fehler: Nichts zu tun
Geladene Plugins: fastestmirror
remi-release-7.rpm | 28 kB 00:00:00
/var/tmp/yum-root-qXCRR2/remi-release-7.rpm wird untersucht: remi-release-7.9-6.el7.remi.noarch
/var/tmp/yum-root-qXCRR2/remi-release-7.rpm wird zum Installieren markiert
Abhängigkeiten werden aufgelöst
--> Transaktionsprüfung wird ausgeführt
---> Paket remi-release.noarch 0:7.9-6.el7.remi markiert, um installiert zu werden
--> Abhängigkeit epel-release = 7 wird für Paket remi-release-7.9-6.el7.remi.noarch verarbeitet
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
install.sh: Zeile 180: yum-config-manager: Kommando nicht gefunden.
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
Geladene Plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?releas...os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unbekannter Fehler"
One of the configured repositories failed (Unbekannt),
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/7/x86_64
>>> Dienste konfigurieren
Failed to execute operation: No such file or directory
Failed to execute operation: No such file or directory
Failed to execute operation: No such file or directory
Failed to execute operation: No such file or directory
>>> SELinux deaktivieren
>>> FTP konfigurieren
sed: kann /etc/vsftpd/vsftpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/vsftpd/vsftpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/vsftpd/vsftpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
>>> Apache konfigurieren
sed: kann /etc/httpd/conf/httpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/httpd/conf/httpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/httpd/conf/httpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/httpd/conf/httpd.conf nicht lesen: Datei oder Verzeichnis nicht gefunden
>>> mySQL/MariaDB konfigurieren
Failed to start mariadb.service: Unit not found.
install.sh: Zeile 215: /usr/bin/mysqladmin: Datei oder Verzeichnis nicht gefunden
install.sh: Zeile 216: mysql: Kommando nicht gefunden.
install.sh: Zeile 217: mysql: Kommando nicht gefunden.
install.sh: Zeile 218: mysql: Kommando nicht gefunden.
install.sh: Zeile 219: mysql: Kommando nicht gefunden.
sed: kann /usr/lib/systemd/system/mariadb.service nicht lesen: Datei oder Verzeichnis nicht gefunden
ln: die symbolische Verknüpfung „/etc/systemd/system/mysqld.service“ konnte nicht angelegt werden: Die Datei existiert bereits
>>> PHP konfigurieren
sed: kann /etc/php.ini nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/php.ini nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/php.ini nicht lesen: Datei oder Verzeichnis nicht gefunden
sed: kann /etc/php.ini nicht lesen: Datei oder Verzeichnis nicht gefunden
>>> Bootvorgang konfigurieren
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.10.0-957.el7.x86_64
Found initrd image: /boot/initramfs-3.10.0-957.el7.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-7413c115a2f546a5a99c64f250926a2d
Found initrd image: /boot/initramfs-0-rescue-7413c115a2f546a5a99c64f250926a2d.img
done
>>> EDOMI installieren
Redirecting to /bin/systemctl stop mysqld.service
Failed to stop mysqld.service: Unit mysqld.service not loaded.
tar: edomi.edomiinstall: Kann open nicht ausführen: Datei oder Verzeichnis nicht gefunden
tar: Error is not recoverable: exiting now
Kommentar