ZM overunning my machine (FC3) based

Airwolf · Post by **Airwolf** » Fri Sep 23, 2005 2:40 pm

Hi everyone

Been running 1.2.3 for a while now and i have noticed that after leaving it running for a few days, ZM seems to 'overwelm' my machine with lots of disk activity and the only thing to get it back to normal is a reboot.

Rebooting as i cannot get a screen back to shut it down gracefully or look at any logs.

Also, notice that due to the placement i still gets lots of alarms due to sunlight/ shade changes. I have tried different zone settings to no avail.

Any ideas?

many thanks

jameswilson · Post by **jameswilson** » Fri Sep 23, 2005 3:12 pm

yes i have ideas.
How many inputs you running
what res
what fps
what have you got set analytsis wise
what jpeg quality u saving
what function are these inputs
and whats the basic specs of the machine
what else is it doing?

James

ps lots of things it could be
btw are you using cordels distro

Airwolf · Post by **Airwolf** » Fri Sep 23, 2005 5:40 pm

Hi Jamie

here we go

733 PII, 256mb RAM' 50gig disk, Rage PRO 128 graphics, Cordel's distro on FC3.

1 input, 3 zones, modect, set to default low bandwidth

main zone is active, 1 zone is inclusive, and the other preclusive within the active zone.

It's a dedicated machine for ZM connected over a wireless network to my main system.

I could open up a port and let you in for a look if you like. travelling next week so it might not be soon?

jameswilson · Post by **jameswilson** » Fri Sep 23, 2005 5:43 pm

just let me at the console first open port 80 and ill look for something glaringly obvious

Airwolf · Post by **Airwolf** » Fri Sep 23, 2005 6:00 pm

sent PM

jameswilson · Post by **jameswilson** » Fri Sep 23, 2005 6:27 pm

sorted over pm

Post by **zoneminder** » Mon Sep 26, 2005 9:22 pm

Are you able to disclose what the problem was?

Phil

Post by **cordel** » Tue Sep 27, 2005 3:29 am

If it is from my iso, It might be a cron that is enabled by default in FC3 to run updatedb for the locate command. I didn't disable it because I didn't think anyone would try to run it on a PII.
Here's the cron that Fedora has on by default that is probably loading your system up:
/etc/cron.daily/slocate.cron

Here are the other cron jobs set by default in FC3:
/etc/cron.daily/prelink
/etc/cron.daily/logrotate
/etc/cron.daily/yum.cron (this is only enabled if the yum service is started)
/etc/cron.daily/slocate.cron
/etc/cron.daily/0anacron
/etc/cron.daily/00-makewhatis.cron
/etc/cron.daily/rpm
/etc/cron.daily/00webalizer
/etc/cron.daily/00-logwatch
/etc/cron.daily/tmpwatch
/etc/cron.weekly/0anacron
/etc/cron.weekly/00-makewhatis.cron
/etc/cron.monthly/0anacron

slocate can take a while to do it's thing depending on how big the drive is and how full it might be. I think this would be worth looking into if your going to run it on anything lower than a PIII 500. I would take more than 24 hours before the first cron would be run.
Regards,
Cordel

jameswilson · Post by **jameswilson** » Tue Sep 27, 2005 7:27 am

nowt complicated.
no limit on fps
and system was set to analsye everythimh etc and load was peaking at about 5 aftyer i changed a few things on it load approx .2

James

Post by **cordel** » Wed Sep 28, 2005 6:14 am

Yep that will do it too

Although the info above is good for people to know as well but not as critical as setting zm correctly