-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missing some NRTM data? #188
Comments
not showing in rpsl_objects:
btw, 185.21.224.0/24 seems to be missing too. though a 194.151.0.0/17 which came in 5 minutes later is present. |
just looking at diffs, and noticed this nrtm change:
but querying irrd4 shows the old origin:
expected to see:
|
Assuming we're still logging all SQL queries, I need the full postgresql logs from the 10 minutes or so surrounding all of the failed updates. I don't have access to the logs myself. These updates have been successfully processed in my local install. I'll do some more digging in the database too. |
@mxsasha you should now be able to read |
Working from the RIPE update, the NRTM update had a serial of 43672782, and seems to have been inserted into the database correctly:
This seems to match with the expected object, so the NRTM update was correctly processed. A query slightly before this updated rpsl_objects. However, these entries were deleted, because a few hours later:
It seems IRRd was restarted around that time, with force_reload set for most or all sources. We reloaded at serial 43668026 (4756 earlier than the ADD for 185.21.225.0/24AS2442):
However, the first NRTM update retrieval used a serial that was 7715 higher than CURRENTSERIAL of the dump:
The 185.21.225.0/24AS42442 update was not in the dump, and was skipped over when retrieving NRTM updates. A similar scenario happened for the two APNIC updates. The issue is that serial_newest_seen is not reset between full reloads, which will be fixed. |
Note that another forced full reload is required to correct the data. |
Unsure what happened here, an NRTM update came in:
IRRd v2 picked it up:
But IRRd v4 still shows only the overlapping route object, and the /24 from above is missing.
The text was updated successfully, but these errors were encountered: