SocketException: socket closed at java. Make sure anyone can read it Also test on a insecure Windows box. Often Symantic disables stuff you need. Post by haus » Wed Nov 21, pm I checked permissions. I also tried chown and chgrp'ing everything to www-data, but that doesn't seem to help either. I will probably try an install from scratch someday when I have time rather than using the. For now, though, I'm still trying to learn the basics of the system before I start tweaking things.
I hope Lee's instructions helped the OP, at least! And as always thanks to the folks here for ideas to try. I still can not see the fluent video shown by cambozola. The image showed 1 fps. The stages that each number represents are as follows,. Using the above images you should be able to tell at all stages what ZM is doing to determine if an event should happen or not. They are useful diagnostic tools but as is mentioned elsewhere they will massively slow your system down and take up a great deal more space.
You should never leave ZM running for any length of time with diagnostic images on. With capture cards ZoneMinder will pull images as fast as it possibly can unless limited by configuration. ZoneMinder and any similar application uses the frame grabber interface to copy frames from video memory into user memory.
This takes some time, plus if you have several inputs sharing one capture chip it has to switch between inputs between captures which further slows things down. On average a card that can capture at 25fps per chip PAL for one input will do maybe fps for two, fps for three and for four. For a 30fps NTSC chip the figures will be correspondingly higher.
However sometimes it is necessary to slow down capture even further as after an input switch it may take a short while for the new image to settle before it can be captured without corruption.
This requires no capture or processing unless you do an explicit capture via the J or ctrl-J keys for instance. Some cards or drivers do not support the frame grabber interface at all so may not work with ZoneMinder even though you can view the stream in xawtv.
If you can grab a still using the grab functionality of xawtv then in general your card will work with ZoneMinder.
Lastly, please look for errors created by the zmc processes. By default FireFox only supports a small number of simultaneous connections.
Using the montage view usually requires one persistent connection for each camera plus intermittent connections for other information such as statuses. You will need to increase the number of allowed connections to use the montage view with more than a small number of cameras. Certain FireFox extensions such as FasterFox may also help to achieve the same result. Enter about:config in the address bar. Browsers such a Chrome and Safari only support upto 6 streams from the same domain.
The various elements of ZoneMinder can be involved in some pretty intensive activity, especially while analysing images for motion. However generally this should not overwhelm your machine unless it is very old or underpowered.
There are a number of specific reasons why processor loads can be high either by design or by accident. To figure out exactly what is causing it in your circumstances requires a bit of experimentation. Also speed of disk etc will make some difference during event capture and also if you are watching the whole time then you may have a bunch of zms processes running also. I think the biggest factors are image size, colour depth and capture rate. The timeline view is a new view allowing you to see a graph of alarm activity over time and to quickly scan and home in on events of interest.
However this feature is highly complex and still in beta. It is based extensively on HTML div tags, sometimes lots of them. Whilst FireFox is able to render this view successfully other browsers, particular Internet Explorer do not seem able to cope and so present a messed up view, either always or when there are a lot of events.
Using the timeline view is only recommended when using FireFox, however even then there may be issues. This function has from time to time been corrupted in the SVN release or in the stable releases, try and reinstall from a fresh download.
Please see this online excel sheet. Note that this is just an estimate. Or go to this link for the Axis bandwidth calculator. Although this is aimed at Axis cameras it still produces valid results for any kind of IP camera. As a quick guide I have 4 cameras at x storing 1 fps except during alarm events. Many Linux distributions nowadays are built with security in mind. One of the latest methods of achieving this is via SELinux Secure Linux which controls who is able to run what in a more precise way then traditional accounting and file based permissions link.
If you are seeing entries in your system log like:. You then have two choices. Disabling SELinux is usually performed by editing its configuration file e.
However if you run a public server you should read up on the risks associated with disabled Secure Linux before disabling it. Note that SELinux may cause errors other than those listed above.
If you are in any doubt then it can be worth disabling SELinux experimentally to see if it fixes your problem before trying other solutions. You will immediately be asked to login.
Note that if you choose to enable webserver auth, zmNinja may have issues. Please read the zmNinja FAQ on basic authentication for more information. Also please note that zmNinja does not support digest authentication. Zoneminder is a superb application in every way, but it does a job that needs a lot of horsepower especially when using multiple IP cameras. IP Cams require an extra level of processing to analogue cards as the jpg or mjpeg images need to be decoded before analysing.
This needs grunt. If you have lots of cameras, you need lots of grunt. Why do ZM need so much grunt? Think what Zoneminder is actually doing. In modect mode ZM is: 1. Fetching a jpeg from the camera. Either in single part or multipart stream 2. Decoding the jpeg image. Comparing the zoned selections to the previous image or images and applying rules.
If in alarm state, writing that image to the disk and updating the mysql database. Decoding the images is what takes the real power from the processor and this is the main reason why analogue cameras which present an image ready-decoded in memory take less work. If the load is consistently high over Occasional peaks are fine, normal and nothing to worry about. Zoneminder shows Load on the main page top right as well as disk space. A load of 1.
Also worth noting that a load of 4. For a better and full explanation of Load: Please read this. The previous documentation explained how to use turbo jpeg libraries as an optimization technique.
These libraries have long been part of standard linux distros since that article was authored and hence that section has been removed. The following are good things to try, in no particular order;.
Processor specific commands can be found in the GCC manual along with some more options that may increase performance. A typical mbit LAN will cope with most setups easily. You do not need to rebuild ZM for X10 support. You will need to install the perl module and switch on X10 in the options, then restart. A run state is a particular configuration of monitor functions that you want to use at any time.
To save a run state you should first configure your monitors for Modect, Record, Monitor etc as you would want them during one of the times of day. Then click on the running state link at the top of the Console view. The final step you need to take, is scheduling the time the changes take effect. For this you can use cron. A simple entry to change to the Daylight state at at 8am and to the nighttime state at 8pm would be as follows,.
On Ubuntu 7. Although the example above describes changing states at different times of day, the same principle can equally be applied to days of the week or other more arbitrary periods. ZoneMinder includes a perl API which means you can create a script to interact with the ZM shared memory data and use it in your own scripts to react to ZM alarms or to trigger ZM to generate new alarms.
ZoneMinder provides a sample alarm script called zmalarm. Here are some things that will help you track down whats wrong. This is also how to obtain the info that we need to help you on the forums. Refer to the logging discussion in Options - Logging for more details on where logs are stored and how to enable various log levels. Since ZM is dependent on other components to work, you might not find errors in ZM but in the other components.
If ZM is not functioning, you should always be able to find an error in at least one of these logs. Researching the web I found this to be faster for larger tables as events grow and much more reliable. One tool I use is mysqltuner.
This is run from the command line and gives clear instructions as to what values to change. If these instructions are not clear to you I recommend my friend Google. On a new system under load we recommend running mysqltuner daily until you get to stability with the amount of events you store. When you run mysqltuner you will be prompted to enter the admin user normally root and then the password. Many of the settings in MySQL are "default" and are not listed in the configuration file.
Something like this:. It would seem that ffmpeg has possibly changed things again, no real supprise there but it complicates building ZM. If you increase the image size on a camera, it's always best to close down any streams and restart ZM to make sure that all memory is released. I guess you are using the default module supplied with CentOS.
I think, not sure about this though, that it is missing some capabilities. The way I tuned my zones was to walk out in front of the camera and stand at the furthest distance from the camera where it would be useful to detect motion. Then I replayed the footage and took a still of my standing away from the camera, loaded it into a photo editor and cropped the image to the size of my body.
Then looking at the image attibutes gave me the dimensions of the remaining space, I took the height and width and multiplied them to get a minumum number of changed pixels I wanted to cause an alarm.
0コメント