ASnull null when using ASN() function on 3.2-1721

16 views
Skip to first unread message

Ian Coetzee

unread,
Dec 17, 2025, 7:16:54 PM (2 days ago) Dec 17
to sFlow-RT
Hi Team,

After upgrading to 3.2-1721 we are unable to resolve ip addresses to ASN's, the result comes up as null. Previously we were on 3.1, can't remember the build number.

Increasing the log level, I am seeing the following

Dec 17 08:38:11 run-rt[358538]: FINER: decode header error, com.sflow.rt.B.F(Decoder.java:3574)
Dec 17 08:38:11 run-rt[358538]: FINER: decode header error, com.sflow.rt.B.h(Decoder.java:3774)
Dec 17 08:38:11 run-rt[358538]: FINER: decode header error, com.sflow.rt.B.F(Decoder.java:3574)
Dec 17 08:38:11 run-rt[358538]: FINER: decode header error, com.sflow.rt.B.h(Decoder.java:3774)

Perhaps an error in the parsing functions?

Kind regards
Ian Coetzee

Peter Phaal

unread,
Dec 17, 2025, 8:54:15 PM (2 days ago) Dec 17
to sFlow-RT
Hi Ian,

Thank you for reporting the problem. There is an issue with the 3.2-1721 build that affected asn (and country) lookups that we have fixed. Please download 3.2-1722 and confirm that it is working for you.

The "decode header error" messages you are seeing with the FINER log level aren't really errors, they are artifacts of the way the packet decoder works when there isn't enough data in the packet header to fully decode a field.

Peter

Ian Coetzee

unread,
Dec 18, 2025, 1:20:05 AM (2 days ago) Dec 18
to sFlow-RT
Hi Peter,

Thank you, appreciate the quick response. All happy now, ASN resolving.

One thing I noted, is under About the application still thinks it is build 1721.

Kind regards
Ian Coetzee

Peter Phaal

unread,
Dec 18, 2025, 1:29:59 PM (2 days ago) Dec 18
to sFlow-RT
Hi Ian,

Thanks again for your feedback. The 3.2 release moved from Java 11 to Java 17 so that we could use maintained versions of services that sFlow-RT depends on (e.g. Jetty 12). This ensures we have the latest security updates, but unfortunately, involved some major API changes and changes to the release process. I believe we have them sorted out now and we have updated 3.2-1722 release packages.

Regards,
Peter

Reply all
Reply to author
Forward
0 new messages