View Issue Details

IDProjectCategoryView StatusLast Update
0007647Kali LinuxGeneral Bugpublic2022-03-30 18:32
Reportercredi Assigned Tosteev  
PriorityhighSeverityblockReproducibilityalways
Status resolvedResolutionno change required 
Product Version2022.1 
Summary0007647: Dutch mirror offline for several days
Description

The dutch mirror (http://ftp1.nluug.nl/os/Linux/distr/kali) has been offline for several days, making me unable to update my kali on different machines.

Steps To Reproduce

sudo apt update from The Netherlands

Activities

steev

steev

2022-03-29 20:09

manager   ~0015974

It is loading here, are you sure it's actually down?

credi

credi

2022-03-29 20:21

reporter   ~0015976

I am getting the error below at both home and at work.

Get:8 http://ftp2.nluug.nl/os/Linux/distr/kali kali-rolling/contrib amd64 Contents (deb) [155 kB]
Ign:8 http://ftp2.nluug.nl/os/Linux/distr/kali kali-rolling/contrib amd64 Contents (deb)
Ign:4 http://http.kali.org/kali kali-rolling/main amd64 Contents (deb)
Ign:8 http://http.kali.org/kali kali-rolling/contrib amd64 Contents (deb)
Err:4 http://http.kali.org/kali kali-rolling/main amd64 Contents (deb)
File has unexpected size (41442477 != 41433921). Mirror sync in progress?

Ending with
E: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/main/Contents-amd64 File has unexpected size (41442477 != 41433921). Mirror sync in progress? [IP: 145.220.21.40 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

A colleague told me this happens when the mirror is down so I assumed that's the problem, my apologies is it's another issue.

steev

steev

2022-03-29 20:23

manager   ~0015977

Typically when the message is "Mirror sync in progress?" it means that the mirror is in the middle of syncing, and not down. It could be that you are attempting to update at the same time(s) that the mirror happens to be syncing. Are you always attempting to sync at the same times? Can you give it a couple of hours and try again?

credi

credi

2022-03-29 20:25

reporter   ~0015978

Definitely! I'll try again tomorrow. I tried it yesterday (about 30 hours ago) and today multiple times, colleague mentioned he had the same issue on Sunday.

credi

credi

2022-03-30 13:27

reporter   ~0015979

Issue still ongoing, same message, different network, instance and time than yesterday.

credi

credi

2022-03-30 18:26

reporter   ~0015981

Looks like it works again!

steev

steev

2022-03-30 18:32

manager   ~0015982

Okay, I'll close this, but we'll keep an eye on the mirror.

Issue History

Date Modified Username Field Change
2022-03-29 19:55 credi New Issue
2022-03-29 20:09 steev Note Added: 0015974
2022-03-29 20:21 credi Note Added: 0015976
2022-03-29 20:23 steev Note Added: 0015977
2022-03-29 20:25 credi Note Added: 0015978
2022-03-30 13:27 credi Note Added: 0015979
2022-03-30 18:26 credi Note Added: 0015981
2022-03-30 18:32 steev Assigned To => steev
2022-03-30 18:32 steev Status new => resolved
2022-03-30 18:32 steev Resolution open => no change required
2022-03-30 18:32 steev Note Added: 0015982