Camera disappears after "Gone into alert state"

[Sigge]

It comes back if I restart Zoneminder.

Were can I get more debug info on this?

Thanks,

2018-06-12 10:44:38.973868 zma_m8 1631 INF Monitor-8: 862804 - Gone into alert state zm_monitor.cpp 1704

[Sigge]

To clarify: Can I switch on debug for all m8? Can only see instruction for setting it per component not per monitor.

[rockedge]

describe what "disappears" means. The camera stream stops and/or the camera crashes?

[Sigge]

Well, monitor page is blank. Also blank (missing) in montage view. Not blue, no broken link symbol. And no more log entry's after "Gone into alert state".

[bbunge]

Linux distro and version? Instructions used to install Zoneminder? Also, tell us about your server hardware: processor, RAM, size of hard drive and etc...

[Sigge]

Ok its:
xubuntu, 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
HW: i5, 8 Gb ram, 256 GB ssd.
It is installed many years ago using the easy way guide.
The monitor get its feed from a live555proxy process and is configured as Ffmpeg.

What processes can be interesting at and after "gone into alert state"?

The error can come after a long time of good function so I do not want to turn on to much debugging.

Thanks,

[Sigge]

So I added this for debug logging.
_zmc_m8|_zma_m8

Now I wait ....

[bbunge]

Ok its:
xubuntu, 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
HW: i5, 8 Gb ram, 256 GB ssd.
It is installed many years ago using the easy way guide.
The monitor get its feed from a live555proxy process and is configured as Ffmpeg.

What processes can be interesting at and after "gone into alert state"?

The error can come after a long time of good function so I do not want to turn on to much debugging.

Thanks,

Xubuntu is a desktop version of Ubuntu, 4.13.0-45 is the Linux kernel not the distro version. Which easy version from the WIKI? There have been many changes over the years...

[Sigge]

Yes, it was xubuntu 16.04 at the time. I do not remember exactly the install procedure. It is now upgraded to17.10.

I am now watching zmc and zmf with debug level 2. But for now the monitor works. So I am waiting.....

[Sigge]

Ok, so now the monitor has disappeared. My debug log does not say anything to me. Looks like zma crashes in the middle of writing a log entry?

Any idea what I should do more?

Thanks,

Here are some logs:
Web UI:
2018-06-17 12:43:04.329842 zma_m8 8846 INF Monitor-8: 420000 - Analysing at 5.00 fps zm_monitor.cpp 1296
2018-06-17 12:39:44.311780 zma_m8 8846 INF Monitor-8: 419000 - Analysing at 5.00 fps zm_monitor.cpp 1296
2018-06-17 12:36:24.333841 zma_m8 8846 INF Monitor-8: 418000 - Analysing at 5.00 fps zm_monitor.cpp 1296
2018-06-17 12:33:04.339252 zma_m8 8846 INF Monitor-8: 417000 - Analysing at 5.00 fps zm_monitor.cpp 1296
2018-06-17 12:29:44.340933 zma_m8 8846 INF Monitor-8: 416000 - Analysing at 5.00 fps zm_monitor.cpp 1296
2018-06-17 12:28:57.308596 zma_m8 8846 INF Monitor-8: 415765 - Gone into prealarm state zm_monitor.cpp 1689
2018-06-17 12:26:24.319156 zma_m8 8846 INF Monitor-8: 415000 - Analysing at 5.00 fps zm_monitor.cpp 1296

2018-06-17 12:45:27.959634 zmc_m8 18593 INF Priming capture from rtsp://192.168.2.100:8554/proxyStream zm_ffmpeg_camera.cpp 104
2018-06-17 12:45:27.955679 zmc_m8 18593 INF Starting Capture version 1.30.4 zmc.cpp 247
2018-06-17 12:45:21.478220 zmc_m8 12669 INF Got signal 15 (Terminated), exiting zm_signal.cpp 40
2018-06-17 12:42:37.704154 zmc_m8 12669 INF Monitor-8: 225000 - Capturing at 5.00 fps zm_monitor.cpp 3125
2018-06-17 12:39:17.709339 zmc_m8 12669 INF Monitor-8: 224000 - Capturing at 5.00 fps zm_monitor.cpp 3125
2018-06-17 12:35:57.699740 zmc_m8 12669 INF Monitor-8: 223000 - Capturing at 5.00 fps zm_monitor.cpp 3125
2018-06-17 12:32:37.692115 zmc_m8 12669 INF Monitor-8: 222000 - Capturing at 5.00 fps zm_monitor.cpp 3125

/var/log/zm/debug:

06/17/18 12:45:08.113867 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Bortre]
06/17/18 12:45:08.114247 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Mellersta]
06/17/18 12:45:08.114640 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone UpperRight]
06/17/18 12:45:08.115000 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Terrass]
06/17/18 12:45:08.342002 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Bortre]
06/17/18 12:45:08.342354 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Mellersta]
06/17/18 12:45:08.342731 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone UpperRight]
06/17/18 12:45:08.343069 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Terrass]
06/17/18 12:45:08.536916 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Bortre]
06/17/18 12:45:08.537364 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Mellersta]
06/17/18 12:45:08.537911 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone UpperRight]
06/17/18 12:45:08.538383 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Terrass]
06/17/18 12:45:08.832948 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Bortre]
06/17/18 12:45:08.833297 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Mellersta]
06/17/18 12:45:08.833678 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone UpperRight]
06/17/18 12:45:08.834021 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Terrass]
06/17/18 12:45:08.928250 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Bortre]
06/17/18 12:45:08.928705 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active zone Mellersta]
06/17/18 12:45:08.929219 zma_m8[8846].DB3-zm_monitor.cpp/3308 [Checking active

[Sigge]

I still have zmc and zma processes running:

www-data 8846 1.4 13.3 1517968 1076364 ? S giu16 46:54 /usr/bin/zma -m 8
www-data 18593 0.0 10.3 1267024 832356 ? S giu17 0:13 /usr/bin/zmc -m 8

When I click on the problematic monitor link the zms doesn't appear in the ps list. For a working monitor, the nph-zms starts.

[Sigge]

I have changed the Swap path to: /dev/shm and the problem seems to have disappeared.

[Sigge]

This problem still exists. Looks like somethings gone wrong between live555proxy and zmc.

Anyone have a clue or can point me in some direction?

06/27/18 16:46:34.814917 zmc_m8[21411].Using network protocols without global network initialization. Please use avformat_network_init(), this will become mandatory later.
Using network protocols without global network initialization. Please use avformat_network_init(), this will become mandatory later.
[tcp @ 0x56307fb993e0] No default whitelist set
[rtsp @ 0x56307fb97240] SDP:
v=0
o=- 1529619463341213 1 IN IP4 127.0.1.1
s=LIVE555 Streaming Media v2017.01.26
i=LIVE555 Streaming Media v2017.01.26
t=0 0
a=tool:LIVE555 Streaming Media v2017.01.26
a=type:broadcast
a=control:*
a=range:npt=0-
a=x-qt-text-nam:LIVE555 Streaming Media v2017.01.26
a=x-qt-text-inf:LIVE555 Streaming Media v2017.01.26
m=video 0 RTP/AVP 96
c=IN IP4 0.0.0.0
b=AS:4
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=4D0029;sprop-parameter-sets=R00AKZmgHgCJ+WEAAAMD6AAAJxCE,SO48gA==
a=control:track1

Failed to parse interval end specification ''
[rtsp @ 0x56307fb97240] video codec set to: h264
[rtsp @ 0x56307fb97240] RTP Packetization Mode: 1
[rtsp @ 0x56307fb97240] RTP Profile IDC: 4d Profile IOP: 0 Level: 29
[rtsp @ 0x56307fb97240] Extradata set to 0x56307fb99210 (size: 33)
[rtsp @ 0x56307fb97240] setting jitter buffer size to 0
[rtsp @ 0x56307fb97240] hello state=0
Failed to parse interval end specification ''
[h264 @ 0x56307fb9ab00] nal_unit_type: 7, nal_ref_idc: 2
[h264 @ 0x56307fb9ab00] nal_unit_type: 8, nal_ref_idc: 2

[Sigge]

I am upgrading live555 to see if that makes a difference.

[Sigge]

The camera is still dropping out. Same zmc log. Zmc is running but uses 0 cpu. Same with zma. No zmf process.

Still getting the same zmc log:
07/02/18 18:47:13.260321 zmc_m8[21774].Using network protocols without global network initialization. Please use avformat_network_init(), this will become mandatory later.
Using network protocols without global network initialization. Please use avformat_network_init(), this will become mandatory later.
[tcp @ 0x56460e4b03e0] No default whitelist set
[rtsp @ 0x56460e4ae240] SDP:
v=0
o=- 1530222990565680 1 IN IP4 127.0.1.1
s=LIVE555 Streaming Media v2018.04.25
i=LIVE555 Streaming Media v2018.04.25
t=0 0
a=tool:LIVE555 Streaming Media v2018.04.25
a=type:broadcast
a=control:*
a=range:npt=0-
a=x-qt-text-nam:LIVE555 Streaming Media v2018.04.25
a=x-qt-text-inf:LIVE555 Streaming Media v2018.04.25
m=video 0 RTP/AVP 96
c=IN IP4 0.0.0.0
b=AS:4
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=4D0029;sprop-parameter-sets=R00AKZmgHgCJ+WEAAAMD6AAAD6CE,SO48gA==
a=control:track1

Failed to parse interval end specification ''
[rtsp @ 0x56460e4ae240] video codec set to: h264
[rtsp @ 0x56460e4ae240] RTP Packetization Mode: 1
[rtsp @ 0x56460e4ae240] RTP Profile IDC: 4d Profile IOP: 0 Level: 29
[rtsp @ 0x56460e4ae240] Extradata set to 0x56460e4b0210 (size: 33)
[rtsp @ 0x56460e4ae240] setting jitter buffer size to 0
[rtsp @ 0x56460e4ae240] hello state=0
Failed to parse interval end specification ''
[h264 @ 0x56460e4b1b00] nal_unit_type: 7, nal_ref_idc: 2
[h264 @ 0x56460e4b1b00] nal_unit_type: 8, nal_ref_idc: 2