"Blue Screen" issue

Forum for questions and support relating to the 1.30.x releases only.
Post Reply
francis3
Posts: 9
Joined: Wed Jan 16, 2019 8:30 am

"Blue Screen" issue

Post by francis3 » Thu Feb 14, 2019 2:10 pm

Hi all,
quite new setup here,
as described in my previous forum post:

viewtopic.php?f=36&t=27960

It runs quite well now and I'm really happy with it.

But every now and then (maybe every 3/4 days), now 7 days from the last event
one of the two monitors shows the "blue screen".

I've checked the stream from the camera with an external program (vlc), an the video is fine.
In the meantime the system is not loaded at all.

To get the image again I have to disable the monitor then re-enable it, or restart ZM.

Here the logs of today's event:

[

Code: Select all

Feb 14 11:10:18 zm zma_m2[9968]: INF [Monitor-2: 1522 - Gone into alarm state]
Feb 14 11:10:18 zm zma_m2[9968]: INF [Monitor-2: 1522 - Opening new event 20161, alarm start]
Feb 14 11:10:23 zm zma_m2[9968]: INF [Monitor-2: 1544 - Gone into alert state]
Feb 14 11:10:24 zm zma_m2[9968]: INF [Monitor-2: 1552 - Gone back into alarm state]
Feb 14 11:10:30 zm zma_m2[9968]: INF [Monitor-2: 1580 - Gone into alert state]
Feb 14 11:10:30 zm zma_m2[9968]: INF [Monitor-2: 1582 - Gone back into alarm state]
Feb 14 11:10:31 zm zma_m2[9968]: INF [Monitor-2: 1587 - Gone into alert state]
Feb 14 11:10:36 zm zma_m2[9968]: INF [Monitor-2: 1612 - Left alarm state (20161) - 115(55) images]
Feb 14 11:10:36 zm zma_m2[9968]: INF [Monitor-2: 1612 - Closing event 20161, alarm end]
Feb 14 11:10:59 zm zma_m1[32136]: INF [Monitor-1: 859000 - Analysing at 5.00 fps]
Feb 14 11:11:43 zm zmc_m2[9936]: INF [Monitor-2: 2000 - Capturing at 4.98 fps]
Feb 14 11:11:54 zm zma_m2[9968]: INF [Monitor-2: 2000 - Analysing at 5.03 fps]
Feb 14 11:13:20 zm zmc_m1[1080]: INF [Monitor-1: 1232000 - Capturing at 5.00 fps]
Feb 14 11:14:18 zm zma_m1[32136]: INF [Monitor-1: 860000 - Analysing at 5.03 fps]
Feb 14 11:14:24 zm zmwatch[9309]: INF [Restarting capture daemon for Monitor-2, time since last capture 12 seconds (1550139264-1550139252)]
Feb 14 11:14:24 zm zmdc[9244]: INF ['zmc -m 2' sending stop to pid 9936 at 19/02/14 11:14:24]
Feb 14 11:14:24 zm zmc_m2[9936]: INF [Got signal 15 (Terminated), exiting]
Feb 14 11:14:30 zm zmdc[9244]: WAR ['zmc -m 2' has not stopped at 19/02/14 11:14:30. Sending KILL to pid 9936]
Feb 14 11:14:30 zm zmdc[9244]: INF ['zmc -m 2' crashed, signal 8]
Feb 14 11:14:40 zm zmdc[9244]: INF [Starting pending process, zmc -m 2]
Feb 14 11:14:40 zm zmdc[9244]: INF ['zmc -m 2' starting at 19/02/14 11:14:40, pid = 11068]
Feb 14 11:14:40 zm zmdc[11068]: INF ['zmc -m 2' started at 19/02/14 11:14:40]
Feb 14 11:14:40 zm zmc_m2[11068]: INF [Starting Capture version 1.30.4]
Feb 14 11:14:40 zm zmc_m2[11068]: INF [Priming capture from rtsp://xxxxxxxxx:xxxxxxxxx@192.168.1.252:554/videoMain]
Feb 14 11:15:12 zm zmc_m2[11068]: INF [av_read_frame returned "End of file". Reopening stream.]
Feb 14 11:15:12 zm zma_m2[9968]: WAR [Signal: Lost]
Feb 14 11:16:05 zm zma_m2[9968]: INF [Monitor-2: 3000 - Analysing at 3.98 fps]
Feb 14 11:16:40 zm zmc_m1[1080]: INF [Monitor-1: 1233000 - Capturing at 5.00 fps]
Feb 14 11:17:38 zm zma_m1[32136]: INF [Monitor-1: 861000 - Analysing at 5.00 fps]
Feb 14 11:17:58 zm zmc_m2[11068]: INF [Monitor-2: 1000 - Capturing at 5.05 fps]
Feb 14 11:18:51 zm zma_m2[9968]: INF [Monitor-2: 4000 - Analysing at 6.02 fps]
Feb 14 11:20:00 zm zmc_m1[1080]: INF [Monitor-1: 1234000 - Capturing at 5.00 fps]

Best way to deal with the issue?
Maybe a script that periodically check the logs and restart zoneminder?
Or a curl call to disable and then re-enable the camera?
From what I understand reading the logs the monitor is working fine.
Except from:

Code: Select all

 WAR [Signal: Lost]
Btw, after the warning, monitor2 seems Capturing and Analyzing just fine:

Code: Select all

Feb 14 11:17:38 zm zma_m1[32136]: INF [Monitor-1: 861000 - Analysing at 5.00 fps]
Feb 14 11:17:58 zm zmc_m2[11068]: INF [Monitor-2: 1000 - Capturing at 5.05 fps]
Feb 14 11:18:51 zm zma_m2[9968]: INF [Monitor-2: 4000 - Analysing at 6.02 fps]
Feb 14 11:20:00 zm zmc_m1[1080]: INF [Monitor-1: 1234000 - Capturing at 5.00 fps]
Feb 14 11:20:44 zm zmc_m2[11068]: INF [Monitor-2: 2000 - Capturing at 6.02 fps]
Feb 14 11:20:58 zm zma_m1[32136]: INF [Monitor-1: 862000 - Analysing at 5.00 fps]
Feb 14 11:21:38 zm zma_m2[9968]: INF [Monitor-2: 5000 - Analysing at 5.99 fps]
Feb 14 11:23:20 zm zmc_m1[1080]: INF [Monitor-1: 1235000 - Capturing at 5.00 fps]
Feb 14 11:23:31 zm zmc_m2[11068]: INF [Monitor-2: 3000 - Capturing at 5.99 fps]
Feb 14 11:24:18 zm zma_m1[32136]: INF [Monitor-1: 863000 - Analysing at 5.00 fps]
Feb 14 11:24:24 zm zma_m2[9968]: INF [Monitor-2: 6000 - Analysing at 6.02 fps]
Feb 14 11:26:18 zm zmc_m2[11068]: INF [Monitor-2: 4000 - Capturing at 5.99 fps]
Feb 14 11:26:40 zm zmc_m1[1080]: INF [Monitor-1: 1236000 - Capturing at 5.00 fps]
Feb 14 11:27:11 zm zma_m2[9968]: INF [Monitor-2: 7000 - Analysing at 5.99 fps]
Feb 14 11:27:38 zm zma_m1[32136]: INF [Monitor-1: 864000 - Analysing at 5.00 fps]
Feb 14 11:29:04 zm zmc_m2[11068]: INF [Monitor-2: 5000 - Capturing at 6.02 fps]
Feb 14 11:29:58 zm zma_m2[9968]: INF [Monitor-2: 8000 - Analysing at 5.99 fps]
Feb 14 11:30:00 zm zmc_m1[1080]: INF [Monitor-1: 1237000 - Capturing at 5.00 fps]
Feb 14 11:30:58 zm zma_m1[32136]: INF [Monitor-1: 865000 - Analysing at 5.00 fps]
Feb 14 11:31:51 zm zmc_m2[11068]: INF [Monitor-2: 6000 - Capturing at 5.99 fps]
Feb 14 11:32:44 zm zma_m2[9968]: INF [Monitor-2: 9000 - Analysing at 6.02 fps]
Feb 14 11:32:53 zm zmaudit[9302]: INF [Deleted 70 log table entries by time]
Feb 14 11:33:20 zm zmc_m1[1080]: INF [Monitor-1: 1238000 - Capturing at 5.00 fps]
Feb 14 11:34:18 zm zma_m1[32136]: INF [Monitor-1: 866000 - Analysing at 5.00 fps]
Feb 14 11:34:37 zm zmc_m2[11068]: INF [Monitor-2: 7000 - Capturing at 6.02 fps]
Feb 14 11:35:31 zm zma_m2[9968]: INF [Monitor-2: 10000 - Analysing at 5.99 fps]
Feb 14 11:36:40 zm zmc_m1[1080]: INF [Monitor-1: 1239000 - Capturing at 5.00 fps]
Feb 14 11:37:24 zm zmc_m2[11068]: INF [Monitor-2: 8000 - Capturing at 5.99 fps]
Feb 14 11:37:38 zm zma_m1[32136]: INF [Monitor-1: 867000 - Analysing at 5.00 fps]
Feb 14 11:38:17 zm zma_m2[9968]: INF [Monitor-2: 11000 - Analysing at 6.02 fps]
Feb 14 11:40:00 zm zmc_m1[1080]: INF [Monitor-1: 1240000 - Capturing at 5.00 fps]
Feb 14 11:40:10 zm zmc_m2[11068]: INF [Monitor-2: 9000 - Capturing at 6.02 fps]
Feb 14 11:40:58 zm zma_m1[32136]: INF [Monitor-1: 867996 - Gone into alarm state]


Any help would be appreciated.


Regards,
francis3

User avatar
snake
Posts: 153
Joined: Sat May 21, 2016 2:20 am

Re: "Blue Screen" issue

Post by snake » Thu Feb 14, 2019 5:37 pm

This has been addressed before. It boils down to this:

Some types of cameras will occasionally drop out. Other brands are not affected.
Developers are aware of the issue.

You have a couple of options, including: upgrading to newer ZM, making a script via API that restarts lost cameras, using modect, using a different brand of camera, adjusting ZMWATCH.pl timeout level in options... If you are interested in more discussion, search the forums.

What I do is:
Change zmwatch.pl timeout to a higher number (MAX_RESTART_DELAY is the name of the config)
Change affected cameras to modect, which appears to work better for me.


Just curious, what brand / model of camera do you have?

francis3
Posts: 9
Joined: Wed Jan 16, 2019 8:30 am

Re: "Blue Screen" issue

Post by francis3 » Fri Feb 15, 2019 1:40 pm

Hi snake!!!
Thank you for your kind answer!

The cameras are a couple of Foscam Cube Model C1 v3
with the last available firmware.

It's a budget choice, but the image quality is not bad for my purposes.
Btw, I have to say the plugin issue to gain control of the cameras via HTTP interface is an absolute nightmare.

They are starting point for my ZM project, gonna get more serious cameras asap.

To solve the issue, I'm gonna start with the easy option.
Modifying the suggested parameter MAX_RESTART_DELAY, going to double the default value of 600.

The two cameras are already working in modect mode.

Then I'm gonna investigate the API. But how do I spot a lost camera? From the logs posted above, to me, after the event,
end the warning

Code: Select all

WAR [Signal: Lost]
the camera is working fine


Again thx,
francis3

bbunge
Posts: 2315
Joined: Mon Mar 26, 2012 11:40 am
Location: Pennsylvania

Re: "Blue Screen" issue

Post by bbunge » Fri Feb 15, 2019 2:28 pm

If you are using rtsp try forcing tcp.

francis3
Posts: 9
Joined: Wed Jan 16, 2019 8:30 am

Re: "Blue Screen" issue

Post by francis3 » Fri Feb 15, 2019 4:30 pm

Yes, I'm using rtsp.
And the remote method is already TCP.


Thx bbunge,
francis3

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests