search

QuantumEntangledAndy / neolink

An RTSP bridge to Reolink IP cameras
GNU Affero General Public License v3.0
247 stars 39 forks source link

udpsource spewing info logs #245

Closed si458 closed 2 months ago

si458 commented 2 months ago

Describe the bug running the latest docker image this morning seems to have randomly started spewing udpsource logs

[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] sent: 0
[2024-04-26T08:57:30Z INFO  neolink_core::bc_protocol::connection::udpsource] recieved: 0

To Reproduce Steps to reproduce the behavior. Example:

  1. docker run --network host -it -e "NEO_LINK_MODE=mqtt-rtsp" --volume=$PWD/config.toml:/etc/neolink.toml quantumentangledandy/neolink:latest

Expected behavior i believe the udpsource should of been debug logs and not info logs, and i should not see these log

Versions NVR software: Neolink software: Reolink camera model and firmware:

QuantumEntangledAndy commented 2 months ago

Ah yeah. Actually they were info on purpose to reduce the need for the testers to set the log level. I meant to swap those to trace level after we were done.

QuantumEntangledAndy commented 2 months ago

Give me half hour or so for me to get somewhere I can setup my laptop

si458 commented 2 months ago

no worries! no rush! just totally threw me at first! keep up amazing work! 👍

si458 commented 2 months ago

Latest build fixed the udpsource But I'm still seeing loads of udpdiscovery info messages?

[2024-04-26T16:41:42Z INFO  neolink_core::bc_protocol::connection::discovery] Got discovery UdpDiscovery { tid: 96, payload: M2cQr(M2cQr { reg: None, relay: None, log: None, t: None }) } for 15.188.197.53:9999
[2024-04-26T16:41:42Z INFO  neolink_core::bc_protocol::connection::discovery] Got discovery UdpDiscovery { tid: 125, payload: M2cQr(M2cQr { reg: None, relay: None, log: None, t: None }) } for 132.226.204.68:9999
[2024-04-26T16:41:42Z INFO  neolink_core::bc_protocol::connection::discovery] Got discovery UdpDiscovery { tid: 138, payload: M2cQr(M2cQr { reg: None, relay: None, log: None, t: None }) } for 129.213.189.52:9999
[2024-04-26T16:41:42Z INFO  neolink_core::bc_protocol::connection::discovery] Got discovery UdpDiscovery { tid: 189, payload: M2cQr(M2cQr { reg: None, relay: None, log: None, t: None }) } for 193.123.95.178:9999
[2024-04-26T16:41:42Z INFO  neolink_core::bc_protocol::connection::discovery] Got discovery UdpDiscovery { tid: 118, payload: M2cQr(M2cQr { reg: None, relay: None, log: None, t: None }) } for 144.24.42.1:9999
[2024-04-26T16:41:42Z INFO  neolink_core::bc_protocol::connection::discovery] Got discovery UdpDiscovery { tid: 56, payload: M2cQr(M2cQr { reg: None, relay: None, log: None, t: None }) } for 16.163.195.33:9999
si458 commented 2 months ago

ok thanks latest build now hides those messages too! will close this issue!