Current serial number for some databases is not exposed

[job]

Perhaps related to how some of the data sources are set up, but I'd expect to see 186 instead of the current output. Or phrased differently, how can we query for the current serial of any source?

hanna:~ job$ whois -h irrd01.ip.gin.ntt.net '!jRPKI'
A9
RPKI:N:-
C

[job]

Config for source RPKI is in #180

[mxsasha]

This depends on what we consider the current serial. There's two different concepts of first/last serial in IRRd. First question, what do you actually do with the !j output?

[job]

1) We use !j to query the server to discover what the last serial is and if that is comparable with the NRTM source. To see if we for instance our out of sync with RIPE. 2) check if the serial for the special databases as rpki / registrobr / arin-Whois increases day over day. Phrased differently: !j offers a way to inspect the server without having access to the psql database.

…

On Mon, Jan 28, 2019 at 18:23 Sasha Romijn ***@***.***> wrote: This depends on what we consider the current serial. There's two different concepts of first/last serial in IRRd. First question, what do you actually do with the !j output? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#181 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJY2KRkse8hlQPASkJ3hiTuteGkqOtmks5vHzH_gaJpZM4aVydF> .

[mxsasha]

This is fixed, but note that the serials provided by !j now do not correlate to which serials are available over NRTM (that was the original behaviour).