Page 1 of 1

After upgrading to 1.36 from 34 no cameras

Posted: Mon Sep 26, 2022 7:47 pm
by pqmertz
The cameras were working before. I can view past recorded events but all the cameras now say.

Monitor is not capturing. We will be unable to provide an image.

Had been using remote and motion detection for most cameras.

What do I have to change after the upgrade to get my cameras back?
Note: Been using ZM for a long time.

I had some issues getting everything updated, but now seem to have all the server parts running.

What is the command to make sure the database fully upgraded as well?

Thanks much.

Re: After upgrading to 1.36 from 34 no cameras

Posted: Tue Sep 27, 2022 7:44 am
by Magic919
You will need to look in the logs for clues.

zmupdate.pl and zmupdate.pl -f will take care of the DB.

Re: After upgrading to 1.36 from 34 no cameras

Posted: Mon Oct 03, 2022 4:29 pm
by pqmertz
Well it says everything is updated. BUT the logs are not happy at all All sorts of errors... again these cameras worked before the upgrade.

I reduced the cameras to 2 and now I get this over and over again.

"10/3/22, 12:05:57 PM CDT",zmdc,,1426,INF,"'zmc -m 9' starting at 22/10/03 12:05:57, pid = 3552",zmdc.pl,'-
"10/3/22, 12:05:57 PM CDT",zmdc,,3552,INF,"'zmc -m 9' started at 22/10/03 12:05:57",zmdc.pl,'-
"10/3/22, 12:05:57 PM CDT",zmdc,,1426,INF,"Starting pending process, zmc -m 9",zmdc.pl,'-
"10/3/22, 12:05:55 PM CDT",zmdc,,1426,ERR,"'zmc -m 8' exited abnormally, exit status 255",zmdc.pl,'-
"10/3/22, 12:05:55 PM CDT",zmc_m8,,3547,FAT,"Failed to bind RTCP server",zm_rtp_ctrl.cpp,264
"10/3/22, 12:05:55 PM CDT",zmc_m8,,3547,ERR,"bind(), Could not bind",zm_comms.cpp,559
"10/3/22, 12:05:55 PM CDT",zmc_m8,,3543,INF,"Starting Capture version 1.36.26",zmc.cpp,220
"10/3/22, 12:05:55 PM CDT",zmdc,,3543,INF,"'zmc -m 8' started at 22/10/03 12:05:55",zmdc.pl,'-
"10/3/22, 12:05:55 PM CDT",zmdc,,1426,INF,"'zmc -m 8' starting at 22/10/03 12:05:55, pid = 3543",zmdc.pl,'-
"10/3/22, 12:05:55 PM CDT",zmdc,,1426,INF,"Starting pending process, zmc -m 8",zmdc.pl,'-
"10/3/22, 12:05:47 PM CDT",zmdc,,1426,ERR,"'zmc -m 9' exited abnormally, exit status 255",zmdc.pl,'-
"10/3/22, 12:05:47 PM CDT",zmc_m9,,3538,FAT,"Failed to bind RTCP server",zm_rtp_ctrl.cpp,264
"10/3/22, 12:05:47 PM CDT",zmc_m9,,3538,ERR,"bind(), Could not bind",zm_comms.cpp,559
"10/3/22, 12:05:47 PM CDT",zmc_m9,,3534,INF,"Starting Capture version 1.36.26",zmc.cpp,220
"10/3/22, 12:05:47 PM CDT",zmdc,,1426,INF,"'zmc -m 9' starting at 22/10/03 12:05:47, pid = 3534",zmdc.pl,'-
"10/3/22, 12:05:47 PM CDT",zmdc,,3534,INF,"'zmc -m 9' started at 22/10/03 12:05:47",zmdc.pl,'-
"10/3/22, 12:05:47 PM CDT",zmdc,,1426,INF,"Starting pending process, zmc -m 9",zmdc.pl,'-
"10/3/22, 12:05:45 PM CDT",zmdc,,1426,ERR,"'zmc -m 8' exited abnormally, exit status 255",zmdc.pl,'-
"10/3/22, 12:05:45 PM CDT",zmc_m8,,3529,FAT,"Failed to bind RTCP server",zm_rtp_ctrl.cpp,264
"10/3/22, 12:05:45 PM CDT",zmc_m8,,3529,ERR,"bind(), Could not bind",zm_comms.cpp,559
"10/3/22, 12:05:45 PM CDT",zmc_m8,,3525,INF,"Starting Capture version 1.36.26",zmc.cpp,220
"10/3/22, 12:05:45 PM CDT",zmdc,,3525,INF,"'zmc -m 8' started at 22/10/03 12:05:45",zmdc.pl,'-
"10/3/22, 12:05:45 PM CDT",zmdc,,1426,INF,"'zmc -m 8' starting at 22/10/03 12:05:45, pid = 3525",zmdc.pl,'-
"10/3/22, 12:05:45 PM CDT",zmdc,,1426,INF,"Starting pending process, zmc -m 8",zmdc.pl,'-

Re: After upgrading to 1.36 from 34 no cameras

Posted: Mon Oct 03, 2022 5:29 pm
by pqmertz
Just started experimenting if I changed the method from RTP/RTSP to RTP/Unicast I now connect.

Re: After upgrading to 1.36 from 34 no cameras

Posted: Mon Oct 03, 2022 6:02 pm
by pqmertz
My server load is 3X+ more then before. So it can't keep up and creating more events on MODECT than it needs to and not really recording anything.

Is the newer version that much worse when it comes to efficiency?

EDIT: Yes my server is now running at 55 load for 12 cores so it dropping frames and triggering event after event. (which causes MORE work) Very frustrated.

Re: After upgrading to 1.36 from 34 no cameras

Posted: Mon Oct 03, 2022 10:02 pm
by iconnor
Set a MaxImageBuffer setting.

1.36 is actually more efficient, but it exposes weaknesses in your system that you were likely ignoring before.

Switch to ffmpeg monitor types if you were using remote before. Set MaxImageBuffer, and if you have a large value in ImageBuffers, set that to 3. You are likely using double the ram due to that. Set MaxImageBuffer = old value of ImageBuffer.