Filesystem event does not exist in database
Posted: Tue Mar 12, 2019 6:26 pm
Version: 1.30.4
Pretty sure I installed through EPEL / Yum, but it has been a while
Centos 6.9
Hello,
I believe we have had some kind of hard drive issue. We've had to restart zoneminder service a few times, but today I noticed after doing so that the events all reset to 0. Nothing for the total events... It is a Dell server, and I do not currently have an iDRAC installed - otherwise I would have checked disk health.
It appears that it is deleting the files because they no longer exist in the database.
I have 2 drives I believe are mirrored for the OS, and 4 drives are setup for storage.
In fstab, see the following (removed most of the characters in UUID - not sure if that was useful or not in terms of security):
Seeing a bunch of entries like the following:
I'm wondering if the database was rebuilt (maybe the location was unmounted) with the hard drive issue. I'm guessing there's no way to recover from this, as it appears to be actually deleting the files. We originally were at 94% disk utilization, and it has gone all the way down to 21% and still going.
I'm planning on getting an iDRAC installed, and adding a solarwinds account so it can do more than poll ICMP. But is there anything I can do or check on my end to confirm my thoughts? How about a way to prevent this specific issue? It looks like I'll be installing CentOS 7 and the newest version if I've lost everything here.
Pretty sure I installed through EPEL / Yum, but it has been a while
Centos 6.9
Hello,
I believe we have had some kind of hard drive issue. We've had to restart zoneminder service a few times, but today I noticed after doing so that the events all reset to 0. Nothing for the total events... It is a Dell server, and I do not currently have an iDRAC installed - otherwise I would have checked disk health.
It appears that it is deleting the files because they no longer exist in the database.
I have 2 drives I believe are mirrored for the OS, and 4 drives are setup for storage.
In fstab, see the following (removed most of the characters in UUID - not sure if that was useful or not in terms of security):
Code: Select all
UUID=be9c / ext4 defaults 1 1
UUID=fe92 /boot ext4 defaults 1 2
UUID=b16c /home ext4 defaults 1 2
UUID=b17d swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/home/zoneminder/events /var/lib/zoneminder/events none defaults,bind 0 2
/home/zoneminder/images /var/lib/zoneminder/images none defaults,bind 0 2
Code: Select all
Mar 12 13:23:33 zoneminder2 zmaudit[3350]: INF [Filesystem event '1/2004220' does not exist in database]
Mar 12 13:23:33 zoneminder2 zmaudit[3350]: INF [deleting]
Mar 12 13:23:33 zoneminder2 zmaudit[3350]: INF [Filesystem event '1/1936861' does not exist in database]
Mar 12 13:23:33 zoneminder2 zmaudit[3350]: INF [deleting]
Mar 12 13:23:33 zoneminder2 zmaudit[3350]: INF [Filesystem event '1/1664147' does not exist in database]
Mar 12 13:23:33 zoneminder2 zmaudit[3350]: INF [deleting]
Mar 12 13:23:33 zoneminder2 zmaudit[3350]: INF [Filesystem event '1/1887045' does not exist in database]
I'm planning on getting an iDRAC installed, and adding a solarwinds account so it can do more than poll ICMP. But is there anything I can do or check on my end to confirm my thoughts? How about a way to prevent this specific issue? It looks like I'll be installing CentOS 7 and the newest version if I've lost everything here.