ZoneMinder Forums

Had just rebooted to test if that would "fix" and finished phpmyadmin install to pick inside the DB and saw e-mails are now coming with the right config: Hello, An alarm has been detected at XYZ Dr. The details are as follows :- Monitor : Door Time : 2021-01-27 17:46:10 Event Id : 3459 Length : 9.40 ...

Have my options > e-mail, set as follow: opt_email: checked email_subject: ZoneMinder: Alarm - %MN% - %EI% email_body: Hello, An alarm has been detected at xyz Dr. The details are as follows :- Monitor : %MN% Time : %ET% . . . e-mails are been generated with the default subject: ZoneMinder: Alarm ...

Thanks, I've rolled back to 1.34.22, as I didn't find the cause for this.

By the way ... that 1 on my 1st screen is the monitor #. I've noticed that it changes as I go down the monitors.

Guys, Created a new VM with ubuntu 20.04 and install ZM 1.35.16. Followed iconnor instruction and installed from his repo. Mapped a NFS export and added as storage; added two IP cams, deleted default zone and created a new one -> Zones shows 0 - It was showing 0 before as well. Funny thing is that ...

Not saying you don't have a point. I have taken all measures to prevent Zoneminder to cause problems and it seems to be working correctly, as designed. I've noticed that VMWare is filling the datastore with disks and was using 98% of the dataset. That could be the reason that the VM stopped without ...

Before I moved ZM to a VM, I was running it on a CentOS 7 server with 2x2TiB HDDs with the same partition scheme, where root had 90% on the total space (~3.6TiB) for several months without encountering this issue. I'll follow your suggestion to test and create a small VHD for the OS/ZM and a second ...

I've been running into this issue from time to time. The VM will stop without space and I have to restore a snapshot to get it going. My ZM VM has a 1TiB VHD and the PurgeWhenFull filter is running and set to 89% of the disk space. I even set a cron job to alert me if the disk space utilization went ...

Yes, that's right. During the installation and upgrade process you were prompted, no less than three times, to follow the README instructions during any installation or upgrade. I can point them out to you if you want. I've done everything I know to alert you to follow the README, other than jump ...

Try following the README instructions. ZoneMinder is guaranteed not to work if you don't. Another classic case of RTFM? I'm running as stated above after db migration, but I only did an yum update and the version was updated, so how should I know I had to run it to migrate the db? I maybe expecting ...

Running after db migration.

Note: zmupdate.pl displays: Upgrading to version 1.29.1 from 1.29 (Not exact words). Is it referring to the db version or ZM version? It may be misleading.

Upgrade finished. Log shows: 2016-08-04 07:47:03.900350 zmpkg 4958 FAT Version mismatch, system is version 1.30.0, database is 1.29.0, please run zmupdate.pl to update.

Oh, and if you are willing to be a guinea pig.... If you enable the testing repo on your system under /etc/yum.repos.d and do a yum update, you will get a newer ffmpeg, newer vlc, and a new zoneminder package, which has been built against these newer packages. It should just magically upgrade, but ...

Very complex network and maybe creating lots of double nat'ing in the process. I run all my home n/w with only one router (a pfsense) and several 1gb switches. For wireless I'd recommend using your routers as APs, if you really need for places that the "main" Ap can't provide a good connection ...

Bought two Foscam from Amazon in April. As I was planning to use it with WiFi and it has not performed well, even with a new AP installed on my roof 50ft from it, I returned one. Yesterday the 2nd one died, after three months of use, so here's the catch. Checked Amazon and return period has passed ...