Hi
I would need your help to upgrade my CentOS server. When running "yum update", none of the repo are found and it's trying over and over on all possible mirrors like this:
http://ftp.df.lth.se/pub/centos/7.0.140 ... repomd.xml: (28, 'Resolving timed out after 30387 milliseconds')
Trying other mirror.
I've finally found out that version 7.0.1406 is deprecated: http://mirror.zetup.net/CentOS/7.0.1406/readme
I've tried to edit CentOS-Base.repo and change the url but it's built with the variable $releasever:
#baseurl=http://mirror.centos.org/centos/$releas ... $basearch/
Question is how to edit this variable?
stuck on 7.0.1406
-
- Posts: 4
- Joined: 2014/09/17 11:05:17
stuck on 7.0.1406
Last edited by daftendireckt on 2015/04/29 08:42:46, edited 1 time in total.
-
- Posts: 10642
- Joined: 2005/08/05 15:19:54
- Location: Northern Illinois, USA
Re: stuck on 7.0.1406
You don't. It does not need to be changed, and changing it will break updates.
Is your network working?
Can you ping an external IP address?
Are you using a proxy?
Is your network working?
Can you ping an external IP address?
Are you using a proxy?
Re: stuck on 7.0.1406
You can also try yum clean all
Please post the output from rpm -q centos-release and rpm -q --qf '%{version}\n' centos-release
Please post the output from rpm -q centos-release and rpm -q --qf '%{version}\n' centos-release
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 4
- Joined: 2014/09/17 11:05:17
Re: stuck on 7.0.1406
Ok... shame on me! That was a network issue with no access to the internet
I fell into the trap as the repo address was also unreachable from my laptop but that's true that a timeout issue is different from an 404 error. Anyway, thanks for pointing me in the right direction, my server is now up to date.
I fell into the trap as the repo address was also unreachable from my laptop but that's true that a timeout issue is different from an 404 error. Anyway, thanks for pointing me in the right direction, my server is now up to date.