ZoneMinder Forums

In my 1.36 install, things seem to be working fine. Yet, the log file shows red continuously. I pulled a number of errors from that file that are: Date/Time Component Server PID Level Message File Line 3/16/25, 8:40:55 PM UTC web_php 12387 ERR socket_sendto( /run/zm/zms-116151s.sock ) failed ...

I had seen, somewhere, that there was an issue if Zoneminders time settings were different than the OS time settings. I am desiring to move to UTC, which is what I normally use. Since that represents a jump forward in time, I don't have to worry about duplicating or conflicting time stamps. Will ...

BINGO! I guess I should change my name to Thomas and take on the nickname of Doubting. I did not expect the UUIDs to change. The system worked prior to the failure of the drive. I simply reassigned one of the drives, so I expected that UUID to remain the same. What I left out was that I also ...

New information to add: Prior to the drive failure, I had in the fstab file the following entries: UUID=7c6c1200-d024-487c-b5ae-784c1a411439 /media/S2/ ext4 noatime,nodiratime,nofail 0 0 UUID=9bab49ec-57dd-43a7-9d54-6d6ec5023b28 /media/S1/ ext4 noatime,nodiratime,nofail 0 0 Upon replacing the drive ...

I have three storage locations on my system. All three are on independent drives. Default should never get touched, except in the event of equipment failure. S1 is very active and gets written to almost constantly. S2 was added to offload most cameras from S1. At some time, the S1 drive failed. I ...

Perhaps that could be it. What it catches on the wireless NIC is anything but a camera. I have Amcrest cameras and a Netgear POE switch on the hardwire NIC.

Those are the settings that I use. After that, the determination to save depends on how you set up the zones.

I found the issue. The Hard Drive became dislodged from it's mounting and was hanging by it's cable. Found the I/O errors in the log and investigated. The whole system is mounted in an inaccessible area, so the errant drive was not visually detected. I may try to reassign the default as I saw ...

I noted a camera discovery feature. The system that I set up has dual NICs. The feature seemed to work on the wireless NIC - which is my gateway to the larger network. It would be nice for the feature to recognize multiple NICs. My cameras are all POE.

I have 1.37.65 running on Ubuntu 24.04. Looking at the Storage drop down, I noted that default is 97% full. I have two external hard drives servicing my set up and have all of my cameras reporting to one or the other. Why would some events suddenly be directed to default and how can I get them moved ...

That was it.192.168 got keyed as 192.169. As many times as I looked at it, my eyes did not resolve that single digit. As far as backing up the database, I noted that there seems to be a change in the tables. I may, however use the concept for part of the set up of the remaining cameras. Many thanks.

I originally set up a 1.36 Zoneminder system on Ubuntu 24.04 with a four core processor. Because there seems to be conditions under which the Load raises into the 60s and the system becomes non responsive, I decided to duplicate it on a more capable system. I next installed Zoneminder on Ubuntu 24 ...