OpenNMS

Null (\0) characters in logmsg field of events causes org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.8.12
  • Fix Version/s: 1.8.14, 1.9.91, 1.11.0
  • Component/s: Event/Trap Configuration
  • Security Level: Default (Default Security Scheme)
  • Labels:

Description

The logmsg field wasn't being escaped to handle \0 characters. Cropped up because Dell Drac5/6 test snmp traps contain null octets in one of their parameters, and the default trap event incldues all parms in the logmsg field.

Fix and unit test attached.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tomás Heredia added a comment -

Same here. Tested on 1.8.9
Our Aruba controllers send almost all traps with nulls on them

Show
Tomás Heredia added a comment - Same here. Tested on 1.8.9 Our Aruba controllers send almost all traps with nulls on them
Hide
Permalink
Benjamin Reed added a comment -

Looks reasonable to me, merged to 1.8+.

Show
Benjamin Reed added a comment - Looks reasonable to me, merged to 1.8+.

People

  • Assignee:
    Benjamin Reed
    Reporter:
    Duncan Mackintosh
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: