tickets #55205
closedrepopush to ftp.uni-stuttgart.de - No mirror to scan. Exiting.
100%
Description
When we push repositories to Uni Stuttgart, the subsequent mirror scan always returns with "to No mirror to scan. Exiting.".
For instance:
mb -b mirrordb1 scan ftp.uni-stuttgart.de -d repositories/network:/osmocom:/latest/Debian_10
This is easily seen in the logs: /srv/bs/logs/2019/mm/dd - as far back as 2016.
It looks like there is no repositories/ at ftp.uni-stuttgart.de - the rsync is assuccessful, but somehow nbot published.
Probably need to talk to the ftpadmin:
# mb show ftp.uni-stuttgart.de
identifier : ftp.uni-stuttgart.de
operatorName : Universität Stuttgart
operatorUrl : http://www.uni-stuttgart.de/
baseurl : http://ftp.uni-stuttgart.de/opensuse/
baseurlFtp : ftp://ftp.uni-stuttgart.de/opensuse/
baseurlRsync : rsync://ftp.uni-stuttgart.de/opensuse/
region : eu
country : de
asn : 553
prefix : 129.69.0.0/16
lat,lng : 48.767,9.183
regionOnly : False
countryOnly : False
asOnly : True
prefixOnly : False
ipv6Only : False
otherCountries :
fileMaxsize : 0
publicNotes :
score : 100
enabled : True
statusBaseurl : True
admin : Lorenz Adena
adminEmail : adena@rus.uni-stuttgart.de
Updated by pjessen about 4 years ago
- Status changed from New to In Progress
- Assignee set to pjessen
- Priority changed from Low to Normal
The repo push seems to be working just fine, but the content is not available under repositories as we expect:
mb -b mirrordb1 scan ftp.uni-stuttgart.de-buildservice -d repositories/security:/logging/openSUSE_Leap_15.1
Checking for existance of 'repositories/security:/logging/openSUSE_Leap_15.1' directory
.
No mirror to scan. Exiting.
==== end scan ===== RC=0 ============ 20200209-094646
A manual scan without "repositories/" :
# mb -b mirrordb1 scan ftp.uni-stuttgart.de-buildservice -d security:/logging/openSUSE_Leap_15.1
Checking for existance of 'security:/logging/openSUSE_Leap_15.1' directory
.
Scheduling scan on:
ftp.uni-stuttgart.de-buildservice
Completed in 0 seconds
Sun Feb 9 09:49:24 2020 ftp.uni-stuttgart.de-buildservice: starting
Sun Feb 9 09:49:26 2020 ftp.uni-stuttgart.de-buildservice: files in 'security:/logging/openSUSE_Leap_15.1' before scan: 0
Sun Feb 9 09:49:26 2020 ftp.uni-stuttgart.de-buildservice: scanned 176 files (569/s) in 0s
Sun Feb 9 09:49:26 2020 ftp.uni-stuttgart.de-buildservice: files to be purged: 0
Sun Feb 9 09:49:26 2020 ftp.uni-stuttgart.de-buildservice: total files in 'security:/logging/openSUSE_Leap_15.1' after scan: 176 (delta: 176)
Sun Feb 9 09:49:26 2020 ftp.uni-stuttgart.de-buildservice: purged old files in 0s.
Sun Feb 9 09:49:26 2020 ftp.uni-stuttgart.de-buildservice: done.
Completed in 2 seconds
The mirror is also not listed on mirrors.o.o which is surely weird??
Updated by pjessen about 4 years ago
# mb scan ftp.uni-stuttgart.de
Sun Feb 9 09:52:49 2020 ftp.uni-stuttgart.de: starting
Sun Feb 9 09:52:57 2020 ftp.uni-stuttgart.de: total files before scan: 2613833
Sun Feb 9 10:25:24 2020 ftp.uni-stuttgart.de: scanned 2414632 files (1239/s) in 1947s
Sun Feb 9 10:25:44 2020 ftp.uni-stuttgart.de: files to be purged: 199483
Sun Feb 9 10:25:46 2020 ftp.uni-stuttgart.de: total files after scan: 2414632 (delta: -199201)
Sun Feb 9 10:25:46 2020 ftp.uni-stuttgart.de: purged old files in 22s.
Sun Feb 9 10:25:46 2020 ftp.uni-stuttgart.de: done.
Completed in 33.0 minutes
Updated by pjessen about 4 years ago
The reason ftp.uni-stuttgart.de is not listed on mirrors.op.o is - of course - because it is not listed by "mb mirrorlist". Now I just have to work out why that is. I wonder if it might have to do with this mirror being marked as "asonly".
Updated by pjessen about 4 years ago
Yes, "mb mirrorlist" does not include mirrors that are prefixonly or asonly:
NOT(self.conn.Server.q.prefixOnly),
NOT(self.conn.Server.q.asOnly)
Updated by pjessen about 4 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
I am going to close this. It is a non-public mirror. so we don't really care as it does not affect our mirroring.