Omada Controller v5.14.26.1 problem with rsyslog/telegraf timestamp

Omada Controller v5.14.26.1 problem with rsyslog/telegraf timestamp

Omada Controller v5.14.26.1 problem with rsyslog/telegraf timestamp
Omada Controller v5.14.26.1 problem with rsyslog/telegraf timestamp
2024-07-24 20:12:51 - last edited 2024-07-26 02:34:43
Tags: #syslog
Hardware Version:
Firmware Version: v5.14.26.1

After upgrading to 5.14 rsyslog is not able to parse timestamp correctly using RSYSLOG_SyslogProtocol23Format for forwarding to telegraf syslog plugin.

 

Error from telegraf:

[inputs.syslog] Error in plugin: expecting an app-name (from 1 to max 48 US-ASCII characters) or a nil value [col 51]

 

Old version 5.13.30.8 is working correct exampel of syslog message.

 

11:05:56.249249 IP (tos 0x0, ttl 64, id 29689, offset 0, flags [DF], proto UDP (17), length 142)
    10.110.0.162.38343 > DESKTOP-DR266RC.hoiland.eu.syslog: [udp sum ok] SYSLOG, length: 114
        Facility local3 (19), Severity warning (4)
        Msg: 1 2024-07-24T09:05:53.803Z Omada Controller - - - asada failed to log in to the controller from 10.110.0.178.
        0x0000:  3c31 3536 3e31 2032 3032 342d 3037 2d32
        0x0010:  3454 3039 3a30 353a 3533 2e38 3033 5a20
        0x0020:  4f6d 6164 6120 436f 6e74 726f 6c6c 6572
        0x0030:  202d 202d 202d 2061 7361 6461 2066 6169
        0x0040:  6c65 6420 746f 206c 6f67 2069 6e20 746f
        0x0050:  2074 6865 2063 6f6e 7472 6f6c 6c65 7220
        0x0060:  6672 6f6d 2031 302e 3131 302e 302e 3137
        0x0070:  382e

 

New version 5.14.26.1 is not working.

 

11:01:01.747431 IP (tos 0x0, ttl 64, id 44753, offset 0, flags [DF], proto UDP (17), length 137)
    10.110.0.222.58203 > pi.hole.syslog: [udp sum ok] SYSLOG, length: 109
        Facility local3 (19), Severity warning (4)
        Msg: 1 2024-07-24 10:00:58 Omada Controller - - - asada failed to log in to the controller from 10.110.0.178.
        0x0000:  3c31 3536 3e31 2032 3032 342d 3037 2d32
        0x0010:  3420 3130 3a30 303a 3538 204f 6d61 6461
        0x0020:  2043 6f6e 7472 6f6c 6c65 7220 2d20 2d20
        0x0030:  2d20 6173 6164 6120 6661 696c 6564 2074
        0x0040:  6f20 6c6f 6720 696e 2074 6f20 7468 6520
        0x0050:  636f 6e74 726f 6c6c 6572 2066 726f 6d20
        0x0060:  3130 2e31 3130 2e30 2e31 3738 2e

 

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Omada Controller v5.14.26.1 problem with rsyslog/telegraf timestamp-Solution
2024-07-26 02:31:24 - last edited 2024-07-26 02:34:43

  @torfinn 

We have updated our log format; please update the log resolution algorithm as well.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#3
Options
1 Reply
Re:Omada Controller v5.14.26.1 problem with rsyslog/telegraf timestamp-Solution
2024-07-26 02:31:24 - last edited 2024-07-26 02:34:43

  @torfinn 

We have updated our log format; please update the log resolution algorithm as well.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#3
Options