Error with node-red-contrib-syslog-input 1.0.1

General
1

I have an application for this node but am running into some issues. I am successfully getting SYSLOG data to hit the input node, but the input node is not happy with the message. It is giving me this error:

Invalid message received: {"timestamp":"2019-11-14T22:26:31.890Z","address":"192.168.15.39","family":"IPv4","port":20514,"size":143,"msg":"<22>24/09/2016      15:04:31        User Activity                   User admin of PDU 1 Rack:AA01-MS:SideA from host 192.168.15.160 logged out\u0000"}

The <22> by the date 24/09/2016 is red in the debugger, but not sure if this was a part of the original syslog msg or if it was added by the node. Maybe I need to tweak the code of this node to work? Any suggestions?

2

I'm getting the same error:

nodered:

"Invalid message received: {"timestamp":"2022-02-15T13:53:43.226Z","address":"10.0.0.1","family":"IPv4","port":40146,"size":40,"msg":"<27>Feb 15 14:53:43 routar stubby[6262]:"}"

original message on OpenWRT:

Tue Feb 15 14:53:43 2022 daemon.err stubby[6262]:

looks like the daemon (in my case stubby) sends empty lines to syslog and there's no message. the syslog input node sends this as a warning in debug console and I cannot get rid of it.

is there anything in nodered I can do? maybe catch warnings or something?