Zoneminder monitor went from working to blue screen; changing from hostname to IP fixed issue. Why?

[scott.borisch]

Hello,

My zoneminder installation had been working fine for weeks, and then it suddenly started returning a blue screen. I tried rebooting the PC and power cycling the camera but it had no effect. I could see the Amcrest Android app still worked so didn't look like a camera issue. I then changed "Source => Source Path" from using the hostname back to using the IP address (xxx.xxx.xxx.xxx). That fixed the issue. I then changed back to the hostname again, and it still kept working. Any idea why this happened? I want to prevent it from happening again. Below is the log just before I fixed the issue.
The reason I am using hostname is the camera is on DHCP and hence the IP address might change (and has). I suspect it may be possible to configure the camera for static IP -- I have not checked. But I only see a reason to do this if there is some known issue with using hostname.
Thanks.

2017-05-16 06:16:03.460266 zmc_m1 3359 WAR Buffer overrun at index 16, image 138366, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:16:03.387467 zma_m1 3516 INF driveway_cam: 75000 - Analysing at 250.00 fps zm_monitor.cpp 1296
2017-05-16 06:16:02.783679 zmc_m1 3359 INF driveway_cam: 138000 - Capturing at 1000.00 fps zm_monitor.cpp 3125
2017-05-16 06:16:01.075456 zmc_m1 3359 INF driveway_cam: 137000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:16:00.330576 zmc_m1 3359 WAR Last image read from shared memory 1 seconds ago, zma may have gone away zm_monitor.cpp 3100
2017-05-16 06:16:00.227681 zmc_m1 3359 WAR Buffer overrun at index 37, image 136587, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:16:00.063568 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:16:00.026338 zmc_m1 3359 WAR Buffer overrun at index 37, image 136537, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:59.974248 zma_m1 3516 INF driveway_cam: 74000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:59.000968 zmc_m1 3359 INF driveway_cam: 136000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:57.298226 zmc_m1 3359 INF driveway_cam: 135000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:56.746748 zmc_m1 3359 WAR Buffer overrun at index 32, image 134732, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:56.574656 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:56.440828 zmc_m1 3359 WAR Buffer overrun at index 32, image 134682, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:56.363025 zma_m1 3516 INF driveway_cam: 73000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:55.241333 zmc_m1 3359 INF driveway_cam: 134000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:53.573266 zmc_m1 3359 INF driveway_cam: 133000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:53.214737 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:53.213246 zmc_m1 3359 WAR Buffer overrun at index 17, image 132817, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:53.143753 zma_m1 3516 INF driveway_cam: 72000 - Analysing at 250.00 fps zm_monitor.cpp 1296
2017-05-16 06:15:51.783789 zmc_m1 3359 INF driveway_cam: 132000 - Capturing at 1000.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:50.014511 zmc_m1 3359 INF driveway_cam: 131000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:49.887620 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:49.881651 zmc_m1 3359 WAR Buffer overrun at index 27, image 130977, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:49.818913 zma_m1 3516 INF driveway_cam: 71000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:48.237132 zmc_m1 3359 INF driveway_cam: 130000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:48.007713 zmc_m1 3676 ERR Unable to open input rtsp://admin:admin@AMC00309F89098ZPW4:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif due to: Operation now in progress zm_ffmpeg_camera.cpp 269
2017-05-16 06:15:46.810890 zmc_m1 3359 WAR Buffer overrun at index 20, image 129170, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:46.637353 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:46.605156 zmc_m1 3359 WAR Buffer overrun at index 20, image 129120, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:46.559500 zma_m1 3516 INF driveway_cam: 70000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:46.336032 zmc_m1 3359 INF driveway_cam: 129000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:44.660059 zmc_m1 3359 INF driveway_cam: 128000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:43.482549 zmc_m1 3359 WAR Buffer overrun at index 20, image 127320, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:43.310909 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:43.304190 zmc_m1 3359 WAR Buffer overrun at index 20, image 127270, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:43.234092 zma_m1 3516 INF driveway_cam: 69000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:42.742002 zmc_m1 3359 INF driveway_cam: 127000 - Capturing at 1000.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:41.068351 zmc_m1 3359 INF driveway_cam: 126000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:40.157002 zma_m1 3516 INF driveway_cam: 68000 - Analysing at 250.00 fps zm_monitor.cpp 1296
2017-05-16 06:15:39.241742 zmc_m1 3359 INF driveway_cam: 125000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:37.897840 zmc_m1 3676 ERR Unable to open input rtsp://admin:admin@AMC00309F89098ZPW4:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif due to: Operation now in progress zm_ffmpeg_camera.cpp 269
2017-05-16 06:15:37.525075 zmc_m1 3359 INF driveway_cam: 124000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:36.865126 zmc_m1 3359 WAR Buffer overrun at index 14, image 123664, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:36.666266 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:36.609038 zmc_m1 3359 WAR Buffer overrun at index 14, image 123614, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:36.547421 zma_m1 3516 INF driveway_cam: 67000 - Analysing at 250.00 fps zm_monitor.cpp 1296
2017-05-16 06:15:35.432900 zmc_m1 3359 INF driveway_cam: 123000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:33.691330 zmc_m1 3359 INF driveway_cam: 122000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:33.298549 zmc_m1 3359 WAR Last image read from shared memory 1 seconds ago, zma may have gone away zm_monitor.cpp 3100
2017-05-16 06:15:33.195915 zmc_m1 3359 WAR Buffer overrun at index 44, image 121794, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:33.023207 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:33.011436 zmc_m1 3359 WAR Buffer overrun at index 44, image 121744, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:32.937862 zma_m1 3516 INF driveway_cam: 66000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:31.704774 zmc_m1 3359 INF driveway_cam: 121000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:30.784540 zmc_m1 3676 ERR Unable to open input rtsp://admin:admin@AMC00309F89098ZPW4:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif due to: Operation now in progress zm_ffmpeg_camera.cpp 269
2017-05-16 06:15:29.966934 zmc_m1 3359 INF driveway_cam: 120000 - Capturing at 1000.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:29.772705 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:29.684046 zmc_m1 3359 WAR Buffer overrun at index 32, image 119882, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:29.620950 zma_m1 3516 INF driveway_cam: 65000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:28.156478 zmc_m1 3359 INF driveway_cam: 119000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:26.538229 zma_m1 3516 INF driveway_cam: 64000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:26.427866 zmc_m1 3359 INF driveway_cam: 118000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:24.517970 zmc_m1 3359 INF driveway_cam: 117000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:23.195437 zma_m1 3516 INF driveway_cam: 63000 - Analysing at 250.00 fps zm_monitor.cpp 1296
2017-05-16 06:15:22.733103 zmc_m1 3359 INF driveway_cam: 116000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:20.959073 zmc_m1 3359 INF driveway_cam: 115000 - Capturing at 1000.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:20.688508 zmc_m1 3676 ERR Unable to open input rtsp://admin:admin@AMC00309F89098ZPW4:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif due to: Operation now in progress zm_ffmpeg_camera.cpp 269
2017-05-16 06:15:19.987832 zma_m1 3516 INF driveway_cam: 62000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:19.203756 zmc_m1 3359 INF driveway_cam: 114000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:17.386658 zmc_m1 3359 INF driveway_cam: 113000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:16.730899 zmc_m1 3359 WAR Buffer overrun at index 32, image 112682, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:16.546519 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:16.512636 zmc_m1 3359 WAR Buffer overrun at index 32, image 112632, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:16.459933 zma_m1 3516 INF driveway_cam: 61000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:15.360084 zmc_m1 3359 INF driveway_cam: 112000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:13.555905 zmc_m1 3359 INF driveway_cam: 111000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:13.242716 zma_m1 3516 INF driveway_cam: 60000 - Analysing at 250.00 fps zm_monitor.cpp 1296
2017-05-16 06:15:11.693114 zmc_m1 3359 INF driveway_cam: 110000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:10.596554 zmc_m1 3676 ERR Unable to open input rtsp://admin:admin@AMC00309F89098ZPW4:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif due to: Operation now in progress zm_ffmpeg_camera.cpp 269
2017-05-16 06:15:09.942900 zmc_m1 3359 INF driveway_cam: 109000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:09.852943 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:09.620903 zmc_m1 3359 WAR Buffer overrun at index 46, image 108946, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:09.542399 zma_m1 3516 INF driveway_cam: 59000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:07.972450 zmc_m1 3359 INF driveway_cam: 108000 - Capturing at 1000.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:06.360032 zmc_m1 3359 WAR Buffer overrun at index 46, image 107096, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:06.185273 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:15:06.172353 zmc_m1 3359 WAR Buffer overrun at index 46, image 107046, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:15:06.033063 zma_m1 3516 INF driveway_cam: 58000 - Analysing at 250.00 fps zm_monitor.cpp 1296
2017-05-16 06:15:06.017687 zmc_m1 3359 INF driveway_cam: 107000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:04.081047 zmc_m1 3359 INF driveway_cam: 106000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:02.715588 zma_m1 3516 INF driveway_cam: 57000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:15:02.306639 zmc_m1 3359 INF driveway_cam: 105000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:15:00.492578 zmc_m1 3676 ERR Unable to open input rtsp://admin:admin@AMC00309F89098ZPW4:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif due to: Operation now in progress zm_ffmpeg_camera.cpp 269
2017-05-16 06:15:00.402820 zmc_m1 3359 INF driveway_cam: 104000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:14:59.434928 zmc_m1 3359 WAR Buffer overrun at index 23, image 103473, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:14:59.249998 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:14:59.217251 zmc_m1 3359 WAR Buffer overrun at index 23, image 103423, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:14:59.139685 zma_m1 3516 INF driveway_cam: 56000 - Analysing at 250.00 fps zm_monitor.cpp 1296
2017-05-16 06:14:58.431793 zmc_m1 3359 INF driveway_cam: 103000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:14:56.671827 zmc_m1 3359 INF driveway_cam: 102000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:14:55.807352 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:14:55.797946 zmc_m1 3359 WAR Buffer overrun at index 41, image 101541, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:14:55.730331 zma_m1 3516 INF driveway_cam: 55000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:14:54.770703 zmc_m1 3359 INF driveway_cam: 101000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:14:52.998028 zmc_m1 3359 INF driveway_cam: 100000 - Capturing at 1000.00 fps zm_monitor.cpp 3125
2017-05-16 06:14:52.451346 zmc_m1 3359 WAR Buffer overrun at index 30, image 99730, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:14:52.272873 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:14:52.270925 zmc_m1 3359 WAR Buffer overrun at index 30, image 99680, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:14:52.193166 zma_m1 3516 INF driveway_cam: 54000 - Analysing at 250.00 fps zm_monitor.cpp 1296
2017-05-16 06:14:51.093910 zmc_m1 3359 INF driveway_cam: 99000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:14:50.392534 zmc_m1 3676 ERR Unable to open input rtsp://admin:admin@AMC00309F89098ZPW4:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif due to: Operation now in progress zm_ffmpeg_camera.cpp 269
2017-05-16 06:14:49.321887 zmc_m1 3359 INF driveway_cam: 98000 - Capturing at 500.00 fps zm_monitor.cpp 3125
2017-05-16 06:14:48.936993 zmc_m1 3359 WAR Buffer overrun at index 35, image 97835, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:14:48.853082 zma_m1 3516 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1324
2017-05-16 06:14:48.731451 zmc_m1 3359 WAR Buffer overrun at index 35, image 97785, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 3094
2017-05-16 06:14:48.674382 zma_m1 3516 INF driveway_cam: 53000 - Analysing at 333.33 fps zm_monitor.cpp 1296
2017-05-16 06:14:47.307378 zmc_m1 3359 INF driveway_cam: 97000 - Capturing at 500.00 fps zm_monitor.cpp 3125

[bbunge]

Sounds like you have a network issue and not a So reminder issue. Use your router to assign an IP address to devices you want to remain constant.

[mikb]

This is indeed a networking issue, it sounds like the IP address changed, so ZM was looking at where the camera *was* ... I second the idea of keeping things static-IP wherever possible, to avoid surprises like this.

Now, shifting the blame back to Zoneminder

How often does Zoneminder "look up" the hostname to get the IP address? Is it cacheing this information, such that an IP address change would never be caught until ... ZM restarts? Or would stopping and restarting a camera cause a new lookup? Maybe, on errors such as "camera is not contactable", it might be good to repeat the DNS lookup.

[bbunge]

As I said, it Is not a Zoneminder issue. If you are using a host name you should look to your local DNS to find out how often it resolves name to IP. Static or assigned for cameras on local LAN is always best.

[scott.borisch]

Putting the camera on static IP is fine so long as it supports it, which I expect it will.

[scott.borisch]

Confirmed, it does.