bryan
(Bryan Baer)
January 19, 2017, 8:54pm
1
When running freepbx 14 test environment yum update processing is fine from package1.sangoma.com until looking for these packages:
kernel-headers-3.10.0-514.6.1.el7.x86_64: [Errno 256] No more mirrors to try.
kernel-3.10.0-514.6.1.el7.x86_64: [Errno 256] No more mirrors to try.
python-perf-3.10.0-514.6.1.el7.x86_64: [Errno 256] No more mirrors to try.
Those packages are not part of the repository’s on package1, I tried the links manually. I’m guessing somewhere a dependency is broken.
FPlay
(F Play)
January 19, 2017, 9:26pm
3
Same here
[root@freepbx ~]# yum clean all
Loaded plugins: fastestmirror
Cleaning repos: sng-base sng-epel sng-extras sng-pkgs sng-updates
Cleaning up everything
Cleaning up list of fastest mirrors
[root@freepbx ~]# yum update
Loaded plugins: fastestmirror
sng-base | 3.6 kB 00:00:00
sng-epel | 4.3 kB 00:00:00
sng-extras | 3.4 kB 00:00:00
sng-pkgs | 2.9 kB 00:00:00
sng-updates | 3.4 kB 00:00:00
(1/8): sng-epel/7/x86_64/group_gz | 170 kB 00:00:00
(2/8): sng-base/7/x86_64/group_gz | 155 kB 00:00:00
(3/8): sng-pkgs/7/x86_64/primary_db | 396 kB 00:00:00
(4/8): sng-epel/7/x86_64/updateinfo | 722 kB 00:00:00
(5/8): sng-extras/7/x86_64/primary_db | 98 kB 00:00:00
(6/8): sng-updates/7/x86_64/primary_db | 2.2 MB 00:00:01
(7/8): sng-epel/7/x86_64/primary_db | 4.5 MB 00:00:01
(8/8): sng-base/7/x86_64/primary_db | 5.6 MB 00:00:02
Determining fastest mirrors
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:3.10.0-514.6.1.el7 will be installed
---> Package kernel-headers.x86_64 0:3.10.0-514.2.2.el7 will be updated
---> Package kernel-headers.x86_64 0:3.10.0-514.6.1.el7 will be an update
---> Package python-perf.x86_64 0:3.10.0-514.2.2.el7 will be updated
---> Package python-perf.x86_64 0:3.10.0-514.6.1.el7 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
========================================================================================================================================================
Package Arch Version Repository Size
========================================================================================================================================================
Installing:
kernel x86_64 3.10.0-514.6.1.el7 sng-updates 37 M
Updating:
kernel-headers x86_64 3.10.0-514.6.1.el7 sng-updates 4.8 M
python-perf x86_64 3.10.0-514.6.1.el7 sng-updates 4.0 M
Transaction Summary
========================================================================================================================================================
Install 1 Package
Upgrade 2 Packages
Total download size: 46 M
Is this ok [y/d/N]: y
Downloading packages:
sng-updates/7/x86_64/prestodelta | 275 kB 00:00:00
kernel-3.10.0-514.6.1.el7.x86_ FAILED
http://package1.sangoma.net/os/7.3/updates/x86_64/Packages/kernel-3.10.0-514.6.1.el7.x86_64.rpm: [Errno 14] HTTP Error 404 - Not Found0 B --:--:-- ETA
Trying other mirror.
To address this issue please refer to the below knowledge base article
https://access.redhat.com/articles/1320623
If above article doesn't help to resolve this issue please create a bug on https://issues.freepbx.org/
python-perf-3.10.0-514.6.1.el7 FAILED
http://package1.sangoma.net/os/7.3/updates/x86_64/Packages/python-perf-3.10.0-514.6.1.el7.x86_64.rpm: [Errno 14] HTTP Error 404 - Not Found--:--:-- ETA
Trying other mirror.
kernel-headers-3.10.0-514.6.1. FAILED
http://package1.sangoma.net/os/7.3/updates/x86_64/Packages/kernel-headers-3.10.0-514.6.1.el7.x86_64.rpm: [Errno 14] HTTP Error 404 - Not Found--:-- ETA
Trying other mirror.
Error downloading packages:
kernel-headers-3.10.0-514.6.1.el7.x86_64: [Errno 256] No more mirrors to try.
kernel-3.10.0-514.6.1.el7.x86_64: [Errno 256] No more mirrors to try.
python-perf-3.10.0-514.6.1.el7.x86_64: [Errno 256] No more mirrors to try.
tm1000
(Andrew Nagy)
January 19, 2017, 9:28pm
4
We are aware of this issue and do not have an ETA at this time.
xrobau
(Rob Thomas)
January 19, 2017, 9:37pm
5
This is an upstream issue, and there’s nothing we can do about it until those files are released. Sorry!
bryan
(Bryan Baer)
January 19, 2017, 9:43pm
6
No worries!
Just making sure it was known, didn’t see anything anywhere about it.
tm1000
(Andrew Nagy)
January 19, 2017, 10:31pm
7
This is now resolved
yum clean metadata
yum update
1 Like