Hello,
I am trying to upgrade nagiosxi from version 5.2.3 to the current version on CentOS Linux 7 (Core) but get stuck on the following error:
Error downloading packages:
php-imap-5.4.16-7.el7.x86_64: [Errno 256] No more mirrors to try.
It seems that all the known links are down for this specific package. What steps should i take in order to perform the upgrade? I know the package can still be found online, should i download and install it manually in a specific folder?
Kind regards,
upgrade fails: no more mirrors to try
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: upgrade fails: no more mirrors to try
Hi,
Ok, let's get this resolved for you. It might be a connection issue to the repository or a corrupted yum cache. Please run the following command:
and then try running the upgrade once more. If it fails again, post the whole output to the thread along with the output of the following command.
Benjamin
Ok, let's get this resolved for you. It might be a connection issue to the repository or a corrupted yum cache. Please run the following command:
Code: Select all
yum clean allCode: Select all
yum repolist -vAs of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
Bart_Decloedt
- Posts: 3
- Joined: Wed Mar 04, 2015 8:13 am
Re: upgrade fails: no more mirrors to try
Hi,
That indeed cleared that message.
Sadly enough I now get this one instead:
"Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again"
As for the entire output, since I am performing the upgrade from a ssh terminal i cannot post the entire output. I have added everything i could below, i get this both when I perform the upgrade and when i run the yum command.
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. Disable the repository, 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>
4. 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
That indeed cleared that message.
Sadly enough I now get this one instead:
"Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again"
As for the entire output, since I am performing the upgrade from a ssh terminal i cannot post the entire output. I have added everything i could below, i get this both when I perform the upgrade and when i run the yum command.
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. Disable the repository, 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>
4. 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
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: upgrade fails: no more mirrors to try
Hello @Bart_Decloedt,
If you encounter any errors, please post them to thread along with the output of yum repolist -v. Thanks.
Reference:
https://support.nagios.com/forum/viewto ... 16&t=47223
https://support.nagios.com/forum/viewto ... =6&t=53567
https://stackoverflow.com/questions/267 ... y-its-path
Trying editing the vi /etc/yum.repos.d/epel.repo configuration file and change the repo address from https to http and run the upgrade once more."Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again"
If you encounter any errors, please post them to thread along with the output of yum repolist -v. Thanks.
Reference:
https://support.nagios.com/forum/viewto ... 16&t=47223
https://support.nagios.com/forum/viewto ... =6&t=53567
https://stackoverflow.com/questions/267 ... y-its-path
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
Bart_Decloedt
- Posts: 3
- Joined: Wed Mar 04, 2015 8:13 am
Re: upgrade fails: no more mirrors to try
Hello Benjamin,
Your last recommendation did the trick so thanks for your help.
Kind Regards,
Bart
Your last recommendation did the trick so thanks for your help.
Kind Regards,
Bart
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: upgrade fails: no more mirrors to try
Great!Bart_Decloedt wrote:Hello Benjamin,
Your last recommendation did the trick so thanks for your help.
Kind Regards,
Bart
Locking thread