new source path
-
- Posts: 1373
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
new source path
How do I cram this from 1.36.25 into .21?
rtsp://192.168.1.217:554/user=admin_password=Buffy4@sdCA_channel=0_stream=1.sdp?real_stream
gave
rtsp://192.168.1.217:554/user=admin_password=Buffy4@sdCA_channel=0_stream=1.sdp?real_stream
gave
Re: new source path
@ symbols really mess up url parsing. All the special characters are not valid in a URL. They have to be % encoded. So the @ has to be %40
https://www.w3schools.com/tags/ref_urlencode.ASP
https://www.w3schools.com/tags/ref_urlencode.ASP
-
- Posts: 1373
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: new source path
Yes, but that's not really part of the the URL, is it? anyway I changed it in 1.36 and copy/paste into 1.37, and it does this:
and looks like this on the console
but it doesn't work on either...because the camera wants the plain @, I suppose.
This works in 1.36
and looks like this on the console
but it doesn't work on either...because the camera wants the plain @, I suppose.
This works in 1.36
Re: new source path
We are going to need to see debug logs.
Everything in the url is url and must be properly encoded. Just because it generally works, doesn't mean it is correct.
This is actually why we now have the separate username and password fields, to deal with weird characters in the password.
But this cam wants it in the query part of the url. We are probably url-encoding what we are given before sending to the cam, and so we have a double url-encoding. At least that's my suspicion.
Everything in the url is url and must be properly encoded. Just because it generally works, doesn't mean it is correct.
This is actually why we now have the separate username and password fields, to deal with weird characters in the password.
But this cam wants it in the query part of the url. We are probably url-encoding what we are given before sending to the cam, and so we have a double url-encoding. At least that's my suspicion.
-
- Posts: 1373
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: new source path
OK. Makes sense.
So what log(s) do you need?
Please give settings as I don't really understand how those settings work - Maybe because I didn't restart after trying change them?
So what log(s) do you need?
Please give settings as I don't really understand how those settings work - Maybe because I didn't restart after trying change them?
Re: new source path
Options->Logging->ZM_DEBUG checked
LOG_DEBUG_TARGET => clear or _zmc
LOG_DEBUG_LEVEL => 3
restart. Then /var/log/zm/zmc_mwhateveridnumber.log should have lots of great debugging info.
I was under the impression that the console should filter auth etc out of the source url. This is controlled by Options->Web->WEB_FILTER_SOURCE
LOG_DEBUG_TARGET => clear or _zmc
LOG_DEBUG_LEVEL => 3
restart. Then /var/log/zm/zmc_mwhateveridnumber.log should have lots of great debugging info.
I was under the impression that the console should filter auth etc out of the source url. This is controlled by Options->Web->WEB_FILTER_SOURCE
-
- Posts: 1373
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: new source path
I have the web filter turned off.
I’ll get back later with the log.
Thanks!
I’ll get back later with the log.
Thanks!
-
- Posts: 1373
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: new source path
Not sure this says much useful.
I notice the user and password fields are not shown when used, even with the web filter turned off. Not sure I like that.
Code: Select all
09/16/22 00:33:16.564975 zmc_m19[92491].ERR-zmc.cpp/267 [Failed to prime capture of initial monitor]
09/16/22 00:33:22.605734 zmc_m19[92491].ERR-zm_ffmpeg_camera.cpp/323 [Unable to open input rtsp://192.168.1.219:554/user=admin_password=Buffy4%40sdCA_channel=0_stream=1.sdp?real_stream due to: Server returned 4XX Client Error, but not one of 40{0,1,3,4}]
09/16/22 00:33:22.605798 zmc_m19[92491].ERR-zmc.cpp/267 [Failed to prime capture of initial monitor]
09/16/22 00:33:29.636744 zmc_m19[92491].ERR-zm_ffmpeg_camera.cpp/323 [Unable to open input rtsp://192.168.1.219:554/user=admin_password=Buffy4%40sdCA_channel=0_stream=1.sdp?real_stream due to: Server returned 4XX Client Error, but not one of 40{0,1,3,4}]
09/16/22 00:33:29.636910 zmc_m19[92491].ERR-zmc.cpp/267 [Failed to prime capture of initial monitor]
09/16/22 00:33:37.661843 zmc_m19[92491].ERR-zm_ffmpeg_camera.cpp/323 [Unable to open input rtsp://192.168.1.219:554/user=admin_password=Buffy4%40sdCA_channel=0_stream=1.sdp?real_stream due to: Server returned 4XX Client Error, but not one of 40{0,1,3,4}]
09/16/22 00:33:37.661927 zmc_m19[92491].ERR-zmc.cpp/267 [Failed to prime capture of initial monitor]
09/16/22 00:33:46.695421 zmc_m19[92491].ERR-zm_ffmpeg_camera.cpp/323 [Unable to open input rtsp://192.168.1.219:554/user=admin_password=Buffy4%40sdCA_channel=0_stream=1.sdp?real_stream due to: Server returned 4XX Client Error, but not one of 40{0,1,3,4}]
09/16/22 00:33:46.695496 zmc_m19[92491].ERR-zmc.cpp/267 [Failed to prime capture of initial monitor]
09/16/22 00:33:56.696152 zmc_m19[92491].ERR-zm_ffmpeg_camera.cpp/323 [Unable to open input rtsp://192.168.1.219:554/user=admin_password=Buffy4%40sdCA_channel=0_stream=1.sdp?real_stream due to: Immediate exit requested]
Re: new source path
You didn't follow my instructions for turning on debug. Those logs contain no debugging info.
-
- Posts: 1373
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: new source path
Yeah, that's what I thought.
$ sudo service zoneminder restart
And even a reboot...
and LOG_DEBUG_TARGET blank and _zmc along with LOG_DEBUG_LEVEL UP TO 9
So I'm at a loss.
So maybe something else is wonky? thenOptions->Logging->ZM_DEBUG checked (LOG_DEBUG ?)
LOG_DEBUG_TARGET => clear or _zmc
LOG_DEBUG_LEVEL => 3
$ sudo service zoneminder restart
And even a reboot...
and LOG_DEBUG_TARGET blank and _zmc along with LOG_DEBUG_LEVEL UP TO 9
So I'm at a loss.
Re: new source path
Ok, LOG_LEVEL_FILE also needs to be set to DEBUG
-
- Posts: 1373
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: new source path log
Code: Select all
[attachment=0]zmc_m19.log[/attachment]
- Attachments
-
- zmc_m19.log
- (94.85 KiB) Downloaded 195 times
Re: new source path
Wow... 451 not available due to legal reasons!
I think what we need to do here, is smarten up the username/password stripping out code so that it doesn't mange the url. I don't really understand why it doesn't like the % encoded url... but at the end of the day I think we should send what the user has put in regardless of whether it is right or not.
So... stay tuned.
I think what we need to do here, is smarten up the username/password stripping out code so that it doesn't mange the url. I don't really understand why it doesn't like the % encoded url... but at the end of the day I think we should send what the user has put in regardless of whether it is right or not.
So... stay tuned.
-
- Posts: 1373
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: new source path
Yeah, I have very mixed feelings about that, but I guess ya gotta do what works.
Thanks for your time.
Thanks for your time.