• Lỗi không cài được VPSSIM trên VULTR location Japan ( Updated: Cách khắc phục)

  • Thông báo lỗi bạn gặp và mọi người giúp fix.

Thông báo lỗi bạn gặp và mọi người giúp fix.
 #2372  by uminamy
 25 Sep 2018 15:20
Em thấy nó ghi thông báo như này không biết là đã cài thành công hay chưa luôn:
Code: Select all
[root@vultr4gb1 ~]# curl https://get.vpssim.vn -o vpssim && sh vpssim
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2662  100  2662    0     0   3736      0 --:--:-- --:--:-- --:--:--  3733
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"


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/7/x86_64
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Đoạn trên nó thông báo những lỗi gì vậy thưa anh và có ảnh hưởng không?
Get 25 USD Free To USE VPSSIM
 #2374  by uminamy
 25 Sep 2018 15:54
Nhiều lỗi lắm anh ạ :( ko biết VPS của e có bị làm sao ko nữa.
Sau đó nó có chạy các bước nhưng bước nào cũng một đống thông báo lỗi.
Sau khi bấm Cài MariaDB 10.3:


error: open of glibc-2.22.90-21.el7.x86_64.rpm failed: No such file or directory
error: open of glibc-common-2.22.90-21.el7.x86_64.rpm failed: No such file or directory
error: open of glibc-devel-2.22.90-21.el7.x86_64.rpm failed: No such file or directory

Xong các bước tiếp theo vẫn rất nhiều lỗi - khi cài Nginx Mainline:

Error Summary
-------------
Disk Requirements:
At least 208MB more space needed on the / filesystem.

Error downloading packages:
MariaDB-client-10.3.9-1.el7.centos.x86_64: Insufficient space in download directory /var/cache/yum/x86_64/7/mariadb/packages
* free 39 M
* needed 53 M
MariaDB-server-10.3.9-1.el7.centos.x86_64: Insufficient space in download directory /var/cache/yum/x86_64/7/mariadb/packages
* free 39 M
* needed 123 M


Error Summary
-------------
Disk Requirements:
At least 33MB more space needed on the / filesystem.

Sau đó e chuyển qua cài Nginx Stable thì cũng hiện nhiều lỗi khác trong đó đoạn cuối có:
Restarting nginx (via systemctl): Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details.
[FAILED]
.........

gzip: GeoIP.dat.gz: No such file or directory
Redirecting to /bin/systemctl start iptables.service
Failed to start iptables.service: Unit not found.
The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, force-reload, status). For other actions, please try to use systemctl.
Failed to start php-fpm.service: Unit not found.
Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details.

Cuối cùng VPSSim vẫn thông báo cài đặt thành công nhưng e ko chắc vì trong quá trình có quá nhiều thông báo.
 #2376  by uminamy
 25 Sep 2018 15:59
VPS của em ban đầu chưa có gì cả thì em có cài Nano Editor với lệnh: yum install nano, sau đó e cũng nhân jđc một đống thông báo lỗi - như vậy là VPS của em có lỗi gì à anh?

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 retrieve metalink for repository: epel/x86_64. Please verify its path and try again

Em đang reinstall lại VPS rồi nhưng e vẫn muốn biết tình trạng như này là do đâu có phải thi thoảng các VPS mới sẽ bị vậy hay sao?
 #2377  by nguyenoanh
 25 Sep 2018 16:04
Lỗi này do kết nối của VPS tới server Centos.
Có thể do lỗi của VPS hoặc do server centos.
Nếu VPS không có kết nối internet thì cũng có thể xuất hiện lỗi tương tự

Nếu VPS không kết nối được internet thì check lệnh ping tới google.com sẽ không có kết quả.
uminamy liked this
 #2378  by uminamy
 25 Sep 2018 16:22
Em đã Reinstall lại và mọi thứ lặp lại y hệt như ban đầu. Ngay cả cài Nano editor cũng bị lỗi như cũ (em Ping Google vẫn đc). Em cài VPSSIM thì nó thông báo như này rồi ngừng ko chạy nữa:

[root@vultr4gb1 ~]# curl http://get.vpssim.vn -o vpssim && sh vpssim
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2662 100 2662 0 0 6101 0 --:--:-- --:--:-- --:--:-- 6105
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7 ... nfra=stock error was
14: HTTP Error 503 - Service Unavailable


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/7/x86_64
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7 ... nfra=stock error was
14: HTTP Error 503 - Service Unavailable


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/7/x86_64
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7 ... nfra=stock error was
14: HTTP Error 503 - Service Unavailable


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/7/x86_64
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:09 --:--:-- 0curl: (6) Could not resolve host: vpssim.vn; Unknown error
chmod: cannot access ‘/etc/vpssim/.tmp/vpssim-setup’: No such file or directory

bash: /etc/vpssim/.tmp/vpssim-setup: No such file or directory
 #2381  by nguyenoanh
 25 Sep 2018 16:28
Em chờ một lúc nữa rồi cài đặt lại nhé.
Vừa mới rebuild xong, rồi cài đặt ngay nên network chưa ổn định.
Code: Select all
Could not resolve host: vpssim.vn
Nó chưa kết nối tới vpssim.vn đây này.
Get 25 USD Free To USE VPSSIM