Project

General

Profile

Bug #7233

Log aggregation processing doesn't handle ipv6 addresses

Added by Peter Slaughter almost 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Category:
d1_log_aggregation
Start date:
2015-06-25
Due date:
% Done:

100%

Story Points:
Sprint:

Description

The setCOUNTERfields method causes an uncaught exception when a log record with an ipv6 address is
encountered. The method should be either updated to handle ipv6 addresses or
check the address type and ignore it if it is ipv6 format. In either case, error
checking should be improved. Below is a sample traceback:

org.dataone.cn.batch.logging.type.LogEntrySolrItem.setCOUNTERfields(LogEntrySolrItem.java:364)
java.lang.IllegalArgumentException: Could not parse [2001:4898:80e0:ee43::3]

History

#1 Updated by Dave Vieglais almost 9 years ago

The issue is slightly more general in that in some cases the ipAddress field contains garbage. The aggregator code should gracefully fail such records.

#2 Updated by Peter Slaughter almost 9 years ago

  • Assignee set to Peter Slaughter

#3 Updated by Peter Slaughter almost 9 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30

#4 Updated by Peter Slaughter almost 9 years ago

  • Status changed from In Progress to Testing
  • % Done changed from 30 to 50

#5 Updated by Peter Slaughter almost 9 years ago

  • Status changed from Testing to Closed
  • % Done changed from 50 to 100

Tested, verified in stage environment (cn-stage-ucsb-1)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)