"volumes": {
"/config": {
"description": "Choose a Share for the data and configuration data. (you can add seperate shares for events later by attaching a volume to /config/data/events)",
"label": "Config Storage",
"min_size": "1073741824"
},
"/config/mysql": {
"description": "Choose a Share for the database.",
"label": "MySQL Storage",
"min_size": "1073741824"
},
"/config/data": {
"description": "Choose a Share for the data.",
"label": "ZM Data Storage",
"min_size": "1073741824"
},
}
@magicalyak Hello again. Iām a little concerned that if we āover doā the separation itās get to be overly complicated to setup. As you already have it seems to be a nice split. ie special location for db (as we discussed when you first did the 1.29 Rock-on), because btrfs+db can require special attention, and then another for all the data and config. If the new v1.30 ZM Rock-on mirrors this then we have a communication issue not a technical one.
Also we have the existing User Docs of ZoneMinder Rock-on and if the 2 versions of zm differ re share allocation then we are making our own monster and adding to potential confusion. Especially given you left open the possibility to add additional shares if need be, hence allowing for more advanced configurations if need be.
@glenngould Are you saying that you have no file entries appearing where you might of otherwise found them with @magicalyak 's v1.29 zoneminder Rock-on? Or is this related to your size reporting issue?
Which may just be a current artefact of Raid5/6 use (apologies but yet to investigate further).
Apologies if Iām jumping in here inappropriately.
Thatās a good point, you can add storage after and just change the paths in the options to point to them. I donāt think adding 2 new shares would add value or be anything new compared to doing that.
My whole concern or observation is that during installation you are requested to create two new shares (data & db)ā¦,for v1.29 the events are correctly stored into the ādata shareā while v1.30 stores the event in none of the created shares. It is stored under ā/var/cache/zoneminder/eventsā as pointed out by @magicalyak
EDIT: Iāve just had time and checkedā¦there are no events at ā/var/cache/zoneminder/eventsā like mentioned by @magicalyak - still unclear to me where they are stored
In the options, does it show the /config path for the events and images directories (in 1.29)? It may just be that we need to do manually do this in 1.30. Can you try that?
@magicalyak If you need a cheep camera to test zoneminder with, grab an old cell phone and install IP Web cam on it. Works well with Zone minder, over home wifi network. I had a temporary home security system set up using the 1.29 zoneminder rockon and 4 old phones.
Iāve used the āfindā command with regards to āeventsā with the following output, BUT if I look up within those indicated folders by using āmcāā¦none of them are visible? Iām doing this as root userā¦
FYI - Attention, it seems ZM asks you after a while for a donation, hidden pop-up which prevents/stops any recording!
ā¦just found out that since 2 weeks nothing was recorded, so I logged into the WebUI and realized this blocked pop-up. -> now it is working again
I canāt remember, maybe this type of pop-up showed up at the beginning and I set it to āno thanks, never donateā and therefore I faced never this type of unexpected service stop while using 1.29 compared to 1.30.
Hi,
anyone looked into this again recently (upgrading the rockon repository)? Almost 2 years are overā¦
It seems there is version 1.30.4 out and on https://github.com/ZoneMinder/zoneminder there is versions ongoing 1.31 or 1.32 and even higherā¦
