#zoneminder

Hey jzaw - not sure if you are still around - think my internet connection is acting flakey... Anyway, I'm running the secondary server basically to serve up the locally connected little webcan to the primary box.

jzaw, not sure if there is a better way to do that - but that is what I did.

Anyone ever migrated a zm instance of db + data onto another server running same version of zm?

ive restored all and it is not picking up the events in zm

all in right folders etc

do i need to run zmupdate.pl or something?

have you tried mysql commands directly to see the db is there ?

+--------------------+---------------+ | DB Name | DB Size in MB | +--------------------+---------------+ | information_schema | 0.0 | | mysql | 0.7 | | performance_schema | 0.0 | | zm | 7.7 | +--------------------+---------------+

yea shes in there

in zm events is at 0

the data is in the same dir as the machine i migrated it from

which is..

var/cache/zoneminder/events

i heard if you stop zm, then restore db and data, then start it, it will go through syncing and then start again

but didnt seem to happen

it starts, but just does not pick them up, can i simply delete the zm db and add a new one and try restoring again?

does it make any difference if i restore the data or db first?

also getting.

2016-06-28 12:37:54.226475zma_m32382WARWaiting for capture daemonzm_monitor.cpp503 2016-06-28 12:37:53.172737zma_m32382WARWaiting for capture daemonzm_monitor.cpp503 2016-06-28 12:37:52.072657zma_m32382WARWaiting for capture daemonzm_monitor.cpp503 2016-06-28 12:37:50.980909zma_m32382WARWaiting for capture daemonzm_monitor.cpp503 2016-06-28 12:37:49.922510zma_m32382WARWaiting for capture daemonzm_

ok so ive restored the db again and its hsowing the events

but its not playing them

or allowing me to stream the cams live

also

2016-06-28 13:13:37.805741web_php2789ERRsocket_sendto( /var/run/zm/zms-800929s.sock ) failed: No such file or directory/usr/share/zoneminder/www/includes/functions.php2371

looked on that line and its referring to http version, so change it to 1.1 from 1.0 and restarted zm tna..

also.. ERR'zmc -m 3' exited abnormally, exit status 255zmdc.pl

zmjm: I got no errors either using 1.1 or 1.0

zmc -m 3' exited abnormally, exit status 255 zmdc.pl its's normal error if it's showing up right after you close a stream window

and it looks like you closed the monitor number 3

what browser are you using to play the streams ?

morning

Hey asker

hey ic0n - clarification on your comment on large videos "yeah, they need to be encoded differently, or have zms send them in chunks." --> I assume the video is encoded correctly, but view_video needs to change to handle large files?

No. Look, mp4 has a specific structure. You can hack it so that players can start playing it instantly but that is not what it was designed for. It is not a streaming structure.

Right now, we aren't doing much other than stuff the h264 frames into the mp4 file. We need to be doing all those hacks if we want to just send the file for viewing. The other way to go is have zms re-encode to something that is more for streaming. Basically re-chunk up the video on teh fly

okay, but that is not what I'm asking. I'm specifically referring to the point of large files just not playing when I use view_video - irrespective of how much time it takes.

my question was does view_video handle large files today (even it it takes several minutes) --> I can't seem to maek it work

it works fine for me, but I don't know how large they would have to be

the ones you had me look at yesterday all worked fine for me in chrome.

view_video literally just sends the file. I's not smart about it.

maybe if we were talking about a 2gb file I could see there being a problem...

okay thanks. Curious why you think putting header at the top is a hack? Thats what web optimized settings in programs like handbrake essentially do and also reading http://xhelmboyx.tripod.com/formats/mp4-layout.txt --> it also talks about the header being at the start of the file

Load: 0 / Disk: 90% that's a very lean system :D

on a completely unrelated note, I wonder if anything has changed in motion detection with 1.30 - same settings and its not catching many events

all that rotation work we did could screw things up if you camera is rotated... other than that, I don't recall anything happening in motion detection

ic0n: i was actually looking at some x264 stuff this morning randomly....is there any way to implement the -moov_size_bytes to reserve space at the beginning of the file for the moov atom to allow playback starting without downloading the whole file?

feel free to call me a noob and stfu

It's all a matter of getting the ffmpeg libraries to do it. It takes a lot of googling and reading ffmpeg docs. And every release of ffmpeg changes everything. Time consuming. These are things that will have to be done though in order for video branch to go primetime.

asker, ping ... re RewriteBase path in .htaccess in api

everytime i recompile and make install

it overwrites that and puts /zm/api

seems to be hardcoded

rather than picking up from my /etc/zm.conf that i have path /

Yes, it is

thus Rewritebase should be /api in my case

i have to

root@zoneminder:/var/www/api# find ./ -type f -name ".htaccess" -exec sed -i 's/\/zm//g' {} +

ever time

who do we prod to pick up the right path ?

./cmakecacheimport.sh /etc/zm.conf

should pick up the righ tpath

which entity in zm.conf are you thinking it should pick from?

it does for zm itself ... events etc are in the right place

# Path to ZoneMinder web files

ZM_PATH_WEB=/var/www

# Path to ZoneMinder cgi files

ZM_PATH_CGI=/var/cgi-bin

my events are in /var/www

/zm/api is not a real path

oh soz those are the entries from /etc/zm.conf

its a routing directive

I don't see anything in zm.conf that can be reliably used, I might be mistaken though

well my api

is in /var/www/api

cos that's the path to web

real path and routing path are different

they are mapped in apache's config afair

my sites-enabled/000-default.conf

says

DocumentRoot /var/www/

if I recall correctly, the apache conf. of ZM that is supplied enabled htaccess in the config file and the rule is in htaccess

so the API path in htaccess is completely a function of apache/web server not zm.conf

now does it have to be hard coded? no

how do we correct it, to pick up wherever api goes? no idea

who to ask? no idea too :-p

that api/.htaccess gets overwritten by the make install (after compilation)

right.

htaccess is hard coded

any reason it has to be?

I don't know how to make it not hard-coded

where would I pick up the value from?

and why not use the value for the root from zm.conf ?

ah

cos that's where zm installs it after all

what is "root from zm.conf" ?

[15:23:35] <jzaw> # Path to ZoneMinder web files

[15:23:35] <jzaw> ZM_PATH_WEB=/var/www

sorry for repaste

other ppl have edited that path to their own choosing

right, that cannnot work

rather than having https://<ip>/zm

that path is the "real directory"

i wanted just http://<ip>

in my case: