Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

dnf cannot reconstruct rpm from disk files

i tryed to run updates this evning but for some reason a error happend in a important security package

 selinux-policy-3.14.1-37.fc28.noarch.rpm: Already downloaded         
/var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 1148 bytes from offset 8275012)
cannot reconstruct rpm from disk files
Some packages were not downloaded. Retrying.

The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'

im not certain but i think selinux policy was updated this morning so i decided to turn off the wifi adapter to get a look at where dnf was downloading from (mirrors.fedoraproject.org) then i ran traceroute

[root@localhost ~]# traceroute mirrors.fedoraproject.org
traceroute to mirrors.fedoraproject.org (140.211.169.206), 30 hops max, 60 byte packets
 1  _gateway (192.168.0.1)  3.507 ms  7.353 ms  7.225 ms
 2  50.66.**.** (50.66.**.**)  10.940 ms  24.553 ms  38.069 ms
 3  rc3no-be112-1.cg.shawcable.net (64.59.131.101)  39.733 ms  39.955 ms  40.458 ms
 4  rc2wt-be100.wa.shawcable.net (66.163.75.233)  42.020 ms  41.102 ms  41.097 ms
 5  rc1wt-be18-1.wa.shawcable.net (66.163.64.81)  44.205 ms  43.286 ms  54.521 ms
 6  six.tr-cps.internet2.edu (206.81.80.77)  55.078 ms  214.055 ms  38.143 ms
 7  lo-0.8.rtsw.port.net.internet2.edu (64.57.20.224)  40.512 ms  39.677 ms  40.794 ms
 8  198.32.165.198 (198.32.165.198)  42.076 ms  43.320 ms  42.703 ms
 9  ptck-p1-gw.nero.net (207.98.64.168)  44.346 ms  47.684 ms ptck-p2-gw.nero.net (207.98.64.170)  45.967 ms
10  corv-p1-gw.nero.net (207.98.64.25)  49.117 ms  50.670 ms corv-p2-gw.nero.net (207.98.64.27)  47.030 ms
11  corv-car1-gw.nero.net (207.98.64.19)  49.869 ms corv-car1-gw.nero.net (207.98.64.17)  38.505 ms  39.210 ms
12  proxy09.fedoraproject.org (140.211.169.206)  80.852 ms !X  80.977 ms !X  80.071 ms !X

is this the correct route for the connection? should i do something? why is selinux-policy being updated again?