CURL source not working on fresh install 1.36.12

Discussions related to the 1.36.x series of ZoneMinder
Post Reply
sergeys
Posts: 2
Joined: Sat Jan 15, 2022 4:49 am

CURL source not working on fresh install 1.36.12

Post by sergeys »

Hi,

I installed fresh CentOS 8, installed Zoneminder from scratch. Transferred my database from 1.29.0, and used zmupgrade. When I started the daemon, none of the cameras are working (I use CURL source exclusively). I cleared out the database, and added created a fresh database with empty config. Added a camera with CURL source, and I keep getting a lot of "Failed to prime capture of initial monitor" in the logs without any explanation.

I tried using CURL to get the image, and was able to retrieve it without any problems, and save it in events folder.

Here's what I'm seeing in /var/log/messages:
Jan 14 23:47:24 melbourne zmdc[114483]: INF ['zmc -m 1' starting at 22/01/14 22:47:24, pid = 114510]
Jan 14 23:47:24 melbourne zmdc[114510]: INF ['zmc -m 1' started at 22/01/14 22:47:24]
Jan 14 23:47:24 melbourne zmc_m1[114510]: INF [zmc_m1] [Starting Capture version 1.36.12]
Jan 14 23:47:24 melbourne zmdc[114483]: INF ['zmfilter.pl --filter_id=1 --daemon' starting at 22/01/14 22:47:24, pid = 114515]
Jan 14 23:47:24 melbourne zmdc[114515]: INF ['zmfilter.pl --filter_id=1 --daemon' started at 22/01/14 22:47:24]
Jan 14 23:47:24 melbourne zmdc[114483]: INF ['zmfilter.pl --filter_id=2 --daemon' starting at 22/01/14 22:47:24, pid = 114519]
Jan 14 23:47:24 melbourne zmdc[114519]: INF ['zmfilter.pl --filter_id=2 --daemon' started at 22/01/14 22:47:24]
Jan 14 23:47:24 melbourne zmfilter_1[114515]: INF [Scanning for events using filter id '1']
Jan 14 23:47:24 melbourne zmdc[114483]: INF ['zmwatch.pl' starting at 22/01/14 22:47:24, pid = 114523]
Jan 14 23:47:24 melbourne zmdc[114523]: INF ['zmwatch.pl' started at 22/01/14 22:47:24]
Jan 14 23:47:24 melbourne zmfilter_2[114519]: INF [Scanning for events using filter id '2']
Jan 14 23:47:25 melbourne zmwatch[114523]: INF [Watchdog starting, pausing for 30 seconds]
Jan 14 23:47:25 melbourne zmdc[114483]: INF ['zmstats.pl' starting at 22/01/14 22:47:25, pid = 114528]
Jan 14 23:47:25 melbourne zmdc[114528]: INF ['zmstats.pl' started at 22/01/14 22:47:25]
Jan 14 23:47:25 melbourne systemd[1]: Started ZoneMinder CCTV recording and security system.
Jan 14 23:47:25 melbourne systemd[1]: session-c30.scope: Succeeded.
Jan 14 23:47:25 melbourne zmstats[114528]: INF [Stats Daemon starting in 30 seconds]
Jan 14 23:47:25 melbourne zmc_m1[114510]: ERR [zmc_m1] [Failed to prime capture of initial monitor]
Jan 14 23:47:27 melbourne zmc_m1[114510]: ERR [zmc_m1] [Failed to prime capture of initial monitor]
Jan 14 23:47:30 melbourne zmc_m1[114510]: ERR [zmc_m1] [Failed to prime capture of initial monitor]
Jan 14 23:47:34 melbourne zmc_m1[114510]: ERR [zmc_m1] [Failed to prime capture of initial monitor]
In zmc log for monitor 1, I see that image is being downloaded, but nothing happens, and it's an endless loop of failed to prime capture:
01/14/22 23:07:09.277943 zmc_m1[114917].DB1-zm_monitor.cpp/971 [Mapped file /dev/shm/zm.mmap.1 (18667960 bytes) to unlocked memory]
01/14/22 23:07:09.277948 zmc_m1[114917].DB3-zm_monitor.cpp/1004 [Aligning shared memory images to the next 64 byte boundary]
01/14/22 23:07:09.277959 zmc_m1[114917].DB3-zm_monitor.cpp/1014 [Allocated 3 3 image buffers]
01/14/22 23:07:09.297340 zmc_m1[114917].DB3-zm_monitor.cpp/1067 [Success connecting]
01/14/22 23:07:09.303545 zmc_m1[114917].DB1-zmc.cpp/261 [Failed to prime capture of initial monitor]
01/14/22 23:07:09.816399 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: HTTP/1.1 200 OK
01/14/22 23:07:09.816439 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: Content-type: image/jpeg
01/14/22 23:07:09.816452 zmc_m1[114920].DB6-zm_curl_camera.cpp/398 [Content-Type is: image/jpeg
01/14/22 23:07:09.816459 zmc_m1[114920].DB7-zm_curl_camera.cpp/408 [Content type matched as image/jpeg]
01/14/22 23:07:09.816466 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: Content-Length: 151525
01/14/22 23:07:09.816471 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: X-Frame-Options: SAMEORIGIN
01/14/22 23:07:09.816476 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: Date: Sat, 15 Jan 2022 05:07:07 GMT
01/14/22 23:07:09.816480 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header:
01/14/22 23:07:10.035823 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: HTTP/1.1 200 OK
01/14/22 23:07:10.035870 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: Content-type: image/jpeg
01/14/22 23:07:10.035879 zmc_m1[114920].DB6-zm_curl_camera.cpp/398 [Content-Type is: image/jpeg
01/14/22 23:07:10.035885 zmc_m1[114920].DB7-zm_curl_camera.cpp/408 [Content type matched as image/jpeg]
01/14/22 23:07:10.035891 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: Content-Length: 151525
01/14/22 23:07:10.035897 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: X-Frame-Options: SAMEORIGIN
01/14/22 23:07:10.035902 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: Date: Sat, 15 Jan 2022 05:07:07 GMT
01/14/22 23:07:10.035907 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header:
01/14/22 23:07:10.262223 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: HTTP/1.1 200 OK
01/14/22 23:07:10.262271 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: Content-type: image/jpeg
01/14/22 23:07:10.262279 zmc_m1[114920].DB6-zm_curl_camera.cpp/398 [Content-Type is: image/jpeg
01/14/22 23:07:10.262285 zmc_m1[114920].DB7-zm_curl_camera.cpp/408 [Content type matched as image/jpeg]
01/14/22 23:07:10.262291 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: Content-Length: 151199
01/14/22 23:07:10.262297 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: X-Frame-Options: SAMEORIGIN
01/14/22 23:07:10.262302 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header: Date: Sat, 15 Jan 2022 05:07:08 GMT
01/14/22 23:07:10.262306 zmc_m1[114920].DB4-zm_curl_camera.cpp/383 [Got header:
01/14/22 23:07:10.304280 zmc_m1[114917].ERR-zmc.cpp/259 [Failed to prime capture of initial monitor]
I see zm_curl_camera.cpp had a fix pushed on Oct 7. And looking at my line numbers in the log, doesn't seem like that commit made it into the release. Is that correct? And if so, is there a future release that this needs to go into? Anything I can do to help?
User avatar
iconnor
Posts: 1917
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: CURL source not working on fresh install 1.36.12

Post by iconnor »

Perhaps it will go into 1.36.13.

You could in the meantime use the remote monitor type.

The curl monitor type is likely to go away. There really isn't any point to it existing.
sergeys
Posts: 2
Joined: Sat Jan 15, 2022 4:49 am

Re: CURL source not working on fresh install 1.36.12

Post by sergeys »

Oh, didn't see that I can use a snapshot URL for remote camera type. I'll try that.

But yes, in the meantime, I installed a dev build of 1.37, and it's working.

Thanks!
Post Reply