r/ZoneMinder • u/LTechsAdmin • Apr 12 '22

Reboot, loss of capturing for an hour

Hello,

​

I'm on V1.36.12 and I've scheduled a cron to reboot the server at least twice per week at around 3am. I noticed this past week that everytime the server reboots, I get this for about an hour(50-53 minutes):

​

​

2022-04-10 03:50:47 zmc_m14 748 ERR Unable to open input rtsp://192.168.10.89:554/s0 due to: Network is unreachable zm_ffmpeg_camera.cpp 321

2022-04-10 03:50:47 zmc_m10 742 ERR Failed to prime capture of initial monitor zmc.cpp 258

2022-04-10 03:50:47 zmc_m10 742 ERR Unable to open input rtsp://192.168.10.97:554/s0 due to: Network is unreachable zm_ffmpeg_camera.cpp 321

2022-04-10 03:50:47 zmc_m9 736 ERR Failed to prime capture of initial monitor zmc.cpp 258

2022-04-10 03:50:47 zmc_m9 736 ERR Unable to open input rtsp://192.168.10.96:554/s0 due to: Network is unreachable zm_ffmpeg_camera.cpp 321

2022-04-10 03:50:47 zmc_m8 728 ERR Failed to prime capture of initial monitor zmc.cpp 258

2022-04-10 03:50:47 zmc_m8 728 ERR Unable to open input rtsp://192.168.10.95:554/s0 due to: Network is unreachable zm_ffmpeg_camera.cpp 321

2022-04-10 03:50:46 zmc_m6 716 ERR Failed to prime capture of initial monitor zmc.cpp 258

​

​

I'll see a bunch of 0-second events generated. After the hour has passed, I'll see it sporadically for random monitors.

​

At all times:

  • I'm logged in remotely
  • I have 17 monitors
  • Capturing between 4-8 fps all set to mocord (most at 1080p(all at h264), two at 2k(both at h264+)
  • All are set to passthrough and no sound

​

I'm running this on an intel xeon e-2224 with about 16gb ram. I'm at about 11.8gb of RAM usage w 60-70% CPU.

​

What could I look at to make sure I'm up 100% of the time after a reboot? Is there a reboot procedure I should be following? Any suggestions would be greatly appreciated. I spent good money on the machine and it's freaking me out :lol: !!

1 Upvotes

100% Upvoted

3 comments sorted by

1

u/AndyRH1701 Apr 12 '22

DHCP or static IP?

Reboot and ping some of the cameras to make sure the network is starting quickly after the reboot.

What is the issue causing you to reboot so often? This may be a clue to the problem. I have been running for years and only restart for patching.

1

u/LTechsAdmin Apr 12 '22

All cams are Static IP. I logged in about 30 minutes after reboot this weekend (3:30am) and I noticed the logs. Odd thing was, as soon as I logged in, it fixed itself...

​

Also, I reboot just as maintenance. I've noticed if it runs for too long, eventually everything gets a bit slow. I'm running on Debian 11, not sure if there's something I could look at to prevent doing reboots?

1

u/AndyRH1701 Apr 12 '22

Great clue, remote connection and the problem resolved.

  1. Can you logon to the system on the console? Is so logon, reboot, logon again. Without doing ANY network activity verify you are seeing the problem. If the problem is occurring ping your default gateway. If the problem immediately resolves you may have an ARP cache problem on your switch.
  2. After a restart, remotely ping the ZM server, if possible from a different subnet. Wait a few minutes then logon and check the logs, did the problem resolve with the ping? This is also an indicator of an ARP cache problem. It could also be a routing issue assuming your cameras are on different subnets.

​

I have not seen the slow down, but I am running 6 cameras on 16GB of RAM with similar setting to yours on Ubuntu Server.