![](https://seccdn.libravatar.org/avatar/184f2936f5d39b27534f4dd7c4d15bfb.jpg?s=120&d=mm&r=g)
Lars Vogdt wrote:
Am 27. September 2017 18:05:33 MESZ schrieb Per Jessen <per@opensuse.org>:
No big deal Lars. I was just wondering as the data seemed to be quite old - olaf hasn't been running for very long?
The database is very old - and Olaf is currently not doing the scans: these are still running on the old machine.
Aha, I was not aware.
Dunno why the data hasn't been updated from there since such a long time - and honestly I just want to get rid of the old machine sonner than later.
=> time to sent an announcement to the mirror last that our scanner now scans from another IP (which is still in the documented range, so normally the should no change be needed on the mirrors side). My problem: atm Olaf just has IPv4 - I need to think how we can manage to let him also scan via IPv6...
To get scanning on ipv6 would be good, agree. Our mirror is taken offline for about 3 minutes when olaf tries the ipv6 address first, then the ipv4 address a little later. Mind you, the pfx2asn table is ipv4 only ...
I've checked the database, pfx2asn was updated. That should be enough.
Thanks for checking!
Just to make sure I got the right place - mirrordb3, right?
But as I don't want to make the mistake twice: can you tell me the SQL statement you used to verify? I want to write a monitoring check for this...
It's not so easy - I happened to notice 'asn 0' and 'prefix 0' being listed for our mirror. "mb iplookup 185.85.248.0". I checked the pfx2asn table, and the prefix (185.95.248.0/22) wasn't listed. That range was allocated in Jan 2015, so I knew some data had to be out of date. Maybe you can check for the downloaded file being out of date? /home/mirrorbrain/oix-full-snapshot-latest.dat.bz2 -- Per Jessen, Zürich (16.2°C) openSUSE mailing list admin -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org