SYSLOG explain? / nodelist fills up

[tozett]

hi,
put in my rasperry-ip with rsyslog as an syslog-server for the esp12-easy R072 and the nodelist on the esp-status-page filled up.
looks good, but what for?

there are (unexplained? where?) syslog-entries:

Code: Select all

Jan 25 11:54:34 ESP Unit: 0 : FLASH: Settings saved
Jan 25 11:54:34 ESP Unit: 0 : FLASH: Settings saved
Jan 25 11:55:02 ESP Unit: 0 : WD   : Uptime 18 ConnectFailures 0 FreeMem 25512
Jan 25 11:55:02 192.168.14.44 ▒#001#030▒4▒▒▒▒#016,#000("@#011#000#000
Jan 25 11:55:32 ESP Unit: 0 : WD   : Uptime 18 ConnectFailures 0 FreeMem 25512
Jan 25 11:55:32 192.168.14.44 ▒#001#030▒4▒▒▒▒#016,#000("@#001#000#000
Jan 25 11:55:47 ESP Unit: 0 : FLASH: Settings saved
Jan 25 11:55:47 ESP Unit: 0 : FLASH: Settings saved
Jan 25 11:56:02 ESP Unit: 0 : WD   : Uptime 19 ConnectFailures 0 FreeMem 25512
Jan 25 11:56:02 ESP Unit: 0 : UDP  : Send Sysinfo message
Jan 25 11:56:02 192.168.14.44 ▒#001#030▒4▒▒▒▒#016,#000("@#005#000#000

they must have a meaning, the devs must have thought about something, as he putted this in.
for what is it useful in this wonderful ESPeasy-piece?

thanks..

[Martinus]

I guess you entered 514 in the UPD port box and it looks like the binary system info messages are now send to the syslog server as well because it's using UDP broadcast IP for ESP Easy system messages. The syslog server can't understand this binary data...

You can enter any arbitrary port number in that box, as long as it does not conflict with other systems listening on the same port for other purposes (like the UDP server). I use 65500.

The node list can be used for (future) communication between ESP unit's.

[tozett]

ok, thanks.
for me the udp seemed to belong to syslog, sometimes you need to configure syslog: IP, PORT, LEVEL...
here the UDP port does not belong to the syslog-configuration. as i first thought, but it was not right.

besides that, all the entries from "Tools/Advanced" seems logically belong to CONFIG-settings, doesnt they?

while the binary node-infos where transmitted to my rsyslog, i noticed some breakdowns of my tplink openwrt CC4xxxx router...
i now removed the udp port entry and will see if that killed my router or the newly traffic to syslog....

[tozett]

as it now runs stable, i think the binary data may killed my open-wrt WLAN AP. ....
i dont know if one has to think over, to ommit binary data for node-communication.
to prevent similar sideeffects. but i did not investigate this further. i am glad now, it runs...