"Shared data size conflict in shared_data for monitor"

Discussions related to the 1.36.x series of ZoneMinder
RonRN18
Posts: 34
Joined: Tue Aug 13, 2019 1:00 am

"Shared data size conflict in shared_data for monitor"

Post by RonRN18 »

I was have no problems at all with my system until today. The only change I can think of is that I saw that there was an update to ZoneMinder 1.36.23, so I upgraded. I then noticed that all of a sudden, all of my monitors have become unstable. I saw that in the logs, I am seeing nearly constant errors with lines saying something akin to: "Shared data size conflict in shared_data for monitor INSIDE Office Left, expected 768, got 760". The"INSIDE Office Left" is the name of one of the monitors. Each monitor will display for a few seconds... then go black, and then after a couple more seconds, return.
sphillips
Posts: 8
Joined: Fri Jul 06, 2018 10:21 am

Re: "Shared data size conflict in shared_data for monitor"

Post by sphillips »

yes i can confirm after update had the same problem on ubuntu 20.04

Aug 5 17:56:00 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Frente24h, expected 768, got 760]
Aug 5 17:56:00 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Frente, expected 768, got 760]
Aug 5 17:56:00 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Cozinha, expected 768, got 760]
Aug 5 17:56:00 server zmc_m3[1294317]: ERR [zmc_m3] [Failed to capture image from monitor 3 Cozinha (1/1)]
Aug 5 17:56:00 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Lavanderia, expected 768, got 760]
Aug 5 17:56:01 server zmc_m4[1294322]: ERR [zmc_m4] [Failed to capture image from monitor 4 Lavanderia (1/1)]
Aug 5 17:56:01 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Consultorio, expected 768, got 760]
Aug 5 17:56:01 server zmc_m5[1294329]: ERR [zmc_m5] [Failed to capture image from monitor 5 Consultorio (1/1)]
Aug 5 17:56:01 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Entrada, expected 768, got 760]
Aug 5 17:56:01 server zmc_m6[1294336]: ERR [zmc_m6] [Failed to capture image from monitor 6 Entrada (1/1)]
Aug 5 17:56:11 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Frente24h, expected 768, got 760]
Aug 5 17:56:11 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Frente, expected 768, got 760]
Aug 5 17:56:11 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Cozinha, expected 768, got 760]
Aug 5 17:56:11 server zmc_m3[1294798]: ERR [zmc_m3] [Failed to capture image from monitor 3 Cozinha (1/1)]
Aug 5 17:56:11 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Lavanderia, expected 768, got 760]
Aug 5 17:56:12 server zmc_m4[1294804]: ERR [zmc_m4] [Failed to capture image from monitor 4 Lavanderia (1/1)]
Aug 5 17:56:12 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Consultorio, expected 768, got 760]
Aug 5 17:56:12 server zmc_m5[1294808]: ERR [zmc_m5] [Failed to capture image from monitor 5 Consultorio (1/1)]
Aug 5 17:56:12 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Entrada, expected 768, got 760]
Aug 5 17:56:12 server zmc_m6[1294815]: ERR [zmc_m6] [Failed to capture image from monitor 6 Entrada (1/1)]
Aug 5 17:56:22 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Frente24h, expected 768, got 760]
Aug 5 17:56:22 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Frente, expected 768, got 760]
Aug 5 17:56:22 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Cozinha, expected 768, got 760]
Aug 5 17:56:23 server zmc_m3[1294884]: ERR [zmc_m3] [Failed to capture image from monitor 3 Cozinha (1/1)]
Aug 5 17:56:23 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Lavanderia, expected 768, got 760]
Aug 5 17:56:23 server zmc_m4[1294892]: ERR [zmc_m4] [Failed to capture image from monitor 4 Lavanderia (1/1)]
Aug 5 17:56:23 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Consultorio, expected 768, got 760]
Aug 5 17:56:23 server zmc_m5[1294891]: ERR [zmc_m5] [Failed to capture image from monitor 5 Consultorio (1/1)]
Aug 5 17:56:23 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Entrada, expected 768, got 760]
Aug 5 17:56:24 server zmc_m6[1294890]: ERR [zmc_m6] [Failed to capture image from monitor 6 Entrada (1/1)]
Aug 5 17:56:34 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Frente24h, expected 768, got 760]
Aug 5 17:56:34 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Frente, expected 768, got 760]
Aug 5 17:56:34 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Cozinha, expected 768, got 760]
Aug 5 17:56:34 server zmc_m3[1294941]: ERR [zmc_m3] [Failed to capture image from monitor 3 Cozinha (1/1)]
Aug 5 17:56:34 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Lavanderia, expected 768, got 760]
Aug 5 17:56:34 server zmc_m4[1294942]: ERR [zmc_m4] [Unable to open input http://server_local_ip/videostream.cgi?user=user&pwd=pass&rate=15 due to: Immediate exit requested]
Aug 5 17:56:34 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Consultorio, expected 768, got 760]
Aug 5 17:56:34 server zmc_m5[1294950]: ERR [zmc_m5] [Failed to capture image from monitor 5 Consultorio (1/1)]
Aug 5 17:56:34 server zmwatch[1294362]: ERR [Shared data size conflict in shared_data for monitor Entrada, expected 768, got 760]
Aug 5 17:56:34 server zmc_m6[1294949]: ERR [zmc_m6] [Failed to capture image from monitor 6 Entrada (1/1)]
Aug 5 17:56:44 server zmwatch[1294362]: ERR [Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running.]
Aug 5 17:56:45 server zmwatch[1294362]: ERR [Memory map file '/dev/shm/zm.mmap.2' does not exist in zmMemAttach. zmc might not be running.]
Aug 5 17:56:45 server zmwatch[1294362]: ERR [Memory map file '/dev/shm/zm.mmap.3' does not exist in zmMemAttach. zmc might not be running.]
Aug 5 17:56:45 server zmwatch[1294362]: ERR [Memory map file '/dev/shm/zm.mmap.4' does not exist in zmMemAttach. zmc might not be running.]
Aug 5 17:56:45 server zmwatch[1294362]: ERR [Memory map file '/dev/shm/zm.mmap.5' does not exist in zmMemAttach. zmc might not be running.]
Aug 5 17:56:45 server zmwatch[1294362]: ERR [Memory map file '/dev/shm/zm.mmap.6' does not exist in zmMemAttach. zmc might not be running.]
it will just keep looping that, on the webui cameras will go up and down
Last edited by sphillips on Sat Aug 06, 2022 12:15 am, edited 1 time in total.
leewells
Posts: 11
Joined: Tue Dec 01, 2020 4:06 pm

Re: "Shared data size conflict in shared_data for monitor"

Post by leewells »

I'm seeing the same thing. Running Ubuntu 18.04.6. I finally built 1.36.21 from scratch using packpack, so I could downgrade (I couldn't find an older .deb file anywhere). I did try building 1.36.23 and it had the same "data size conflict' errors as the iconnor ppa version.
rip
Posts: 36
Joined: Sun Sep 02, 2012 8:59 pm

Re: "Shared data size conflict in shared_data for monitor"

Post by rip »

Yes. 1.36.23 annihilated my setup. The funny thing is, the changes are minor.

I suspect Packet queue, TZ change would not seem to be very traumatic unless the formatting really messes up the DB.
https://github.com/ZoneMinder/zoneminde ... ...1.36.23
keithp
Posts: 7
Joined: Sat Aug 06, 2022 12:44 am

Re: "Shared data size conflict in shared_data for monitor"

Post by keithp »

+1 for seeing this on 20.04. Very similar messages for me across 3 cameras that end with "expected 768, got 760". There are also, "..., shared data not valid" messages with those. I also noticed that while I do have /dev/shm mounted and the 3 camera files in there with activity (i.e. timestamps are being updated), /dev/shm in the console never moves off 0%.

Additionally after searching around, I tried the following things that did NOT work...

1) downgrade ffmpeg from 4.2.7 to 4.2.2
2) increasing MaxImageBufferCount (cleaned up errors in the log but that is it)
3) stopping zmwatch.pl... seems to work for a bit but then things got really bad... had to restart a camera twice for some odd reason and a couple of minutes after that the system load was up past 40.

I'm really not sure what is going on but I upgraded to 1.36.21 on 8/2. That version still had my camera's cycling offline but I could not pull up the log. It at one point seemed to be stable so I thought maybe it was just taking longer to settle down. I noticed today the problem returned and decided to do another update which installed .23 and since then the system has not been stable at all.

I really don't want to go back to 1.34.x but I'm at a loss and I really don't want to leave the system down.
tsp84
Posts: 226
Joined: Thu Dec 24, 2020 4:04 am

Re: "Shared data size conflict in shared_data for monitor"

Post by tsp84 »

the data structure "shared_data" is expected to be 768 bytes but is returning 760 bytes which is causing the error. ic0n is pushing a fix asap if not already done.
Magic919
Posts: 986
Joined: Wed Sep 18, 2013 6:56 am

Re: "Shared data size conflict in shared_data for monitor"

Post by Magic919 »

Just roll back to 1.36.21 pending a fix. Wait until someone else has tried .24 if you are being cautious.
-----------------------------------------------------------------------
I'm nothing to do with ZM, ZMNinja or ZMES, I just use them.
Contribute funding to the devs here - https://opencollective.com/zoneminder
seaweed
Posts: 2
Joined: Thu Jul 14, 2022 5:43 pm

Re: "Shared data size conflict in shared_data for monitor"

Post by seaweed »

Magic919 wrote: Sat Aug 06, 2022 5:57 am Just roll back to 1.36.21 pending a fix. Wait until someone else has tried .24 if you are being cautious.
Is it possible to rollback if you are using the ppa or do you need to build it from source?
Magic919
Posts: 986
Joined: Wed Sep 18, 2013 6:56 am

Re: "Shared data size conflict in shared_data for monitor"

Post by Magic919 »

I go here https://launchpad.net/~iconnor/+archive ... tate=built

Download the .deb file. Run sudo dpkg -i on the file.
-----------------------------------------------------------------------
I'm nothing to do with ZM, ZMNinja or ZMES, I just use them.
Contribute funding to the devs here - https://opencollective.com/zoneminder
seaweed
Posts: 2
Joined: Thu Jul 14, 2022 5:43 pm

Re: "Shared data size conflict in shared_data for monitor"

Post by seaweed »

Magic919 wrote: Sat Aug 06, 2022 9:59 am I go here https://launchpad.net/~iconnor/+archive ... tate=built

Download the .deb file. Run sudo dpkg -i on the file.
Thankyou much appreciated I'm back to 1.36.21 now and everything running again
Magic919
Posts: 986
Joined: Wed Sep 18, 2013 6:56 am

Re: "Shared data size conflict in shared_data for monitor"

Post by Magic919 »

You’re welcome. I’d suggest keeping the file handy as a bit of insurance.
-----------------------------------------------------------------------
I'm nothing to do with ZM, ZMNinja or ZMES, I just use them.
Contribute funding to the devs here - https://opencollective.com/zoneminder
User avatar
iconnor
Posts: 2055
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: "Shared data size conflict in shared_data for monitor"

Post by iconnor »

1.36.24 looks to be good.
ZMBrian
Posts: 27
Joined: Thu Apr 28, 2016 2:46 pm

Re: "Shared data size conflict in shared_data for monitor"

Post by ZMBrian »

Upgrading to 1.36.24 resolved my issue. Thanks iConnor for a quick resolution!
sphillips
Posts: 8
Joined: Fri Jul 06, 2018 10:21 am

Re: "Shared data size conflict in shared_data for monitor"

Post by sphillips »

iconnor wrote: Sat Aug 06, 2022 2:43 pm 1.36.24 looks to be good.
thank you all looks well again
JerWah
Posts: 1
Joined: Sat Aug 06, 2022 9:30 pm

Re: "Shared data size conflict in shared_data for monitor"

Post by JerWah »

Can also confirm 1.36.24 fixed my issues.
Post Reply