Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPU usage increases to 100% #320

Open
barttim-oss opened this issue Nov 6, 2024 · 2 comments
Open

CPU usage increases to 100% #320

barttim-oss opened this issue Nov 6, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@barttim-oss
Copy link

Describe the bug
I have the application as an add-on in my HomeAssistant, unfortunately the CPU usage increases constantly until it eventually reaches 100% and blocks my entire HomeAssistant server

To Reproduce

  1. Launch Neolink: with only mqtt on
  2. wait an hour

Versions
Neolink software: neolink-latest
Reolink camera model and firmware: 4x Argus 3 Pro
HA-Hardware: PC with 13th Gen Intel® Core™ i9-13900H, HA gets 12 of the Cores

Can you help me? What do you need to find the Isue

@barttim-oss barttim-oss added the bug Something isn't working label Nov 6, 2024
@MatthiasPetermann
Copy link

Same here.... funny enough I have a similiar issue on both ends, on the Broker side (eclipse-mosquitto/mosquitto#2807) and just now observed for the first time on the client side (neolink with the same setting as yours with just mqtt enabled). I have no idea, yet but investigating...

@MatthiasPetermann
Copy link

A small update on this: In the meantime, I have switched my MQTT broker from Mosquitto to NATS and can confirm that this issue also occurs with NATS. My Neolink configuration is as follows:

[mqtt]
broker_addr = "10.0.0.14"
port = 1883
credentials = [ "neolink", "**********"]
enable_motion = true

[[cameras]]
name = "Einfahrt"
username = "admin"
password = "*********"
uid = "***************"
  [cameras.mqtt]
  enable_motion = true
  enable_preview = true
  preview_update = 2000
  [cameras.pause]
  on_motion = true
  timeout = 2.1

[[cameras]]
name = "Garten"
username = "admin"
password = "*********"
uid = "*********************"
  [cameras.mqtt]
  enable_motion = true
  enable_preview = true
  preview_update = 2000
  [cameras.pause]
  on_motion = true
  timeout = 2.1

I had to restart neolink to bring it back to normal operation. Next time - I guess this will happen in the next 24 hours - I am prepared to run a dtrace script and hopefully can prepare some detailed logs which function consumes most cpu time to narrow it down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants