ZoneMinder Forums

I have a 438 mb tar file of a 4 gb debug log but the website states the file is to large. This server only does Zoneminder it runs Ubuntu 22.04. it did not matter if ad blocker is disabled or not. I updated java to the most recent version. Java reports openjdk version "11.0.24" 2024-07-16, OpenJDK ...

maybe this will help

after updating to 1.36.34 getting undefined - setConstant() in file ?view=log component web_js. This is with both Ubuntu 20.04 and 22.04. Non increasing dts is spamming the log about 15 entries per second. That is not new, been doing this for quite a while. Set the log levels to error on all, seems ...

Let me clarify.

The server running ZM is not used for the internet except for updates. All this server does is run ZM and check for updates. I have to move debug files and other info to this workstation. Attachments only accept .TXT.

I suspect a counter was reset to zero, but I'm unsure what counter since events continued to the next sequential number. This is only on Ubuntu 22.04 BTW, 20.04 is working as planned. Zmstorage and Zmstoragec are the disks used for events. Unable to post print screens since the board does not accept ...

All events stored on the HD's were deleted. I normally shut down ZM before a reboot to prevent orphan events. If one just restarts with ZM running you get orphaned events and the audit has to clean it up. I just discovered the event counter was not reset. I scanned some Ubuntu logs to find out what ...

This is more of a FYI. Ubuntu 22.04.02. As part of Canonical's standard updates a firmware update as also done. In order for the the firmware update to take effect the system needed to be restarted. Shut down Zoneminder normally waited for activity to stop, rebooted and after the restart all of the ...

1944x2562 works fine with Ubuntu 20.04, not Ubuntu 22.04. Had to change he configuration of the camera to get 2562x1944 to work on 22.04, which meant I had to change it on 20.04. Chose rotate right and 2562x1944 (which appears to be the 5m default) in Zoneminder and it works. Using Ubuntu 22.04, ZM ...

I have one 5mp camera that would not start ZM 1.36.29. The camera resolution was set to 1944x2592 which is 5mp sideways. Changing the ZM camera resolution to 2592x1944 and changing the camera configuration to be flipped 180 degrees and mirrored fixed the problem. This is an Amcrest IP5M-T1179E.

Changed the authority of /dev/shm to public all and this seems to have fixed the Monitor SHM not connected issue.

Updated to 1.36.29. This fixed the logs issue, but still get monitor shm not connected for the camera. Audits are not running, running them manually from the command line (zmaudit.pl) works fine.

Loaded 1.36.38 and now on the Ubuntu 22.04 system and can't view logs in the browser. It displays loading please wait. The camera with the problem is not fixed. Changed the capture function to none. zmdc generated zmc has not stopped five times and the PID appears to have ended after that. The ...

Made some changes. I wiped the partition containing Ubuntu 22.04 and zoneminder. Installed Ubuntu 22.04 from the iso. Installed ZM, configured it, got it working, and the camera that was failing is still failing. I've attached those two debug logs. The system is having problems getting the previous ...

ZMDC.log reports malloc(): corrupted top size for the camera not working.

Changed the image buffers, but ZM still posts Monitor shm not connected on the Ubuntu 22.04 server. Fortunately the ubuntu 20.04 server is working great. Oh ZM V 1.36.26 I left that out of the original post.