ZoneMinder Forums

Unfortunately backtraces have been useless for years. A better option would be turn on debug logging at level 3 and see what is happening right before the crash. Or install valgrind and run it under that. EDIT: You did turn on debug, I can see that now. So it crashed when starting up opening up the ...

well you have to have gsoap installed.

sudo apat-get install gsoap libgsoap-dev

And then build the package.

Unfortunately we havn't figured out a good way of including this code in the packages.

You will have to build your own, preferably using the do_debian_package.sh script in the misc directory.

This isn't TOO bad to figure out, but you might just want to wait for us to figure it out.

You have a filter that is deleting in-progress events. Fix it. It should at least have an EndDateTime is not null rule, but also rules to make it delete OLD events not new.

You should enable the update disk filter then.

Shouldn't happen. Might mean that you have two filters deleting at the same time.

Deleting an event happens in two steps. First we delete from the db, then from the file system. There should be no warnings.

Very unlikely. Just add my ppa and upgrade to our packaged version.

You can reduce your image buffers setting... to like 3 which is the default now.

The event is supposed to exist on disk... so we can delete it... it not being there is abnormal.

zmu is used to get the current status or give commands to the running zmc process. There has long been an issue with it hanging on exit. I thought I had it fixed, but maybe not. It's not something I can reproduce reliably.

It is not a process that should stay resident. You can kill -9 them.

how about the output of ps ax | grep zm

There should be roughly 1 db connection per process.

Cool thanks for figuring that out. I have added support for older php and will include that in 1.36.20

Don't waste your time. It has nothing to do with keyframe interval.

I'll have to take a look at the code. I think it should still do it.

1.36.15 had some issues, this being one. Upgrade to 1.36.18/19.