#zoneminder

but suits me :D

any time i have to rebuild the VM or reinstall zm

i only have to make sure i fstab mount the nfs vol and add the symlink

and ive got as much storage as i need (the nfs vol is actually a zpool to which i can add as many vdevs as i like)

keeps the VM img small

and paths in config standard

jzaw, not what i meant

i've created a LV on another drive and mounted that using vps.mount to my 10GB container

i was talking about the symlink over bind-mount suggestion

Question: Why can't I just symlink the newdrive to the events folder? Answer: Because it does not work in every case. Many rpm and deb packages need the file folders set up exactly the way they were when the first zoneminder package was installed. Changing that around can cause package upgrades to fail, or worse you could lose all your data!

this is in the FAQ, so i went with what knnniggett recommended

fair enough

though, its still an absolute dir in fstab, so i don't see the difference

seems its working, however i don't know how to tell if the data is residing in both folders

but if zm sees a *dir* as /var/www/events

surely it doesnt matter if it's a symlink ?

jzaw, yea i have no idea, just what knnniggett said ^

ok :)

By symlinking, what you are doing is changing the folder structure from what the package installed. What do you expect to happen after a package upgrade? Right, the package will put it back to the way it was. This has caused some user to lose all their events.

interesting

This is by design for any package

cos if that were to happen ... ie i get symlink overwirtten by a dir

then my orig data is still on the mount ?

The way around that is to mount your volume to the folder, rather than symlink

ah k

i can do that /me nods

knnniggett, so with that setup, if i go to /var/cache/zoneminder, i'll be seeing the data from my mount ?

what happens if folder youre mounting to isnt empty ?

same thing that always happens.... the original files are no longer accessible because the mount is covering them up. The steps in the Wiki I linked earlier show how to safely migrate your events so you don't lose them

knnniggett, can you confirm with the setup in the wiki that one would be seeing files in /var/cache/zoneminder ?

right now symlink removed and stuff mounted to events and images

thanks knnniggett

If any of you are willing to beta test, apparently you can put an absolute path for the events folder under options. However, we need to test this to makes sure there are no issues across multiple distros and upgrades

That way we don't have to worry about bind mounts or symlinks

ill have to make some time and spin up another VM and try the movie storage build too

ren0v0: the folder is different across different distros. So the answer to your question is "maybe".

knnniggett, i'll rephrase, the folder IS /var/cache/zoneminder, i've followed the FAQ and bind-mounted this to my mount, new events are appearing in /var/cache/zoneminder, is this correct?

Would it be useful to have a mode where ZM allows for live view of a monitor but does not keep pre-capturing? pre-capturing takes up precious memory for lower end systems and prohibits us from adding multiple monitors that don't need any sort of recording but just viewing

Ah wait, what if I use monitor mode and set buffer to 1 ? will that help?

asker_: correct. Just adjust your buffers

so the min. buffer I am allowed is 10

I don't know. Did the system tell you that?

yup

it spoke with a popup

It said "Sorry asker, I just can't do that"

yeah, looks like I submitted a patch to integrate Siri into it and you merged it :-D

Oh, I was quoting HAL from Space Odessy

So which buffer where you trying to change?

s/where/were

reducing too much causes too many RTSP errors

slow down your framerate?

buffers tab

*Which* buffer on the buffers tab?

all of them. current setting:

image buffer size = 10 (min), warmup = 5 pre = 5, post = 5, stream = 5

reduce frame rate: good idea, but the camera lets me go down to 5 not less

should I make it 1 in ZM

[ WAR [Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size]]

Yeah, I wouldn't go any lower than 5 fps

so looks like 10 is too less

that sucks - 10 = 10 images

Can you set your pre to just 1?

ok

don't know what that will do

other than reduce the amount of pre-roll

darn that killed it. camerapc zmwatch[5312]: ERR [Unable to run "/usr/local/bin/zmdc.pl restart zmc -m 3", output is "Unable to connect to server"]

lets see if it recovers

works, but keeps throwing RTSP warnings

Sep 28 10:16:35 camerapc zmc_m3[6788]: WAR [Unexpected format RTSP interleaved data, resyncing by 1064 bytes]

and a dump of various bytes

Sep 28 10:17:01 camerapc zmc_m3[6788]: ERR [Unexpected channel selector 51 in RTSP interleaved data]

Sep 28 10:17:01 camerapc zmc_m3[6788]: WAR [Unexpected format RTSP interleaved data, resyncing by 33 bytes]

I don't think the current code is geared to work with minimal buffers

It's really not. I think it needs to change because keeping that many decoded frames is taking up a huge amount of memory on HD cameras.

yup, so it seems

also knnniggett : do the RTSP WAR [Unexpected format RTSP interleaved data, resyncing by 1210 bytes] need to be warnings? They seem to be temporary frame issues and don't affect the overall feed. Should they be demoted to Debug instead of DB logging it at warning level?

(because it dumps a large sequence of bytes after that)

don't know

maybe the dump bytes should be Debug

It's the whole shared memory bit that makes it complex. Which is why I want zmc to just write the stream and then have zma load it back from disk and get rid of the shared memory thing...

but still keep SHM on for events as the perl processes use them?

shm would still be used to for general info sharing. Just not buffers. Then make buffers dynamic.

looking at the code - I wonder if to validate the concept, I can modify Monitor::connect and Monitor::getImage to load from a real file instead of the mmaped file

good morning

morning simon

morning

Wow, I just read the best described trouble thread ever: http://www.zoneminder.com/forums/viewtopic.php?...

Titler: ZoneMinder - Forums - View topic - [1.28.1]+[Miniserver-Ubuntu14.04]+[video.mjpg] = unwatchable

that guy gets a gold star for content

and I get asked why my branch names are verbose...

knnniggett: are you still tracking the problem with current master and mjpeg cameras? I'm using some of those and I don't think I have any problems...

yeah my airlink cam is working good

knnnniggett: My airlink cameras get into a state where they won't send an image. Their UI still works and they start working fine after a reboot. So I just have a script reboot them every night.

in the event list... listing the id# seems a bit redundant. Given that it is in the name and if needed could be seen in the url when you hover over the link

augh

fixxxermet: can you find a few minutes to look at how the api event delete has been implemented? If I use the API to delete an event, it says success but then it looks like it's not removing both the event and frame DB entries and any subsequent API queries on events returns a failure with "cannot find frame for event XXXX"

I had to clear all my events to get back to sane state

calling zmaudit manually did not help either - API was still in funky state

ic0n: Yes, still having problems with my airlink. It's a demo camera and has been recently powered on. If I "yum downgrade" back to 1.28.1 the camera starts working again. Still trying to figure out the cause, but I really haven't had time yet to spend on it.

which model?

SkyIPCam1777W

I'm getting "can't bind", but that is a red herring... the frontend does create the socket, but it loops and tries to create the socket a second time

There was a PR that reduced the wait time to 2/10's of a second. Putting that back to 1 second was the first thing I tried, but that did not fix the issue

Looks just like my 777, but with usb....

you have tried rebooting right? We havn't done much to capture....

Actually that's a dumb suggestion

Yes, and I get the same results in CentOS 6, CentOS 7, and Fedora 22

The lack of a helpful error message is making this tough to figure out

Oh, and guess what? When I turn on debug.... the camera starts working?!?!?!

hmm.. I can't seem to find that other half of my 777.... just have the main circuit board... also need a 5v power adapter.

Mine has a hole in it where I let the soldering iron touch it. :-) Didn't hit the electronics fortunately

ah

fixed that event delete API problem. PR submitted. knnniggett ic0n when is your next package coming out? The next release of the app will cause pain if people don't apply the merged patches

I can do one today.

aha

lovely

thanks

This is a new one: max blob count reached. Unable to allocate new blobs so terminating. Zone settings may be too sensitive.

whoa

augh

ah knnniggett http://www.zoneminder.com/forums/viewtopic.php?... --> so this fail2ban stuff is pretty popular, it seems