Closed falco1717 closed 2 months ago
2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Starting process: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Starting new process: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=ipc msg=IPC Client Connected 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=gstreamer msg=Received unDemand for doorbell. Delaying for 60 second to see if there is a new demand. 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=ipc msg=Emitted event: unDemand 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF MediaMTX v1.9.0 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF configuration loaded from /home/node/app/tmp/nestmtx.yml 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 ERR listen tcp4 0.0.0.0:9996: bind: address already in use 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF waiting for running hooks 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Process exited: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Starting process: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Starting new process: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF MediaMTX v1.9.0 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF configuration loaded from /home/node/app/tmp/nestmtx.yml 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 ERR listen tcp4 0.0.0.0:9996: bind: address already in use 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF waiting for running hooks 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Process exited: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Starting process: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Starting new process: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF MediaMTX v1.9.0 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF configuration loaded from /home/node/app/tmp/nestmtx.yml 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 ERR listen tcp4 0.0.0.0:9996: bind: address already in use 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF waiting for running hooks 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Process exited: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Starting process: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Starting new process: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF MediaMTX v1.9.0 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF configuration loaded from /home/node/app/tmp/nestmtx.yml 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 ERR listen tcp4 0.0.0.0:9996: bind: address already in use 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=mediamtx msg=2024/08/31 22:13:36 INF waiting for running hooks 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Process exited: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Starting process: mediamtx 2024/08/31 03:13PM 30 pid=8 hostname=d3ab07bfa73a service=pm3 msg=Starting new process: mediamtx
Which version are you using?
Testing
Which operating system are you using?
Describe the issue
Leave Nest doorbell wired connected to synology to record and it will go offline after 6 hours or so
Describe how to replicate the issue
Did you attach the server logs?
yes
Did you attach a network dump?
no