Closed bwthor closed 7 months ago
I believe this has already been addressed and should come out with 0.6.3
You can test with this build:
https://github.com/QuantumEntangledAndy/neolink/actions/runs/6388831582
There are a few more errors to address in that build involving the new push notifications and the need and enough data callbacks
You can test with this build:
https://github.com/QuantumEntangledAndy/neolink/actions/runs/6388831582
There are a few more errors to address in that build involving the new push notifications and the need and enough data callbacks
I finally got a chance to try this build, and unfortunately still get the neolink.exe crash if I unplug a camera or two.
Could you provide a debug log with the following
set RUST_LOG="neolink=debug"
neolink.exe rtsp --config=config.toml 2&>1 > neolink.log
Sorry, I'm not sure about these commands.
I entered the first one on the command prompt and hit enter, then entered the second one, and get this syntax error...
neolink.exe rtsp --config=config.toml 2&>1 > neolink.log
The syntax of the command is incorrect.
The first one turns on the debug log and the second one starts neolink but redirects the output to a file
I think I see the issue I made it should be > neolink.log 2>&1
with the &
after the >
Sorry...I'm dumb and don't understand what I'm missing in the log syntax. Get this now, and the neolink.log was not populated.
C:\Users\me\neolink>set RUST_LOG="neolink=debug"
C:\Users\me\neolink>neolink.exe rtsp --config=config.toml 2>&1 > neolink.log
warning: invalid logging spec 'debug"', ignoring it
I UNPLUGGED CAMERAS AT THIS POINT
thread 'RUST_BACKTRACE=1
environment variable to display a backtrace
It should have made a file in the same folder as neolink called neolink.log
was this not the case? I don't use windows so I cannot test your cmd command but perhaps the order is important neolink.exe rtsp --config=config.toml > neolink.log 2>&1
Please also try the latest build so I can match up the line numbers easier
The could not build pipeline: channel closed
comes at the point where gstreamer tries to create a media. It asks my code to make it then errors if there was anything wrong in there.
Channel closed
seems to suggest that the issue is happening when it tries to send the appsrc from the media creation code through the channel into the other thread. This should only be closed if the reciever of the channel is close
The other end of the channel should not be closed. I keep that channel alive in another thread, if there is no camera it either sends cached data or a repeat of he last IFrame.
This is why i want the debug logs. The debug logs will print out useful info to tell me when the channel might be lost
New build, same results... neolink.log is created, but nothing is entered into the file. I still think the RUST log capture may not be right, I get that bold message after starting neolink.
C:\Users\me\neolink>set RUST_LOG="neolink=debug"
C:\Users\me\neolink>neolink.exe rtsp --config=config.toml 2>&1 > neolink.log
warning: invalid logging spec 'debug"', ignoring it
Cameras unplugged here
thread 'RUST_BACKTRACE=1
environment variable to display a backtrace
Also noticed when running the new build, the main stream is just an all gray screen in Blueiris. Substream looks normal, but when clicking to view the Main stream, it switches, then goes all gray. Switched back to 62, and camera streams are back to normal.
Ah another BI user... Currently having issues with that client on the main stream. Not sure why
I am wondering if BI and frigate are going to conflict with each other. To get frigate to work over pause I made it so that it repeats a keyframe if no frame was sent for over 1s, this is to stop frigate form thinking we are disconnected. But perhaps the way BI decodes the stream it dosen't like the extra keyframe out of place
Lets get those log working first. I am just googling here, coz no windows, so if you can try to also find out how to do this things will go much faster.
This is what I do on bash in macos
export RUST_LOG="neolink=debug"
neolink rtsp --config=neolink.toml 2>&1 >neolink.log
When I do this all output is directed to file so I cannot see it
In macos and linux I can do this to see the log and print to file
export RUST_LOG="neolink=debug"
neolink rtsp --config=neolink.toml 2>&1 | tee neolink.log
Which has the nice benifit of letting me see the log in the terminal and write it to file
If the 2>&1
is missnig then the log will be empty, which I think is what you are reporting. Perhaps you can screen shot what you typed so I can double check it
BTW are you using powershell or CMD?
Power shell has a tee like command it seems https://superuser.com/questions/74127/tee-for-windows
Sorry, had to run out for a bit. I was using CMD, but can certainly try Powershel. I'll report back.
Powershell might be more trouble then it is worth.
Send me the screen shot of your cmd command and I will check them
OK, I hope this is correct. From Widnows Command Prompt.
set RUST_LOG=neolink=debug neolink.exe rtsp --config=config.toml > neolink.log 2>&1
I don't suppose you can repeat that with just one camera. All of those overlapping error messages make it hard to work out the order of events.
Also you seem to be getting the Cancel 3
error message. I have another user who is getting this but I cannot seem to replicate it. Can you let me know what you are doing to replicate? Are you disconnecting at a certain point in the setup? I am hoping its not a windows only type of error
p.s. put logs in spoilers like this
<details>
<summary>log</summary>
LOG HERE
</details>
The blank lines between the ``` are important
Ok so this build likely fixes the issue with Cancel3 (which was your first error). I'll see what else your log might suggest
And this build turns the panic into a soft error instead. The rtsp client will get a 500 error instead.
Updated build coz of typo
OK, running new build with only one camera configured. When I unplugged the camera, I did not see the error. Attached log is this config. I am still seeing the gray screen on the Main Stream.
I set the config back to all cams, and unplugged the entire group, and still no error. LMK if you would like me to test anything else.
Updated build coz of typo
Hello, I have the exact same issue under the latest release, but this build's link the expired. Would you be able to link either a Windows build that doesn't have the pipeline issue, or a Linux one that doesn't end up on a memory leak?
I'm afraid I cannot set up a cron job or something to automatically restart the process in any OS, because my only NVR, a Lorex 4k one, randomly deletes RTSP channels after they go down, no matter what I do, so in order to minimize the manual labour of remapping the cannels every day, I'd like Reolink to be constantly running.
Thank you very much in advance.
@martorell-jpg memory leak should be fixed in master now and on next release. Could you test one of those and open a new issue about memory leak (or post on one of the issues actually on the memory leak where we have active discussion)
I am closing this for inactivity and because the code based has changed a lot since this issue
Describe the bug A clear and concise description of what the bug is. Running this manually from a command prompt, Works fine until any of the cameras are disconnected, then I get the crash.
To Reproduce Steps to reproduce the behavior. Example:
[[cameras]] name = "Ch1" username = "admin" password = "mysecretpass" address = "192.168.0.14"
[[cameras]] name = "Ch2" username = "admin" password = "mysecretpass" address = "192.168.0.15"
[[cameras]] name = "Ch3" username = "admin" password = "mysecretpass" address = "192.168.0.16"
[[cameras]] name = "Ch4" username = "admin" password = "mysecretpass" address = "192.168.0.17"
[[cameras]] name = "Backyard8MP" username = "admin" password = "mysecretpass" address = "192.168.0.13"