GRS Import does not fill inetnum and inet6num

[Eduard3000]

Hi Ripe Whois Team,

just did a grs import, but the tables inetnum and inet6num are not filled.

Followed your instructions (and its pretty slow and bootstrap does not work, sizes of files > 15MB?!)

So how to get that too? And how to make Bootstrapping work (want to cmp if it is faster!)?

Regards, Eduard

[prakash5331]

Facing the same issue :-(

[Tim---]

Hi,

I had the same problem (no inetnum on the first grsImport), but after the third try they are imported correctly. Maybe the objects they reference must be imported first ?

If you want to investigate, you can increase the verbosity of the server in the file log4j.xml. Replace each instance of INFO with DEBUG and restart the whois server. You will see

My initial import was also slow (>2days estimate). Unless you are bound by the CPU or the RAM, it's probably because mariadb flushes to disk after each transaction for reliability. You can disable this behavior during the initial import by setting innodb_flush_log_at_trx_commit = 0 in the mariadb configuration, and restarting the mariadb server. Of course, you probably don't want to do it on a production server.

[Tim---]

I stumbled back on this issue. This time retrying doesn't seem to work. But it looks like aut-num is also missing in the file.

I guess this may be linked to the management of authoritative resources (from delegated-ripencc-extended-latest), which impacts precisely inetnum, inet6num and aut-num. Unfortunately I was not able to debug deeper to see where it fails :/.

[Tim---]

I think I found the root cause of the problem. The authoritative resources are downloaded by the Scheduler (AuthoritativeResourceImportTask) once a day. So when you force only the grsImport, the authoritative data is present, and the import of aut-num, inetnum and inet6num will be missing.

The solution would be to force the execution of all the tasks of the Scheduler using ./whois.init jmx with these arguments :

bean net.ripe.db.whois:name=DailyScheduler
run runDailyScheduledTasks true

It doesn't work on the first import (although the table INTERNALS_LOCAL.authoritative_resource is filled). However, it will work on the second import.