ZoneMinder Wiki - User contributions [en]

Using a dedicated Hard Drive

2018-03-07T02:10:38Z

Knnniggett:

==ZoneMinder 1.31 or Newer==
Please follow the steps shown on our readthedocs site:
http://zoneminder.readthedocs.io/en/latest/installationguide/dedicateddrive.html

==ZoneMinder 1.30.4 or Older==
Note: Here is a reliable method to mount a drive or external share using systemd in Ubuntu or Debian:
https://wiki.zoneminder.com/Common_Issues_with_Zoneminder_Installation_on_Ubuntu#Use_Systemd_to_Mount_Internal_Drive_or_NAS
This can also be done in Centos or Red Hat distros...

On many installs you may wish to dedicate a hard drive or partition for Zoneminder events. There are many reasons why you may want to change the storage location - security, data segregation, preventing encroachment onto OS partition by zoneminder etc.

It's not terribly difficult to do, but may be non-obvious to the untaught so here's a brief guide.

Some commands here are based on Debian/Ubuntu installs

1. Become root or "sudo -s" to gain root privs.

2. Stop Zoneminder. "service zoneminder stop", "/usr/bin/zmpkg.pl stop", or "systemctl stop zoneminder"

3. Mount your new partition onto the root filesystem, ensuring it is automatically remounted at boot time by editing /etc/fstab -- For the benefit of this guide, I'm calling my new partition /newdrive

''Note this new partition can be a local drive, raid partition, lvm/md device, external NAS, SAN, NFS share or SMB share. The only condition is that the I/O throughput should be up to handling what Zoneminder will throw at it. For that speed reason, some favour non-journalled filesystems and accept the extra risk of data corruption''

4. Locate Zoneminder's "events" and "images" directories. In Debian and Ubuntu, these are under /var/cache/zoneminder. In CentOS and Fedora, these are under /var/lib/zoneminder.

''If you wish to copy the data across, MOVE the events and images directories to /newdrive/zoneminder ''(Note this will take a long time on systems with many events). Also, DO NOT restart zoneminder until this entire process is completed. Doing so will cause all your events to be lost!''

If you don't wish to preserve the data, it is MUCH faster to simply delete or rename the original events and images dirs and create new directories in /newdrive/zoneminder. There is no need to remove the "orphaned" entries in the database, zmaudit will take care of those.

Eg:

mkdir /newdrive/zoneminder/events

mv /var/lib/zoneminder/events/* /var/lib/zoneminder/events_old/
-- or --
rm -rf /var/lib/zoneminder/events/

Add these lines in fstab to bind-mount an alternate location:

/dev/sdX1 /newdrive ext3 defaults 0 2
/newdrive/zoneminder/images /var/cache/zoneminder/images none defaults,bind 0 2
/newdrive/zoneminder/events /var/cache/zoneminder/events none defaults,bind 0 2

or in some cases,

/newdrive/zoneminder/images /var/lib/zoneminder/images none defaults,bind 0 2
/newdrive/zoneminder/events /var/lib/zoneminder/events none defaults,bind 0 2

or if you have a separate partition for each:

/dev/sdX1 /var/cache/zoneminder/images ext3 defaults 0 2
/dev/sdX2 /var/cache/zoneminder/events ext3 defaults 0 2
(Repeat for images)

5. Ensure ZoneMinder can write to the new destination by changing the owner and group to that of the web server user account. Debian based distros typically use "www-data" as the web server user account while many rpm based distros use "apache".

chown -R apache:apache /newdrive/zoneminder

6. Finally, mount /newdrive and test your fstab entries ("mount -a"). Restart zoneminder ( "service zoneminder start", "/usr/bin/zmpkg.pl start", or "systemctl start zoneminder") Monitor its operation and ensure new events are being created normally and are viewable. Zoneminder should also update the "Disk: %%" on its Console screen to reflect the disk space on its new partition.

FREQUENTLY ASKED QUESTIONS

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!

Question:
I noticed that there is an events folder under /usr/share/zoneminder/www, can I mount my dedicated hard drive or volume to that folder?
Answer:
This will not work in every case either and should be avoided. The events and images folders under /usr/share/zoneminder/www are actually symbolic links that point to the real folders under /var/lib/zoneminder (or /var/cache/zoneminder). Altering this in any way has the same affect as the answer to the first question.

Hardware Compatibility List

2017-08-15T17:05:27Z

Knnniggett: /* Network Digitizer */

The ZoneMinder Wiki is community based. That means the list below is only as good as those who chose to maintain it. Did you find something outdated? Did you get a camera working, which is not shown in the list below? Please consider adding or improving this list.

== IP Network Cameras ==
Most modern IP cameras are ONVIF compliant, which means most modern IP Camera should work with ZoneMinder. There are some caveats to this general rule. Cameras which (only) send an encrypted stream will not work with any third party recording software. Some "cloud" cameras fit into this category. You should verify one can adjust camera parameters such as frame rate, resolution, contrast, etc within the camera's web portal. This, in itself, is not a show stopper, but it will make your experience a lot easier.

The following list of IP cameras is not exhaustive. If your camera is not listed, it does not mean it will not work with ZoneMinder. Rather it likely means no one has taken the time to add it to the list. Please consider adding your camera to this list once you get it working.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amcrest QCam]]

* [[Amovision AM-Q630M]]

* [[Android]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[COT Pro]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[DBPower]] (H.264 Model, possibly others)

* [[Digoo]] At least M1Q, probably more.

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[EyeSpy247]] (Branded Sercomm RC8021)

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, IN-5907HD, possibly others)

* [[InternetEye]] M6840

* [[Keekoon]] KK002 (KK001 and 3 are probably the same)

* [[Level One]] some

* [[Lilin]] LR7022

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Netcat]] IP Cameras

* [[Pelco]] IP Cameras

* [[Revotech]] I6032W-P

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[Sricam]]

* [[TMEZON]] Some

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== IP Video Encoder ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source. An easy way to find these are to search for video encoders or video servers, e.g. 8 channel video encoder, or 2 channel video server. Note that analog video encoders are becoming obsolete, as HD analog video encoders become the norm.

* [[Synectics E100]] encoder

*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Single Board Computers ==

Single board computers such as the Raspberry Pi, Odroid, Beagleboard, and many others. Can function as ZM server (standalone or external) and/or as a [https://wiki.zoneminder.com/How_to_share_an_USB_camera_from_a_remote_ZM_server_to_another_ZM_Server camera].

* [[Raspberry Pi - Raspbian]]

* [[Raspberry Pi 2 - Fedora]]

* [[Raspberry Pi 2 - Raspbian]]

* [[Odroid - XU4 - Ubuntu Mate]]

* [[Beaglebone Black - Devuan Jessie]]

* [[Dedicated SBC Camera Monitor]] Beaglebone w/Devuan Jessie as video monitor.

Hardware Compatibility List

2017-08-15T17:04:20Z

Knnniggett: /* IP Network Cameras */

The ZoneMinder Wiki is community based. That means the list below is only as good as those who chose to maintain it. Did you find something outdated? Did you get a camera working, which is not shown in the list below? Please consider adding or improving this list.

== IP Network Cameras ==
Most modern IP cameras are ONVIF compliant, which means most modern IP Camera should work with ZoneMinder. There are some caveats to this general rule. Cameras which (only) send an encrypted stream will not work with any third party recording software. Some "cloud" cameras fit into this category. You should verify one can adjust camera parameters such as frame rate, resolution, contrast, etc within the camera's web portal. This, in itself, is not a show stopper, but it will make your experience a lot easier.

The following list of IP cameras is not exhaustive. If your camera is not listed, it does not mean it will not work with ZoneMinder. Rather it likely means no one has taken the time to add it to the list. Please consider adding your camera to this list once you get it working.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amcrest QCam]]

* [[Amovision AM-Q630M]]

* [[Android]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[COT Pro]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[DBPower]] (H.264 Model, possibly others)

* [[Digoo]] At least M1Q, probably more.

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[EyeSpy247]] (Branded Sercomm RC8021)

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, IN-5907HD, possibly others)

* [[InternetEye]] M6840

* [[Keekoon]] KK002 (KK001 and 3 are probably the same)

* [[Level One]] some

* [[Lilin]] LR7022

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Netcat]] IP Cameras

* [[Pelco]] IP Cameras

* [[Revotech]] I6032W-P

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[Sricam]]

* [[TMEZON]] Some

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizer ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source. An easy way to find these are to search for video encoders or video servers, e.g. 8 channel video encoder, or 2 channel video server. Note that analog video encoders are becoming obsolete, as HD analog video encoders become the norm.

* [[Synectics E100]] encoder

*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Single Board Computers ==

Single board computers such as the Raspberry Pi, Odroid, Beagleboard, and many others. Can function as ZM server (standalone or external) and/or as a [https://wiki.zoneminder.com/How_to_share_an_USB_camera_from_a_remote_ZM_server_to_another_ZM_Server camera].

* [[Raspberry Pi - Raspbian]]

* [[Raspberry Pi 2 - Fedora]]

* [[Raspberry Pi 2 - Raspbian]]

* [[Odroid - XU4 - Ubuntu Mate]]

* [[Beaglebone Black - Devuan Jessie]]

* [[Dedicated SBC Camera Monitor]] Beaglebone w/Devuan Jessie as video monitor.

Hardware Compatibility List

2017-08-15T17:01:46Z

Knnniggett:

The ZoneMinder Wiki is community based. That means the list below is only as good as those who chose to maintain it. Did you find something outdated? Did you get a camera working, which is not shown in the list below? Please consider adding or improving this list.

== IP Network Cameras ==
Most modern IP cameras are ONVIF compliant, which means most modern IP Camera should work with ZoneMinder. There are some caveats to this general rule. Cameras which (only) send an encrypted stream will not work with any third party recording software. Some "cloud" cameras fit into this category. While not a show stopper, you should verify one can adjust camera parameters such as frame rate, resolution, contrast, etc within the camera's web portal.

The following list of IP cameras is not exhaustive. If your camera is not listed, it does not mean it will not work with ZoneMinder. Rather it likely means no one has taken the time to add it to the list. Please consider adding your camera to this list once you get it working.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amcrest QCam]]

* [[Amovision AM-Q630M]]

* [[Android]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[COT Pro]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[DBPower]] (H.264 Model, possibly others)

* [[Digoo]] At least M1Q, probably more.

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[EyeSpy247]] (Branded Sercomm RC8021)

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, IN-5907HD, possibly others)

* [[InternetEye]] M6840

* [[Keekoon]] KK002 (KK001 and 3 are probably the same)

* [[Level One]] some

* [[Lilin]] LR7022

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Netcat]] IP Cameras

* [[Pelco]] IP Cameras

* [[Revotech]] I6032W-P

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[Sricam]]

* [[TMEZON]] Some

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizer ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source. An easy way to find these are to search for video encoders or video servers, e.g. 8 channel video encoder, or 2 channel video server. Note that analog video encoders are becoming obsolete, as HD analog video encoders become the norm.

* [[Synectics E100]] encoder

*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Single Board Computers ==

Single board computers such as the Raspberry Pi, Odroid, Beagleboard, and many others. Can function as ZM server (standalone or external) and/or as a [https://wiki.zoneminder.com/How_to_share_an_USB_camera_from_a_remote_ZM_server_to_another_ZM_Server camera].

* [[Raspberry Pi - Raspbian]]

* [[Raspberry Pi 2 - Fedora]]

* [[Raspberry Pi 2 - Raspbian]]

* [[Odroid - XU4 - Ubuntu Mate]]

* [[Beaglebone Black - Devuan Jessie]]

* [[Dedicated SBC Camera Monitor]] Beaglebone w/Devuan Jessie as video monitor.

CentOS

2017-08-11T20:48:20Z

Knnniggett: /* Installation Instructions */

=== Installation Instructions ===
To install ZoneMinder on RHEL, CentOS, and compatible clones, please refer to the instructions shown on our readthedocs site.
[https://zoneminder.readthedocs.io/en/latest/installationguide/redhat.html Redhat - ZoneMinder Documentation]

==== Archived Installation Instructions ====
What follows is a link to old installation instructions which predate rpm installations from zmrepo or rpmfusion. They are kept solely for reference.
[[CentOS/Archived]]

Fedora

2017-08-11T20:47:38Z

Knnniggett: /* Installation Instructions */

=== Installation Instructions ===
To install ZoneMinder on Fedora, please refer to the instructions shown on our readthedocs site.
[https://zoneminder.readthedocs.io/en/latest/installationguide/redhat.html Redhat - ZoneMinder Documentation]

==== Archived Installation Instructions ====
What follows is a link to old installation instructions, which predate rpm installations from zmrepo or rpmfusion. These instructions are kept solely for reference.
[[Fedora/Archived]]

CentOS

2017-08-10T13:50:28Z

Knnniggett:

=== Installation Instructions ===
To install ZoneMinder on RHEL, CentOS, and compatible clones, please refer to the instructions shown on our readthedocs site.
[https://zoneminder.readthedocs.io/en/stable/installationguide/redhat.html Redhat - ZoneMinder Documentation]

==== Archived Installation Instructions ====
What follows is a link to old installation instructions which predate rpm installations from zmrepo or rpmfusion. They are kept solely for reference.
[[CentOS/Archived]]

Fedora

2017-08-10T13:48:33Z

Knnniggett:

=== Installation Instructions ===
To install ZoneMinder on Fedora, please refer to the instructions shown on our readthedocs site.
[https://zoneminder.readthedocs.io/en/stable/installationguide/redhat.html Redhat - ZoneMinder Documentation]

==== Archived Installation Instructions ====
What follows is a link to old installation instructions, which predate rpm installations from zmrepo or rpmfusion. These instructions are kept solely for reference.
[[Fedora/Archived]]

Fedora

2017-08-10T13:48:22Z

Knnniggett:

=== Installation Instructions ===
To install ZoneMinder on Fedora, please refer to the instructions shown on our readthedocs site.
[https://zoneminder.readthedocs.io/en/stable/installationguide/redhat.html Redhat - ZoneMinder Documentation]

==== Archived Installation Instructions ====
What follows is a link to old installation instructions, which predate rpm installations from zmrepo or rpmfusion. These instructions are kept solely for reference.
[[Fedora/Archived]]

CentOS

2017-08-10T01:56:26Z

Knnniggett:

CentOS/Archived

2017-08-10T01:55:56Z

Knnniggett: Created page with "== CentOS 5.6 & ZoneMinder 1.25.0 == This guide is for CentOS v5.6 (Notes for using this guide with CentOS 6 are in chapter 2.) with ZoneMinder v1.25.0 which are the ne..."

== CentOS 5.6 & ZoneMinder 1.25.0 ==
This guide is for CentOS v5.6 (Notes for using this guide with CentOS 6 are in chapter 2.) with ZoneMinder v1.25.0 which are the newest released versions as of this update (Summer 2011). If you are attempting to install newer versions of either using this guide, you will have to adjust file and directory names denoted below.

=== Step One - Get CentOS ===
You can download the “.iso” file(s) for CentOS from http://www.centos.org/ 
Alternatively download the net-install version of CentOS which is basically just the first CD.
Here is one location to download the net-install version: 
Download i386: http://mirror.symnds.com/distributions/CentOS-vault/5.6/isos/i386/CentOS-5.6-i386-netinstall.iso 
Download 64 bit: http://mirror.symnds.com/distributions/CentOS-vault/5.6/isos/x86_64/CentOS-5.6-x86_64-netinstall.iso 
Mirrors List: http://mirror.centos.org/centos/5/isos/

=== Step Two - Installation Source ===
Regardless of which method you use, the next few steps are the same. 
Begin by booting your system up with either cd/dvd. 
Choose the options that best fit your environment until you reach the “Installation Method”.

[[Image:centosnetinstal-http.png]]

Choose '''HTTP''' ONLY if you are using the net-install method. Otherwise, you probably want to choose '''Local CDROM'''. 

If you are using the net-install method then enter: 
Website Name: '''mirror.centos.org''' 
CentOS Directory: (for i386) '''/centos/5.6/os/i386''' 
CentOS Directory: (for 64 bit) '''/centos/5.6/os/x86_64'''

=== Step Three - Installation Packages ===
On the first screen, un-check "Desktop - Gnome" then check "Server" (not Server-GUI) 
Make sure that you have "Customize now" selected at the bottom. (do not check "Packages from CentOS Extras")

[[Image:centosinstall-packages1.png]]

Click "Next" to continue 

Once presented with the custom package selection, un-check/check the following:
Applications = Check only "Editors" and "Text Based Internet"
Development = Check only "Development Libraries" and "Development Tools"
Servers = Un-check everything
Base System = Check only "Base" (you can check Administration Tools and System Tools if you need them, but they are not necessary)

[[Image:Centosinstall-packages2.png]]

Now let the system finish the installation.

[[Image:centosisntall-end.png]]

=== Step Four - Configuration ===
After the first reboot, the setup screen should appear. If not, log into the system and type "setup"

[[Image:centosinstall-setup1.png]]

Select "Firewall Configuration" and set the "Security Level" and "SELinux" to "Disabled."

[[Image:centosinstall-setup2.png]]

Next, we are going to disable a number of system services. Go back to the setup screen and select "System Services" 
Un-Check:
apmd
bluetooth
cups
hidd
ip6tables
iptables
netfs
nfslock
pcscd
portmap
After disabling the services, select "Disable Now and On Boot", exit the setup tool, and log into the system if you haven't already.
*Screen is a simple program that allows you to run commands from a "Hosted" command line interface. This helps if you loose your connection to the server for any reason in that it enables you to resume (screen -r) right where you left off. Often times, I will start a large update/upgrade, leave it for the day, then come back and see where it's at later. Screen allows you to do that without having to be connected.
*Install Screen
yum install screen
*To start a screen session just type
screen
*If you get disconnected and need to resume your session of screen simply type
screen -r

=== Step Five - Installing ZoneMinder 1.25.0 ===
First, we need to download files and prepare the system
*Add the RPM Forge repository to CentOS. This will allow the installation of a number of services/applications later without having to manually install them.
<pre># For i386 CentOS 5.x run:
rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm

# For 64 bit CentOS 5.x run:
rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm</pre>
*Download the needed files, ZoneMinder 1.25.0 and the Cambozola addon
wget http://www2.zoneminder.com/downloads/ZoneMinder-1.25.0.tar.gz
wget http://www.zoneminder.com/sites/zoneminder.com/downloads/cambozola.jar
*Now let's install all the services and programs that will be needed (''If you encounter any dependency errors using yum, try running '''yum clean all''' then re-try the install command(s).'')

*tip: Copy/paste two lines at a time

<pre>
yum -y install mysql mysql-server mysql-devel php php-gd php-mysql httpd gcc \
pcre-devel gd mod_ssl glib2-devel gcc-c++ ntp gnutls-devel ImageMagick

yum -y install libjpeg-devel perl-Archive-Tar perl-MIME-Lite perl-MIME-tools \
perl-Date-Manip perl-LWP-UserAgent-Determined

yum -y install perl-PHP-Serialization perl-Device-SerialPort perl-Archive-Zip perl-Sys-Mmap \
perl-Module-Load subversion git yasm bzip2 bzip2-devel bzip2-libs lbzip2</pre>
*Now let's update everything within the new CentOS install
yum -y update
*At this point, it might be useful to reboot your system. Oddly, sometimes things don't work right unless you reboot after all the updates
reboot -or- shutdown -r now
*After rebooting, log into your system
==== Install ffmpeg ====
*Now we need to make sure we use the latest "tested" version of "ffmpeg". This is the latest version of ffmpeg that the ZoneMinder developers have tested with. Download, compile and install ffmpeg:
<pre>git clone git://git.videolan.org/ffmpeg.git
cd ffmpeg
./configure --enable-gpl --enable-shared --enable-pthreads
make
</pre>

*The following commands must be done as '''root'''

<pre>
make install
make install-libs
</pre>
edit /etc/ld.so.conf and add the line "/usr/local/lib"
<pre>
ldconfig -v
</pre>

*Next, run 'ffmpeg' from the command line. Make sure you do not get any errors:

<pre>
ffmpeg
</pre>

*If 'ffmpeg' runs correctly, you'll see something similar to this:

<pre>
ffmpeg version N-32260-gaebb56e, Copyright (c) 2000-2011 the FFmpeg developers
built on Aug 31 2011 21:41:49 with gcc 4.1.2 20080704 (Red Hat 4.1.2-50)
configuration: --enable-shared --enable-swscale --enable-gpl --enable-pthreads
libavutil 51. 14. 0 / 51. 14. 0
libavcodec 53. 12. 0 / 53. 12. 0
libavformat 53. 10. 0 / 53. 10. 0
libavdevice 53. 3. 0 / 53. 3. 0
libavfilter 2. 37. 0 / 2. 37. 0
libswscale 2. 0. 0 / 2. 0. 0
libpostproc 51. 2. 0 / 51. 2. 0
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'
</pre>

==== Enable services ====
*Turn everything on. These commands must be run as root.

<pre>
chkconfig httpd on
chkconfig mysqld on
chkconfig ntpd on
service httpd start
service mysqld start
service ntpd start
</pre>
==== Install Zoneminder ====
*Next, we need to extract the contents of the ZoneMinder "tar" file, then jump into its directory.
<pre>
cd /root/ # Or your work directory for this installation
tar -zxvf ZoneMinder-1.25.0.tar.gz
cd ZoneMinder-1.25.0
</pre>
*Now we are going to configure ZoneMinder with some additional parameters. What is listed are the default CentOS directory locations.
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin

Note: It seems for Zoneminder to build with newer versions of ffmpeg, (certainly 0.6.3) you'll need to append CPPFLAGS="-D__STDC_CONSTANT_MACROS" to the end of the
./configure line thus:

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-ffmpeg=/usr/local/share/ffmpeg CPPFLAGS="-D__STDC_CONSTANT_MACROS"

There is a section in the FAQ ''"When running configure, I get a lot of messages about not being able to compile the ffmpeg libraries"'' about this [[http://www.zoneminder.com/wiki/index.php/FAQ]].

Worth mentioning here is the section in the FAQ under the heading "''My load is too high, how can I reduce it?''" [[http://www.zoneminder.com/wiki/index.php/FAQ]]. This descibes how you can possibly reduce CPU load by half by
changing the system's jpeg libraries and building Zoneminder with processor specific instructions.
Since CentOS 6.4 CentOS now comes with libjpeg_turbo as the standard JPEG library leading to a more optimised Zoneminder.

By default ZM_DB_HOST=localhost, ZM_DB_NAME=zm, ZM_DB_USER=zmuser, and ZM_DB_PASS=zmpass.
*Change "zmuser" (if you want) with the user that you will use within MySQL to access the ZoneMinder database
*Change "zmpass" with the password you will be using with the "zmuser" account
So if you wish to change it, use a command like:
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass

*if you get the configure "error zm requires libmysqlclient.a" with 64 bit CentOS add the following to the end of your configure statement
--with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql"

e.g. For CentOS 5.6 64-bit with support for ffmpeg. The whole command must be executed on one line. Make sure to change the '''zmpass''' to a password that matches your installation.
<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-ffmpeg=/usr/local/share/ffmpeg --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql" CXXFLAGS="-D__STDC_CONSTANT_MACROS"
</pre>
* Run '''make''' and '''make install''' after running the configuration steps above.

make
# Run the next command as root
make install

==== Configure MySQL ====
*Need to add a password for the root user of MySQL
*Create the zm database
*Create the zm database user with permissions and password
mysql
mysql> SET PASSWORD FOR root@localhost=PASSWORD('new_root_password');
>Query OK, 0 rows affected (0.00 sec)
mysql> create database zm;
>Query OK, 1 row affected (0.01 sec)
mysql> CREATE USER 'your_zm_user'@'localhost' IDENTIFIED BY 'your_zm_password_from_above';
Query OK, 0 rows affected (0.01 sec)
mysql> grant CREATE, INSERT, SELECT, DELETE, UPDATE on zm.* to your_zm_user@localhost;
>Query OK, 0 rows affected (0.02 sec)
mysql> exit
>Bye
*Import the tables into the zm database
cd /root/ZoneMinder-1.25.0
mysql -u root -p zm < db/zm_create.sql

==== Finalize Installation of ZoneMinder ====
'''All remaining CLI commands need to be run as root.'''
*Make ZoneMinder startup automatically after a reboot
# from the ZoneMinder-1.25 source directory
cp scripts/zm /etc/init.d/
chmod +x /etc/init.d/zm
chkconfig zm on
*Add the Cambozola Java web interface
cp cambozola.jar /var/www/html/zm/
*Make sure you have permission to view it from apache:
chown apache:apache /var/www/html/zm/cambozola.jar
*Start ZoneMinder
service zm start

Note: You may get an error when you try to start Zoneminder using the 'zm' startup script as per this forum post: [[http://www.zoneminder.com/forums/viewtopic.php?f=21&t=17827]] .
The reason for this was the default 'zm' startup script was formatted with DOS line endings. If you get the errors as detailed in the above post then the fix is to convert the
'zm' file to use UNIX style line endings. You can do this in the Vim text editor whilst editing the 'zm' file thus: ':set fileformat=unix' then save the file ':wq'. You can also
use the utility dos2unix to convert the file.

* tick the box for support for the Cambozola addon within your ZoneMinder installation: http://ip-address/zm (Options->Images tab->OPT_CAMBOZOLA)

Now have fun and add your cameras to ZoneMinder knowing you now have a very stable and streamlined OS to run it on.

== CentOS 6 Notes ==

The installation for CentOS 6 is pretty much the same.
Download CentOS 6 minimal installation ISO (CentOS-6.0-i386-minimal.iso – 257MB). Burn to CD and install. We only want to be running in console text mode not GUI graphics mode. During installation configure network and tick to enable network adapter.
* Login as root and update the base install:
<pre>yum -y update</pre>
* Install required packages, other useful packages, and their dependencies
<pre>
yum groupinstall core
yum groupinstall base
yum install gcc gcc-c++ wget bison mysql-devel mysql-server php php-mysql php-pear php-pear-DB php-mbstring \
nano tftp-server httpd make ncurses-devel libtermcap-devel sendmail sendmail-cf caching-nameserver \
sox newt-devel libxml2-devel libtiff-devel php-gd audiofile-devel gtk2-devel subversion nano kernel-devel \
bison-devel ncurses zlib zlib-devel openssl openssl-devel gnutls-devel php-process perl-Time-HiRes
</pre>

Suggestion:
To remove various configure/make errors in Centos 6.2, you may also want to install:<pre>
bzip2-libs ffmpeg-devel ffmpeg-php perl-Net-SFTP-Foreign perl-Expect perl-LWPx-ParanoidAgent.x86_64</pre>

Now we continue from step four (4).
==== Installation of ZoneMinder ====
* In step five (5) the correct RPM Forge repository is:
<pre># For i686 CentOS 6.x run:
rpm -Uhv http://apt.sw.be/redhat/el6/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.i686.rpm

# For 64 bit CentOS 6.x run:
rpm -Uhv http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm</pre>

* In step five (5) the command that seems to configure zoneminder correctly is:
<pre>
CXXFLAGS=-D__STDC_CONSTANT_MACROS ./configure --with-webdir=/var/www/html/zm \
--with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache \
ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=your_zm_user ZM_DB_PASS=your_zm_password ZM_SSL_LIB=openssl
</pre>

Suggestion:
For Centos 6.2, I used the following configure string for success:<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=<zm user> ZM_DB_PASS=<zm user passwd> ZM_SSL_LIB=openssl --with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql" --with-ffmpeg=/usr/share/ffmpeg CXXFLAGS="-D__STDC_CONSTANT_MACROS" </pre>

==== Troubleshooting FFmpeg Errors Building ZoneMinder ====
Using the git version of FFmpeg can cause the ZoneMinder make process to fail with unresolved symbols in ffmpeg. To remedy this, use version 0.6.5 of FFmpeg with the same configure instructions as the normal install above.
FFmpeg 0.6.5: http://ffmpeg.org/releases/ffmpeg-0.6.5.tar.bz2
==== Troubleshooting Blank Page ====
If everything went ok but when accessing zoneminder's web page at http://localhost/zm, the page is blank this means that there is a problem with PHP short tags. Edit setting short_open_tag in php.ini (/etc/php.ini) and change it to On.
* Restart apache server with:
<pre>service httpd restart</pre> and you should be up and running.
==== Trouble shooting full drive with CentOS 6 ====
The default drive structure has chaned from that of CentOS 5 having the full drive allocated to the /root partition. CentOS 6 by default makes a logical volume 'LVM' of 10% your drives space for the /root partition and the remaining drive as the /home partion with the exception of the swap and boot partitions.

The will cause Zoneminder to fill the /root partition as the /var/www/html/zm/events directory is by default located here, you can use the system-config-lvm utility to re-adjust this partition balance if your system has been installed with the default partition structure.

It is best to install CentOS 6 with a custom partition layout that is the same as CentOS 5 structure, you can also if using a single physical had drive do with out the LVM drives and create an EXT4 /root partion along with the standard /boot and /swap partitions.

----

[[== '''P.S.''' ==]] aspcicc@jumpy.it
(Update: This does not appear to be required any more.)

Hi! and thanks for your guide.. i want to add a little correction that have made me crazy to resolve, when I poweroff or reboot system i obtain an error related to mysql database and i have understood that the problem was because mysqld is stopped before zoneminder to be more specific there isn't a link under rc0.d (halt) and rc6.d (reboot) to zoneminder that for this lack is simply killed by killall. To resolve this problem you need to add at the start of zm (under /etc/init.d) the line

' # chkconfig: 345 99 01 ' (without ' of course)

and then run
chkconfig --level 345 zm on
chkconfig --level 06 zm off

So the link to shutdown zm is created under rc0.d and rc6.d and zoneminder is started at the end of poweron and stopped at the beginning of the poweroff

For information about priority starting and stopping processes see: http://www.netadmintools.com/art94.html

----

Added Dependency: ImageMagick

Removed Dependency: perl-Time-HiRes, which causes a conflict with the default perl package.

Also, mysql seems to install with no password for the root user, and the zm DB create script creates the database on the fly, which means that the database create command needs to have the "-p zm" removed from the command line.

Could someone verify that this is correct, to make sure it's not just something I missed?

Thanks!
terry@cnysupport.com

----
Struggling to get x264 and ffmpeg working? I used the latest SVN versions not the Centos packages. But I was getting

''ffmpeg: error while loading shared libraries: libavdevice.so.53: cannot open shared object file: No such file or directory''

I followed these instructions:

<pre>cd /etc/ld.so.conf.d</pre>

* add another file: custom-libs.conf
* inside, put :

<pre>/usr/local/lib</pre>

* save the file
* run ldconfig
<pre>ldconfig</pre>

BeeryGaz

----

==== Failed monitors or ZM refusing to start ====
A problem that took me some time to figure out on two installations was SElinux.
SElinux stops Zoneminder from accessing some system parts or doing some functions so will cause various errors or simply drive you nuts trying to figure out.

Look at the following page on how to disable SElinux or use permissive mode.

<pre>http://www.centos.org/docs/5/html/5.2/Deployment_Guide/sec-sel-enable-disable.html</pre>

Some of the errors that I was getting with a fresh install on CentOS 6 was
<pre>
2013-02-16 16:13:10.828590 zmwatch 14898 ERR Can't open memory map file '/dev/shm/zm.mmap.1': No such file or directory zmwatch.pl
2013-02-16 16:13:10.736988 zmfix 15317 ERR Can't stat /dev/video0: Permission denied zmfix.cpp
</pre>

----
== ZoneMinder 1.26.x ==

Zoneminder after a long period of none development is now being developed by the community, these notes are to try and help with the installation of the new release on CentOS 5 and CentOS 6.
All testing has been done on a CentOS 6.4 fresh install server.

=== Cmake installation notes ===

Compiling of Zoneminder can now be done with the 'Cmake' command in replacement of the ./configure command this should automatically configure the build with the minimum of parameters. The 'Cmake' command at time of writing produced a partially working installation with the main files installed into /usr/local/bin/zoneminder and associated folders, different from the above guides.

The webfiles require to be linked via a zoneminder.conf file located with in the /disto/redhat directory inside the build directory that requires to be coped to the /etc/httpd/conf.d directory, this will need to be edited to the correct location of the webfiles and remove the local only command as indicated with in the file.

The Cmake install failed to use my BTTV capture card producing various errors with a potential solution given here <pre>http://www.zoneminder.com/forums/viewtopic.php?f=30&t=21709</pre>

=== ./configure compile ===

To install via the traditional ./configure method you first need to run the ./bootstrap.sh file to generate the required configure file, the install can then progress as the above installation guides.

This method has produced a fully working installation at time of writing.

== pt_BR Instructions ==

Here is a good walkthrough install of zoneminder in CentOS using the rpm package method. It is intended to Portuguese (pt or pt_BR) audience.

<pre>http://dulimind.blogspot.com.br/2015/02/zoneminder-no-centos-6-metodo-facil-com.html</pre>
----

[[Categories: Linux distributions]]

Fedora

2017-08-10T01:54:04Z

Knnniggett:

Fedora/Archived

2017-08-10T01:51:36Z

Knnniggett: Created page with "==Fedora 18 (alpha)== *FIXED: ''if you get problems with Live Video not working'' due to a problem with the sockets. **ERROR: socket_sendto permission errors. *Make sure..."

==Fedora 18 (alpha)==
*FIXED: ''if you get problems with Live Video not working'' due to a problem with the sockets. 
**ERROR: socket_sendto permission errors.
*Make sure your cgi-bin ScriptAlias is correct as shown below. 
*''ffmpeg libraries from Fedora rpms do not work'' with zm. You have to install from source (yuck).

This is how I got it installed... 

Do all the following as sudo (or root) 
'''install packages''' 
yum install mysql mysql-server zoneminder 

''' disable selinux 
vi /etc/selinux/config 
*change the word 'enforcing' to 'disabled' 

'''REBOOT'''

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf
* in the section - <Directory "/usr/share/zoneminder/www">
**remove the line "Deny from all # DELETE THIS LINE"
**remove the '-Indexes' on the Options line on Line 17 )I don't think the '-' is supposed to be there
**Comment out the Order and Allow lines and insert the new syntax 'Require all granted' as a new line
* I also got a ScriptAlias error for the cgi-bin/zm alias so I commented the cgi-bin scriptAlias in the /etc/httpd/conf/httpd.conf

#F18 /etc/httpd/conf.d.zoneminder.conf
Alias /zm "/usr/share/zoneminder/www"
<Directory "/usr/share/zoneminder/www">
Options FollowSymLinks
AllowOverride All
# NEW format
Require all granted
# The code unfortunately uses short tags in many places
php_value short_open_tag 1
#Deny from all # DELETE THIS LINE
</Directory>
ScriptAlias /cgi-bin "/usr/libexec/zoneminder/cgi-bin"
<Directory "/usr/libexec/zoneminder/cgi-bin">
Options +ExecCGI +MultiViews +SymLinksIfOwnerMatch
AllowOverride All
# NEW format
Require all granted
php_value short_open_tag 1
</Directory>
 
'''start httpd:''' 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 17==
'''install packages''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 14==
'''install packages:''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
/etc/init.d/mysqld start 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
/etc/init.d/httpd start 

'''start zoneminder''' 
/etc/init.d/zoneminder start 

==Fedora 11, 12 and 13==
'''The Easy Way''' Adapted from a forum post by "hiredguntech" or just search the forum for "flowers for candy"

Step-by-step installation of ZM v1.24.2 on Fedora-12.

(1) load fc12 using the netinstall ISO (the CD wants to use dhcp and doesn't work well with an assigned fixed IP) - turn off 'office' and turn on 'server' and 'development'. Besure to include a large /var partition through custom partitioning and use localhost instead of what it suggests (domain.localhost ?). Also, if you're using a capture card install it (them) in the system before starting the netinstall CD. Save these steps as a .txt file so the code can be cut and paste into the terminal with ease.

[2] Remove evolution from task bar (right click... (not a requirement)).

[3] Set screensaver to NOT require password and set it to 20 minutes or more (menu-system::preferences::screensaver).

(4) Disable SELinux. (menu-system::Admin::SELinux Mgmnt; change system default enforcing mode to disabled).

[5] Enable sudo for yourself. From a terminal (menu-Application::System Tools::Terminal),
Code:

su

(enter root password)

echo ''''YourUserName''' ALL=(ALL) ALL' >> /etc/sudoers (put YOUR user name from FC12 installation in place of '''YourUserName''')

(6) Set up the RPM Fusion Repository (in open terminal).

Code:

rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm

rpm -ivh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

exit

exit (closes terminal window)

(7) Install the pre-requisites, (menu-System::Administration::Add/Remove Software) type in the search field the following package names and select each of the closest match (there will be 'other' packages related or similar named - look for the right one, and check-it.)

mysql-server

mysql-devel

pcre-devel

ffmpeg

ffmpeg-devel

Hit the 'Apply' button, accept any added packages, type root password, and let this stuff load.

[8] Install any updates that are available, its the yellow icon up by the time.

(9) Enable the services: web and db. (menu-System::Administration::Services) and find the following:

httpd

mysqld

for each of them hit the 'enable button' so you can start them later.

(10) Reboot. This allows all the services to start and settle in.

(11) Now add Zoneminder (menu-System::Administration::Add/Remove Software) Type Zoneminder in the search field select it and apply.

[13] '''Note:''' To edit as root: open a terminal (menu-Application::System Tools::Terminal), su to root, type 'gedit <path/filename>'. Now you have sufficient permissions to edit & save as root.

(14) Edit as root /etc/httpd/conf.d/zoneminder.conf to remove the 'Deny from All' line. It even says 'DELETE THIS LINE', so it should be easy to find. Save it.

(15) As root, [or with sudo] build the zm database (menu-Application::System Tools::Terminal).

Code:

su

(enter root password)

mysql mysql < /usr/share/zoneminder/db/zm_create.sql

mysqladmin reload

mysql mysql

grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass';

\q

exit

exit

(16) Enable zoneminder. (menu-System::Administration::Services) and find zoneminder. Enable it. You can start the service hear also, Or in a terminal:

Code:

service zoneminder start

[18] Last thing - edit the SECOND entry of short_open_tag down at line 229. Again as root (menu-Application::System Tools::Terminal), gedit /etc/php.ini

Change short_open_tag from 'off' to 'on'

[19] reboot. open browser, type 'localhost/zm'

[20] It may be necessary to change the ffmpeg path in options::images to get ffmpeg to make videos. Generally removing the /local from the existing path will fix this issue

'''Or (the original wiki walk through)'''

You should be able to just do "yum install zoneminder", create the zm database, find the zm_create.sql file (rpm -ql zoneminder) and import it to mysql, then start zoneminder. Plus allow web access. Edit /etc/httpd/conf.d/zoneminder.conf and comment out (#) or delete this line :-

Deny from all # DELETE THIS LINE

Restart/reload apache

sudo service httpd restart

This didn't work for me due to 2 problems. First was php.ini section short_open_tag = Off, set to on

short_open_tag = On

Restart/reload apache

sudo service httpd restart

The other problem was zm_create.sql had duplicate indexes reported using phpMyAdmin. Removed all "INSERT INTO MonitorPresets" and "INSERT INTO MonitorPresets" in zm_create.sql and that imported cleanly. Alternatively just import from the command line mysql -u zmuser -p < zm_create.sql

http://www.zoneminder.com/forums/viewtopic.php?p=50242

'''Manual Install Version 1.24.2 with ffmpeg enabled'''

Version 1.23.3 has always compiled ok on Fedora 9/10/11 but I had problems with version 1.24.2.

Problems with compiling fixed by adding #include <cstdio> to all .cpp files in src directory and removing ccache package (yum remove ccache)

http://www.zoneminder.com/forums/viewtopic.php?p=55152

http://www.zoneminder.com/forums/viewtopic.php?t=12515&sid=0da85eb2fc78917d7a78cf788603a320

If using ffmpeg and ffmpeg-devel packages you may see problem compiling with libavutil.a . I could not get ffmpeg to compile so downloaded the Fedora source package and compiled it manually.

yumdownloader --source ffmpeg

sudo rpm -Uvh ffmpeg-0.5-5.20091026svn.fc12.src.rpm

Needed the following packages

sudo yum install dirac-devel faad2-devel gsm-devel imlib2-devel lame-devel libdc1394-devel libtheora-devel libvdpau-devel openjpeg-devel \
schroedinger-devel speex-devel texi2html x264-devel xvidcore-devel yasm

See http://fozzolog.fozzilinymoo.org/tech/2009/11/recompiling-ffmpeg-for-fedora-12-to-add-faac-support.html (don't need to add faac support, just follow procedure)

My rpmbuild failed so from the BUILD/ffmpeg-20091026

make
sudo make install
sudo make install-libs

and configured ZoneMinder to use /usr/local for FFMPEG

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost \
ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr -L/usr/lib/mysql" ZM_SSL_LIB=openssl --with-ffmpeg=/usr/local

==Fedora 8==
* Have packages for Apache and MySQL installed on the system.
* Install the zoneminder RPM package on the system
: Fedora Information for package zoneminder
: * http://koji.fedoraproject.org/koji/packageinfo?packageID=4691
* Configure zoneminder
* Make sure Apache and MySQL services are running
* Edit the zoneminder.conf apache configuration file to allow web connections
vi /etc/httpd/conf.d/zoneminder.conf
* Build the MySQL database table for zoneminder
mysql -p -u root mysql < /usr/share/zoneminder/db/zm_create.sql > mysqladmin -p -u root reload

The Fedora RPM creates /var/log/zoneminder, but the database scripts point logs to /tmp, rather than the new directory.
* Click '''Options''', '''Paths''' tab, and change
ZM_PATH_LOGS = /var/log/zoneminder
* Click '''Options''', '''Debug''' tab, and change
ZM_EXTRA_DEBUG_LOG = /var/log/zoneminder/zm_debug.log+

* Install ffmpeg on Fedora.
Due to licensing the ffmpeg package is absent from Fedora. It can be added from [[Fedora_Linux_Distribution_Reference#Livna:_Get_Important_Packages_Missing_From_Fedora|Livna]].
wget http://rpm.livna.org/livna-release-8.rpm
rpm -ih livna-release-8.rpm
yum install ffmpeg
yum install ffmpeg-devel
Which provides the following: ffmpeg-libs-0.4.9-0.41.20071011.lvn8, ffmpeg-0.4.9-0.41.20071011.lvn8, ffmpeg-devel-0.4.9-0.41.20071011.lvn8

* Test ffmpeg
ffmpeg -f image2 -i %03d-capture.jpg /tmp/movie.mpg

==Fedora 7==
* Builds From source - see [[Fedora Core 6 Step-by-Step]] '''AS WELL AS''' [http://www.zoneminder.com/forums/viewtopic.php?t=9414 Fedora 7 forum topic]
*RPMs are Available in the '''main Fedora 7 distribution''', and in the development 'rawhide' tree.
**Its as easy as running: yum install zoneminder
**Take a look at [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 6==
*Build from source [[Fedora Core 6 Step-by-Step]]

* RPMs are also available right now in '''Fedora Extras''' for Fedora Core 6.
** [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 4==
* http://www.zoneminder.com/forums/viewtopic.php?t=5991 
Set web user and group correctly and set the log dir to a writeable location.
With FC4 there are three things that must be done to get ZM running,:
#is in the /etc/ld.so.conf.d/ dir created a file with 775 perm called zm.conf and add the line '/usr/local/lib' to it and type 'ldconfig' once it is added, also with a fresh install of FC4 make sure SE linux is disabled if you are not using it. Check your log path in options under the paths tab. This will tell you were the log are going to be put.
#Second make sure the path exists.
#Third create the log files if they do not exist and make sure that they have the correct permissions. '''If zm can not open and write the log files, it will not start. '''

Supported distributions

2017-08-10T01:41:32Z

Knnniggett:

Based on either known supported versions in zmrepo, official packages and PPA

[[Fedora]]

[[CentOS]] (includes RHEL, SL, and some clones)

[[Ubuntu]]

[[Debian]]

* TIP: for specific distro install guides, check great articles available under [[contents#Distribution-specific guides]];

Supported distributions

2017-08-10T01:41:18Z

Knnniggett:

Based on either known supported versions in zmrepo, official packages and PPA

[[Fedora]]

[[CentOS]] (includes RHEL, SL, and some clones)

[[Ubuntu]]

[[Debian]] 8

* TIP: for specific distro install guides, check great articles available under [[contents#Distribution-specific guides]];

Supported distributions

2016-11-09T13:10:08Z

Knnniggett:

Based on either known supported versions in zmrepo, official packages and PPA

[[Fedora]] 23 & 24

[[CentOS]] 6 & 7 (includes RHEL, SL, and some clones)

[[Ubuntu]] 14.04, 15.04, 15.10

[[Debian]] 8

* TIP: for specific distro install guides, check great articles available under [[contents#Distribution-specific guides]];

Netcat

2016-03-03T00:25:36Z

Knnniggett: /* Create the Monitor */

== Netcat IP Cameras ==
Netcat is one of many Chinese IP camera vendors.
http://www.netcatcctv.com/English/index.html

Like many other Chinese cameras, if your camera looks similar but goes by a different name, then try the programming steps below.
It may work.

== Helpful Tools ==
The ONVIF Device Manager is a free, Windows only based tool which is very helpful in developing ZoneMinder support for cameras which support the Onvif standard.
https://sourceforge.net/projects/onvifdm/

== Netcat Outdoor PTZ Camera with 20x Optical Zoom ==
[[File:2015518112320.jpg|right]]
Netcat sells several varieties of PTZ cameras. These instructions are based around model PT-PTZ2084. See the photo on the right.
 
 
Be advised, this camera ships with a hard coded ip address of 192.168.1.10. DHCP is turned off. One cannot change this from the camera's web portal. Instead, install the included CMS software onto a Windows machine. Find the Device Manager, and add the device to the CMS sofware. When adding the device, you will have the opportunity to change the ip address of the camera. Be advised, you cannot change the password at this point, even though it may look like you can (you will just get an error). Once the camera has been added to the CMS sofware and appears in the hardware tree on the left, double click it to get the camera to load. Then right click it, and select "Device Config". This will bring up the camera's configuration screens. To avoid lag and other unnecessary problems, it is highly advised to lower the frame to 5 fps.

== Create the Monitor ==

From the Zoneminder console, click "Add New Monitor" and enter the following:

;General:
:Name: {give the camera a name}
:Source Type: ffmpeg
:Function: {select an appropriate function from the dropdown}
:Enabled: Tick
:Maximum FPS: Empty
:Alarm Maximum FPS: Empty
;Source
:Source Path: rtsp://{ip address}:554/user=admin&password={admin password}&channel=1&stream=0.sdp?
:Remote Method: RTP/RTSP
:Options: Empty
:Target colorspace: 32 bit color
:Capture Width: 1920
:Capture Height: 1090
;Control
:Controllable: Tick
:Control Type: Netcat ONVIF
:Control Device: Empty
:Control Address: {ip address}:8899
:Auto Stop Timeout: 1.00
 
NOTE: As of this writing, the Netcat ONVIF control script has just recently made it into the source code.
If you do not have this control script already installed, you will need to import the information from here: https://github.com/ZoneMinder/ZoneMinder/blob/master/scripts/ZoneMinder/lib/ZoneMinder/Control/Netcat.pm

First copy the control script, Netcat.pm, onto your filesystem into the folder with the rest of your control scripts.
Next, save the sql statement shown in the commit to a file, call it netcat.sql, and then use zmcamtool to import it into your system:
''sudo zmcamtool.pl --import netcat.sql'' .

Netcat

2016-03-03T00:24:17Z

Knnniggett: /* Create the Monitor */

== Netcat IP Cameras ==
Netcat is one of many Chinese IP camera vendors.
http://www.netcatcctv.com/English/index.html

Like many other Chinese cameras, if your camera looks similar but goes by a different name, then try the programming steps below.
It may work.

== Helpful Tools ==
The ONVIF Device Manager is a free, Windows only based tool which is very helpful in developing ZoneMinder support for cameras which support the Onvif standard.
https://sourceforge.net/projects/onvifdm/

== Netcat Outdoor PTZ Camera with 20x Optical Zoom ==
[[File:2015518112320.jpg|right]]
Netcat sells several varieties of PTZ cameras. These instructions are based around model PT-PTZ2084. See the photo on the right.
 
 
Be advised, this camera ships with a hard coded ip address of 192.168.1.10. DHCP is turned off. One cannot change this from the camera's web portal. Instead, install the included CMS software onto a Windows machine. Find the Device Manager, and add the device to the CMS sofware. When adding the device, you will have the opportunity to change the ip address of the camera. Be advised, you cannot change the password at this point, even though it may look like you can (you will just get an error). Once the camera has been added to the CMS sofware and appears in the hardware tree on the left, double click it to get the camera to load. Then right click it, and select "Device Config". This will bring up the camera's configuration screens. To avoid lag and other unnecessary problems, it is highly advised to lower the frame to 5 fps.

== Create the Monitor ==

From the Zoneminder console, click "Add New Monitor" and enter the following:

;General:
:Name: {give the camera a name}
:Source Type: ffmpeg
:Function: {select an appropriate function from the dropdown}
:Enabled: Tick
:Maximum FPS: Empty
:Alarm Maximum FPS: Empty
;Source
:Source Path: rtsp://{ip address}:554/user=admin&password={admin password}&channel=1&stream=0.sdp?
:Remote Method: RTP/RTSP
:Options: Empty
:Target colorspace: 32 bit color
:Capture Width: 1920
:Capture Height: 1090
;Control
:Controllable: Tick
:Control Type: Netcat ONVIF
:Control Device: Empty
:Control Address: {ip address}:8899
:Auto Stop Timeout: 1.00
 
NOTE: As of this writing, the Netcat ONVIF control script has not made it into the source code.
If you do not have this control script installed, you will need to import the information from here: https://github.com/ZoneMinder/ZoneMinder/blob/master/scripts/ZoneMinder/lib/ZoneMinder/Control/Netcat.pm

First copy the control script, Netcat.pm, onto your filesystem into the folder with the rest of your control scripts.
Next, save the sql statement shown in the commit to a file, call it netcat.sql, and then use zmcamtool to import it into your system:
''sudo zmcamtool.pl --import netcat.sql'' .

Netcat

2016-02-24T17:26:51Z

Knnniggett: /* Netcat Outdoor PTZ Camera with 20x Optical Zoom */

== Netcat IP Cameras ==
Netcat is one of many Chinese IP camera vendors.
http://www.netcatcctv.com/English/index.html

Like many other Chinese cameras, if your camera looks similar but goes by a different name, then try the programming steps below.
It may work.

== Helpful Tools ==
The ONVIF Device Manager is a free, Windows only based tool which is very helpful in developing ZoneMinder support for cameras which support the Onvif standard.
https://sourceforge.net/projects/onvifdm/

== Netcat Outdoor PTZ Camera with 20x Optical Zoom ==
[[File:2015518112320.jpg|right]]
Netcat sells several varieties of PTZ cameras. These instructions are based around model PT-PTZ2084. See the photo on the right.
 
 
Be advised, this camera ships with a hard coded ip address of 192.168.1.10. DHCP is turned off. One cannot change this from the camera's web portal. Instead, install the included CMS software onto a Windows machine. Find the Device Manager, and add the device to the CMS sofware. When adding the device, you will have the opportunity to change the ip address of the camera. Be advised, you cannot change the password at this point, even though it may look like you can (you will just get an error). Once the camera has been added to the CMS sofware and appears in the hardware tree on the left, double click it to get the camera to load. Then right click it, and select "Device Config". This will bring up the camera's configuration screens. To avoid lag and other unnecessary problems, it is highly advised to lower the frame to 5 fps.

== Create the Monitor ==

From the Zoneminder console, click "Add New Monitor" and enter the following:

;General:
:Name: {give the camera a name}
:Source Type: ffmpeg
:Function: {select an appropriate function from the dropdown}
:Enabled: Tick
:Maximum FPS: Empty
:Alarm Maximum FPS: Empty
;Source
:Source Path: rtsp://{ip address}:554/user=admin&password={admin password}&channel=1&stream=0.sdp?
:Remote Method: RTP/RTSP
:Options: Empty
:Target colorspace: 32 bit color
:Capture Width: 1920
:Capture Height: 1090
;Control
:Controllable: Tick
:Control Type: Netcat ONVIF
:Control Device: Empty
:Control Address: {ip address}:8899
:Auto Stop Timeout: 1.00
 
NOTE: As of this writing, the Netcat ONVIF control script has not made it into the source code.
If you do not have this control script installed, you will need to import the information from this commit: https://github.com/knnniggett/ZoneMinder/commit/7a42a8c3f96dfffdc360b297d6b26157b8bd5b97

First copy the control script, Netcat.pm, onto your filesystem into the folder with the rest of your control scripts.
Next, save the sql statement shown in the commit to a file, call it netcat.sql, and then use zmcamtool to import it into your system:
''sudo zmcamtool.pl --import netcat.sql'' .

Netcat

2016-02-24T17:26:38Z

Knnniggett: /* Netcat Outdoor PTZ Camera with 20x Optical Zoom */

== Netcat IP Cameras ==
Netcat is one of many Chinese IP camera vendors.
http://www.netcatcctv.com/English/index.html

Like many other Chinese cameras, if your camera looks similar but goes by a different name, then try the programming steps below.
It may work.

== Helpful Tools ==
The ONVIF Device Manager is a free, Windows only based tool which is very helpful in developing ZoneMinder support for cameras which support the Onvif standard.
https://sourceforge.net/projects/onvifdm/

== Netcat Outdoor PTZ Camera with 20x Optical Zoom ==
[[File:2015518112320.jpg|right]]
Netcat sells several varieties of PTZ cameras. These instructions are based around model PT-PTZ2084. See the photo on the right.
 
Be advised, this camera ships with a hard coded ip address of 192.168.1.10. DHCP is turned off. One cannot change this from the camera's web portal. Instead, install the included CMS software onto a Windows machine. Find the Device Manager, and add the device to the CMS sofware. When adding the device, you will have the opportunity to change the ip address of the camera. Be advised, you cannot change the password at this point, even though it may look like you can (you will just get an error). Once the camera has been added to the CMS sofware and appears in the hardware tree on the left, double click it to get the camera to load. Then right click it, and select "Device Config". This will bring up the camera's configuration screens. To avoid lag and other unnecessary problems, it is highly advised to lower the frame to 5 fps.

== Create the Monitor ==

From the Zoneminder console, click "Add New Monitor" and enter the following:

;General:
:Name: {give the camera a name}
:Source Type: ffmpeg
:Function: {select an appropriate function from the dropdown}
:Enabled: Tick
:Maximum FPS: Empty
:Alarm Maximum FPS: Empty
;Source
:Source Path: rtsp://{ip address}:554/user=admin&password={admin password}&channel=1&stream=0.sdp?
:Remote Method: RTP/RTSP
:Options: Empty
:Target colorspace: 32 bit color
:Capture Width: 1920
:Capture Height: 1090
;Control
:Controllable: Tick
:Control Type: Netcat ONVIF
:Control Device: Empty
:Control Address: {ip address}:8899
:Auto Stop Timeout: 1.00
 
NOTE: As of this writing, the Netcat ONVIF control script has not made it into the source code.
If you do not have this control script installed, you will need to import the information from this commit: https://github.com/knnniggett/ZoneMinder/commit/7a42a8c3f96dfffdc360b297d6b26157b8bd5b97

First copy the control script, Netcat.pm, onto your filesystem into the folder with the rest of your control scripts.
Next, save the sql statement shown in the commit to a file, call it netcat.sql, and then use zmcamtool to import it into your system:
''sudo zmcamtool.pl --import netcat.sql'' .

Netcat

2016-02-24T17:18:23Z

Knnniggett: /* Helpful Tools */

Netcat

2016-02-24T17:18:08Z

Knnniggett: /* Netcat IP Cameras */

Netcat

2016-02-24T17:15:29Z

Knnniggett: /* Create the Monitor */

Netcat

2016-02-24T17:14:35Z

Knnniggett: /* Create the Monitor */

Hardware Compatibility List

2016-02-24T17:13:38Z

Knnniggett: /* Network Cameras */

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amovision AM-Q630M]]

* [[Android]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[InternetEye]] M6840

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Netcat]] IP Cameras

* [[Pelco]] IP Cameras

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

* Video cameras & safes for antitheft purpose on the website http://www.infosafe.fr

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Raspberry Pi - Raspbian ==

ZM 1.25 is already in Raspbian. Newer development packages are available.

You will want libjpeg-turbo from the following repository by adding to your /etc/apt/sources.list

deb http://zarrenspry.info/repos/apt/raspbian testing main
deb-src http://zarrenspry.info/repos/apt/raspbian testing main

Add gpg by

wget -O - http://zarrenspry.info/zarrenspry.gpg.key|apt-key add -

apt-get install libturbojpeg8 libturbojpeg8-dev

If using the Pi camera, you will need to enable it in raspi-config as well as loading the v4l2 kernel module by adding the following to your /etc/modules

bcm2835-v4l2

Although the camera will can capture high res, you don't have enough RAM currently to do so. Especially if you have the early 256MB model. So ust stick to 640x480.

You should be able to get around 20fps, but if you do anything involving the CPU you will get underruns.

== Raspberry Pi 2 - Fedora ==

The latest version of ZoneMinder is available for the Raspberry Pi 2 when running Fedora.
Browse to the zmrepo site for installation instructions: https://zmrepo.zoneminder.com/

Netcat

2016-02-24T17:12:15Z

Knnniggett: Created page with "== Netcat IP Cameras == Netcat is one of many Chinese IP camera vendors. http://www.netcatcctv.com/English/index.html Like many other Chinese cameras, if your camera looks s..."

File:2015518112320.jpg

2016-02-24T16:47:17Z

Knnniggett: netcat ptz camera

netcat ptz camera

Hardware Compatibility List

2016-02-19T16:54:11Z

Knnniggett: /* Network Cameras */

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amovision AM-Q630M]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[InternetEye]] M6840

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Pelco]] IP Cameras

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

* Video cameras & safes for antitheft purpose on the website http://www.infosafe.fr

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Raspberry Pi - Raspbian ==

ZM 1.25 is already in Raspbian. Newer development packages are available.

You will want libjpeg-turbo from the following repository by adding to your /etc/apt/sources.list

deb http://zarrenspry.info/repos/apt/raspbian testing main
deb-src http://zarrenspry.info/repos/apt/raspbian testing main

Add gpg by

wget -O - http://zarrenspry.info/zarrenspry.gpg.key|apt-key add -

apt-get install libturbojpeg8 libturbojpeg8-dev

If using the Pi camera, you will need to enable it in raspi-config as well as loading the v4l2 kernel module by adding the following to your /etc/modules

bcm2835-v4l2

Although the camera will can capture high res, you don't have enough RAM currently to do so. Especially if you have the early 256MB model. So ust stick to 640x480.

You should be able to get around 20fps, but if you do anything involving the CPU you will get underruns.

== Raspberry Pi 2 - Fedora ==

The latest version of ZoneMinder is available for the Raspberry Pi 2 when running Fedora.
Browse to the zmrepo site for installation instructions: https://zmrepo.zoneminder.com/

Hardware Compatibility List

2016-02-19T16:53:47Z

Knnniggett: /* Network Cameras */

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amovision AM-Q630M]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[InternetEye]] M6840

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Pelco]] Pelco IP Cameras

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

* Video cameras & safes for antitheft purpose on the website http://www.infosafe.fr

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Raspberry Pi - Raspbian ==

ZM 1.25 is already in Raspbian. Newer development packages are available.

You will want libjpeg-turbo from the following repository by adding to your /etc/apt/sources.list

deb http://zarrenspry.info/repos/apt/raspbian testing main
deb-src http://zarrenspry.info/repos/apt/raspbian testing main

Add gpg by

wget -O - http://zarrenspry.info/zarrenspry.gpg.key|apt-key add -

apt-get install libturbojpeg8 libturbojpeg8-dev

If using the Pi camera, you will need to enable it in raspi-config as well as loading the v4l2 kernel module by adding the following to your /etc/modules

bcm2835-v4l2

Although the camera will can capture high res, you don't have enough RAM currently to do so. Especially if you have the early 256MB model. So ust stick to 640x480.

You should be able to get around 20fps, but if you do anything involving the CPU you will get underruns.

== Raspberry Pi 2 - Fedora ==

The latest version of ZoneMinder is available for the Raspberry Pi 2 when running Fedora.
Browse to the zmrepo site for installation instructions: https://zmrepo.zoneminder.com/

Pelco

2016-02-19T16:53:03Z

Knnniggett: Created page with "== Pelco Developer Network == The following page provides helpful technical information for Pelco cameras: http://pdn.pelco.com/content/rtp-video-streaming-over-http == Sarix..."

== Pelco Developer Network ==
The following page provides helpful technical information for Pelco cameras:
http://pdn.pelco.com/content/rtp-video-streaming-over-http

== Sarix IE10 ==
These settings will likely work for all Sarix IE series cameras.

From the Zoneminder console, click "Add New Monitor" and enter the following:

;General (tab)
:Name: {give the camera a name}
:Source Type: ffmpeg
:Function: {select an appropriate function from the dropdown}
:Enabled: Tick
:Maximum FPS: Empty
:Alarm Maximum FPS: Empty
;Source (tab)
:Source Path: rtsp://{ip address}:554/stream1
:Remote Method: RTP/Unicast
:Target Colorspace: 32 (only use 24 on old cpu's with no SSE instruction set)
:Capture Width: 1280
:Capture Height: 1026

VLC reports the image is 1026 pixels high, rather than 1024. That is not a typo.

Hardware Compatibility List

2016-02-19T16:40:26Z

Knnniggett: /* Raspberry Pi */

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amovision AM-Q630M]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[InternetEye]] M6840

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

* Video cameras & safes for antitheft purpose on the website http://www.infosafe.fr

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Raspberry Pi - Raspbian ==

ZM 1.25 is already in Raspbian. Newer development packages are available.

You will want libjpeg-turbo from the following repository by adding to your /etc/apt/sources.list

deb http://zarrenspry.info/repos/apt/raspbian testing main
deb-src http://zarrenspry.info/repos/apt/raspbian testing main

Add gpg by

wget -O - http://zarrenspry.info/zarrenspry.gpg.key|apt-key add -

apt-get install libturbojpeg8 libturbojpeg8-dev

If using the Pi camera, you will need to enable it in raspi-config as well as loading the v4l2 kernel module by adding the following to your /etc/modules

bcm2835-v4l2

Although the camera will can capture high res, you don't have enough RAM currently to do so. Especially if you have the early 256MB model. So ust stick to 640x480.

You should be able to get around 20fps, but if you do anything involving the CPU you will get underruns.

== Raspberry Pi 2 - Fedora ==

The latest version of ZoneMinder is available for the Raspberry Pi 2 when running Fedora.
Browse to the zmrepo site for installation instructions: https://zmrepo.zoneminder.com/

Hardware Compatibility List

2016-02-19T16:39:38Z

Knnniggett: /* Raspberry Pi */

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amovision AM-Q630M]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[InternetEye]] M6840

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

* Video cameras & safes for antitheft purpose on the website http://www.infosafe.fr

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Raspberry Pi ==

ZM 1.25 is already in Raspbian. Newer development packages are available.

You will want libjpeg-turbo from the following repository by adding to your /etc/apt/sources.list

deb http://zarrenspry.info/repos/apt/raspbian testing main
deb-src http://zarrenspry.info/repos/apt/raspbian testing main

Add gpg by

wget -O - http://zarrenspry.info/zarrenspry.gpg.key|apt-key add -

apt-get install libturbojpeg8 libturbojpeg8-dev

If using the Pi camera, you will need to enable it in raspi-config as well as loading the v4l2 kernel module by adding the following to your /etc/modules

bcm2835-v4l2

Although the camera will can capture high res, you don't have enough RAM currently to do so. Especially if you have the early 256MB model. So ust stick to 640x480.

You should be able to get around 20fps, but if you do anything involving the CPU you will get underruns.

The latest version of ZoneMinder is available for the Raspberry Pi 2 when running Fedora.
Browse to the zmrepo site for installation instructions: https://zmrepo.zoneminder.com/

Fedora

2016-01-30T23:36:35Z

Knnniggett:

The Fedora Project is a Red Hat sponsored, community-supported open source project. Its stated goal is to promote the rapid progress of free (as in freedom) and open source software and content, and its rapid innovation is possible using open processes and public forums.
'''

The project is led by the Fedora Project Board, which is comprised of community leaders and Red Hat members, and this group steers the direction of the project and of Fedora Core, the Linux distribution it develops. Red Hat employees work with the code alongside community members, and many Fedora Project innovations make their way into new releases of Red Hat Enterprise Linux.

ZoneMinder is developed on the Fedora distribution and no special actions are usually required for installation.

== Zmrepo - A ZoneMinder repository for RPM based distros ==
The ZoneMinder development team would like to introduce you to a new, easier way to install ZoneMinder on Fedora. Zmrepo is meant to be a turn-key solution. There is no compiling, no installing modules from CPAN, and no more complicated repository instructions.

This repository brings together a ZoneMinder rpm built by the development team, with all features enabled. This is in comparison to past ZoneMinder rpm's found in the Fedora repositories, which do not have ffmpeg support built-in. Zmrepo includes all dependencies that are not found in the default Fedora repositories. A few Perl modules are built by us, but all the rest of the dependencies are mirrored from popular sites such as EPEL and RPMFusion. There is no longer a need to add these additional repositories to your system. Zmrepo takes care of that for you.

==== Purpose ====
The primary purpose for developing ZoneMinder rpms for Fedora is to get an idea of how well ZoneMinder works on the bleeding edge of software development. We don't use Fedora in our production systems and consequently these rpms do not get the same share of testing that the ZoneMinder rpms for RHEL/CentOS do. However, they do give us the unique opportunity to solve any problems caused by new software widgets (looking at you systemd) before they trickle down to RHEL/CentOS.

==== Who Should Use ====
Those that want to use the latest and greatest packages available should use this repository over the RHEL/CentOS repository. Keep in mind that this comes with the real possibility Fedora may throw in something new, which might cause a problem with ZoneMinder.

==== Supported Versions ====
Fedora distributions have a relatively short life cycle. A new version of Fedora is scheduled to be released [https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle every 6 months]. It is the goal of the ZoneMinder development team to provide and support ZoneMinder rpms for the two most recent versions of Fedora. Rpms built for older versions of Fedora may exist in zmrepo, but they will not be maintained and may be deleted at some point in the future.

==== Installation====

Please navigate to http://zmrepo.zoneminder.com/ and select your distro from the drop-down to view the installation instructions.

Remember to follow the steps documented in README.Fedora following installation of the ZoneMinder rpm.

==Fedora 18 (alpha)==
*FIXED: ''if you get problems with Live Video not working'' due to a problem with the sockets. 
**ERROR: socket_sendto permission errors.
*Make sure your cgi-bin ScriptAlias is correct as shown below. 
*''ffmpeg libraries from Fedora rpms do not work'' with zm. You have to install from source (yuck).

This is how I got it installed... 

Do all the following as sudo (or root) 
'''install packages''' 
yum install mysql mysql-server zoneminder 

''' disable selinux 
vi /etc/selinux/config 
*change the word 'enforcing' to 'disabled' 

'''REBOOT'''

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf
* in the section - <Directory "/usr/share/zoneminder/www">
**remove the line "Deny from all # DELETE THIS LINE"
**remove the '-Indexes' on the Options line on Line 17 )I don't think the '-' is supposed to be there
**Comment out the Order and Allow lines and insert the new syntax 'Require all granted' as a new line
* I also got a ScriptAlias error for the cgi-bin/zm alias so I commented the cgi-bin scriptAlias in the /etc/httpd/conf/httpd.conf

#F18 /etc/httpd/conf.d.zoneminder.conf
Alias /zm "/usr/share/zoneminder/www"
<Directory "/usr/share/zoneminder/www">
Options FollowSymLinks
AllowOverride All
# NEW format
Require all granted
# The code unfortunately uses short tags in many places
php_value short_open_tag 1
#Deny from all # DELETE THIS LINE
</Directory>
ScriptAlias /cgi-bin "/usr/libexec/zoneminder/cgi-bin"
<Directory "/usr/libexec/zoneminder/cgi-bin">
Options +ExecCGI +MultiViews +SymLinksIfOwnerMatch
AllowOverride All
# NEW format
Require all granted
php_value short_open_tag 1
</Directory>
 
'''start httpd:''' 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 17==
'''install packages''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 14==
'''install packages:''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
/etc/init.d/mysqld start 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
/etc/init.d/httpd start 

'''start zoneminder''' 
/etc/init.d/zoneminder start 

==Fedora 11, 12 and 13==
'''The Easy Way''' Adapted from a forum post by "hiredguntech" or just search the forum for "flowers for candy"

Step-by-step installation of ZM v1.24.2 on Fedora-12.

(1) load fc12 using the netinstall ISO (the CD wants to use dhcp and doesn't work well with an assigned fixed IP) - turn off 'office' and turn on 'server' and 'development'. Besure to include a large /var partition through custom partitioning and use localhost instead of what it suggests (domain.localhost ?). Also, if you're using a capture card install it (them) in the system before starting the netinstall CD. Save these steps as a .txt file so the code can be cut and paste into the terminal with ease.

[2] Remove evolution from task bar (right click... (not a requirement)).

[3] Set screensaver to NOT require password and set it to 20 minutes or more (menu-system::preferences::screensaver).

(4) Disable SELinux. (menu-system::Admin::SELinux Mgmnt; change system default enforcing mode to disabled).

[5] Enable sudo for yourself. From a terminal (menu-Application::System Tools::Terminal),
Code:

su

(enter root password)

echo ''''YourUserName''' ALL=(ALL) ALL' >> /etc/sudoers (put YOUR user name from FC12 installation in place of '''YourUserName''')

(6) Set up the RPM Fusion Repository (in open terminal).

Code:

rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm

rpm -ivh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

exit

exit (closes terminal window)

(7) Install the pre-requisites, (menu-System::Administration::Add/Remove Software) type in the search field the following package names and select each of the closest match (there will be 'other' packages related or similar named - look for the right one, and check-it.)

mysql-server

mysql-devel

pcre-devel

ffmpeg

ffmpeg-devel

Hit the 'Apply' button, accept any added packages, type root password, and let this stuff load.

[8] Install any updates that are available, its the yellow icon up by the time.

(9) Enable the services: web and db. (menu-System::Administration::Services) and find the following:

httpd

mysqld

for each of them hit the 'enable button' so you can start them later.

(10) Reboot. This allows all the services to start and settle in.

(11) Now add Zoneminder (menu-System::Administration::Add/Remove Software) Type Zoneminder in the search field select it and apply.

[13] '''Note:''' To edit as root: open a terminal (menu-Application::System Tools::Terminal), su to root, type 'gedit <path/filename>'. Now you have sufficient permissions to edit & save as root.

(14) Edit as root /etc/httpd/conf.d/zoneminder.conf to remove the 'Deny from All' line. It even says 'DELETE THIS LINE', so it should be easy to find. Save it.

(15) As root, [or with sudo] build the zm database (menu-Application::System Tools::Terminal).

Code:

su

(enter root password)

mysql mysql < /usr/share/zoneminder/db/zm_create.sql

mysqladmin reload

mysql mysql

grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass';

\q

exit

exit

(16) Enable zoneminder. (menu-System::Administration::Services) and find zoneminder. Enable it. You can start the service hear also, Or in a terminal:

Code:

service zoneminder start

[18] Last thing - edit the SECOND entry of short_open_tag down at line 229. Again as root (menu-Application::System Tools::Terminal), gedit /etc/php.ini

Change short_open_tag from 'off' to 'on'

[19] reboot. open browser, type 'localhost/zm'

[20] It may be necessary to change the ffmpeg path in options::images to get ffmpeg to make videos. Generally removing the /local from the existing path will fix this issue

'''Or (the original wiki walk through)'''

You should be able to just do "yum install zoneminder", create the zm database, find the zm_create.sql file (rpm -ql zoneminder) and import it to mysql, then start zoneminder. Plus allow web access. Edit /etc/httpd/conf.d/zoneminder.conf and comment out (#) or delete this line :-

Deny from all # DELETE THIS LINE

Restart/reload apache

sudo service httpd restart

This didn't work for me due to 2 problems. First was php.ini section short_open_tag = Off, set to on

short_open_tag = On

Restart/reload apache

sudo service httpd restart

The other problem was zm_create.sql had duplicate indexes reported using phpMyAdmin. Removed all "INSERT INTO MonitorPresets" and "INSERT INTO MonitorPresets" in zm_create.sql and that imported cleanly. Alternatively just import from the command line mysql -u zmuser -p < zm_create.sql

http://www.zoneminder.com/forums/viewtopic.php?p=50242

'''Manual Install Version 1.24.2 with ffmpeg enabled'''

Version 1.23.3 has always compiled ok on Fedora 9/10/11 but I had problems with version 1.24.2.

Problems with compiling fixed by adding #include <cstdio> to all .cpp files in src directory and removing ccache package (yum remove ccache)

http://www.zoneminder.com/forums/viewtopic.php?p=55152

http://www.zoneminder.com/forums/viewtopic.php?t=12515&sid=0da85eb2fc78917d7a78cf788603a320

If using ffmpeg and ffmpeg-devel packages you may see problem compiling with libavutil.a . I could not get ffmpeg to compile so downloaded the Fedora source package and compiled it manually.

yumdownloader --source ffmpeg

sudo rpm -Uvh ffmpeg-0.5-5.20091026svn.fc12.src.rpm

Needed the following packages

sudo yum install dirac-devel faad2-devel gsm-devel imlib2-devel lame-devel libdc1394-devel libtheora-devel libvdpau-devel openjpeg-devel \
schroedinger-devel speex-devel texi2html x264-devel xvidcore-devel yasm

See http://fozzolog.fozzilinymoo.org/tech/2009/11/recompiling-ffmpeg-for-fedora-12-to-add-faac-support.html (don't need to add faac support, just follow procedure)

My rpmbuild failed so from the BUILD/ffmpeg-20091026

make
sudo make install
sudo make install-libs

and configured ZoneMinder to use /usr/local for FFMPEG

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost \
ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr -L/usr/lib/mysql" ZM_SSL_LIB=openssl --with-ffmpeg=/usr/local

==Fedora 8==
* Have packages for Apache and MySQL installed on the system.
* Install the zoneminder RPM package on the system
: Fedora Information for package zoneminder
: * http://koji.fedoraproject.org/koji/packageinfo?packageID=4691
* Configure zoneminder
* Make sure Apache and MySQL services are running
* Edit the zoneminder.conf apache configuration file to allow web connections
vi /etc/httpd/conf.d/zoneminder.conf
* Build the MySQL database table for zoneminder
mysql -p -u root mysql < /usr/share/zoneminder/db/zm_create.sql > mysqladmin -p -u root reload

The Fedora RPM creates /var/log/zoneminder, but the database scripts point logs to /tmp, rather than the new directory.
* Click '''Options''', '''Paths''' tab, and change
ZM_PATH_LOGS = /var/log/zoneminder
* Click '''Options''', '''Debug''' tab, and change
ZM_EXTRA_DEBUG_LOG = /var/log/zoneminder/zm_debug.log+

* Install ffmpeg on Fedora.
Due to licensing the ffmpeg package is absent from Fedora. It can be added from [[Fedora_Linux_Distribution_Reference#Livna:_Get_Important_Packages_Missing_From_Fedora|Livna]].
wget http://rpm.livna.org/livna-release-8.rpm
rpm -ih livna-release-8.rpm
yum install ffmpeg
yum install ffmpeg-devel
Which provides the following: ffmpeg-libs-0.4.9-0.41.20071011.lvn8, ffmpeg-0.4.9-0.41.20071011.lvn8, ffmpeg-devel-0.4.9-0.41.20071011.lvn8

* Test ffmpeg
ffmpeg -f image2 -i %03d-capture.jpg /tmp/movie.mpg

==Fedora 7==
* Builds From source - see [[Fedora Core 6 Step-by-Step]] '''AS WELL AS''' [http://www.zoneminder.com/forums/viewtopic.php?t=9414 Fedora 7 forum topic]
*RPMs are Available in the '''main Fedora 7 distribution''', and in the development 'rawhide' tree.
**Its as easy as running: yum install zoneminder
**Take a look at [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 6==
*Build from source [[Fedora Core 6 Step-by-Step]]

* RPMs are also available right now in '''Fedora Extras''' for Fedora Core 6.
** [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 4==
* http://www.zoneminder.com/forums/viewtopic.php?t=5991 
Set web user and group correctly and set the log dir to a writeable location.
With FC4 there are three things that must be done to get ZM running,:
#is in the /etc/ld.so.conf.d/ dir created a file with 775 perm called zm.conf and add the line '/usr/local/lib' to it and type 'ldconfig' once it is added, also with a fresh install of FC4 make sure SE linux is disabled if you are not using it. Check your log path in options under the paths tab. This will tell you were the log are going to be put.
#Second make sure the path exists.
#Third create the log files if they do not exist and make sure that they have the correct permissions. '''If zm can not open and write the log files, it will not start. '''

Using a dedicated Hard Drive

2015-09-28T12:32:02Z

Knnniggett:

On many installs you may wish to dedicate a hard drive or partition for Zoneminder events. There are many reasons why you may want to change the storage location - security, data segregation, preventing encroachment onto OS partition by zoneminder etc.

It's not terribly difficult to do, but may be non-obvious to the untaught so here's a brief guide.

Some commands here are based on Debian/Ubuntu installs

1. Become root or "sudo -s" to gain root privs.

2. Stop Zoneminder. "service zoneminder stop", "/usr/bin/zmpkg.pl stop", or "systemctl stop zoneminder"

3. Mount your new partition onto the root filesystem, ensuring it is automatically remounted at boot time by editing /etc/fstab -- For the benefit of this guide, I'm calling my new partition /newdrive

''Note this new partition can be a local drive, raid partition, lvm/md device, external NAS, SAN, NFS share or SMB share. The only condition is that the I/O throughput should be up to handling what Zoneminder will throw at it. For that speed reason, some favour non-journalled filesystems and accept the extra risk of data protection''

4. Locate Zoneminder's "events" and "images" directories. In Debian and Ubuntu, these are under /var/cache/zoneminder. In CentOS and Fedora, these are under /var/lib/zoneminder.

''If you wish to copy the data across, MOVE the events and images directories to /newdrive ''(Note this will take a long time on systems with many events). Also, DO NOT restart zoneminder until this entire process is completed. Doing so will cause all your events to be lost!''

If you don't wish to preserve the data, it is MUCH faster to simply delete or rename the original events and images dirs and create new directories in /newdrive. There is no need to remove the "orphaned" entries in the database, zmaudit will take care of those.

Eg:

mkdir /newdrive/events

mv /var/lib/zoneminder/events /var/lib/zoneminder/events_old
-- or --
rm -rf /var/lib/zoneminder/events

Add these lines in fstab to bind-mount an alternate location:

/dev/sdX1 /otherdrive ext3 defaults 0 2
/otherdrive/zoneminder/images /var/cache/zoneminder/images none defaults,bind 0 2
/otherdrive/zoneminder/events /var/cache/zoneminder/events none defaults,bind 0 2

or in some cases,

/otherdrive/zoneminder/images /var/lib/zoneminder/images none defaults,bind 0 2
/otherdrive/zoneminder/events /var/lib/zoneminder/events none defaults,bind 0 2

or if you have a separate partition for each:

/dev/sdX1 /var/cache/zoneminder/images ext3 defaults 0 2
/dev/sdX2 /var/cache/zoneminder/events ext3 defaults 0 2
(Repeat for images)

5. Ensure ZoneMinder can write to the new destination by changing the owner and group to that of the web server user account. Debian based distros typically use "www-data" as the web server user account while many rpm based distros use "apache".

chown -R apache:apache /otherdrive/zoneminder

6. Finally, restart zoneminder ( "service zoneminder start", "/usr/bin/zmpkg.pl start", or "systemctl start zoneminder") Monitor its operation and ensure new events are being created normally and are viewable. Zoneminder should also update the "Disk: %%" on its Console screen to reflect the disk space on its new partition.

FREQUENTLY ASKED QUESTIONS

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!

Question:
I noticed that there is an events folder under /usr/share/zoneminder/www, can I mount my dedicated hard drive or volume to that folder?
Answer:
This will not work in every case either and should be avoided. The events and images folders under /usr/share/zoneminder/www are actually symbolic links that point to the real folders under /var/lib/zoneminder (or /var/cache/zoneminder). Altering this in any way has the same affect as the answer to the first question.

Hardware Compatibility List

2015-08-18T12:37:42Z

Knnniggett: /* Network Cameras */

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Howell-Tempest VC 878B-Q]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

[[IEI Technology Corp. IVC-268G-R20]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to generate a video stream without the requirement of activex controls. If the requirements state Internet Explorer is the only supported browser, then the camera may not work. The other option is to grab JPEG images (snapshots), if the camera supports that option, which will work but at a lower frame rate.

'''Help us keep this list accurate.'''

The hardware compatibility list is maintained by you, the community. If you see something that is no longer up to date, please consider revising it. Naturally, be respectful with your edits. Those before you have put in a lot of effort into this documentation.

'''Maintaining PTZ Control Scripts is particularly important.'''

It is important to understand that many of the control scripts were written for older versions of ZoneMinder and may require changes to work with the most recent version. When reviewing control scripts, look at the date it was created (see the history tab at the top). If that date is not recent then the script may not work with the latest version. When in doubt, ask in the user forum.

If you discover the control script in this WiKi has already been added to ZoneMinder, then please update the WiKi to reflect that.

'''Consider adding your script to ZoneMinder.'''

If you are willing to do the work, we will gladly add new control scripts to ZoneMinder, as long as they have been tested to work properly. This requires submitting a pull request on our github site with the control script and the necessary sql bits to make it show up in the console. Once the control script has been added to the source tree, it will be maintained by the developers and will (should?) always work for you. This is really the best option as it avoids the endless maintenance required to keep the WiKi up to date.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amovision AM-Q630M]]

* [[Anran VGB101-IP]]

* [[Apexis]] most if not all (only tested some)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[Dahua]] (IPC-HDB3200C, probably others)

* [[D-Link]] Most

* [[EasyN]] (Mini Speed Dome 1BF)

* [[Edimax]] only tested some

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 & GXV3611_HD tested)

* [[Hikvision]] Some

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[InternetEye]] M6840

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[Swann]] Some

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Vstar T7833WIP HD Dome Network Camera]]

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* [[ZoneWay ZW-NC863M-P Megapixel IP]]

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

* [[Bosch VIP X1 Single-channel]] video encoder [http://products.boschsecuritysystems.eu/en/EMEA/products/bxp/SKU15449253232961378955-CATMda7ec5dc0edf5b1a0b8cb619e2e11308]

* Video cameras & safes for antitheft purpose on the website http://www.infosafe.fr

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: Advent AWC213, Creative Labs VF0420, [[Logitech QuickCam Express]], Logitech HD C270, QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

== Raspberry Pi ==

ZM 1.25 is already in Raspbian. Newer development packages are available.

You will want libjpeg-turbo from the following repository by adding to your /etc/apt/sources.list

deb http://zarrenspry.info/repos/apt/raspbian testing main
deb-src http://zarrenspry.info/repos/apt/raspbian testing main

Add gpg by

wget -O - http://zarrenspry.info/zarrenspry.gpg.key|apt-key add -

apt-get install libturbojpeg8 libturbojpeg8-dev

If using the Pi camera, you will need to enable it in raspi-config as well as loading the v4l2 kernel module by adding the following to your /etc/modules. You will also need to assign more than 128M to the GPU.

bcm2835-v4l2

Although the camera will can capture high res, you don't have enough RAM currently to do so. Especially if you have the early 256MB model. So just stick to 640x480.

You should be able to get around 20fps, but if you do anything involving the CPU you will get underruns.

Fedora

2015-05-27T12:42:34Z

Knnniggett: /* Installation */

The Fedora Project is a Red Hat sponsored, community-supported open source project. Its stated goal is to promote the rapid progress of free (as in freedom) and open source software and content, and its rapid innovation is possible using open processes and public forums.
'''

The project is led by the Fedora Project Board, which is comprised of community leaders and Red Hat members, and this group steers the direction of the project and of Fedora Core, the Linux distribution it develops. Red Hat employees work with the code alongside community members, and many Fedora Project innovations make their way into new releases of Red Hat Enterprise Linux.

ZoneMinder is developed on the Fedora distribution and no special actions are usually required for installation.

== Zmrepo - A ZoneMinder repository for RPM based distros ==
The ZoneMinder development team would like to introduce you to a new, easier way to install ZoneMinder on Fedora. Zmrepo is meant to be a turn-key solution. There is no compiling, no installing modules from CPAN, and no more complicated repository instructions.

This repository brings together a ZoneMinder rpm built by the development team, with all features enabled. This is in comparison to past ZoneMinder rpm's found in the Fedora repositories, which do not have ffmpeg support built-in. Zmrepo includes all dependencies that are not found in the default Fedora repositories. A few Perl modules are built by us, but all the rest of the dependencies are mirrored from popular sites such as EPEL and RPMFusion. There is no longer a need to add these additional repositories to your system. Zmrepo takes care of that for you.

==== Purpose ====
The primary purpose for developing ZoneMinder rpms for Fedora is to get an idea of how well ZoneMinder works on the bleeding edge of software development. We don't use Fedora in our production systems and consequently these rpms do not get the same share of testing that the ZoneMinder rpms for RHEL/CentOS do. However, they do give us the unique opportunity to solve any problems caused by new software widgets (looking at you systemd) before they trickle down to RHEL/CentOS.

==== Who Should Use ====
Those that want to use the latest and greatest packages available should use this repository over the RHEL/CentOS repository. Keep in mind that this comes with the real possibility Fedora may throw in something new, which might cause a problem with ZoneMinder.

==== Supported Versions ====
Fedora distributions have a relatively short life cycle. A new version of Fedora is scheduled to be released [https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle every 6 months]. It is the goal of the ZoneMinder development team to provide and support ZoneMinder rpms for the two most recent versions of Fedora. Today, those two versions are Fedora 22 and 21. Rpms built for older versions of Fedora may exist in zmrepo, but they will not be maintained and may be deleted at some point in the future.

==== Installation====

Please navigate to http://zmrepo.zoneminder.com/ and select your distro from the drop-down to view the installation instructions.

Remember to follow the steps documented in README.Fedora following installation of the ZoneMinder rpm.

==Fedora 18 (alpha)==
*FIXED: ''if you get problems with Live Video not working'' due to a problem with the sockets. 
**ERROR: socket_sendto permission errors.
*Make sure your cgi-bin ScriptAlias is correct as shown below. 
*''ffmpeg libraries from Fedora rpms do not work'' with zm. You have to install from source (yuck).

This is how I got it installed... 

Do all the following as sudo (or root) 
'''install packages''' 
yum install mysql mysql-server zoneminder 

''' disable selinux 
vi /etc/selinux/config 
*change the word 'enforcing' to 'disabled' 

'''REBOOT'''

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf
* in the section - <Directory "/usr/share/zoneminder/www">
**remove the line "Deny from all # DELETE THIS LINE"
**remove the '-Indexes' on the Options line on Line 17 )I don't think the '-' is supposed to be there
**Comment out the Order and Allow lines and insert the new syntax 'Require all granted' as a new line
* I also got a ScriptAlias error for the cgi-bin/zm alias so I commented the cgi-bin scriptAlias in the /etc/httpd/conf/httpd.conf

#F18 /etc/httpd/conf.d.zoneminder.conf
Alias /zm "/usr/share/zoneminder/www"
<Directory "/usr/share/zoneminder/www">
Options FollowSymLinks
AllowOverride All
# NEW format
Require all granted
# The code unfortunately uses short tags in many places
php_value short_open_tag 1
#Deny from all # DELETE THIS LINE
</Directory>
ScriptAlias /cgi-bin "/usr/libexec/zoneminder/cgi-bin"
<Directory "/usr/libexec/zoneminder/cgi-bin">
Options +ExecCGI +MultiViews +SymLinksIfOwnerMatch
AllowOverride All
# NEW format
Require all granted
php_value short_open_tag 1
</Directory>
 
'''start httpd:''' 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 17==
'''install packages''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 14==
'''install packages:''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
/etc/init.d/mysqld start 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
/etc/init.d/httpd start 

'''start zoneminder''' 
/etc/init.d/zoneminder start 

==Fedora 11, 12 and 13==
'''The Easy Way''' Adapted from a forum post by "hiredguntech" or just search the forum for "flowers for candy"

Step-by-step installation of ZM v1.24.2 on Fedora-12.

(1) load fc12 using the netinstall ISO (the CD wants to use dhcp and doesn't work well with an assigned fixed IP) - turn off 'office' and turn on 'server' and 'development'. Besure to include a large /var partition through custom partitioning and use localhost instead of what it suggests (domain.localhost ?). Also, if you're using a capture card install it (them) in the system before starting the netinstall CD. Save these steps as a .txt file so the code can be cut and paste into the terminal with ease.

[2] Remove evolution from task bar (right click... (not a requirement)).

[3] Set screensaver to NOT require password and set it to 20 minutes or more (menu-system::preferences::screensaver).

(4) Disable SELinux. (menu-system::Admin::SELinux Mgmnt; change system default enforcing mode to disabled).

[5] Enable sudo for yourself. From a terminal (menu-Application::System Tools::Terminal),
Code:

su

(enter root password)

echo ''''YourUserName''' ALL=(ALL) ALL' >> /etc/sudoers (put YOUR user name from FC12 installation in place of '''YourUserName''')

(6) Set up the RPM Fusion Repository (in open terminal).

Code:

rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm

rpm -ivh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

exit

exit (closes terminal window)

(7) Install the pre-requisites, (menu-System::Administration::Add/Remove Software) type in the search field the following package names and select each of the closest match (there will be 'other' packages related or similar named - look for the right one, and check-it.)

mysql-server

mysql-devel

pcre-devel

ffmpeg

ffmpeg-devel

Hit the 'Apply' button, accept any added packages, type root password, and let this stuff load.

[8] Install any updates that are available, its the yellow icon up by the time.

(9) Enable the services: web and db. (menu-System::Administration::Services) and find the following:

httpd

mysqld

for each of them hit the 'enable button' so you can start them later.

(10) Reboot. This allows all the services to start and settle in.

(11) Now add Zoneminder (menu-System::Administration::Add/Remove Software) Type Zoneminder in the search field select it and apply.

[13] '''Note:''' To edit as root: open a terminal (menu-Application::System Tools::Terminal), su to root, type 'gedit <path/filename>'. Now you have sufficient permissions to edit & save as root.

(14) Edit as root /etc/httpd/conf.d/zoneminder.conf to remove the 'Deny from All' line. It even says 'DELETE THIS LINE', so it should be easy to find. Save it.

(15) As root, [or with sudo] build the zm database (menu-Application::System Tools::Terminal).

Code:

su

(enter root password)

mysql mysql < /usr/share/zoneminder/db/zm_create.sql

mysqladmin reload

mysql mysql

grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass';

\q

exit

exit

(16) Enable zoneminder. (menu-System::Administration::Services) and find zoneminder. Enable it. You can start the service hear also, Or in a terminal:

Code:

service zoneminder start

[18] Last thing - edit the SECOND entry of short_open_tag down at line 229. Again as root (menu-Application::System Tools::Terminal), gedit /etc/php.ini

Change short_open_tag from 'off' to 'on'

[19] reboot. open browser, type 'localhost/zm'

[20] It may be necessary to change the ffmpeg path in options::images to get ffmpeg to make videos. Generally removing the /local from the existing path will fix this issue

'''Or (the original wiki walk through)'''

You should be able to just do "yum install zoneminder", create the zm database, find the zm_create.sql file (rpm -ql zoneminder) and import it to mysql, then start zoneminder. Plus allow web access. Edit /etc/httpd/conf.d/zoneminder.conf and comment out (#) or delete this line :-

Deny from all # DELETE THIS LINE

Restart/reload apache

sudo service httpd restart

This didn't work for me due to 2 problems. First was php.ini section short_open_tag = Off, set to on

short_open_tag = On

Restart/reload apache

sudo service httpd restart

The other problem was zm_create.sql had duplicate indexes reported using phpMyAdmin. Removed all "INSERT INTO MonitorPresets" and "INSERT INTO MonitorPresets" in zm_create.sql and that imported cleanly. Alternatively just import from the command line mysql -u zmuser -p < zm_create.sql

http://www.zoneminder.com/forums/viewtopic.php?p=50242

'''Manual Install Version 1.24.2 with ffmpeg enabled'''

Version 1.23.3 has always compiled ok on Fedora 9/10/11 but I had problems with version 1.24.2.

Problems with compiling fixed by adding #include <cstdio> to all .cpp files in src directory and removing ccache package (yum remove ccache)

http://www.zoneminder.com/forums/viewtopic.php?p=55152

http://www.zoneminder.com/forums/viewtopic.php?t=12515&sid=0da85eb2fc78917d7a78cf788603a320

If using ffmpeg and ffmpeg-devel packages you may see problem compiling with libavutil.a . I could not get ffmpeg to compile so downloaded the Fedora source package and compiled it manually.

yumdownloader --source ffmpeg

sudo rpm -Uvh ffmpeg-0.5-5.20091026svn.fc12.src.rpm

Needed the following packages

sudo yum install dirac-devel faad2-devel gsm-devel imlib2-devel lame-devel libdc1394-devel libtheora-devel libvdpau-devel openjpeg-devel \
schroedinger-devel speex-devel texi2html x264-devel xvidcore-devel yasm

See http://fozzolog.fozzilinymoo.org/tech/2009/11/recompiling-ffmpeg-for-fedora-12-to-add-faac-support.html (don't need to add faac support, just follow procedure)

My rpmbuild failed so from the BUILD/ffmpeg-20091026

make
sudo make install
sudo make install-libs

and configured ZoneMinder to use /usr/local for FFMPEG

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost \
ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr -L/usr/lib/mysql" ZM_SSL_LIB=openssl --with-ffmpeg=/usr/local

==Fedora 8==
* Have packages for Apache and MySQL installed on the system.
* Install the zoneminder RPM package on the system
: Fedora Information for package zoneminder
: * http://koji.fedoraproject.org/koji/packageinfo?packageID=4691
* Configure zoneminder
* Make sure Apache and MySQL services are running
* Edit the zoneminder.conf apache configuration file to allow web connections
vi /etc/httpd/conf.d/zoneminder.conf
* Build the MySQL database table for zoneminder
mysql -p -u root mysql < /usr/share/zoneminder/db/zm_create.sql > mysqladmin -p -u root reload

The Fedora RPM creates /var/log/zoneminder, but the database scripts point logs to /tmp, rather than the new directory.
* Click '''Options''', '''Paths''' tab, and change
ZM_PATH_LOGS = /var/log/zoneminder
* Click '''Options''', '''Debug''' tab, and change
ZM_EXTRA_DEBUG_LOG = /var/log/zoneminder/zm_debug.log+

* Install ffmpeg on Fedora.
Due to licensing the ffmpeg package is absent from Fedora. It can be added from [[Fedora_Linux_Distribution_Reference#Livna:_Get_Important_Packages_Missing_From_Fedora|Livna]].
wget http://rpm.livna.org/livna-release-8.rpm
rpm -ih livna-release-8.rpm
yum install ffmpeg
yum install ffmpeg-devel
Which provides the following: ffmpeg-libs-0.4.9-0.41.20071011.lvn8, ffmpeg-0.4.9-0.41.20071011.lvn8, ffmpeg-devel-0.4.9-0.41.20071011.lvn8

* Test ffmpeg
ffmpeg -f image2 -i %03d-capture.jpg /tmp/movie.mpg

==Fedora 7==
* Builds From source - see [[Fedora Core 6 Step-by-Step]] '''AS WELL AS''' [http://www.zoneminder.com/forums/viewtopic.php?t=9414 Fedora 7 forum topic]
*RPMs are Available in the '''main Fedora 7 distribution''', and in the development 'rawhide' tree.
**Its as easy as running: yum install zoneminder
**Take a look at [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 6==
*Build from source [[Fedora Core 6 Step-by-Step]]

* RPMs are also available right now in '''Fedora Extras''' for Fedora Core 6.
** [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 4==
* http://www.zoneminder.com/forums/viewtopic.php?t=5991 
Set web user and group correctly and set the log dir to a writeable location.
With FC4 there are three things that must be done to get ZM running,:
#is in the /etc/ld.so.conf.d/ dir created a file with 775 perm called zm.conf and add the line '/usr/local/lib' to it and type 'ldconfig' once it is added, also with a fresh install of FC4 make sure SE linux is disabled if you are not using it. Check your log path in options under the paths tab. This will tell you were the log are going to be put.
#Second make sure the path exists.
#Third create the log files if they do not exist and make sure that they have the correct permissions. '''If zm can not open and write the log files, it will not start. '''

CentOS

2015-05-27T12:42:24Z

Knnniggett: /* Installation */

The intent of this walk through is to install a very base/bare bones installation of CentOS that runs only ZoneMinder. This would be for a dedicated ZoneMinder server with no GUI or any unnecessary services running. The reason for the very light-weight installation is to make the majority of system resources available to ZoneMinder, not the OS. With this installation, memory is reduced to around 140-160MB, and CPU usage is practically nonexistent. The CentOS base installation is very easy to install and doesn’t take too much time as long as you have some type of broadband connection. There are many ways to install CentOS, but this article covers only two, because they are related.

''All CLI operations/commands in this How-To are done as root, in the /root directory. The reasoning is that this system would be in a secure environment to begin with. However, if you need to add a user to run these services to better secure the system, then you can, but keep in mind that some items must run as root.''

== Zmrepo - A ZoneMinder repository for RPM based distros ==
The ZoneMinder development team would like to introduce you to a new, easier way to install ZoneMinder on CentOS. Zmrepo is meant to be a turn-key solution. There is no compiling, no installing modules from CPAN, and no more complicated repository instructions.

This repository brings together a ZoneMinder rpm built by the development team, with all features enabled. It also includes all dependencies that are not found in the default CentOS repositories. A few Perl modules are built by us, but all the rest of the dependencies are mirrored from popular sites such as EPEL and RPMFusion. There is no longer a need to add these additional repositories to your system. Zmrepo takes care of that for you.

==== Who Should Use ====
The development team strictly uses CentOS, but these packages should work on Red Hat Enterprise Linux and Scientific Linux. The rpms in zmrepo are intended to work with ''default installations'' of these Linux distributions. Modified versions are not guaranteed to work. Continue to the Disclaimer below for details.

Please report any issues with RHEL and SL, as we have no way of pro-actively discovering them.

==== Disclaimer ====
This could also be appropriately called '''Who should not Use''' zmrepo.

The goal behind CentOS is that of an enterprise operating system. Stability is prioritized over the latest and greatest version of a particular package. Fortunately, bug fixes are backported. Consequently, you should ''never'' replace the core packages in CentOS! If you truly think that you "have to have" some package that is newer than what is found in the default repository then you should consider using a different Linux distro.

The CentOS maintainers have a great write-up that describes this in much more detail [http://wiki.centos.org/PackageManagement/SourceInstalls here]. Pay close attention to the all the do's, dont's, and "this will break" comments.

Zmrepo extends this same philosophy onto ZoneMinder. While ZoneMinder requires many dependencies to work, zmrepo will not overwrite any core packages. It only adds packages that, otherwise, would not be available.

One other case is worth mentioning. This repository is intended ''only'' for those who have installed RHEL/CentOS/SL using the '''official installation media for that distribution'''! This means that these rpms are not intended to work with third parties that release their own spin of CentOS, which contain their own third party application preinstalled. Third parties are allowed to modify the original distribution in any way, which means we can't guarantee the rpms in zmrepo will be compatible.

For example, if you installed "CentOS" using an installation disk from an Astericks vendor, then the rpms in zmrepo are known not to work.

==== Installation ====

Please navigate to http://zmrepo.zoneminder.com/ and select your distro from the drop-down to view the installation instructions.

Remember to follow the steps documented in README.Centos7 following installation of the ZoneMinder rpm.

== CentOS 5.6 & ZoneMinder 1.25.0 ==
This guide is for CentOS v5.6 (Notes for using this guide with CentOS 6 are in chapter 2.) with ZoneMinder v1.25.0 which are the newest released versions as of this update (Summer 2011). If you are attempting to install newer versions of either using this guide, you will have to adjust file and directory names denoted below.

=== Step One - Get CentOS ===
You can download the “.iso” file(s) for CentOS from http://www.centos.org/ 
Alternatively download the net-install version of CentOS which is basically just the first CD.
Here is one location to download the net-install version: 
Download i386: http://mirror.symnds.com/distributions/CentOS-vault/5.6/isos/i386/CentOS-5.6-i386-netinstall.iso 
Download 64 bit: http://mirror.symnds.com/distributions/CentOS-vault/5.6/isos/x86_64/CentOS-5.6-x86_64-netinstall.iso 
Mirrors List: http://mirror.centos.org/centos/5/isos/

=== Step Two - Installation Source ===
Regardless of which method you use, the next few steps are the same. 
Begin by booting your system up with either cd/dvd. 
Choose the options that best fit your environment until you reach the “Installation Method”.

[[Image:centosnetinstal-http.png]]

Choose '''HTTP''' ONLY if you are using the net-install method. Otherwise, you probably want to choose '''Local CDROM'''. 

If you are using the net-install method then enter: 
Website Name: '''mirror.centos.org''' 
CentOS Directory: (for i386) '''/centos/5.6/os/i386''' 
CentOS Directory: (for 64 bit) '''/centos/5.6/os/x86_64'''

=== Step Three - Installation Packages ===
On the first screen, un-check "Desktop - Gnome" then check "Server" (not Server-GUI) 
Make sure that you have "Customize now" selected at the bottom. (do not check "Packages from CentOS Extras")

[[Image:centosinstall-packages1.png]]

Click "Next" to continue 

Once presented with the custom package selection, un-check/check the following:
Applications = Check only "Editors" and "Text Based Internet"
Development = Check only "Development Libraries" and "Development Tools"
Servers = Un-check everything
Base System = Check only "Base" (you can check Administration Tools and System Tools if you need them, but they are not necessary)

[[Image:Centosinstall-packages2.png]]

Now let the system finish the installation.

[[Image:centosisntall-end.png]]

=== Step Four - Configuration ===
After the first reboot, the setup screen should appear. If not, log into the system and type "setup"

[[Image:centosinstall-setup1.png]]

Select "Firewall Configuration" and set the "Security Level" and "SELinux" to "Disabled."

[[Image:centosinstall-setup2.png]]

Next, we are going to disable a number of system services. Go back to the setup screen and select "System Services" 
Un-Check:
apmd
bluetooth
cups
hidd
ip6tables
iptables
netfs
nfslock
pcscd
portmap
After disabling the services, select "Disable Now and On Boot", exit the setup tool, and log into the system if you haven't already.
*Screen is a simple program that allows you to run commands from a "Hosted" command line interface. This helps if you loose your connection to the server for any reason in that it enables you to resume (screen -r) right where you left off. Often times, I will start a large update/upgrade, leave it for the day, then come back and see where it's at later. Screen allows you to do that without having to be connected.
*Install Screen
yum install screen
*To start a screen session just type
screen
*If you get disconnected and need to resume your session of screen simply type
screen -r

=== Step Five - Installing ZoneMinder 1.25.0 ===
First, we need to download files and prepare the system
*Add the RPM Forge repository to CentOS. This will allow the installation of a number of services/applications later without having to manually install them.
<pre># For i386 CentOS 5.x run:
rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm

# For 64 bit CentOS 5.x run:
rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm</pre>
*Download the needed files, ZoneMinder 1.25.0 and the Cambozola addon
wget http://www2.zoneminder.com/downloads/ZoneMinder-1.25.0.tar.gz
wget http://www.zoneminder.com/sites/zoneminder.com/downloads/cambozola.jar
*Now let's install all the services and programs that will be needed (''If you encounter any dependency errors using yum, try running '''yum clean all''' then re-try the install command(s).'')

*tip: Copy/paste two lines at a time

<pre>
yum -y install mysql mysql-server mysql-devel php php-gd php-mysql httpd gcc \
pcre-devel gd mod_ssl glib2-devel gcc-c++ ntp gnutls-devel ImageMagick

yum -y install libjpeg-devel perl-Archive-Tar perl-MIME-Lite perl-MIME-tools \
perl-Date-Manip perl-LWP-UserAgent-Determined

yum -y install perl-PHP-Serialization perl-Device-SerialPort perl-Archive-Zip perl-Sys-Mmap \
perl-Module-Load subversion git yasm bzip2 bzip2-devel bzip2-libs lbzip2</pre>
*Now let's update everything within the new CentOS install
yum -y update
*At this point, it might be useful to reboot your system. Oddly, sometimes things don't work right unless you reboot after all the updates
reboot -or- shutdown -r now
*After rebooting, log into your system
==== Install ffmpeg ====
*Now we need to make sure we use the latest "tested" version of "ffmpeg". This is the latest version of ffmpeg that the ZoneMinder developers have tested with. Download, compile and install ffmpeg:
<pre>git clone git://git.videolan.org/ffmpeg.git
cd ffmpeg
./configure --enable-gpl --enable-shared --enable-pthreads
make
</pre>

*The following commands must be done as '''root'''

<pre>
make install
make install-libs
</pre>
edit /etc/ld.so.conf and add the line "/usr/local/lib"
<pre>
ldconfig -v
</pre>

*Next, run 'ffmpeg' from the command line. Make sure you do not get any errors:

<pre>
ffmpeg
</pre>

*If 'ffmpeg' runs correctly, you'll see something similar to this:

<pre>
ffmpeg version N-32260-gaebb56e, Copyright (c) 2000-2011 the FFmpeg developers
built on Aug 31 2011 21:41:49 with gcc 4.1.2 20080704 (Red Hat 4.1.2-50)
configuration: --enable-shared --enable-swscale --enable-gpl --enable-pthreads
libavutil 51. 14. 0 / 51. 14. 0
libavcodec 53. 12. 0 / 53. 12. 0
libavformat 53. 10. 0 / 53. 10. 0
libavdevice 53. 3. 0 / 53. 3. 0
libavfilter 2. 37. 0 / 2. 37. 0
libswscale 2. 0. 0 / 2. 0. 0
libpostproc 51. 2. 0 / 51. 2. 0
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'
</pre>

==== Enable services ====
*Turn everything on. These commands must be run as root.

<pre>
chkconfig httpd on
chkconfig mysqld on
chkconfig ntpd on
service httpd start
service mysqld start
service ntpd start
</pre>
==== Install Zoneminder ====
*Next, we need to extract the contents of the ZoneMinder "tar" file, then jump into its directory.
<pre>
cd /root/ # Or your work directory for this installation
tar -zxvf ZoneMinder-1.25.0.tar.gz
cd ZoneMinder-1.25.0
</pre>
*Now we are going to configure ZoneMinder with some additional parameters. What is listed are the default CentOS directory locations.
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin

Note: It seems for Zoneminder to build with newer versions of ffmpeg, (certainly 0.6.3) you'll need to append CPPFLAGS="-D__STDC_CONSTANT_MACROS" to the end of the
./configure line thus:

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-ffmpeg=/usr/local/share/ffmpeg CPPFLAGS="-D__STDC_CONSTANT_MACROS"

There is a section in the FAQ ''"When running configure, I get a lot of messages about not being able to compile the ffmpeg libraries"'' about this [[http://www.zoneminder.com/wiki/index.php/FAQ]].

Worth mentioning here is the section in the FAQ under the heading "''My load is too high, how can I reduce it?''" [[http://www.zoneminder.com/wiki/index.php/FAQ]]. This descibes how you can possibly reduce CPU load by half by
changing the system's jpeg libraries and building Zoneminder with processor specific instructions.
Since CentOS 6.4 CentOS now comes with libjpeg_turbo as the standard JPEG library leading to a more optimised Zoneminder.

By default ZM_DB_HOST=localhost, ZM_DB_NAME=zm, ZM_DB_USER=zmuser, and ZM_DB_PASS=zmpass.
*Change "zmuser" (if you want) with the user that you will use within MySQL to access the ZoneMinder database
*Change "zmpass" with the password you will be using with the "zmuser" account
So if you wish to change it, use a command like:
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass

*if you get the configure "error zm requires libmysqlclient.a" with 64 bit CentOS add the following to the end of your configure statement
--with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql"

e.g. For CentOS 5.6 64-bit with support for ffmpeg. The whole command must be executed on one line. Make sure to change the '''zmpass''' to a password that matches your installation.
<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-ffmpeg=/usr/local/share/ffmpeg --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql" CXXFLAGS="-D__STDC_CONSTANT_MACROS"
</pre>
* Run '''make''' and '''make install''' after running the configuration steps above.

make
# Run the next command as root
make install

==== Configure MySQL ====
*Need to add a password for the root user of MySQL
*Create the zm database
*Create the zm database user with permissions and password
mysql
mysql> SET PASSWORD FOR root@localhost=PASSWORD('new_root_password');
>Query OK, 0 rows affected (0.00 sec)
mysql> create database zm;
>Query OK, 1 row affected (0.01 sec)
mysql> CREATE USER 'your_zm_user'@'localhost' IDENTIFIED BY 'your_zm_password_from_above';
Query OK, 0 rows affected (0.01 sec)
mysql> grant CREATE, INSERT, SELECT, DELETE, UPDATE on zm.* to your_zm_user@localhost;
>Query OK, 0 rows affected (0.02 sec)
mysql> exit
>Bye
*Import the tables into the zm database
cd /root/ZoneMinder-1.25.0
mysql -u root -p zm < db/zm_create.sql

==== Finalize Installation of ZoneMinder ====
'''All remaining CLI commands need to be run as root.'''
*Make ZoneMinder startup automatically after a reboot
# from the ZoneMinder-1.25 source directory
cp scripts/zm /etc/init.d/
chmod +x /etc/init.d/zm
chkconfig zm on
*Add the Cambozola Java web interface
cp cambozola.jar /var/www/html/zm/
*Make sure you have permission to view it from apache:
chown apache:apache /var/www/html/zm/cambozola.jar
*Start ZoneMinder
service zm start

Note: You may get an error when you try to start Zoneminder using the 'zm' startup script as per this forum post: [[http://www.zoneminder.com/forums/viewtopic.php?f=21&t=17827]] .
The reason for this was the default 'zm' startup script was formatted with DOS line endings. If you get the errors as detailed in the above post then the fix is to convert the
'zm' file to use UNIX style line endings. You can do this in the Vim text editor whilst editing the 'zm' file thus: ':set fileformat=unix' then save the file ':wq'. You can also
use the utility dos2unix to convert the file.

* tick the box for support for the Cambozola addon within your ZoneMinder installation: http://ip-address/zm (Options->Images tab->OPT_CAMBOZOLA)

Now have fun and add your cameras to ZoneMinder knowing you now have a very stable and streamlined OS to run it on.

== CentOS 6 Notes ==

The installation for CentOS 6 is pretty much the same.
Download CentOS 6 minimal installation ISO (CentOS-6.0-i386-minimal.iso – 257MB). Burn to CD and install. We only want to be running in console text mode not GUI graphics mode. During installation configure network and tick to enable network adapter.
* Login as root and update the base install:
<pre>yum -y update</pre>
* Install required packages, other useful packages, and their dependencies
<pre>
yum groupinstall core
yum groupinstall base
yum install gcc gcc-c++ wget bison mysql-devel mysql-server php php-mysql php-pear php-pear-DB php-mbstring \
nano tftp-server httpd make ncurses-devel libtermcap-devel sendmail sendmail-cf caching-nameserver \
sox newt-devel libxml2-devel libtiff-devel php-gd audiofile-devel gtk2-devel subversion nano kernel-devel \
bison-devel ncurses zlib zlib-devel openssl openssl-devel gnutls-devel php-process perl-Time-HiRes
</pre>

Suggestion:
To remove various configure/make errors in Centos 6.2, you may also want to install:<pre>
bzip2-libs ffmpeg-devel ffmpeg-php perl-Net-SFTP-Foreign perl-Expect perl-LWPx-ParanoidAgent.x86_64</pre>

Now we continue from step four (4).
==== Installation of ZoneMinder ====
* In step five (5) the correct RPM Forge repository is:
<pre># For i686 CentOS 6.x run:
rpm -Uhv http://apt.sw.be/redhat/el6/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.i686.rpm

# For 64 bit CentOS 6.x run:
rpm -Uhv http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm</pre>

* In step five (5) the command that seems to configure zoneminder correctly is:
<pre>
CXXFLAGS=-D__STDC_CONSTANT_MACROS ./configure --with-webdir=/var/www/html/zm \
--with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache \
ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=your_zm_user ZM_DB_PASS=your_zm_password ZM_SSL_LIB=openssl
</pre>

Suggestion:
For Centos 6.2, I used the following configure string for success:<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=<zm user> ZM_DB_PASS=<zm user passwd> ZM_SSL_LIB=openssl --with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql" --with-ffmpeg=/usr/share/ffmpeg CXXFLAGS="-D__STDC_CONSTANT_MACROS" </pre>

==== Troubleshooting FFmpeg Errors Building ZoneMinder ====
Using the git version of FFmpeg can cause the ZoneMinder make process to fail with unresolved symbols in ffmpeg. To remedy this, use version 0.6.5 of FFmpeg with the same configure instructions as the normal install above.
FFmpeg 0.6.5: http://ffmpeg.org/releases/ffmpeg-0.6.5.tar.bz2
==== Troubleshooting Blank Page ====
If everything went ok but when accessing zoneminder's web page at http://localhost/zm, the page is blank this means that there is a problem with PHP short tags. Edit setting short_open_tag in php.ini (/etc/php.ini) and change it to On.
* Restart apache server with:
<pre>service httpd restart</pre> and you should be up and running.
==== Trouble shooting full drive with CentOS 6 ====
The default drive structure has chaned from that of CentOS 5 having the full drive allocated to the /root partition. CentOS 6 by default makes a logical volume 'LVM' of 10% your drives space for the /root partition and the remaining drive as the /home partion with the exception of the swap and boot partitions.

The will cause Zoneminder to fill the /root partition as the /var/www/html/zm/events directory is by default located here, you can use the system-config-lvm utility to re-adjust this partition balance if your system has been installed with the default partition structure.

It is best to install CentOS 6 with a custom partition layout that is the same as CentOS 5 structure, you can also if using a single physical had drive do with out the LVM drives and create an EXT4 /root partion along with the standard /boot and /swap partitions.

----

[[== '''P.S.''' ==]] aspcicc@jumpy.it
(Update: This does not appear to be required any more.)

Hi! and thanks for your guide.. i want to add a little correction that have made me crazy to resolve, when I poweroff or reboot system i obtain an error related to mysql database and i have understood that the problem was because mysqld is stopped before zoneminder to be more specific there isn't a link under rc0.d (halt) and rc6.d (reboot) to zoneminder that for this lack is simply killed by killall. To resolve this problem you need to add at the start of zm (under /etc/init.d) the line

' # chkconfig: 345 99 01 ' (without ' of course)

and then run
chkconfig --level 345 zm on
chkconfig --level 06 zm off

So the link to shutdown zm is created under rc0.d and rc6.d and zoneminder is started at the end of poweron and stopped at the beginning of the poweroff

For information about priority starting and stopping processes see: http://www.netadmintools.com/art94.html

----

Added Dependency: ImageMagick

Removed Dependency: perl-Time-HiRes, which causes a conflict with the default perl package.

Also, mysql seems to install with no password for the root user, and the zm DB create script creates the database on the fly, which means that the database create command needs to have the "-p zm" removed from the command line.

Could someone verify that this is correct, to make sure it's not just something I missed?

Thanks!
terry@cnysupport.com

----
Struggling to get x264 and ffmpeg working? I used the latest SVN versions not the Centos packages. But I was getting

''ffmpeg: error while loading shared libraries: libavdevice.so.53: cannot open shared object file: No such file or directory''

I followed these instructions:

<pre>cd /etc/ld.so.conf.d</pre>

* add another file: custom-libs.conf
* inside, put :

<pre>/usr/local/lib</pre>

* save the file
* run ldconfig
<pre>ldconfig</pre>

BeeryGaz

----

==== Failed monitors or ZM refusing to start ====
A problem that took me some time to figure out on two installations was SElinux.
SElinux stops Zoneminder from accessing some system parts or doing some functions so will cause various errors or simply drive you nuts trying to figure out.

Look at the following page on how to disable SElinux or use permissive mode.

<pre>http://www.centos.org/docs/5/html/5.2/Deployment_Guide/sec-sel-enable-disable.html</pre>

Some of the errors that I was getting with a fresh install on CentOS 6 was
<pre>
2013-02-16 16:13:10.828590 zmwatch 14898 ERR Can't open memory map file '/dev/shm/zm.mmap.1': No such file or directory zmwatch.pl
2013-02-16 16:13:10.736988 zmfix 15317 ERR Can't stat /dev/video0: Permission denied zmfix.cpp
</pre>

----
== ZoneMinder 1.26.x ==

Zoneminder after a long period of none development is now being developed by the community, these notes are to try and help with the installation of the new release on CentOS 5 and CentOS 6.
All testing has been done on a CentOS 6.4 fresh install server.

=== Cmake installation notes ===

Compiling of Zoneminder can now be done with the 'Cmake' command in replacement of the ./configure command this should automatically configure the build with the minimum of parameters. The 'Cmake' command at time of writing produced a partially working installation with the main files installed into /usr/local/bin/zoneminder and associated folders, different from the above guides.

The webfiles require to be linked via a zoneminder.conf file located with in the /disto/redhat directory inside the build directory that requires to be coped to the /etc/httpd/conf.d directory, this will need to be edited to the correct location of the webfiles and remove the local only command as indicated with in the file.

The Cmake install failed to use my BTTV capture card producing various errors with a potential solution given here <pre>http://www.zoneminder.com/forums/viewtopic.php?f=30&t=21709</pre>

=== ./configure compile ===

To install via the traditional ./configure method you first need to run the ./bootstrap.sh file to generate the required configure file, the install can then progress as the above installation guides.

This method has produced a fully working installation at time of writing.

== pt_BR Instructions ==

Here is a good walkthrough install of zoneminder in CentOS using the rpm package method. It is intended to Portuguese (pt or pt_BR) audience.

<pre>http://dulimind.blogspot.com.br/2015/02/zoneminder-no-centos-6-metodo-facil-com.html</pre>
----

[[Categories: Linux distributions]]

Fedora

2015-05-27T12:40:39Z

Knnniggett: /* Supported Versions */

The Fedora Project is a Red Hat sponsored, community-supported open source project. Its stated goal is to promote the rapid progress of free (as in freedom) and open source software and content, and its rapid innovation is possible using open processes and public forums.
'''

The project is led by the Fedora Project Board, which is comprised of community leaders and Red Hat members, and this group steers the direction of the project and of Fedora Core, the Linux distribution it develops. Red Hat employees work with the code alongside community members, and many Fedora Project innovations make their way into new releases of Red Hat Enterprise Linux.

ZoneMinder is developed on the Fedora distribution and no special actions are usually required for installation.

== Zmrepo - A ZoneMinder repository for RPM based distros ==
The ZoneMinder development team would like to introduce you to a new, easier way to install ZoneMinder on Fedora. Zmrepo is meant to be a turn-key solution. There is no compiling, no installing modules from CPAN, and no more complicated repository instructions.

This repository brings together a ZoneMinder rpm built by the development team, with all features enabled. This is in comparison to past ZoneMinder rpm's found in the Fedora repositories, which do not have ffmpeg support built-in. Zmrepo includes all dependencies that are not found in the default Fedora repositories. A few Perl modules are built by us, but all the rest of the dependencies are mirrored from popular sites such as EPEL and RPMFusion. There is no longer a need to add these additional repositories to your system. Zmrepo takes care of that for you.

==== Purpose ====
The primary purpose for developing ZoneMinder rpms for Fedora is to get an idea of how well ZoneMinder works on the bleeding edge of software development. We don't use Fedora in our production systems and consequently these rpms do not get the same share of testing that the ZoneMinder rpms for RHEL/CentOS do. However, they do give us the unique opportunity to solve any problems caused by new software widgets (looking at you systemd) before they trickle down to RHEL/CentOS.

==== Who Should Use ====
Those that want to use the latest and greatest packages available should use this repository over the RHEL/CentOS repository. Keep in mind that this comes with the real possibility Fedora may throw in something new, which might cause a problem with ZoneMinder.

==== Supported Versions ====
Fedora distributions have a relatively short life cycle. A new version of Fedora is scheduled to be released [https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle every 6 months]. It is the goal of the ZoneMinder development team to provide and support ZoneMinder rpms for the two most recent versions of Fedora. Today, those two versions are Fedora 22 and 21. Rpms built for older versions of Fedora may exist in zmrepo, but they will not be maintained and may be deleted at some point in the future.

==== Installation====

Please navigate to http://zmrepo.zoneminder.com/ and select your distro from the drop-down to view installation instructions.

Remember to follow the steps documented in README.Fedora following installation of the ZoneMinder rpm.

==Fedora 18 (alpha)==
*FIXED: ''if you get problems with Live Video not working'' due to a problem with the sockets. 
**ERROR: socket_sendto permission errors.
*Make sure your cgi-bin ScriptAlias is correct as shown below. 
*''ffmpeg libraries from Fedora rpms do not work'' with zm. You have to install from source (yuck).

This is how I got it installed... 

Do all the following as sudo (or root) 
'''install packages''' 
yum install mysql mysql-server zoneminder 

''' disable selinux 
vi /etc/selinux/config 
*change the word 'enforcing' to 'disabled' 

'''REBOOT'''

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf
* in the section - <Directory "/usr/share/zoneminder/www">
**remove the line "Deny from all # DELETE THIS LINE"
**remove the '-Indexes' on the Options line on Line 17 )I don't think the '-' is supposed to be there
**Comment out the Order and Allow lines and insert the new syntax 'Require all granted' as a new line
* I also got a ScriptAlias error for the cgi-bin/zm alias so I commented the cgi-bin scriptAlias in the /etc/httpd/conf/httpd.conf

#F18 /etc/httpd/conf.d.zoneminder.conf
Alias /zm "/usr/share/zoneminder/www"
<Directory "/usr/share/zoneminder/www">
Options FollowSymLinks
AllowOverride All
# NEW format
Require all granted
# The code unfortunately uses short tags in many places
php_value short_open_tag 1
#Deny from all # DELETE THIS LINE
</Directory>
ScriptAlias /cgi-bin "/usr/libexec/zoneminder/cgi-bin"
<Directory "/usr/libexec/zoneminder/cgi-bin">
Options +ExecCGI +MultiViews +SymLinksIfOwnerMatch
AllowOverride All
# NEW format
Require all granted
php_value short_open_tag 1
</Directory>
 
'''start httpd:''' 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 17==
'''install packages''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 14==
'''install packages:''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
/etc/init.d/mysqld start 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
/etc/init.d/httpd start 

'''start zoneminder''' 
/etc/init.d/zoneminder start 

==Fedora 11, 12 and 13==
'''The Easy Way''' Adapted from a forum post by "hiredguntech" or just search the forum for "flowers for candy"

Step-by-step installation of ZM v1.24.2 on Fedora-12.

(1) load fc12 using the netinstall ISO (the CD wants to use dhcp and doesn't work well with an assigned fixed IP) - turn off 'office' and turn on 'server' and 'development'. Besure to include a large /var partition through custom partitioning and use localhost instead of what it suggests (domain.localhost ?). Also, if you're using a capture card install it (them) in the system before starting the netinstall CD. Save these steps as a .txt file so the code can be cut and paste into the terminal with ease.

[2] Remove evolution from task bar (right click... (not a requirement)).

[3] Set screensaver to NOT require password and set it to 20 minutes or more (menu-system::preferences::screensaver).

(4) Disable SELinux. (menu-system::Admin::SELinux Mgmnt; change system default enforcing mode to disabled).

[5] Enable sudo for yourself. From a terminal (menu-Application::System Tools::Terminal),
Code:

su

(enter root password)

echo ''''YourUserName''' ALL=(ALL) ALL' >> /etc/sudoers (put YOUR user name from FC12 installation in place of '''YourUserName''')

(6) Set up the RPM Fusion Repository (in open terminal).

Code:

rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm

rpm -ivh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

exit

exit (closes terminal window)

(7) Install the pre-requisites, (menu-System::Administration::Add/Remove Software) type in the search field the following package names and select each of the closest match (there will be 'other' packages related or similar named - look for the right one, and check-it.)

mysql-server

mysql-devel

pcre-devel

ffmpeg

ffmpeg-devel

Hit the 'Apply' button, accept any added packages, type root password, and let this stuff load.

[8] Install any updates that are available, its the yellow icon up by the time.

(9) Enable the services: web and db. (menu-System::Administration::Services) and find the following:

httpd

mysqld

for each of them hit the 'enable button' so you can start them later.

(10) Reboot. This allows all the services to start and settle in.

(11) Now add Zoneminder (menu-System::Administration::Add/Remove Software) Type Zoneminder in the search field select it and apply.

[13] '''Note:''' To edit as root: open a terminal (menu-Application::System Tools::Terminal), su to root, type 'gedit <path/filename>'. Now you have sufficient permissions to edit & save as root.

(14) Edit as root /etc/httpd/conf.d/zoneminder.conf to remove the 'Deny from All' line. It even says 'DELETE THIS LINE', so it should be easy to find. Save it.

(15) As root, [or with sudo] build the zm database (menu-Application::System Tools::Terminal).

Code:

su

(enter root password)

mysql mysql < /usr/share/zoneminder/db/zm_create.sql

mysqladmin reload

mysql mysql

grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass';

\q

exit

exit

(16) Enable zoneminder. (menu-System::Administration::Services) and find zoneminder. Enable it. You can start the service hear also, Or in a terminal:

Code:

service zoneminder start

[18] Last thing - edit the SECOND entry of short_open_tag down at line 229. Again as root (menu-Application::System Tools::Terminal), gedit /etc/php.ini

Change short_open_tag from 'off' to 'on'

[19] reboot. open browser, type 'localhost/zm'

[20] It may be necessary to change the ffmpeg path in options::images to get ffmpeg to make videos. Generally removing the /local from the existing path will fix this issue

'''Or (the original wiki walk through)'''

You should be able to just do "yum install zoneminder", create the zm database, find the zm_create.sql file (rpm -ql zoneminder) and import it to mysql, then start zoneminder. Plus allow web access. Edit /etc/httpd/conf.d/zoneminder.conf and comment out (#) or delete this line :-

Deny from all # DELETE THIS LINE

Restart/reload apache

sudo service httpd restart

This didn't work for me due to 2 problems. First was php.ini section short_open_tag = Off, set to on

short_open_tag = On

Restart/reload apache

sudo service httpd restart

The other problem was zm_create.sql had duplicate indexes reported using phpMyAdmin. Removed all "INSERT INTO MonitorPresets" and "INSERT INTO MonitorPresets" in zm_create.sql and that imported cleanly. Alternatively just import from the command line mysql -u zmuser -p < zm_create.sql

http://www.zoneminder.com/forums/viewtopic.php?p=50242

'''Manual Install Version 1.24.2 with ffmpeg enabled'''

Version 1.23.3 has always compiled ok on Fedora 9/10/11 but I had problems with version 1.24.2.

Problems with compiling fixed by adding #include <cstdio> to all .cpp files in src directory and removing ccache package (yum remove ccache)

http://www.zoneminder.com/forums/viewtopic.php?p=55152

http://www.zoneminder.com/forums/viewtopic.php?t=12515&sid=0da85eb2fc78917d7a78cf788603a320

If using ffmpeg and ffmpeg-devel packages you may see problem compiling with libavutil.a . I could not get ffmpeg to compile so downloaded the Fedora source package and compiled it manually.

yumdownloader --source ffmpeg

sudo rpm -Uvh ffmpeg-0.5-5.20091026svn.fc12.src.rpm

Needed the following packages

sudo yum install dirac-devel faad2-devel gsm-devel imlib2-devel lame-devel libdc1394-devel libtheora-devel libvdpau-devel openjpeg-devel \
schroedinger-devel speex-devel texi2html x264-devel xvidcore-devel yasm

See http://fozzolog.fozzilinymoo.org/tech/2009/11/recompiling-ffmpeg-for-fedora-12-to-add-faac-support.html (don't need to add faac support, just follow procedure)

My rpmbuild failed so from the BUILD/ffmpeg-20091026

make
sudo make install
sudo make install-libs

and configured ZoneMinder to use /usr/local for FFMPEG

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost \
ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr -L/usr/lib/mysql" ZM_SSL_LIB=openssl --with-ffmpeg=/usr/local

==Fedora 8==
* Have packages for Apache and MySQL installed on the system.
* Install the zoneminder RPM package on the system
: Fedora Information for package zoneminder
: * http://koji.fedoraproject.org/koji/packageinfo?packageID=4691
* Configure zoneminder
* Make sure Apache and MySQL services are running
* Edit the zoneminder.conf apache configuration file to allow web connections
vi /etc/httpd/conf.d/zoneminder.conf
* Build the MySQL database table for zoneminder
mysql -p -u root mysql < /usr/share/zoneminder/db/zm_create.sql > mysqladmin -p -u root reload

The Fedora RPM creates /var/log/zoneminder, but the database scripts point logs to /tmp, rather than the new directory.
* Click '''Options''', '''Paths''' tab, and change
ZM_PATH_LOGS = /var/log/zoneminder
* Click '''Options''', '''Debug''' tab, and change
ZM_EXTRA_DEBUG_LOG = /var/log/zoneminder/zm_debug.log+

* Install ffmpeg on Fedora.
Due to licensing the ffmpeg package is absent from Fedora. It can be added from [[Fedora_Linux_Distribution_Reference#Livna:_Get_Important_Packages_Missing_From_Fedora|Livna]].
wget http://rpm.livna.org/livna-release-8.rpm
rpm -ih livna-release-8.rpm
yum install ffmpeg
yum install ffmpeg-devel
Which provides the following: ffmpeg-libs-0.4.9-0.41.20071011.lvn8, ffmpeg-0.4.9-0.41.20071011.lvn8, ffmpeg-devel-0.4.9-0.41.20071011.lvn8

* Test ffmpeg
ffmpeg -f image2 -i %03d-capture.jpg /tmp/movie.mpg

==Fedora 7==
* Builds From source - see [[Fedora Core 6 Step-by-Step]] '''AS WELL AS''' [http://www.zoneminder.com/forums/viewtopic.php?t=9414 Fedora 7 forum topic]
*RPMs are Available in the '''main Fedora 7 distribution''', and in the development 'rawhide' tree.
**Its as easy as running: yum install zoneminder
**Take a look at [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 6==
*Build from source [[Fedora Core 6 Step-by-Step]]

* RPMs are also available right now in '''Fedora Extras''' for Fedora Core 6.
** [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 4==
* http://www.zoneminder.com/forums/viewtopic.php?t=5991 
Set web user and group correctly and set the log dir to a writeable location.
With FC4 there are three things that must be done to get ZM running,:
#is in the /etc/ld.so.conf.d/ dir created a file with 775 perm called zm.conf and add the line '/usr/local/lib' to it and type 'ldconfig' once it is added, also with a fresh install of FC4 make sure SE linux is disabled if you are not using it. Check your log path in options under the paths tab. This will tell you were the log are going to be put.
#Second make sure the path exists.
#Third create the log files if they do not exist and make sure that they have the correct permissions. '''If zm can not open and write the log files, it will not start. '''

Fedora

2015-05-27T12:40:13Z

Knnniggett: /* Installation */

The Fedora Project is a Red Hat sponsored, community-supported open source project. Its stated goal is to promote the rapid progress of free (as in freedom) and open source software and content, and its rapid innovation is possible using open processes and public forums.
'''

The project is led by the Fedora Project Board, which is comprised of community leaders and Red Hat members, and this group steers the direction of the project and of Fedora Core, the Linux distribution it develops. Red Hat employees work with the code alongside community members, and many Fedora Project innovations make their way into new releases of Red Hat Enterprise Linux.

ZoneMinder is developed on the Fedora distribution and no special actions are usually required for installation.

== Zmrepo - A ZoneMinder repository for RPM based distros ==
The ZoneMinder development team would like to introduce you to a new, easier way to install ZoneMinder on Fedora. Zmrepo is meant to be a turn-key solution. There is no compiling, no installing modules from CPAN, and no more complicated repository instructions.

This repository brings together a ZoneMinder rpm built by the development team, with all features enabled. This is in comparison to past ZoneMinder rpm's found in the Fedora repositories, which do not have ffmpeg support built-in. Zmrepo includes all dependencies that are not found in the default Fedora repositories. A few Perl modules are built by us, but all the rest of the dependencies are mirrored from popular sites such as EPEL and RPMFusion. There is no longer a need to add these additional repositories to your system. Zmrepo takes care of that for you.

==== Purpose ====
The primary purpose for developing ZoneMinder rpms for Fedora is to get an idea of how well ZoneMinder works on the bleeding edge of software development. We don't use Fedora in our production systems and consequently these rpms do not get the same share of testing that the ZoneMinder rpms for RHEL/CentOS do. However, they do give us the unique opportunity to solve any problems caused by new software widgets (looking at you systemd) before they trickle down to RHEL/CentOS.

==== Who Should Use ====
Those that want to use the latest and greatest packages available should use this repository over the RHEL/CentOS repository. Keep in mind that this comes with the real possibility Fedora may throw in something new, which might cause a problem with ZoneMinder.

==== Supported Versions ====
Fedora distributions have a relatively short life cycle. A new version of Fedora is scheduled to be released [https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle every 6 months]. It is the goal of the ZoneMinder development team to provide and support ZoneMinder rpms for the two most recent versions of Fedora. Today, those two versions are Fedora 21 and 20. Rpms built for older versions of Fedora may exist in zmrepo, but they will not be maintained and may be deleted at some point in the future.

==== Installation====

Please navigate to http://zmrepo.zoneminder.com/ and select your distro from the drop-down to view installation instructions.

Remember to follow the steps documented in README.Fedora following installation of the ZoneMinder rpm.

==Fedora 18 (alpha)==
*FIXED: ''if you get problems with Live Video not working'' due to a problem with the sockets. 
**ERROR: socket_sendto permission errors.
*Make sure your cgi-bin ScriptAlias is correct as shown below. 
*''ffmpeg libraries from Fedora rpms do not work'' with zm. You have to install from source (yuck).

This is how I got it installed... 

Do all the following as sudo (or root) 
'''install packages''' 
yum install mysql mysql-server zoneminder 

''' disable selinux 
vi /etc/selinux/config 
*change the word 'enforcing' to 'disabled' 

'''REBOOT'''

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf
* in the section - <Directory "/usr/share/zoneminder/www">
**remove the line "Deny from all # DELETE THIS LINE"
**remove the '-Indexes' on the Options line on Line 17 )I don't think the '-' is supposed to be there
**Comment out the Order and Allow lines and insert the new syntax 'Require all granted' as a new line
* I also got a ScriptAlias error for the cgi-bin/zm alias so I commented the cgi-bin scriptAlias in the /etc/httpd/conf/httpd.conf

#F18 /etc/httpd/conf.d.zoneminder.conf
Alias /zm "/usr/share/zoneminder/www"
<Directory "/usr/share/zoneminder/www">
Options FollowSymLinks
AllowOverride All
# NEW format
Require all granted
# The code unfortunately uses short tags in many places
php_value short_open_tag 1
#Deny from all # DELETE THIS LINE
</Directory>
ScriptAlias /cgi-bin "/usr/libexec/zoneminder/cgi-bin"
<Directory "/usr/libexec/zoneminder/cgi-bin">
Options +ExecCGI +MultiViews +SymLinksIfOwnerMatch
AllowOverride All
# NEW format
Require all granted
php_value short_open_tag 1
</Directory>
 
'''start httpd:''' 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 17==
'''install packages''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 14==
'''install packages:''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
/etc/init.d/mysqld start 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
/etc/init.d/httpd start 

'''start zoneminder''' 
/etc/init.d/zoneminder start 

==Fedora 11, 12 and 13==
'''The Easy Way''' Adapted from a forum post by "hiredguntech" or just search the forum for "flowers for candy"

Step-by-step installation of ZM v1.24.2 on Fedora-12.

(1) load fc12 using the netinstall ISO (the CD wants to use dhcp and doesn't work well with an assigned fixed IP) - turn off 'office' and turn on 'server' and 'development'. Besure to include a large /var partition through custom partitioning and use localhost instead of what it suggests (domain.localhost ?). Also, if you're using a capture card install it (them) in the system before starting the netinstall CD. Save these steps as a .txt file so the code can be cut and paste into the terminal with ease.

[2] Remove evolution from task bar (right click... (not a requirement)).

[3] Set screensaver to NOT require password and set it to 20 minutes or more (menu-system::preferences::screensaver).

(4) Disable SELinux. (menu-system::Admin::SELinux Mgmnt; change system default enforcing mode to disabled).

[5] Enable sudo for yourself. From a terminal (menu-Application::System Tools::Terminal),
Code:

su

(enter root password)

echo ''''YourUserName''' ALL=(ALL) ALL' >> /etc/sudoers (put YOUR user name from FC12 installation in place of '''YourUserName''')

(6) Set up the RPM Fusion Repository (in open terminal).

Code:

rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm

rpm -ivh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

exit

exit (closes terminal window)

(7) Install the pre-requisites, (menu-System::Administration::Add/Remove Software) type in the search field the following package names and select each of the closest match (there will be 'other' packages related or similar named - look for the right one, and check-it.)

mysql-server

mysql-devel

pcre-devel

ffmpeg

ffmpeg-devel

Hit the 'Apply' button, accept any added packages, type root password, and let this stuff load.

[8] Install any updates that are available, its the yellow icon up by the time.

(9) Enable the services: web and db. (menu-System::Administration::Services) and find the following:

httpd

mysqld

for each of them hit the 'enable button' so you can start them later.

(10) Reboot. This allows all the services to start and settle in.

(11) Now add Zoneminder (menu-System::Administration::Add/Remove Software) Type Zoneminder in the search field select it and apply.

[13] '''Note:''' To edit as root: open a terminal (menu-Application::System Tools::Terminal), su to root, type 'gedit <path/filename>'. Now you have sufficient permissions to edit & save as root.

(14) Edit as root /etc/httpd/conf.d/zoneminder.conf to remove the 'Deny from All' line. It even says 'DELETE THIS LINE', so it should be easy to find. Save it.

(15) As root, [or with sudo] build the zm database (menu-Application::System Tools::Terminal).

Code:

su

(enter root password)

mysql mysql < /usr/share/zoneminder/db/zm_create.sql

mysqladmin reload

mysql mysql

grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass';

\q

exit

exit

(16) Enable zoneminder. (menu-System::Administration::Services) and find zoneminder. Enable it. You can start the service hear also, Or in a terminal:

Code:

service zoneminder start

[18] Last thing - edit the SECOND entry of short_open_tag down at line 229. Again as root (menu-Application::System Tools::Terminal), gedit /etc/php.ini

Change short_open_tag from 'off' to 'on'

[19] reboot. open browser, type 'localhost/zm'

[20] It may be necessary to change the ffmpeg path in options::images to get ffmpeg to make videos. Generally removing the /local from the existing path will fix this issue

'''Or (the original wiki walk through)'''

You should be able to just do "yum install zoneminder", create the zm database, find the zm_create.sql file (rpm -ql zoneminder) and import it to mysql, then start zoneminder. Plus allow web access. Edit /etc/httpd/conf.d/zoneminder.conf and comment out (#) or delete this line :-

Deny from all # DELETE THIS LINE

Restart/reload apache

sudo service httpd restart

This didn't work for me due to 2 problems. First was php.ini section short_open_tag = Off, set to on

short_open_tag = On

Restart/reload apache

sudo service httpd restart

The other problem was zm_create.sql had duplicate indexes reported using phpMyAdmin. Removed all "INSERT INTO MonitorPresets" and "INSERT INTO MonitorPresets" in zm_create.sql and that imported cleanly. Alternatively just import from the command line mysql -u zmuser -p < zm_create.sql

http://www.zoneminder.com/forums/viewtopic.php?p=50242

'''Manual Install Version 1.24.2 with ffmpeg enabled'''

Version 1.23.3 has always compiled ok on Fedora 9/10/11 but I had problems with version 1.24.2.

Problems with compiling fixed by adding #include <cstdio> to all .cpp files in src directory and removing ccache package (yum remove ccache)

http://www.zoneminder.com/forums/viewtopic.php?p=55152

http://www.zoneminder.com/forums/viewtopic.php?t=12515&sid=0da85eb2fc78917d7a78cf788603a320

If using ffmpeg and ffmpeg-devel packages you may see problem compiling with libavutil.a . I could not get ffmpeg to compile so downloaded the Fedora source package and compiled it manually.

yumdownloader --source ffmpeg

sudo rpm -Uvh ffmpeg-0.5-5.20091026svn.fc12.src.rpm

Needed the following packages

sudo yum install dirac-devel faad2-devel gsm-devel imlib2-devel lame-devel libdc1394-devel libtheora-devel libvdpau-devel openjpeg-devel \
schroedinger-devel speex-devel texi2html x264-devel xvidcore-devel yasm

See http://fozzolog.fozzilinymoo.org/tech/2009/11/recompiling-ffmpeg-for-fedora-12-to-add-faac-support.html (don't need to add faac support, just follow procedure)

My rpmbuild failed so from the BUILD/ffmpeg-20091026

make
sudo make install
sudo make install-libs

and configured ZoneMinder to use /usr/local for FFMPEG

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost \
ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr -L/usr/lib/mysql" ZM_SSL_LIB=openssl --with-ffmpeg=/usr/local

==Fedora 8==
* Have packages for Apache and MySQL installed on the system.
* Install the zoneminder RPM package on the system
: Fedora Information for package zoneminder
: * http://koji.fedoraproject.org/koji/packageinfo?packageID=4691
* Configure zoneminder
* Make sure Apache and MySQL services are running
* Edit the zoneminder.conf apache configuration file to allow web connections
vi /etc/httpd/conf.d/zoneminder.conf
* Build the MySQL database table for zoneminder
mysql -p -u root mysql < /usr/share/zoneminder/db/zm_create.sql > mysqladmin -p -u root reload

The Fedora RPM creates /var/log/zoneminder, but the database scripts point logs to /tmp, rather than the new directory.
* Click '''Options''', '''Paths''' tab, and change
ZM_PATH_LOGS = /var/log/zoneminder
* Click '''Options''', '''Debug''' tab, and change
ZM_EXTRA_DEBUG_LOG = /var/log/zoneminder/zm_debug.log+

* Install ffmpeg on Fedora.
Due to licensing the ffmpeg package is absent from Fedora. It can be added from [[Fedora_Linux_Distribution_Reference#Livna:_Get_Important_Packages_Missing_From_Fedora|Livna]].
wget http://rpm.livna.org/livna-release-8.rpm
rpm -ih livna-release-8.rpm
yum install ffmpeg
yum install ffmpeg-devel
Which provides the following: ffmpeg-libs-0.4.9-0.41.20071011.lvn8, ffmpeg-0.4.9-0.41.20071011.lvn8, ffmpeg-devel-0.4.9-0.41.20071011.lvn8

* Test ffmpeg
ffmpeg -f image2 -i %03d-capture.jpg /tmp/movie.mpg

==Fedora 7==
* Builds From source - see [[Fedora Core 6 Step-by-Step]] '''AS WELL AS''' [http://www.zoneminder.com/forums/viewtopic.php?t=9414 Fedora 7 forum topic]
*RPMs are Available in the '''main Fedora 7 distribution''', and in the development 'rawhide' tree.
**Its as easy as running: yum install zoneminder
**Take a look at [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 6==
*Build from source [[Fedora Core 6 Step-by-Step]]

* RPMs are also available right now in '''Fedora Extras''' for Fedora Core 6.
** [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 4==
* http://www.zoneminder.com/forums/viewtopic.php?t=5991 
Set web user and group correctly and set the log dir to a writeable location.
With FC4 there are three things that must be done to get ZM running,:
#is in the /etc/ld.so.conf.d/ dir created a file with 775 perm called zm.conf and add the line '/usr/local/lib' to it and type 'ldconfig' once it is added, also with a fresh install of FC4 make sure SE linux is disabled if you are not using it. Check your log path in options under the paths tab. This will tell you were the log are going to be put.
#Second make sure the path exists.
#Third create the log files if they do not exist and make sure that they have the correct permissions. '''If zm can not open and write the log files, it will not start. '''

Main Documentation

2015-05-14T15:01:00Z

Knnniggett: /* Installation */

'''Please Note: This documentation is not yet fully updated for changes in versions from 1.23.0 or 1.24. Updates will be applied as soon as possible.'''

* You may also find specific installation and setup guides under [[Contents#Distribution-specific_guides]] and a french translated doc under [[Media:ZoneMinderWikifr-v2.pdf]]

----

==Introduction==

Welcome to ZoneMinder, the all-in-one Linux GPL'd security camera solution.

A while back my garage was burgled and all my power tools were stolen! I realized shortly after that if I'd just had a camera overlooking the door then at least I'd have know exactly when and who did the dirty deed. And so ZoneMinder was born. It's still relatively new but hopefully it has developed into something that can be genuinely useful and prevent similar incidents or even perhaps bring some perpetrators to justice.

PROPOSED ADDITION
''Most commercial "security systems" are designed as a monitoring system that also records. Recording quality can vary from bad to unusable, locating the relevant video can range from challenging to impractical, and exporting can often only be done with the manual present. ZoneMinder was designed primarily to record, and allow easy searches and exporting. Recordings are of the best possible quality, easy to filter and find, and simple to export using any system with a web browser. It also monitors.''

ZoneMinder is designed around a series of independent components that only function when necessary limiting any wasted resource and maximising the efficiency of your machine. A fairly ancient Pentium II PC should be able to track one camera per device at up to 25 frames per second with this dropping by half approximately for each additional camera on the same device. Additional cameras on other devices do not interact so can maintain this frame rate. Even monitoring several cameras still will not overload the CPU as frame processing is designed to synchronise with capture and not stall it.

As well as being fast ZoneMinder is designed to be friendly and even more than that, actually useful. As well as the fast video interface core it also comes with a user friendly and comprehensive PHP based web interface allowing you to control and monitor your cameras from home, at work, on the road, or even a web enabled cell phone. It supports variable web capabilities based on available bandwidth. The web interface also allows you to view events that your cameras have captured and archive them or review them time and again, or delete the ones you no longer wish to keep. The web pages directly interact with the core daemons ensuring full co-operation at all times. ZoneMinder can even be installed as a system service ensuring it is right there if your computer has to reboot for any reason.

The core of ZoneMinder is the capture and analysis of images and there is a highly configurable set of parameters that allow you to ensure that you can eliminate false positives whilst ensuring that anything you don't want to miss will be captured and saved. ZoneMinder allows you to define a set of 'zones' for each camera of varying sensitivity and functionality. This allows you to eliminate regions that you don't wish to track or define areas that will alarm if various thresholds are exceeded in conjunction with other zones.

ZoneMinder is fresh off the keyboard and so comes with no warranty whatsoever, please try it, send your feedback and if you get anything useful out of it let me know.

ZoneMinder is free but if you do get ZoneMinder up and running and find it useful then please feel free to visit http://www.zoneminder.com/donate.html where '''any donations will be appreciated''' and will help to fund future improvements to ZoneMinder. This would be especially relevant if you use ZoneMinder as part of your business, or to protect your property.

==Requirements==
ZoneMinder needs a couple of things to work. If you are installing a package (Debian, Ubuntu, or RedHat) the package should install all of the needed core components. However, you may want to install several optional components (such as ffmpeg) as well. If you are installing from a LiveCD, it will install all of the needed components, but they may not be the latest version. If you compile it from source, ordinarily the ‘configure’ script will check for the presence of required (and optional) components but it is useful to be prepared beforehand.

Firstly, it uses MySQL so you'll need that. In order to compile you need to make sure you have a development installation and not just a runtime; this is because it needs to use the MySQL header files. If you are running an RPM based distribution then it’s probably worth installing all the pure MySQL rpm files to be sure you have the right ones. If you are installing the .deb file, it will install it for you. If you already have a MySQL install, be aware that changes you have made to security or configuration may cause problems.

Next it does things with JPEGs so you'll need at least libjpeg.a which I think come as standard nowadays with most distributions. Users have reported varying degrees of success with other jpeg libraries such as jpeg-mmx but these are not officially supported. If you plan to use network cameras then the Perl Compatible Regular Expression library (libpcre.a) can prove useful but is not always essential. ZoneMinder also uses the netpbm utilities in a very limited way to generate thumbnails under certain circumstances though this can be modified.

ZoneMinder can generate MPEG videos if necessary, for this you'll need either ffmpeg (recommended) or the Berkeley MPEG encoder (mpeg_encode). If you don't have either, don't worry, as the options will be hidden and you'll not really miss too much. Some of the authentication uses openssl MD5 functions, if you get a grumble about these during configuration all it will mean is that authentication won’t be used for streaming. The web interface uses PHP and so you need that in your apache or other web server as well, make sure MySQL support is available either statically or as a module. There are also various perl modules that you may need that vary depending on which options you choose on installation, for more details see later in this document.

Finally, there is quite a bit of image streaming in the package. So if you don't have FireFox or another browser that supports image streaming natively I recommend you get the excellent Cambozola java applet from http://www.charliemouse.com:8080/code/cambozola/ which will let you view the image stream in Internet Explorer and others. Otherwise you're limited to just refreshing still images or mpeg based streams, if you have compatible plugins. As upgraded version have occasionally caused problems, a known working version of Cambozola is also in the [http://www.zoneminder.com/downloads.html Downloads] section of the ZoneMinder website.

Hardware-wise, ZoneMinder has been used with various video and USB cameras with the V4L interface. It will also work with most Network or IP cameras. I don't have a lot of cameras myself so I've not had chance to test it with a huge range personally. However, there are many other people who have used many other products, and there is a list of devices that are definitely known to work on the web site. Please enter you camera on the [[Supported_hardware|Wiki list]] on zoneminder.com if your camera works and is not listed. You do need to have Video4Linux installed. In terms of computer hardware, there are no hard and fast requirements. You may get a system that works with one or two cameras going on an old P200 but you will be able to support more cameras, at a higher frame rate, with faster machines with more RAM. More guidance is available on the web forums.

==Components==
ZoneMinder is not a single monolithic application but is formed from several components. These components primarily include executable compiled binaries which do the main video processing work, perl scripts which usually perform helper and/or external interface tasks and php web scripts which are used for the web interface.

A brief description of each of the principle components follows.

; zmc : This is the ZoneMinder Capture daemon. This binary's job is to sit on a video device and suck frames off it as fast as possible, this should run at more or less constant speed.
; zma : This is the ZoneMinder Analysis daemon. This is the component that goes through the captured frames and checks them for motion which might generate an alarm or event. It generally keeps up with the Capture daemon but if very busy may skip some frames to prevent it falling behind.
; zmf : This is the ZoneMinder Frame daemon. This is an optional daemon that can run in concert with the Analysis daemon and whose function it is to actually write captured frames to disk. This frees up the Analysis daemon to do more analysis (!) and so keep up with the Capture daemon better. If it isn’t running or dies then the Analysis daemon just writes them itself.
; zms : This is the ZoneMinder Streaming server. The web interface connects with this to get real-time or historical streamed images. It runs only when a live monitor stream or event stream is actually being viewed and dies when the event finishes or the associate web page is closed. If you find you have several zms processes running when nothing is being viewed then it is likely you need a patch for apache (see the Troubleshooting section). A non-parsed header version of zms, called nph-zms, is also installed and may be used instead depending on your web server configuration.
; zmu : This is the ZoneMinder Utility. It's basically a handy command line interface to several useful functions. It’s not really meant to be used by anyone except the web page (there's only limited 'help' in it so far) but can be if necessary, especially for debugging video problems.
; zmfix : This is a small binary that exists only to ensure that the video device files can be read by the main capture daemons. It is often the case that these device files are set to be accessible by root only on boot. This binary runs setuid and ensures that they have appropriate permissions. This is not a daemon and runs only on system start and then exits. '''Note that ZoneMinder 1.26.5 was the last release with this utility.''' Running zmfix setuid was a security risk is no longer needed because most modern Linux distros assign local devices to the "video" group. Simply assign the account the capture daemons run under (usually apache or www-data) to the video group.

As well as this there are the web PHP files in the web directory and some perl scripts in the scripts directory. These scripts all have some configuration at the top of the files which should be viewed and amended if necessary and are as follows.

; zmpkg.pl : This is the ZoneMinder Package Control script. This is used by the web interface and service scripts to control the execution of the system as a whole.
; zmdc.pl : This is the ZoneMinder Daemon Control script. This is used by the web interface and the zmpkg.pl script to control and maintain the execution of the capture and analysis daemons, amongst others. You should not need to run this script yourself.
; zmfilter.pl : This script controls the execution of saved filters and will be started and stopped by the web interface based on whether there are filters that have been defined to be autonomous. This script is also responsible for the automatic uploading of events to a 3rd party server.

; zmaudit.pl : This script is used to check the consistency of the event file system and database. It can delete orphaned events, i.e. ones that appear in one location and not the other as well as checking that all the various event related tables are in line. It can be run interactively or in batch mode either from the command line or a cron job or similar. In the zmconfig.pl there is an option to specify fast event deletes where the web interface only deletes the event entry from the database itself. If this is set then it is this script that tidies up the rest.

; zmwatch.pl : This is a simple script purely designed to keep an eye on the capture daemons and restart them if they lockup. It has been known for sync problems in the video drivers to cause this so this script makes sure that nothing important gets missed.
; zmupdate.pl : Currently this script is responsible for checking whether a new version of ZoneMinder is available and other miscellaneous actions related to upgrades and migrations. It is also intended to be a ‘one stop shop’ for any upgrades and will execute everything necessary to update your installation to a new version.
; zmvideo.pl : This script is used from the web interface to generate video files in various formats in a common way. You can also use it from the command line in certain circumstances but this is not usually necessary.
; zmx10.pl : This is an optional script that can be used to initiate and monitor X10 Home Automation style events and interface with an alarm system either by the generation of X10 signals on ZoneMinder events or by initiating ZoneMinder monitoring and capture on receipt of X10 signals from elsewhere, for instance the triggering of an X10 PIR. For example I have several cameras that don’t do motion detection until I arm my alarm system whereupon they switch to active mode when an X10 signal is generated by the alarm system and received by ZoneMinder.
; zmtrigger.pl : This is an optional script that is a more generic solution to external triggering of alarms. It can handle external connections via either internet socket, unix socket or file/device interfaces. You can either use it ‘as is’ if you can interface with the existing format, or override connections and channels to customise it to your needs. The format of triggers used by zmtrigger.pl is as follows "<id>|<action>|<score>|<cause>|<text>|<showtext>" where
:* 'id' is the id number or name of the ZM monitor
:* 'action' is 'on', 'off', 'cancel' or ‘show’ where 'on' forces an alarm condition on, 'off' forces an alarm condition off and 'cancel' negates the previous 'on' or 'off'. The ‘show’ action merely updates some auxiliary text which can optionally be displayed in the images captured by the monitor. Ordinarily you would use 'on' and 'cancel', 'off' would tend to be used to suppress motion based events. Additionally 'on' and 'off' can take an additional time offset, e.g. on+20 which automatically 'cancel's the previous action after that number of seconds.
:* 'score' is the score given to the alarm, usually to indicate it's importance. For 'on' triggers it should be non-zero, otherwise it should be zero.
:* 'cause' is a 32 char max string indicating the reason for, or source of the alarm e.g. 'Relay 1 open'. This is saved in the ‘Cause’ field of the event. Ignored for 'off' or 'cancel' messages
:* 'text' is a 256 char max additional info field, which is saved in the ‘Description’ field of an event. Ignored for 'off' or 'cancel' messages.
:* 'showtext' is up to 32 characters of text that can be displayed in the timestamp that is added to images. The ‘show’ action is designed to update this text without affecting alarms but the text is updated, if present, for any of the actions. This is designed to allow external input to appear on the images captured, for instance temperature or personnel identity etc.

: Note that multiple messages can be sent at once and should be LF or CRLF delimited. This script is not necessarily intended to be a solution in itself, but is intended to be used as ‘glue’ to help ZoneMinder interface with other systems. It will almost certainly require some customisation before you can make any use of it. If all you want to do is generate alarms from external sources then using the ZoneMinder::SharedMem perl module is likely to be easier.

; zmcamtool.pl : This optional script is new for the upcoming 1.27 release of ZoneMinder. It is intended to make it easy to do the following: bring in new ptz controls and camera presets, convert existing monitors into presets, and export custom ptz controls and presets. For the initial release, this script is not integrated into the UI and must be called from the command line. Type ''zmcamtool.pl --help'' from the command line to get an explanation of the different arguments one can pass to the script.
; zmcontrol-*.pl : These are a set of example scripts which can be used to control Pan/Tilt/Zoom class cameras. Each script converts a set of standard parameters used for camera control into the actual protocol commands sent to the camera. If you are using a camera control protocol that is not in the shipped list then you will have to create a similar script though it can be created entirely separately from ZoneMinder and does not need to named as these scripts are. Although the scripts are used to action commands originated from the web interface they can also be used directly or from other programs or scripts, for instance to implement periodic scanning to different presets.
; zmtrack.pl : This script is used to manage the experimental motion tracking feature. It is responsible for detecting that an alarm is taking place and moving the camera to point to the alarmed location, and then subsequently returning it to a defined standby location. As well as moving the camera it also controls when motion detection is suspended and restored so that the action of the camera tracking does not trigger endless further alarms which are not justified.
; zm : This is the (optional) ZoneMinder init script, see below for details.

Finally, there are also a number of ZoneMinder perl modules included. These are used by the scripts above, but can also be used by your own or 3rd party scripts. Full documentation for most modules is available in ‘pod’ form via ‘perldoc’ but the general purpose of each module is as follows.

; ZoneMinder.pm : This is a general ZoneMinder container module. It includes the Base.pm, Config.pm Debug.pm, Database.pm, and SharedMem.pm modules described below. It also exports all of their symbols by default. If you use the other modules directly you have request which symbol tags to import.
; ZoneMinder/Base.pm : This is the base ZoneMinder perl module. It contains only simple data such as version information. It is included by all other ZoneMinder perl modules
; ZoneMinder/Config.pm : This module imports the ZoneMinder configuration from the database.
; ZoneMinder/Debug. pm : This module contains the defined Debug and Error functions etc, that are used by scripts to produce diagnostic information in a standard format.
; ZoneMinder/Database.pm : This module contains database access definitions and functions. Currently not a lot is in this module but it is included as a placeholder for future development.
; ZoneMinder/SharedMem.pm : This module contains standard shared memory access functions. These can be used to access the current state of monitors etc as well as issuing commands to the monitors to switch things on and off. This module effectively provides a ZoneMinder API.
; ZoneMinder/ConfigAdmin.pm : This module is a specialised module that contains the definition, and other information, about the various configuration options. It is not intended for use by 3rd parties.
; ZoneMinder/Trigger/*.pm : These modules contain definitions of trigger channels and connections used by the zmtrigger.pl script. Although they can be used ‘as is’, they are really intended as examples that can be customised or specialised for different interfaces. Contributed modules for new channels or connections will be welcomed and included in future versions of ZoneMinder.

==Building==
To build ZoneMinder from source, the first thing you need to do is run bootstrap.sh. This will create the configure script, which in turn must be executed to define some initial configuration. If you are happy with the default settings for the database host (‘localhost’), name (‘zm’), user (‘zmuser’) and password (‘zmpass’) then you can just type

./bootstrap.sh
./configure --with-webdir=<your web directory> --with-cgidir=<your cgi directory>

where '''--with-webdir''' is the directory to which you want to install the PHP files, and '''--with-cgidir''' is the directory to which you want to install CGI files. These directories could be '''/var/www/html/zm''' and '''/var/www/cgi-bin''' for example.

If you want to override any of the default database values then you can append them to the configure command, for example to use a database password of ‘zmnewpass’ do

./configure --with-webdir=<your web directory> --with-cgidir=<your cgi directory> ZM_DB_PASS=zmnewpass

and so on. The values you can use are ZM_DB_HOST, ZM_DB_NAME, ZM_DB_USER and ZM_DB_PASS. Other than the database name, which is substituted into the database creation script, these values can easily be changed after this step.

If the script cannot find your MySQL installation, for instance if it is installed in an unusual location, then '''--with-mysql''' identifies the root directory where you have installed it, usually /usr.

If you want to use real MPEG based streaming you will need to have built and installed the ffmpeg tools. You can then also use '''--with-ffmpeg=<path to ffmpeg root>''' to help configure find it if it’s not installed in a default location. Note, you have to make sure you have installed the ffmpeg headers and libraries (make installlib) as well as the binaries (make install), or a development package with them in.

If you have built ffmpeg with any additional options which require extra libraries in the link stage then you can use --with-extralibs to pass these libraries to the configure script, to prevent unresolved dependencies. Otherwise ignore this option.

If you are on a 64 bit system you may find that the '''--with-libarch''' option helps you correctly define your library paths.

There are also two further parameters you can add if your web user and group are not both 'apache'. These are '''--with-webuser''' and '''--with-webgroup''' which you would normally change to be your system httpd daemon owner. Alternatively you should be able to create a 'zoneminder' system user, assign that user to your httpd daemon group and then use use 'zoneminder' as the webuser instead of apache or whatever your system uses. This has the additional benefit of partitioning security somewhat and not opening up full access to all web user files in the event of a security breach.

This is also when you have the opportunity to pass any additional flags to the compiler to modify how the application is built. To do this append '''CFLAGS="<options>"''' and '''CXXFLAGS="<options>"''' to pass in compiler flags for 'c' and 'c++' compilation respectively. For instance the default compiler flags are usually --O2 and --g to create binaries with moderate optimisation and debugging symbols. If you wanted to optimise further, including processor specific tweaks but still keep debugging symbols then could use '''CFLAGS="-g -O3 -march=pentium4"''' and '''CXXFLAGS="-g -O3 -march=pentium4"''' for instance. Consult the gcc/g++ documentation for help on these and other options. Also be aware that even if you optimise your ZoneMinder build, any libraries that get linked in will only perform as well as the options used when they were built allows. Thus to get full benefit you would usually need to rebuild libjpeg.a and/or other libraries with similar options.

Type

./configure --help

for details on these, and other, options.

Now you can just type '''make''' to do the build. The first time you run this you may get a warning about a Makefile being rebuilt in the scripts directory, and make will terminate. This is normal and you can just rerun make to complete the build.

==Installation==
Installation via the traditional build-from-source method is discouraged. The current development team, along with other volunteers, have made great strides in developing better methods to get ZoneMinder installed on your distro.

Please navigate to the [https://github.com/ZoneMinder/ZoneMinder ZoneMinder github site] and review the Readme (scroll down) for the most current installation documentation.

===Installation from Source===
This method has been depreciated, but is still useful as a reference.

For a new installation the next thing you will need to do is create your database and database users. So type the commands as follows when in the folder of the extracted zm files,

Create the ZoneMinder database 'zm' and populate it with the tables for ZoneMinder:

$ mysql
mysql> create database zm;
mysql> exit;
$ mysql zm < db/zm_create.sql <This file doesn't exist until after 'make'>

Finally, create a MySQL user account for ZoneMinder:
$ mysql zm
mysql> grant select,insert,update,delete,lock tables,alter on zm.* to '<database user>'@localhost identified by '<database password>';
mysql> quit;
$ mysqladmin reload

You may need to supply a username and password to the mysql commands in the first place to give yourself sufficient privileges to perform the required commands. To do that it's something like:
mysql -uroot -p<root database password> zm.

If you want to host your database on a different machine than that which ZoneMinder is running on then you will need to perform this step on the remote machine and reference the ZoneMinder machine instead of localhost. If you are running remote databases you probably already know all this, if you are not then don’t worry about it!

At this stage typing

make install

will install everything to the desired locations, you may need to su to root first though to give yourself adequate permissions. The installation routine will copy the binaries and scripts to your chosen install location, usually /usr/local/bin and then move zms (and nph-zms) to your cgi-bin area. It will then copy the web files to your chosen directory and ensure they have the right permissions, and install the ZoneMinder perl modules in the standard perl locations. It will also install a copy of the zm.conf file (generated by configure) to your system configuration area (e.g. /usr/local/etc). Finally it tries to link zm.php to index.php but will not overwrite an existing file if it already exists.

The 'zm' script does not get installed automatically as it is not necessary for the operation of the ZoneMinder setup per se and is not necessarily likely to work correctly for distributions other than those from the RedHat or Fedora families. However if you want to ensure that ZoneMinder is started on reboot etc copy it to your init.d directory, usually something like /etc/rc.d/init.d or /etc/inid.d and then add it by doing

chkconfig --add zm

or similar command for your distribution. ZoneMinder will then start up when your machine reboots and can be controlled (by the root user) by doing 'service zm start' or 'service zm stop' etc. You may need to use the ‘—levels’ parameter to chkconfig to ensure that ZoneMinder is started when you need it to.

If you do this you should find that you have files named S99zm in some of the /etc/rcX.d directories and K99zm in some of the others. The S99zm files are used for starting up ZoneMinder on system boot and the K99zm ones are used to close it on system shutdown. The 99 part is a priority, which may run from 0 to 99 and indicates where in the startup and shutdown sequences that ZoneMinder should start or stop. So S99zm means that ZoneMinder should be one of the last things to startup, which is good as it needs things like the database to be running first.

By the same token, the K00zm scripts indicate that ZoneMinder should be one of the first things to shut down. This prevents any nasty messages on your console about the database having gone away first and also will give ZoneMinder chance to shutdown in a controlled manner without introducing any corruption into the database or filesystem.

As mentioned above, this script is for Redhat, and related, distributions only. I would be grateful for any similar scripts for other distributions so if you know of one, or create one, then please send it to me.

If you are running a distribution which doesn’t support the zm script, or if you just prefer more direct control, you can now start ZoneMinder by typing

zmpkg.pl start

which, after a few seconds, should return without error. You can subsequently stop and restart everything by changing the ‘start’ parameter to ‘stop’ or ‘restart’.

Now fire up your web browser, point it at your zm.php and off you go.

Note, if you ever need to uninstall ZoneMinder you can do this by simply typing

make uninstall

though as with installation you may need to change user to have sufficient privileges. This will remove all installed files, however you will need to manually remove any databases you have created.

===Installation from RPM===
Please navigate to the [https://github.com/ZoneMinder/ZoneMinder ZoneMinder github site] and review the Readme (scroll down) for the most current installation documentation.

The following is outdated, but may still be useful.

Installing from RPM is distribution specific so make sure you download the correct RPM for the distribution that you are using.

All documents including this README are installed to the systems default document folder.

Fedora: ''/usr/share/doc/zoneminder-{version number}''

Mandrake:

The packaged version of Zone Minder installs all binarys to /usr/lib/zm including the web pages. So don’t worry when you do not see any files installed to the root directory for your web server. The web pages for Apache are aliased by zoneminder.conf in the apache/conf.d directory which vary depending on your distribution:

Fedora: /etc/httpd/conf.d/zoneminder.conf''

Mandrake:

The Configuration file for setting up the database is located at /etc/zm.conf and will need to be edited to add the user and password that you want Zone Minder to use. After you have installed the Zone Minder package this will be the first thing you want to do. So use your favourite editor and add in the user name and password you want Zone Minder to use. You can also change the database name if you would like.

vi /etc/zm.conf

Start the mysqld service so you can build the database

service mysqld start

Then run zminit to create the database (see discussion page if the command is not found)

/usr/lib/zm/bin/zminit

The user and password that zminit asks for are for the database only. For the user enter root and leave the password blank (unless of course you changed the password). You should see some information showing that it has created the database and no errors.

Set the run levels for the services that Zone Minder requires. I like to set the run levels to 3 and 5 with the following command:

chkconfig –levels 35 mysqld on
chkconfig –levels 35 httpd on

Now start the web server and Zone Minder:

service httpd start
service zm start ; for source code distribtuions
service zoneminder start ; for debian

You should now be able to access the Zone Minder console through the web browser http://localhost/zm

Log files will be located in /var/log/zm

Events are located at /var/lib/zm

===Installation from a .deb===
Please navigate to the [https://github.com/ZoneMinder/ZoneMinder ZoneMinder github site] and review the Readme (scroll down) for the most current installation documentation.

The following is outdated, but may still be useful.

ZoneMinder is now in the Debian repositories. There are downloadable .deb files for Ubuntu for Edgy and Feisty. At this point it is in the repository for Gutsy. After you install, you will need to do some additional work, which is documented in the readme file included in the package. These steps have worked for several people as of the end of Summer 07.

Link Apache

sudo ln -s /etc/zm/apache.conf /etc/apache2/conf.d/zoneminder.conf

Restart Apache

sudo apache2ctl restart

suid zmfix

sudo chmod 4755 /usr/bin/zmfix

Run zmfix

zmfix -a

Fix export problem

sudo chown www-data.www-data /usr/share/zoneminder/temp

edit /etc/sysctl.conf and add the following lines (for 128meg shared mem)

kernel.shmmax = 134217728

Download cambozola.jar and put it in /usr/share/zoneminder
Enable in options->Images.

Set path to ffmpeg in options -> Images
/usr/bin/ffmpeg

test with '''xawtv''' (-nodga may be needed)

===Configuring SELinux Policy===
It has been a constant struggle to maintain an SELinux policy compatible with ZoneMinder. Generally, we recommend you disable SELinux, but if you wish to leave it enabled the most recent SELinux policy files can be found on the [https://github.com/ZoneMinder/ZoneMinder ZoneMinder github site] under the distros subfolder.

What follows is outdated information, which may be deleted if verified it is no longer useful.

To allow zoneminder access attributes on selinux enabled systems you have to create a new policy. Note, that ZoneMinder will run with no issues on a system where SELinux has been disabled.
First create a file named local_zoneminder.te (can be any name you want but if you use a name of a policy that already exists it will be overwritten).

module local_zoneminder 1.0;

require {
type httpd_t;
type initrc_var_run_t;
type initrc_t;
type v4l_device_t;
type file_t;
class unix_stream_socket { read connectto };
class file { read lock };
class shm { unix_read unix_write associate read write getattr };
class chr_file getattr;
}

#============= httpd_t ==============
allow httpd_t initrc_t:unix_stream_socket connectto;
allow httpd_t initrc_t:shm { unix_read unix_write associate read write getattr };
allow httpd_t initrc_var_run_t:file { read lock };
allow httpd_t v4l_device_t:chr_file getattr;

Next execute the following commands to create and load the policy module:

checkmodule -M -m -o local_zoneminder.mod local_zoneminder.te
semodule_package -o local_zoneminder.pp -m local_zoneminder.mod
semodule -i local_zoneminder.pp

*NOTE: this policy module actually gives the httpd user in general permission to do more actions; this is still better than disabling selinux though.

==Upgrading==
===Upgrading from Source===
If you are upgrading from a previous version of ZoneMinder you should follow the Building instructions above. Before proceeding, ensure that any previous version of ZoneMinder has been stopped, then type

make install

to install the binaries, scripts, modules, web and configuration files.

The next step in an upgrade is to run the zmupdate.pl script to make any changes to the database or file system required by the new version. Ordinarily you can run this from your ZoneMinder build directory by doing

zmupdate.pl --version=<from version> [--user=<database user> --pass=<database password>]

where ‘from version’ relates to the version of ZM you are upgrading from, 1.21.1 for example, and not the version you are upgrading to. All updates from that version onwards will be applied; however zmupdate.pl will only work with upgrades from 1.19.0 onwards. The ‘user’ and ‘pass’ options allow you to specify a database user and password with sufficient privilege to ‘alter’ the structure of the database. This is not necessarily the database user you use for ZoneMinder.

The update script will offer you the chance to make a database backup before making any changes. You can use this to restore your database if the upgrade fails or if you simply wish to roll back in the future. Be aware that if you have a lot of entries in your database and/or limited disk space doing a backup may not be feasible or even work. Also the backup only applies to the database and will not save any images or other event detail saved on disk. If successful the backup will be saved in the current directory and will be named <database name>-<from version>.dump. Any previous backups of the same name will be overwritten without warning. The backup file is in the form of a simple sql script and can be used to restore the database simply by typing

mysql < zm-1.21.4.dump

for example.

After having done any backup, the database upgrade will be applied. Check that this is successful before continuing.

Once the upgrade process is complete, you can then restart ZoneMinder using the zmpkg.pl script or using the service control commands for your distribution. You should check /var/log/messages and the other ZoneMinder logs for the first few minutes to ensure that everything comes back up successfully.

==Tutorial==
Once configured, the ZoneMinder console appears through a web browser at [http://localhost/zm/ http://localhost/zm/]

Along the top there are several informational entries like the time of the last update and the current server load. There will also be an indication of the system state which will probably say ‘stopped’ to begin with. This is a link that you can click on to control the ZoneMinder system as a whole.

Below that are various other links including one detailing the current user (in authenticated mode only) and one allowing you to configure your bandwidth. This last one enables you to optimize your settings depending on where you are, the actual values relating to this are defined in the options. If you are using a browser on the same machine or network then choose high, over a cable or DSL link maybe choose medium and over a dialup choose low. You can experiment to see which is best. This setting is retained on a per machine basis with a persistent cookie. Also on this line are a number of other links that will be covered below.

Please bear in mind that from here on the descriptions of the web pages are based on what you will see if you are running as a fully authenticated user. If you are running in un-authenticated mode or as a less privileged user then some elements may not be shown or will be disabled. Authentication is an option that lets you specify whether anyone that goes to the ZoneMinder web pages must log themselves in, in order to be given permissions to perform certain tasks. Running in authenticated mode is recommended if your system is open to the internet at all. During installation a fully privileged user ‘admin’ has been created with a password also of ‘admin’. If you are using authentication you should change this password as soon as possible. Authenticated mode is enabled by checking the box "OPT_USE_AUTH" in the "System" tab of the [http://www.zoneminder.com/wiki/index.php/Main_Documentation#Options_and_Users Options and Users] area.

===Check that your Camera Works!===

To help you get started on the video configuration the best thing is to check your camera with a tool like '''gucview''' '''cheese''' or '''xawtv''' (http://bytesex.org/xawtv/). Please note that just because you can see a video stream in these tools does not necessarily guarantee that your camera will work with ZoneMinder. This is because most tools just ‘map’ the video image through onto screen memory transparently without intercepting it, whereas ZoneMinder needs to capture the image and, usually, inspect it. This is called frame grabbing and to check it you should use the facility in xawtv, or other tool, to capture either one or more still images or possibly a movie. If this works and the images or movie are not garbage then the chances are that ZoneMinder will work fine also.

Once you have validated your camera run '''zmu -d <device_path> -q -v''' to get a dump of the settings (note, you will have to additionally supply a username and password to zmu if you are running in authenticated mode). You can then enter these values into the video related options of the monitor configuration panel. The '<device_path>' referred to here is the path to your video device file, for instance /dev/video0 etc. If 'zmu' gives you an error related to permissions run '''zmfix -a''' to make sure you can access all the video devices.

===Start ZoneMinder===

Zoneminder requires a web server and a background task:

service httpd start
service zoneminder start

Zoneminder captures video from the web server process (e.g. www-data or apache2), so that process must have access to any files or resources necessary.

===Defining Monitors===

To use ZoneMinder properly you need to define at least one Monitor. Essentially, a monitor is associated with a camera and can continually check it for motion detection and such like. So, next click 'Add New Monitor' to bring up the dialog. You will see a bunch of things you have to fill in.

[[Image:ZM_MPEG4_A211A_5.png]]

There are a small number of camera setups that ZoneMinder knows about and which can be accessed by clicking on the ‘Presets’ link. Selecting one of the presets will fill in the monitor configuration with appropriate values but you will still need to enter others and confirm the preset settings.

The options are divided into a set of tabs to make it easier to edit. You do not have to ‘save’ to change to different tab so you can make all the changes you require and then click ‘Save’ at the end. The individual options are explained in a little more detail below,

====Monitor Tab====

; Name : The name for your monitor. This should be made up of alphanumeric characters (a-z,A-Z,0-9) and hyphen (-) and underscore(_) only. Whitespace is not allowed.

; Source Type : This determines whether the camera is a local one attached to a physical video or USB port on your machine, a remote network camera or an image source that is represented by a file (for instance periodically downloaded from a alternate location). Choosing one or the other affects which set of options are shown in the Source tab.

; Function : This essentially defines what the monitor is doing. This can be one of the following;

:* None – The monitor is currently disabled. No streams can be viewed or events generated. Nothing is recorded.
:* Monitor – The monitor is only available for live streaming. No image analysis is done so no alarms or events will be generated, and nothing will be recorded.
:* Modect – or MOtion DEteCTtion. All captured images will be analysed and events generated with recorded video where motion is detected.
:* Record – The monitor will be continuously recorded. Events of a fixed-length will be generated regardless of motion, analogous to a conventional time-lapse video recorder. No motion detection takes place in this mode.
:* Mocord – The monitor will be continuously recorded, with any motion being highlighted within those events.
:* Nodect – or No DEteCTtion. This is a special mode designed to be used with external triggers. In Nodect no motion detection takes place but events are recorded if external triggers require it.

:Generally speaking it is best to choose ‘Monitor’ as an initial setting here.

; Enabled : The enabled field indicates whether the monitor should be started in an active mode or in a more passive state. You will nearly always want to check this box, the only exceptions being when you want the camera to be enabled or disabled by external triggers or scripts. If not enabled then the monitor will not create any events in response to motion or any other triggers.

; Linked Monitors : This field allows you to select other monitors on your system that act as triggers for this monitor. So if you have a camera covering one aspect of your property you can force all cameras to record while that camera detects motion or other events. You can either directly enter a comma separated list of monitor ids or click on ‘Select’ to choose a selection. Be very careful not to create circular dependencies with this feature however you will have infinitely persisting alarms which is almost certainly not what you want! To unlink monitors you can ctrl-click.

;Maximum FPS : On some occasions you may have one or more cameras capable of high capture rates but find that you generally do not require this performance at all times and would prefer to lighten the load on your server. This option permits you to limit the maximum capture rate to a specified value. This may allow you to have more cameras supported on your system by reducing the CPU load or to allocate video bandwidth unevenly between cameras sharing the same video device. This value is only a rough guide and the lower the value you set the less close the actual FPS may approach it especially on shared devices where it can be difficult to synchronise two or more different capture rates precisely. This option controls the maximum FPS in the circumstance where no alarm is occurring only. (Note for IP cameras: ZoneMinder has no way to set or limit the ''mjpeg'' stream the camera passes, some cams you can set this through the url string, others do not. So if you're using ''mjpeg'' feeds you must NOT throttle here at the server end, only the cam end. If you want to use this feature, the server to throttle, then you MUST use ''jpeg'' instead of ''mjpeg'' method to get picture from the camera)

; Alarm Maximum FPS : If you have specified a Maximum FPS it may be that you don’t want this limitation to apply when your monitor is recording motion or other event. This setting allows you to override the Maximum FPS value if this circumstance occurs. As with the Maximum FPS setting leaving this blank implies no limit so if you have set a maximum fps in the previous option then when an alarm occurs this limit would be ignored and ZoneMinder would capture as fast as possible for the duration of the alarm, returning to the limited value after the alarm has concluded. Equally you could set this to the same, or higher (or even lower) value than Maximum FPS for more precise control over the capture rate in the event of an alarm.

; Reference Image Blend %ge : Each analysed image in ZoneMinder is a composite of previous images and is formed by applying the current image as a certain percentage of the previous reference image. Thus, if we entered the value of 10 here, each image’s part in the reference image will diminish by a factor of 0.9 each time round. So a typical reference image will be 10% the previous image, 9% the one before that and then 8.1%, 7.2%, 6.5% and so on of the rest of the way. An image will effectively vanish around 25 images later than when it was added. This blend value is what is specified here and if higher will make slower progressing events less detectable as the reference image would change more quickly. Similarly events will be deemed to be over much sooner as the reference image adapts to the new images more quickly. In signal processing terms the higher this value the steeper the event attack and decay of the signal. It depends on your particular requirements what the appropriate value would be for you but start with 10 here and adjust it (usually down) later if necessary.

; Triggers : This small section lets you select which triggers will apply if the run mode has been set to ‘triggered’ above. The most common trigger is X10 and this will appear here if you indicated that your system supported it during installation. Only X10 is supported as a shipped trigger with ZoneMinder at present but it is possible that other triggers will become available as necessary. You can also just use ‘cron’ jobs or other mechanisms to actually control the camera and keep them completely outside of the ZoneMinder settings. The zmtrigger.pl script is also available to implement custom external triggering.

====Source Tab (local device)====

; Device Path/Channel : Enter the full path to the device file that your camera is attached to, e.g. /dev/video0. Some video devices, e.g. BTTV cards support multiple cameras on one device so in this case enter the channel number in the Channel box or leave it at zero if you're using a USB camera or one with just one channel. Look in [http://www.zoneminder.com/wiki/index.php/Supported_hardware Supported Hardware] section, how to see if your capture card or USB webcam is supported or not, and what extra settings you may have to do, to make it work.
; Device Format : Enter the video format of the video stream. This is defined in various system files (e.g. /usr/include/linux/videodev.h) but the two most common are 0 for PAL and 1 for NTSC.
; Capture Palette : Finally for the video part of the configuration enter the colour depth. ZoneMinder supports a handful of the most common palettes, so choose one here. If in doubt try grey first, and then 24 bit colour. If neither of these work very well then YUV420P or one of the others probably will. There is a slight performance penalty when using palettes other than grey or 24 bit colour as an internal conversion is involved. These other formats are intended to be supported natively in a future version but for now if you have the choice choose one of grey or 24 bit colour.
; Capture Width/Height : The dimensions of the video stream your camera will supply. If your camera supports several just enter the one you'll want to use for this application, you can always change it later. However I would recommend starting with no larger than 320x240 or 384x288 and then perhaps increasing and seeing how performance is affected. This size should be adequate in most cases. Some cameras are quite choosy about the sizes you can use here so unusual sizes such as 197x333 should be avoided initially.
; Keep aspect ratio: When typing in the dimensions of monitors you can click this checkbox to ensure that the width stays in the correct ratio to the height, or vice versa. It allows height to be calculated automatically from width (or vice versa) according to preset aspect ratio. This is preset to 4:3 but can be amended globally via the Options->Config->ZM_DEFAULT_ASPECT_RATIO setting. Aside from 4:3 which is the usual for network and analog cameras another common setting is 11:9 for CIF (352x288) based sources.
; Orientation : If your camera is mounted upside down or at right angles you can use this field to specify a rotation that is applied to the image as it is captured. This incurs an additional processing overhead so if possible it is better to mount your camera the right way round if you can. If you choose one of the rotation options remember to switch the height and width fields so that they apply, e.g. if your camera captures at 352x288 and you choose ‘Rotate Right’ here then set the height to be 352 and width to be 288. You can also choose to ‘flip’ the image if your camera provides mirrored input.

====Source Tab (remote device)====

; Remote Host/Port/Path : Use these fields to enter the full URL of the camera. Basically if your camera is at <nowiki>http://camserver.home.net:8192/cameras/camera1.jpg</nowiki> then these fields will be ''camserver.home.net'', ''8192'' and ''/cameras/camera1.jpg'' respectively. Leave the port at 80 if there is no special port required. If you require authentication to access your camera then add this onto the host name in the form <username>:<password>@<hostname>.com. This will usually be 24 bit colour even if the image looks black and white. Look in [http://www.zoneminder.com/wiki/index.php/Supported_hardware Supported Hardware] > Network Cameras section, how to obtain these strings that may apply to your camera.
; Remote Image Colours : Specify the amount of colours in the captured image. Unlike with local cameras changing this has no controlling effect on the remote camera itself so ensure that your camera is actually capturing to this palette beforehand.
; Capture Width/Height : Make sure you enter here the same values as they are in the remote camera's internal setting.
; Keep aspect ratio: As per local devices.
; Orientation : As per local devices.

For an example to setup a MPEG-4 camera see:
[[How_to_Setup_an_Axis211A_with_MPEG-4_streaming]]

====Source Tab (ffmpeg)====

; Source Path : Use this field to enter the full URL of the stream or file. Look in [http://www.zoneminder.com/wiki/index.php/Supported_hardware Supported Hardware] > Network Cameras section, how to obtain these strings that may apply to your camera. RTSP streams may be specified here.
; Source Colours : Specify the amount of colours in the captured image. Unlike with local cameras changing this has no controlling effect on the remote camera itself so ensure that your camera is actually capturing to this palette beforehand.
; Capture Width/Height : Make sure you enter here the same values as they are in the remote camera's internal setting.
; Keep aspect ratio: As per local devices.
; Orientation : As per local devices.

====Source Tab (file device)====

; File Path : Enter the full path to the file to be used as the image source.
; File Colours : Specify the amount of colours in the image. Usually 24 bit colour.
; Capture Width/Height: As per local devices.
; Keep aspect ratio: As per local devices.
; Orientation : As per local devices.

====Timestamp Tab====

; Timestamp Label Format : This relates to the timestamp that is applied to each frame. It is a ‘strftime’ style string with a few extra tokens. You can add %f to add the decimal hundredths of a second to the frame timestamp, so %H:%M:%S.%f will output time like 10:45:37.45. You can also use %N for the name of the monitor and %Qwhich will be filled by any of the ‘show text’ detailed in the zmtriggers.pl section.
; Timestamp Label X/Y : The X and Y values determine where to put the timestamp. A value of 0 for the X value will put it on the left side of the image and a Y value of 0 will place it at the top of the image. To place the timestamp at the bottom of the image use a value eight less than the image height.

====Buffers Tab====

; Image Buffer Size : This option determines how many frames are held in the ring buffer at any one time. The ring buffer is the storage space where the last ‘n’ images are kept, ready to be resurrected on an alarm or just kept waiting to be analysed. It can be any value you like with a couple of provisos, (see next options). However it is stored in shared memory and making it too large especially for large images with a high colour depth can use a lot of memory. A value of no more than 50 is usually ok. If you find that your system will not let you use the value you want it is probably because your system has an arbitrary limit on the size of shared memory that may be used even though you may have plenty of free memory available. This limit is usually fairly easy to change, see the Troubleshooting section for details.
; Warm-up Frames : This specifies how many frames the analysis daemon should process but not examine when it starts. This allows it to generate an accurate reference image from a series of images before looking too carefully for any changes. I use a value of 25 here, too high and it will take a long time to start, too low and you will get false alarms when the analysis daemon starts up.
; Pre/Post Event Image Buffer : These options determine how many frames from before and after an event should be preserved with it. This allows you to view what happened immediately prior and subsequent to the event. A value of 10 for both of these will get you started but if you get a lot of short events and would prefer them to run together to form fewer longer ones then increase the Post Event buffer size. The pre-event buffer is a true buffer and should not really exceed half the ring buffer size. However the post-event buffer is just a count that is applied to captured frames and so can be managed more flexibly. You should also bear in mind the frame rate of the camera when choosing these values. For instance a network camera capturing at 1FPS will give you 10 seconds before and after each event if you chose 10 here. This may well be too much and pad out events more than necessary. However a fast video card may capture at 25FPS and you will want to ensure that this setting enables you to view a reasonable time frame pre and post event.
; Stream Replay Image Buffer: This option ...
; Alarm Frame Count : This option allows you to specify how many consecutive alarm frames must occur before an alarm event is generated. The usual, and default, value is 1 which implies that any alarm frame will cause or participate in an event. You can enter any value up to 16 here to eliminate bogus events caused perhaps by screen flickers or other transients. Values over 3 or 4 are unlikely to be useful however. Please note that if you have statistics recording enabled then currently statistics are not recorded for the first ‘Alarm Frame Count’-1 frames of an event. So if you set this value to 5 then the first 4 frames will be missing statistics whereas the more usual value of 1 will ensure that all alarm frames have statistics recorded.

====Control Tab====

Note: This tab and its options will only appear if you have selected the ZM_OPT_CONTROL option to indicate that your system contains cameras which are able to be controlled via Pan/Tilt/Zoom or other mechanisms. See the Camera Control section elsewhere in this document for further details on camera control protocols and methods.

; Controllable : Check this box to indicate your camera can be controlled.
; Control Type : Select the control type that is appropriate for your camera. ZoneMinder ships with a small number of predefined control protocols which will works with some cameras without modification but which may have to amended to function with others, Choose the edit link to create new control types or to edit the existing ones.
; Control Device : This is the device that is used to control your camera. This will normally be a serial or similar port. If your camera is a network camera, you will generally not need to specify a control device.
; Control Address : This is the address of your camera. Some control protocols require that each camera is identified by a particular, usually numeric, id. If your camera uses addressing then enter the id of your camera here. If your camera is a network camera then you will usually need to enter the hostname or IP address of it here. This is ordinarily the same as that given for the camera itself.
; Auto Stop Timeout : Some cameras only support a continuous mode of movement. For instance you tell the camera to pan right and then when it is aligned correctly you tell it to stop. In some cases it is difficult to time this precisely over a web interface so this option allows you to specify an automatic timeout where the command will be automatically stopped. So a value of 0.25 here can tell the script to stop moving a quarter of a second after starting. This allows a more precise method of fine control. If this value is left blank or at zero it will be ignored, if set then it will be used as the timeout however it will only be applied for the lower 25% of possible speed ranges. In other words if your camera has a pan speed range of 1 to 100 then selecting to move at 26 or over will be assumed to imply that you want a larger movement that you can control yourself and no timeout will be applied. Selecting motion at lower speeds will be interpreted as requiring finer control and the automatic timeout will be invoked.
; Track Motion : This and the following four options are used with the experimental motion function. This will only work if your camera supports mapped movement modes where a point on an image can be mapped to a control command. This is generally most common on network cameras but can be replicated to some degree on other cameras that support relative movement modes. See the Camera Control section for more details. Check this box to enable motion tracking.
; Track Delay : This is the number of seconds to suspend motion detection for following any movement that the camera may make to track motion.
; Return Location : If you camera supports a ‘home’ position or presets you can choose which preset the camera should return to after tracking motion.
; Return Delay : This is the delay, in seconds, once motion has stopped being detected, before the camera returns to any defined return location.

====X10 Tab====

Note: This tab and its options will only appear if you have indicated that your system supports the X10 home automation protocol during initial system configuration.

; X10 Activation String : The contents of this field determine when a monitor starts and/or stops being active when running in ‘Triggered; mode and with X10 triggers. The format of this string is as follows,

:* n : If you simply enter a number then the monitor will be activated when an X10 ON signal for that unit code is detected and will be deactivated when an OFF signal is detected.
:* !n : This inverts the previous mode, e.g. !5 means that the monitor is activated when an OFF signal for unit code 5 is detected and deactivated by an ON.
:* n+ : Entering a unit code followed by + means that the monitor is activated on receipt of a ON signal for that unit code but will ignore the OFF signal and as such will not be deactivated by this instruction. If you prepend a '!' as per the previous definition it similarly inverts the mode, i.e. the ON signal deactivates the monitor.
:* n+<seconds> : As per the previous mode except that the monitor will deactivate itself after the given number of seconds.
:* n- : Entering a unit code followed by - means that the monitor is deactivated on receipt of a OFF signal for that unit code but will ignore the ON signal and as such will not be activated by this instruction. If you prepend a '!' as per the previous definition it similarly inverts the mode, i.e. the OFF signal activates the monitor.
:* n-<seconds> : As per the previous mode except that the monitor will activate itself after the given number of seconds.

: You can also combine several of these expressions to by separating them with a comma to create multiple circumstances of activation. However for now leave this blank.

; X10 Input Alarm String : This has the same format as the previous field but instead of activating the monitor with will cause a forced alarm to be generated and an event recorded if the monitor is Active. The same definition as above applies except that for activated read alarmed and for deactivated read unalarmed(!). Again leave this blank for now.
; X10 Output Alarm String : This X10 string also has the same format as the two above options. However it works in a slightly different way. Instead of ZoneMinder reacting to X10 events this option controls how ZoneMinder emits X10 signals when the current monitor goes into or comes out of the alarm state. Thus just entering a number will cause the ON signal for that unit code to be sent when going into alarm state and the OFF signal when coming out of alarm state. Similarly 7+30 will send the unit code 7 ON signal when going into alarm state and the OFF signal 30 seconds later regardless of state. The combination of the X10 instruction allows ZoneMinder to react intelligently to, and also assume control of, other devices when necessary. However the indiscriminate use of the Input Alarm and Output Alarm signals can cause some horrendous race conditions such as a light going on in response to an alarm which then causes an alarm itself and so on. Thus some circumspection is required here. Leave this blank for now anyway.

====Misc Tab====

; Event Prefix : By default events are named ‘Event-<event id>’, however you are free to rename them individually as you wish. This option lets you modify the event prefix, the ‘Event-‘ part, to be a value of your choice so that events are named differently as they are generated. This allows you to name events according to which monitor generated them.
; Section Length : This specifies the length (in seconds) of any fixed length events produced when the monitor function is ‘Record’ or ‘Mocord’. Otherwise it is ignored. This should not be so long that events are difficult to navigate nor so short that too many events are generated. A length of between 300 and 900 seconds I recommended.
; Frame Skip : This setting also applies only to the ‘Record’ or ‘Mocord’ functions and specifies how many frames should be skipped in the recorded events. The default setting of zero results in every captured frame being saved. Using a value of one would mean that one frame is skipped between each saved, two means that two frames are skipped between each saved frame etc. An alternate way of thinking is that one in every ‘Frame Skip + 1’ frames is saved. The point of this is to ensure that saved events do not take up too much space unnecessarily whilst still allowing the camera to capture at a fairly high frame rate. The alternate approach is to limit the capture frame rate which will obviously affect the rate at which frames are saved.
; FPS Report Interval : How often the current performance in terms of Frames Per Second is output to the system log. Not used in any functional way so set it to maybe 1000 for now. If you watch /var/log/messages (normally) you will see this value being emitted at the frequency you specify both for video capture and processing.
; Default Scale : If your monitor has been defined with a particularly large or small image size then you can choose a default scale here with which to view the monitor so it is easier or more visible from the web interface.
; Web Colour : Some elements of ZoneMinder now use colours to identify monitors on certain views. You can select which colour is used for each monitor here. Any specification that is valid for HTML colours is valid here, e.g. ‘red’ or ‘#ff0000’. A small swatch next to the input box displays the colour you have chosen.

Finally, click 'Save' to add your monitor.

On the main console listing you will now see your monitor and some of its vital statistics. Most columns are also links and you get to other functions of ZoneMinder by choosing the appropriate one. Describing them left to right, they are as follows.

The first column is the Id, clicking on this gives you the opportunity to edit any of the settings you have just defined your monitor to have.

The next column is the Name column, clicking on this will give you the watch window where you can view a live feed from your camera along with recent events. This is described more fully below.

Following that are the Function and Source columns, which may be represented in various colours. Initially both will be showing red. This means that that monitor is not configured for any function and as a consequence has no zmc (capture) daemon running on it. If it were orange it would mean that a zmc daemon was running but no zma (analysis) daemon and green means both are running. In our case it is red because we defined the Monitor to have a Function of None so no daemons are required.

To get the daemons up and running you can either click on the source listed in the Source column and edit the monitor properties or click on the Function listed and change it to ’Monitor’, which will ensure that one or more appropriate daemons are started automatically. You need to ensure that you have started ZoneMinder before any of these settings actually has any effect.

Having a device status of red or orange does not necessarily constitute an error if you have deliberately disabled a monitor or have just put it into Passive mode.

If you have several cameras (and thus monitors) on a device the device status colour reflects all of them for the capture daemon. So if just one monitor is active then the daemon is active for both even if all the other monitors are switched off.

Once you have changed the function of your monitor, the main console window will be updated to reflect this change. If your device status does not go green then check your system and web server logs to see if it's something obvious.

You can now add further monitors if you have cameras set up to support them. Once you have one or more monitors you may notice the '<n> Monitors' title becomes a link. Clicking on this link will open up a window which allows you to assign your monitors to groups. These let you select certain monitors to view. For instance you may only wish to view outdoor monitors while indoors. You can also choose to view all of them. If you choose a group then your selection will be remembered via a cookie and will be used until you change it. You can call your groups anything you like, though ‘Mobile’ has a special meaning (see Mobile Devices below).

There may also be a ‘Cycle’ link which allows you to cycle through a shot from each of your monitors (in the selected group unless they are switched off) and get a streamed or still image from each in turn. Similarly if you see a link titled ‘Montage’ it will allow you view all your active enabled cameras (in the selected group) simultaneously. Be aware however that this can consume large amounts of bandwidth and CPU so should not be used continuously unless you have resource to burn.

===Defining Zones===
For a very brief step by step guide check out [[How_to_setup_motion_detection#Configure_motion_detection_areas|Configuring motion detection]] .

The next important thing to do with a new monitor is set up Zones for it to use. By default you'll already have one generated for you when you created your monitor but you might want to modify it or add others. Click on the Zones column for your monitor and you should see a small popup window appear which contains an image from your camera overlain with a stippled pattern representing your zone. In the default case this will cover the whole image. The colour of the zones appearing here is determined by what type they are. The default zone is Active and so will be red, Inclusive zones are orange, exclusive zones are purple, preclusive zones are blue and inactive zones are white.

Beneath the zones image will be a table containing a listing of your zones. Clicking on either the relevant bit of the image or on the Id or Name in the table will bring up another window where you can edit the particulars for your Zones. For more information on defining or editing a zone, see [[Defining_Zones|Defining Zones]].

===Viewing Monitors===
As this point you should have one or more Monitors running with one or more Zones each. Returning to the main Console window you will see your monitors listed once more. The columns not explored so far are the Monitor name, and various event totals for certain periods of time. Clicking on any of the event totals will bring up a variation on the same window but click on the Monitor name for now. If it is not a link then this means that that monitor is not running so ensure that you have started ZoneMinder and that your Monitor function is not set to ‘None’. If the link works, clicking on it will pop another window up which should be scaled to contain a heading, an image from your monitor, a status and a list of recent events if any have been generated.

Depending on whether you are able to view a streamed image or not the image frame will either be this stream or a series of stills. You have the option to change from one to the other (if available) at the centre of the top heading. Also along the top are a handful of other links. These let you change the scale of the image stream, modify image settings (for local devices) or close the window. If you have cameras that can be controlled, a ‘Control’ link should also be present which is described below.

The image should be self-explanatory but if it looks like garbage it is possible that the video configuration is wrong so look in your system error log and check for or report anything unusual. The centre of the window will have a tiny frame that just contains a status; this will be 'Idle', 'Alarm' or 'Alert' depending on the function of the Monitor and what's going on in the field of view. Idle means nothing is happening, Alarm means there is an alarm in progress and Alert means that an alarm has happened and the monitor is ‘cooling down’, if another alarm is generated in this time it will just become part of the same event. These indicators are colour coded in green, red and amber.

By default if you have minimised this window or opened other windows in front it will pop up to the front if it goes to Alarm state. This behaviour can be turned off in ‘options’ if required. You can also specify a sound file in the configuration, which will be played when an alarm occurs to alert you to the fact if you are not in front of your computer. This should be a short sound of only a couple of seconds ideally. Note that as the status is refreshed every few seconds it is possible for this not to alert you to every event that takes place, so you shouldn't rely on it for this purpose if you expect very brief events. Alternatively you can decrease the refresh interval for this window in the configuration though having too frequent refreshing may impact on performance.

Below the status is a list of recent events that have occurred, by default this is a listing of just the last 10 but clicking on 'All' will give you a full list and 'Archive' will take you to the event archive for this monitor, more on this later. Clicking on any of the column headings will sort the events appropriately.

From here you can also delete events if you wish. The events themselves are listed with the event id, and event name (which you can change), the time that the event occurred, the length of the event including any preamble and postamble frames, the number of frames comprising the event with the number that actually contain an alarm in brackets and finally a score. This column lists the average score per alarm frame as well as the maximum score that any alarm frame had.

The score is an arbitrary value that essentially represents the percentage of pixels in the zone that are in blobs divided by the square root of the number of blobs and then divided by the size of the zone. This gives a nominal maximum of 100 for a zone and the totals for each zone are added together, Active zones scores are added unchanged, Inclusive zones are halved first and Exclusive zones are doubled. In reality values are likely to be much less than 100 but it does give a simple indication of how major the event was.

===Controlling Monitors===
[[image: Axis_ptz_setting.png|right|thumb|caption| Settings for PTZ on an Axis213]]
For step by step instructions on setting up pan tilt zoom check out [[How_to_setup_an_axis_213_with_pan_tilt_zoom|Axis213 with pan tilt zoom]]

If you have defined your system as having controllable monitors and you are looking at a monitor that is configured for control, then clicking on the ‘Control’ link along the top of the window will change the short event listing area to a control area. The capabilities you have defined earlier determine exactly what is displayed in this window. Generally you will have a Pan/Tilt control area along with one or subsidiary areas such as zoom or focus control to the side. If you have preset support then these will be near the bottom of the window. The normal method of controlling the monitor is by clicking on the appropriate graphics which then send a command via the control script to the camera itself. This may sometimes take a noticeable delay before the camera responds.

It is usually the case that the control arrows are sensitive to where you click on them. If you have a camera that allows different speeds to be used for panning or zooming etc then clicking near the point of the arrow will invoke the faster speed whilst clicking near the base of the arrow will be slower. If you have defined continuous motion then ongoing activities can be stopped by clicking on the area between the arrows, which will either be a graphic in the case of pan/tilt controls or a word in the case of zoom and focus controls etc.

Certain control capabilities such as mapped motion allow direct control by clicking on the image itself when used in browsers which support streamed images directly. Used in this way you can just click on the area of the image that interests you and the camera will centre on that spot. You can also use direct image control for relative motion when the area of the image you click on defines the direction and the distance away from the centre of the image determines the speed. As it is not always very easy to estimate direction near the centre of the image, the active area does not start until a short distance away from the centre, resulting in a ‘dead’ zone in the middle of the image.

===Filtering Events===
For a very brief howto guide on this topic check out [[How_to_export_download_and_view_events#Event_Filter| Event Filter]].

The other columns on the main console window contain various event totals for your monitors over the last hour, day, week and month as well as a grand total and a total for events that you may have archived for safekeeping. Clicking on one of these totals or on the 'All' or 'Archive' links from the monitor window described above will present you with a new display. This is the full event window and contains a list of events selected according to a filter which will also pop up in its own window. Thus if you clicked on a 'day' total the filter will indicate that this is the period for which events are being filtered. The event listing window contains a similar listing to the recent events in the monitor window. The primary differences are that the frames and alarm frames and the score and maximum score are now broken out into their own columns, all of which can be sorted by clicking on the heading. Also this window will not refresh automatically, rather only on request. Other than that, you can choose to view events here or delete them as before.

The other window that appeared is a filter window. You can use this window to create your own filters or to modify existing ones. You can even save your favourite filters to re-use at a future date. Filtering itself is fairly simple; you first choose how many expressions you'd like your filter to contain. Changing this value will cause the window to redraw with a corresponding row for each expression. You then select what you want to filter on and how the expressions relate by choosing whether they are 'and' or 'or' relationships. For filters comprised of many expressions you will also get the option to bracket parts of the filter to ensure you can express it as desired. Then if you like choose how you want your results sorted and whether you want to limit the amount of events displayed.

There are several different elements to an event that you can filter on, some of which require further explanation. These are as follows, 'Date/Time' which must evaluate to a date and a time together, 'Date' and 'Time' which are variants which may only contain the relevant subsets of this, 'Weekday' which as expected is a day of the week.

All of the preceding elements take a very flexible free format of dates and time based on the PHP strtotime function (http://www.php.net/manual/en/function.strtotime.php). This allows values such as 'last Wednesday' etc to be entered. I recommend acquainting yourself with this function to see what the allowed formats are. However automated filters are run in perl and so are parsed by the Date::Manip package. Not all date formats are available in both so if you are saved your filter to do automatic deletions or other tasks you should make sure that the date and time format you use is compatible with both methods. The safest type of format to use is ‘-3 day’ or similar with easily parseable numbers and units are in English.

The other things you can filter on are all fairly self explanatory, except perhaps for 'Archived' which you can use to include or exclude Archived events. In general you'll probably do most filtering on un-archived events. There are also two elements, Disk Blocks and Disk Percent which don’t directly relate to the events themselves but to the disk partition on which the events are stored. These allow you to specify an amount of disk usage either in blocks or in percentage as returned by the ‘df’ command. They relate to the amount of disk space used and not the amount left free. Once your filter is specified, clicking 'submit' will filter the events according to your specification. As the disk based elements are not event related directly if you create a filter and include the term ‘DiskPercent > 95’ then if your current disk usage is over that amount when you submit the filter then all events will be listed whereas if it is less then none at all will. As such the disk related terms will tend to be used mostly for automatic filters (see below). If you have created a filter you want to keep, you can name it and save it by clicking 'Save'.

If you do this then the subsequent dialog will also allow you specify whether you want this filter automatically applied in order to delete events or upload events via ftp to another server and mail notifications of events to one or more email accounts. Emails and messages (essentially small emails intended for mobile phones or pagers) have a format defined in the Options screen, and may include a variety of tokens that can be substituted for various details of the event that caused them. This includes links to the event view or the filter as well as the option of attaching images or videos to the email itself. Be aware that tokens that represent links may require you to log in to access the actual page, and sometimes may function differently when viewed outside of the general ZoneMinder context. The tokens you can use are as follows.

: %EI% Id of the event
: %EN% Name of the event
: %EC% Cause of the event
: %ED% Event description
: %ET% Time of the event
: %EL% Length of the event
: %EF% Number of frames in the event
: %EFA% Number of alarm frames in the event
: %EST% Total score of the event
: %ESA% Average score of the event
: %ESM% Maximum score of the event
: %EP% Path to the event
: %EPS% Path to the event stream
: %EPI% Path to the event images
: %EPI1% Path to the first alarmed event image
: %EPIM% Path to the (first) event image with the highest score
: %EI1% Attach first alarmed event image
: %EIM% Attach (first) event image with the highest score
: %EV% Attach event mpeg video
: %MN% Name of the monitor
: %MET% Total number of events for the monitor
: %MEH% Number of events for the monitor in the last hour
: %MED% Number of events for the monitor in the last day
: %MEW% Number of events for the monitor in the last week
: %MEM% Number of events for the monitor in the last month
: %MEA% Number of archived events for the monitor
: %MP% Path to the monitor window
: %MPS% Path to the monitor stream
: %MPI% Path to the monitor recent image
: %FN% Name of the current filter that matched
: %FP% Path to the current filter that matched
: %ZP% Path to your ZoneMinder console

Finally you can also specify a script which is run on each matched event. This script should be readable and executable by your web server user. It will get run once per event and the relative path to the directory containing the event in question. Normally this will be of the form <MonitorName>/<EventId> so from this path you can derive both the monitor name and event id and perform any action you wish. Note that arbitrary commands are not allowed to be specified in the filter, for security the only thing it may contain is the full path to an executable. What that contains is entirely up to you however.

Filtering is a powerful mechanism you can use to eliminate events that fit a certain pattern however in many cases modifying the zone settings will better address this. Where it really comes into its own is generally in applying time filters, so for instance events that happen during weekdays or at certain times of the day are highlighted, uploaded or deleted. Additionally using disk related terms in your filters means you can automatically create filters that delete the oldest events when your disk gets full. Be warned however that if you use this strategy then you should limit the returned results to the amount of events you want deleted in each pass until the disk usage is at an acceptable level. If you do not do this then the first pass when the disk usage is high will match, and then delete, all events unless you have used other criteria inside of limits. ZoneMinder ships with a sample filter already installed, though disabled. The PurgeWhenFull filter can be used to delete the oldest events when your disk starts filling up. To use it you should select and load it in the filter interface, modify it to your requirements, and then save it making you sure you check the ‘Delete all matches’ option. This will then run in the background and ensure that your disk does not fill up with events.

====Relative items in date strings====

Relative items adjust a date (or the current date if none) forward or backward. The effects of relative items accumulate. Here are some examples:

1 year
1 year ago
3 years
2 days

The unit of time displacement may be selected by the string ‘year’ or ‘month’ for moving by whole years or months. These are fuzzy units, as years and months are not all of equal duration. More precise units are ‘fortnight’ which is worth 14 days, ‘week’ worth 7 days, ‘day’ worth 24 hours, ‘hour’ worth 60 minutes, ‘minute’ or ‘min’ worth 60 seconds, and ‘second’ or ‘sec’ worth one second. An ‘s’ suffix on these units is accepted and ignored.

The unit of time may be preceded by a multiplier, given as an optionally signed number. Unsigned numbers are taken as positively signed. No number at all implies 1 for a multiplier. Following a relative item by the string ‘ago’ is equivalent to preceding the unit by a multiplier with value -1.

The string ‘tomorrow’ is worth one day in the future (equivalent to ‘day’), the string ‘yesterday’ is worth one day in the past (equivalent to ‘day ago’).

The strings ‘now’ or ‘today’ are relative items corresponding to zero-valued time displacement, these strings come from the fact a zero-valued time displacement represents the current time when not otherwise changed by previous items. They may be used to stress other items, like in ‘12:00 today’. The string ‘this’ also has the meaning of a zero-valued time displacement, but is preferred in date strings like ‘this thursday’.

When a relative item causes the resulting date to cross a boundary where the clocks were adjusted, typically for daylight saving time, the resulting date and time are adjusted accordingly.

The fuzz in units can cause problems with relative items. For example, ‘2003-07-31 -1 month’ might evaluate to 2003-07-01, because 2003-06-31 is an invalid date. To determine the previous month more reliably, you can ask for the month before the 15th of the current month. For example:

$ date -R
Thu, 31 Jul 2003 13:02:39 -0700
$ date --date='-1 month' +'Last month was %B?'
Last month was July?
$ date --date="$(date +%Y-%m-15) -1 month" +'Last month was %B!'
Last month was June!

As this applies to ZoneMinder filters, you might want to search for events in a period of time, or maybe for example create a purge filter that removes events older than 30 days.
For the later you would want at least two lines in your filter. The first line should be:

[<Archive Status> <equal to> <Unarchived Only>]

as you don't want to delete your archived events.

Your second line to find events older than 30 days would be:

[and <Date><less than> -30 days]

You use "less than" to indicate that you want to match events before the specified date, and you specify "-30 days" to indicate a date 30 days before the time the filter is run. Of course you could use 30 days ago as well(?).

You should always test your filters before enabling any actions based on them to make sure they consistently return the results you want. You can use the submit button to see what events are returned by your query.

===Viewing Events===
From the monitor or filtered events listing you can now click on an event to view it in more detail. If you have streaming capability you will see a series of images that make up the event. Under that you should also see a progress bar. Depending on your configuration this will either be static or will be filled in to indicate how far through the event you are. By default this functionality is turned off for low bandwidth settings as the image delivery tends to not be able to keep up with real-time and the progress bar cannot take this into account. Regardless of whether the progress bar updates, you can click on it to navigate to particular points in the events.

You will also see a link to allow you to view the still images themselves. If you don't have streaming then you will be taken directly to this page. The images themselves are thumbnail size and depending on the configuration and bandwidth you have chosen will either be the full images scaled in your browser of actual scaled images. If it is the latter, if you have low bandwidth for example, it may take a few seconds to generate the images. If thumbnail images are required to be generated, they will be kept and not re-generated in future. Once the images appear you can mouse over them to get the image sequence number and the image score.

You will notice for the first time that alarm images now contain an overlay outlining the blobs that represent the alarmed area. This outline is in the colour defined for that zone and lets you see what it was that caused the alarm. Clicking on one of the thumbnails will take you to a full size window where you can see the image in all its detail and scroll through the various images that make up the event. If you have the ZM_RECORD_EVENT_STATS option on, you will be able to click the 'Stats' link here and get some analysis of the cause of the event. Should you determine that you don't wish to keep the event, clicking on Delete will erase it from the database and file system. Returning to the event window, other options here are renaming the event to something more meaningful, refreshing the window to replay the event stream, deleting the event, switching between streamed and still versions of the event (if supported) and generating an MPEG video of the event (if supported).

These last two options require further explanation. Archiving an event means that it is kept to one side and not displayed in the normal event listings unless you specifically ask to view the archived events. This is useful for keeping events that you think may be important or just wish to protect. Once an event is archived it can be deleted or unarchived but you cannot accidentally delete it when viewing normal unarchived events.

The final option of generating an MPEG video is still somewhat experimental and its usefulness may vary. It uses the open source ffmpeg encoder to generate short videos, which will be downloaded to your browsing machine or viewed in place. When using the ffmpeg encoder, ZoneMinder will attempt to match the duration of the video with the duration of the event. Ffmpeg has a particularly rich set of options and you can specify during configuration which additional options you may wish to include to suit your preferences. In particular you may need to specify additional, or different, options if you are creating videos of events with particularly slow frame rates as some codecs only support certain ranges of frame rates. A common value for FFMPEG_OUTPUT_OPTIONS under Options > Images might be '-r 25 -b 800k' for 25 fps and 800 kbps. Details of these options can be found in the [http://ffmpeg.org/ffmpeg-doc.html documentation] for the encoders and is outside the scope of this document.

Building an MPEG video, especially for a large event, can take some time and should not be undertaken lightly as the effect on your host box of many CPU intensive encoders will not be good. However once a video has been created for an event it will be kept so subsequent viewing will not incur the generation overhead. Videos can also be included in notification emails, however care should be taken when using this option as for many frequent events the penalty in CPU and disk space can quickly mount up.

===Options and Users===
The final area covered by the tutorial is the options and user section. If you are running in authenticated mode and don’t have system privileges then you will not see this section at all and if you are running in un-authenticated mode then no user section will be displayed.

The various options you can specify are displayed in a tabbed dialog with each group of options displayed under a different heading. Each option is displayed with its name, a short description and the current value. You can also click on the ‘?’ link following each description to get a fuller explanation about each option. This is the same as you would get from zmconfig.pl. A number of option groups have a master option near the top which enables or disables the whole group so you should be aware of the state of this before modifying options and expecting them to make any difference.

If you have changed the value of an option you should then ‘save’ it. A number of the option groups will then prompt you to let you know that the option(s) you have changed will require a system restart. This is not done automatically in case you will be changing many values in the same session, however once you have made all of your changes you should restart ZoneMinder as soon as possible. The reason for this is that web and some scripts will pick up the new changes immediately but some of the daemons will still be using the old values and this can lead to data inconsistency or loss.

One of the options you may notice in the ‘System’ tab allows you to specify the default language for your installation of ZoneMinder. Versions 1.17.0 and later support multiple languages but rely on users to assist in creating language files for specific languages. To specify a language you will have to give the applicable code, thus for UK English this is en_gb, and for US English it would be en_us, if no language is given then UK English is assumed. Most languages will be specified in this nn_mm format and to check which languages are available look for files named zm_lang_*.php in the ZoneMinder build directory where the parts represented by the ‘*’ would be what you would enter as a language. This is slightly unwieldy and will probably be improved in future to make it easier to determine language availability. On checking which languages are available it may be that your preferred language is not currently included and if this is the case please consider doing a translation and sending it back to it may be included in future releases. All the language elements are given in the zm_lang_en_gb.php file along with a few notes to help you understand the format.

As mentioned above, you may also see a ‘users’ tab in the Options area. In this section you will see a list of the current users defined on the system. You can also add or delete users from here. It is recommended you do not delete the admin user unless you have created another fully privileged user to take over the same role. Each user is defined with a name and password (which is hidden) as well as an enabled setting which you can use to temporarily enable or disable users, for example a guest user for limited time access. As well as that there is a language setting that allows you to define user specific languages. Setting a language here that is different than the system language will mean that when that user logs in they will have the web interface presented in their own language rather than the system default, if it is available. Specifying a language here is done in the same way as for the system default language described above.

There are also five values that define the user permissions, these are ‘Stream’, ‘Events’, ‘Control’, ‘Monitors’ and ‘System’ Each can have values of ‘None’, ‘View’ or ‘Edit’ apart from ‘Stream’ which has no ‘Edit’ setting. These values cover access to the following areas; ‘Stream’ defines whether a user is allowed to view the ‘live’ video feeds coming from the cameras. You may wish to allow a user to view historical events only in which case this setting should be ‘none’. The ‘Events’ setting determines whether a user can view and modify or delete any retained historical events. The ‘Control’ setting allows you to indicate whether the user is able to control any Pan/Tilt/Zoom type cameras you may have on your system. The ‘Monitors’ setting specifies whether a user can see the current monitor settings and change them. Finally the ‘System’ setting determines whether a user can view or modify the system settings as a whole, such as options and users or controlling the running of the system as a whole.

As well as these settings there is also a ‘Bandwidth’ setting which can be used to limit the maximum bandwidth that a user can view at and a ‘Monitor Ids’ setting that can be used for non-’System’ users to restrict them to only being able to access streams, events or monitors for the given monitors ids as a comma separated list with no spaces. If a user with ‘Monitors’ edit privileges is limited to specific monitors here they will not be able to add or delete monitors but only change the details of those they have access to. If a user has ‘System’ privileges then the ‘Monitors Ids’ setting is ignored and has no effect.’

That’s pretty much is it for the tour, though there is a lot more to ZoneMinder as you will discover. You should experiment with the various settings to get the results you think are right for your requirements.

==Camera Control==

ZoneMinder provides the facility to control cameras from the web interface and to some extent automatically. Pan/Tilt/Zoom (PTZ) cameras have a wide range of capabilities and use a large number of different protocols making any kind of generic control solution potentially very difficult. To address this ZoneMinder uses two key approaches to get around this problem.

; Definition of Capabilities : For each camera model you use, an entry in the camera capabilities table must be created. These indicate what functions the camera supports and ensure that the interface presents only those capabilities that the camera supports. There are a very large number of capabilities that may be supported and it is very important that the entries in this table reflect the actual abilities of the camera. A small number of example capabilities are included in ZoneMinder, these can be used ‘as is’ or modified.

; Control Scripts : ZoneMinder itself does not generally provide the ability to send commands to cameras or receive responses. What it does is mediate motion requests from the web interface into a standard set of commands which are passed to a script defined in the control capability. Example scripts are provided in ZoneMinder which support a number of serial or network protocols but it is likely that for many cameras new scripts will have to be created. These can be modelled on the example ones, or if control commands already exist from other applications, then the script can just act as a ‘glue’ layer between ZoneMinder and those commands.

It should be emphasised that the control and capability elements of ZoneMinder are not intended to be able to support every camera out of the box. Some degree of development is likely to be required for many cameras. This should often be a relatively straightforward task however if you have a camera that you want to be supported then please feel free to get in touch and I should be able to provide an estimate for how much effort this is likely to be. It is also the case that I have only been able to access this limited number of cameras to test against; some other cameras may use different motion paradigms that don’t fit into the control capability/script architecture that ZoneMinder uses. If you come across any cameras like this then please forward as much information to me as possible so that I may be able to extend the ZoneMinder model to encompass them.

===Control Capabilities===

If you have a camera that supports PTZ controls and wish to use it with ZoneMinder then the first thing you need to do is ensure that it has an accurate entry in the capabilities table. To do this you need to go to the Control tab of the Monitor configuration dialog and select ‘Edit’ where it is listed by the Control Type selection box. This will bring up a new window which lists, with a brief summary, the existing capabilities. To edit an existing capability to modify select the Id or Name of the capability in question, or click on the Add button to add a new control capability. Either of these approaches will create a new window, in familiar style, with tabs along the top and forms fields below. In the case of the capabilities table there are a large number of settings and tabs, the mean and use of these are briefly explained below.

====Main Tab====
; Name : This is the name of the control capability, it will usually make sense to name capabilities after the camera model or protocol being used.
; Type : Whether the capability uses a local (usually serial) or network control protocol.
; Command : This is the full path to a script or application that will map the standard set of ZoneMinder control commands to equivalent control protocol command. This may be one of the shipped example zmcontrol-*.pl scripts or something else entirely.
; Can Wake : This is the first of the actual capability definitions. Checking this box indicates that a protocol command exists to wake up the camera from a sleeping state.
; Can Sleep : The camera can be put to sleep.
; Can Reset : The camera can be reset to a previously defined state.

====Move Tab====
; Can Move : The camera is able move, i.e. pan or tilt.
; Can Move Diagonally : The camera can move diagonally. Some devices can move only vertically or horizontally at a time.
; Can Move Mapped : The camera is able internally map a point on an image to a precise degree of motion to centre that point in the image.
; Can Move Absolute : The camera can move to an absolute location.
; Can Move Relative : The camera can more to a relative location, e.g. 7 point left or up.
; Can Move Continuous : The camera can move continuously in a defined direction until told to stop or the movement limits are reached, e.g. left.

====Pan Tab====
; Can Pan : The camera can pan, or move horizontally.
; Min/Max Pan Range : If the camera supports absolute motion this is the minimum and maximum pan co-ordinates that may be specified, e.g. -100 to 100.
; Min/Man Pan Step : If the camera supports relative motion, this is the minimum and maximum amount of movement that can be specified.
; Has Pan Speed : The camera supports specification of pan speeds.
; Min/Max Pan Speed : The minimum and maximum pan speed supported.
; Has Turbo Pan : The camera supports an additional turbo pan speed.
; Turbo Pan Speed : The actual turbo pan speed.

====Tilt Tab====
Definition of Tilt capabilities, fields as for ‘Pan’ tab.

====Zoom Tab====
; Can Zoom : The camera can zoom.
; Can Zoom Absolute : The camera can zoom to an absolute position.
; Can Zoom Relative : The camera can zoom to a relative position.
; Can Zoom Continuous : The camera can zoom continuously in or out until told to stop or the zoom limits are reached.
; Min/Max Zoom Range : If the camera supports absolute zoom this is the minimum and maximum zoom amounts that may be specified.
; Min/Man Zoom Step : If the camera supports relative zoom, this is the minimum and maximum amount of zoom change that can be specified.
; Has Zoom Speed : The camera supports specification of zoom speed.
; Min/Max Zoom Speed : The minimum and maximum zoom speed supported.

====Focus Tab====
Definition of Focus capabilities, fields as for ‘Zoom’ tab, but with the following additional capability.
; Can Auto Focus : The camera can focus automatically.

====White Tab====
Definition of White Balance capabilities, fields as for ‘Focus’ tab.

====Iris Tab====
Definition of Iris Control capabilities, fields as for ‘Focus’ tab.

====Presets Tab====
; Has Presets : The camera supports preset positions.
; Num Presets : How many presets the camera supports. If the camera supports a huge number of presets then it makes sense to specify a more reasonable number here, 20 or less is recommended.
; Has Home Preset : The camera has a defined ‘home’ position, usually in the mid point of its range.
; Can Set Presets : The camera supports setting preset locations via its control protocol.

===Control Scripts===
The second key element to controlling cameras with ZoneMinder is ensuring that an appropriate control script or application is present. A small number of sample scripts are included with ZoneMinder and can be used directly or as the basis for development. Control scripts are run atomically, that is to say that one requested action from the web interface results in one execution of the script and no state information is maintained. If your protocol requires state information to be preserved then you should ensure that your scripts do this as ZoneMinder has no concept of the state of the camera in control terms.

If you are writing a new control script then you need to ensure that it supports the parameters that ZoneMinder will pass to it. If you already have scripts or applications that control your cameras, the ZoneMinder control script will just act as glue to convert the parameters passed into a form that your existing application understands. If you are writing a script to support a new protocol then you will need to convert the parameters passed into the script to equivalent protocol commands. If you have carefully defined your control capabilities above then you should only expect commands that correspond to those capabilities.

The standard set of parameters passed to control scripts is defined below,
; --device=<device> : This is the control device from the monitor definition. Absent if no device is specified.
; --address=<address> : This is the control address from the monitor definition. This will usually be a hostname or ip address for network cameras or a simple numeric camera id for other cameras.
; --autostop=<timeout> : This indicates whether an automatic timeout should be applied to '''stop''' the given command. It will only be included for '''continuous''' commands, as listed below, and will be a timeout in decimal seconds, probably fractional.
; --command=<command> : This specifies the command that the script should execute. Valid commands are given below.
; --xcoord=<x>, --ycoord=<y> : This specifies the x and/or y coordinates for commands which require them. These will normally be absolute or mapped commands.
; --width=<width>'', ''--height=<height> : This specifies the width and height of the current image, for mapped motion commands where the coordinates values passed must have a context.
; --speed=<speed> : This specifies the speed that the command should use, if appropriate.
; --panspeed=<speed>'', ''--tiltspeed=<speed> : This indicates the specific pan and tilt speeds for diagonal movements which may allow a different motion rate for horizontal and vertical components.
; --step=<step> : This specifies the amount of motion that the command should use, if appropriate. Normally used for relative commands only.
; --panstep=<step>'', ''--tiltstep=<step> : This indicates the specific pan and tilt steps for diagonal movements which may allow a different amount of motion for horizontal and vertical components.
; --preset=<preset> : This specifies the particular preset that relevant commands should operate on.

The '''command''' option listed above may take one of the following commands as a parameter.
; wake : Wake the camera.
; sleep : Send the camera to sleep.
; reset : Reset the camera.
; move_map : Move mapped to a specified location on the image.
; move_pseudo_map : As move_map above. Pseudo-mapped motion can be used when mapped motion is not supported but relative motion is in which case mapped motion can be roughly approximated by careful calibration.
; move_abs_<direction> : Move to a specified absolute location. The direction element gives a hint to the direction to go but can be omitted. If present it will be one of '''up''', '''down''', '''left''', '''right''', '''upleft''', '''upright''', '''downleft''' or '''downright'''.
; move_rel_<direction> : Move a specified amount in the given direction.
; move_con_<direction> : Move continuously in the given direction until told to stop.
; move_stop : Stop any motion which may be in progress.
; zoom_abs_<direction> : Zoom to a specified absolute zoom position. The direction element gives a hint to the direction to go but can be omitted. If present it will be one of '''tele''' or '''wide'''.
; zoom_rel_<direction> : Zoom a specified amount in the given direction.
; zoom_con_<direction> : Zoom continuously in the given direction until told to stop.
; zoom_stop : Stop any zooming which may be in progress.
; focus_auto : Set focusing to be automatic.
; focus_man : Set focusing to be manual.
; focus_abs_<direction> : Focus to a specified absolute focus position. The direction element gives a hint to the direction to go but can be omitted. If present it will be one of '''near''' or '''far'''.
; focus_rel_<direction> : Focus a specified amount in the given direction.
; focus_con_<direction> : Focus continuously in the given direction until told to stop.
; focus_stop : Stop any focusing which may be in progress.
; white_<subcommand> : As per the focus commands, except that direction may be '''in''' or '''out'''.
; iris_<subcommand> : As per the focus commands, except that direction may be '''open''' or '''close'''.
; preset_set : Set the given preset to the current location.
; preset_goto : Move to the given preset.
; preset_home : Move to the '''home''' preset.

==Mobile Devices==

* After 1.24.x, access to the "light" interface changed to http://xxx.xxx.xxx.xxx/zm/index.php?skin=mobile ; You may find that you have a directory named "skins" under ZoneMinder base dir, so you may use one of the existent skins as a base to adapt to your needs;

Type this in your mobile browser: http://xxx.xxx.xxx.xxx/zm/index.php?format=xhtml (deprecated)

ZoneMinder has always had a minimal WML (Wireless Markup Language) capability to allow it to function on mobile phones and similar devices. However as of 1.20.0 this is now deprecated and has been replaced with a new XHTML – Mobile Profile mode as well as the default HTML4. XHTML-MP is a small, and limited, version of XHTML intended for mobile devices and is based on XHTML Basic. It does not contain scripting or other dynamic elements and essentially is a subset of HTML as most people know it.

The ZoneMinder XHTML-MP interface allows you to log into your installation via your phone or mobile devices and perform a limited number of tasks. These include viewing recent events, and monitoring live streams. However unlike the full interfaces these elements are presented as still images requiring manual refreshing. For now the XHTML-MP interface is presented as a prototype interface; rather than one offering full capabilities. As such, please feel free to make comments or offer suggestions via the forums on http://www.zoneminder.com.

As well as XHTML-MP, ideally I’d like to be able to offer a WML2.0 interface. WML2.0 is a blending of WML1.3, which is traditional WAP, and XHTML. As such it offers the scripting that WML has traditionally included plus the better control of mark-up that is the realm of XHTML. Unfortunately so far I’m unaware of any devices that support WML2.0 even if they say they are WAP2 compliant; certainly I’ve never had a phone that does. If you find out that a particular phone does support this then please let me know (or better still send me the phone!).

If you wish to use the XHTML-MP interface to ZoneMinder there is no extra configuration required to enable it per se. However ZoneMinder needs to be able to figure out what kind of content to deliver to particular browsers, so you have two choices. You can edit zm.php and include a definition that corresponds to your phone, describing a small number of basic capabilities, you will see a couple of examples already there, or you can use the comprehensive open source WURFL package available from http://wurfl.sourceforge.net/. You will need to download both the WURFL php files and the wurfl.xml file itself. WURFL is a resource containing information on the capabilities of a huge number of mobile phones, devices and browsers. Thus once it has matched your phone it can determine various capabilities it may possess. This means that ZoneMinder itself only has to deal with these capabilities and not the individual phone types. If you prefer you can also add the format=xHTML url parameter when you load ZoneMinder to force the xHTML format and skip the automatic determination altoghether.

To use WURFL you should install the php files in the same directory as ZoneMinder and then create a ‘wurfl’ sub-directory and ensure it is readable and writeable (or preferably owned by) your web server user. You should put the wurfl.xml file in there. One other thing you may need to change, as the xml file is quite large, is the ‘memory_limit’ setting in php.ini as the default setting of 8Mb may be too small. Once you’ve done this you should find that your phone or device is recognised and if it can support XHTML-MP it will receive that interface. If your phone is very new, or you are using an old version of the XML file you might find that it is not present however. The WURFL library uses a caching strategy to avoid reloading the whole XML file each time so check if a sensible looking cache file has been created in the ‘wurfl’ sub-directory also check the wurfl.log in the same place.

The WURFL is a third party application and as such I am unable to offer support directly for it. If you feel your device is missing or incorrectly represented please contact the authors via their own channels. If on the other hand you have any comments on ZoneMinder on your device specifically please let me know and I would be pleased to hear about it.

As support for cookies in mobile devices is patchy at best, the groups feature is not fully implemented in the XHTML-MP views. Instead if there is a group called ‘Mobile’ already defined then that group will always be effective, if not then all monitors available to the logged in user will be visible,

==Logging==
Most components of ZoneMinder can emit informational, warning, error and debug messages in a standard format. These messages can be logged in one or more locations. By default all messages produced by scripts are logged in <script name>.log files which are placed in the directory defined by the ZM_PATH_LOGS configuration variable. This is initially defined as ‘/tmp’ though it can be overridden (see the Options and Users section above). So for example, the zmpkg.pl script will output messages to /tmp/zmpkg.pl, an example of these messages is

03/01/06 13:46:00.166046 zmpkg[11148].INF [Command: start]

where the first part refers to the date and time of the entry, the next section is the name (or an abbreviated version) of the script, followed by the process id in square brackets, a severity code (INF, WAR, ERR or DBG) and the debug text. If you change the location of the log directory, ensure it refers to an existing directory which the web user has permissions to write to. Also ensure that no logs are present in that directory the web user does not have permission to open. This can happen if you run commands or scripts as the root user for testing at some point. If this occurs then subsequent non-privileged runs will fails due to being unable to open the log files.

As well as specific script logging above, information, warning and error messages are logged via the system syslog service. This is a standard component on Linux systems and allows logging of all sorts of messages in a standard way and using a standard format. On most systems, unless otherwise configured, messages produced by ZoneMinder will go to the /var/log/messages file. On some distributions they may end up in another file, but usually still in /var/log. Messages in this file are similar to those in the script log files but differ slightly. For example the above event in the system log file looks like

Jan 3 13:46:00 shuttle52 zmpkg[11148]: INF [Command: start]

where you can see that the date is formatted differently (and only to 1 second precision) and there is an additional field for the hostname (as syslog can operate over a network). As well as ZoneMinder entries in this file you may also see entries from various other system components. You should ensure that your syslogd daemon is running for syslog messages to be correctly handled.

A number of users have asked how to suppress or redirect ZoneMinder messages that are written to this file. This most often occurs due to not wanting other system messages to be overwhelmed and obscured by the ZoneMinder produced ones (which can be quite frequent by default). In order to control syslog messages you need to locate and edit the syslog.conf file on your system. This will often be in the /etc directory. This file allows configuration of syslog so that certain classes and categories of messages are routed to different files or highlighted to a console, or just ignored. Full details of the format of this file is outside the scope of this document (typing ‘man syslog.conf’ will give you more information) but the most often requested changes are easy to implement.

The syslog service uses the concept of priorities and facilities where the former refers to the importance of the message and the latter refers to that part of the system from which it originated. Standard priorities include ‘info’, ‘warning’, ‘err’ and ‘debug’ and ZoneMinder uses these priorities when generating the corresponding class of message. Standard facilities include ‘mail’, ‘cron’ and ‘security’ etc but as well this, there are eight ‘local’ facilities that can be used by machine specific message generators. ZoneMinder produces it’s messages via the ‘local1’ facility.

So armed with the knowledge of the priority and facility of a message, the syslog.conf file can be amended to handle messages however you like.

So to ensure that all ZoneMinder messages go to a specific log file you can add the following line near the top of your syslog.conf file

<pre># Save ZoneMinder messages to zm.log
local1.* /var/log/zm/zm.log</pre>

which will ensure that all messages produced with the local1 facility are routed to fhe /var/log/zm/zm.log file. However this does not necessarily prevent them also going into the standard system log. To do this you will need to modify the line that determines which messages are logged to this file. This may look something like

<pre># Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;news.none;authpriv.none;cron.none /var/log/messages</pre>

by default. To remove ZoneMinder messages altogether from this file you can modify this line to look like

<pre>*.info;local1.!*;mail.none;news.none;authpriv.none;cron.none /var/log/messages</pre>

which instructs syslog to ignore any messages from the local1 facility. If however you still want warnings and errors to occur in the system log file, you could change it to

<pre>*.info;local1.!*;local1.warning;mail.none;news.none;authpriv.none;cron.none /var/log/messages</pre>

which follows the ignore instruction with a further one to indicate that any messages with a facility of local1 and a priority of warning or above should still go into the file.

These recipes are just examples of how you can modify the logging to suit your system, there are a lot of other modifications you could make. If you do make any changes to syslog.conf you should ensure you restart the syslogd process or send it a HUP signal to force it to reread its configuration file otherwise your changes will be ignored.

The discussion of logging above began by describing how scripts produce error and debug messages. The way that the binaries work is slightly different. Binaries generate information, warning and error messages using syslog in exactly the same way as scripts and these messages will be handled identically. However debug output is somewhat different. For the scripts, if you want to enable debug you will need to edit the script file itself and change the DBG_LEVEL constant to have a value of 1. This will then cause debug messages to be written to the <script>.log file as well as the more important messages. Debug messages however are not routed via syslog. Scripts currently only have one level of debug so this will cause any and all debug messages to be generated. Binaries work slightly differently and while you can edit the call to zmDbgInit that is present in every binary’s ‘main’ function to update the initial value of the debug level, there are easier ways.

The simplest way of collecting debug output is to click on the Options link from the main ZoneMinder console view and then go to the Debug tab. There you will find a number of debug options. The first thing you should do is ensure that the ZM_EXTRA_DEBUG setting is switched on. This enables debug generally. The next thing you need to do is select the debug target, level and destination file using the relevant options. Click on the ‘?’ by each option for more information about valid settings. You will need to restart ZoneMinder as a whole or at least the component in question for logging to take effect. When you have finished debugging you should ensure you switch debug off by unchecking the ZM_EXTRA_DEBUG option and restarting ZoneMinder. You can leave the other options as you like as they are ignored if the master debug option is off.

Once you have debug being logged you can modify the level by sending USR1 and USR2 signals to the relevant binary (or binaries) to increase or decrease the level of debug being emitted with immediate effect. This modification will not persist if the binary gets restarted however.

If you wish to run a binary directly from the command line to test specific functionality or scenarios, you can set the ZM_DBG_LEVEL and ZM_DBG_LOG environment variables to set the level and log file of the debug you wish to see, and the ZM_DBG_PRINT environment variable to 1 to output the debug directly to your terminal.

All ZoneMinder logs can now be rotated by logrotate. A sample logrotate config file is shown below.

<pre>/var/log/zm/*.log {
missingok
notifempty
sharedscripts
postrotate
/usr/local/bin/zmpkg.pl logrot 2> /dev/null > /dev/null || true
endscript
}</pre>

==Troubleshooting==
Please see the [[Troubleshooting]] Page.

==To Do==
Seeing as ZoneMinder is so young and has kind of evolved rather than being planned there are a bunch of improvements and enhancements still to do, here is just a sample.

* Perhaps split out devices - I think devices should probably be a separate table and class from monitors. Not critical but would represent a better model.
* Support multicasting real-time video streaming. Current video streaming methods tend to lag after a while. This is a limitation of a single tcp stream per se I think. Using multicasting would make this more responsive.
* Support mpeg video as an input. This is easy to pick up if it’s a tcp stream, but a bit more of a pain if it’s over udp.
* Mouseover help - A bit more help popping up when you mouseover things would be handy. A bit more help full stop actually.
* Automatic device configuration - Video 4 Linux supports various device queries, it should be possible to get most of the device capability information from the device itself. The zmu utility does this now but it's not yet integrated into the web pages.
* Extend the API. Well ok it's not really got an API yet but the image data is held in shared memory in a very simple format. In theory you could use the capture daemon to grab the images and other things could read them from memory, or the analysis daemon could read images from elsewhere. Either way this should be done through an API, and would need a library I think. Also the zmu utility could probably do a whole lot more to enable other things to manage when the daemons become active etc. The perl modules in 1.22.0 are a first step in this direction.
* Allow ZoneMinder to 'train' itself by allowing the user to select events that are considered important and to discard those that should be ignored. ZoneMinder will interpolate, add a bit of magic, and recommend settings that will support this selection automatically thereafter. The hooks for this are already in to some extent.
* Add sound support to allow a captured audio channel to be associated with a video device. Work on this feature has already begun.
* Comments - Needs many more, but that's just me I'm hopeless at commenting things out. I'll get round to it soon though honest! You're lucky to even get this document.

==Bugs==
* When opening a link to an event etc from a notification email the window that is opened is just a regular browser window and not in the context of a proper ZoneMinder web interface. Thus it comes up too big usually (not a major issue) and also things like 'Delete' don't work as it wants to do things to its parent (which is more of a major issue).
* The .sock files used by the *nix sockets I suspect may have the odd permission issue now and again. I think everything recovers from it but it needs checking out.
Probably bucket loads more, just fire them at me.
*X10 support broken see my notes for workaround.
http://www.zoneminder.com/forums/viewtopic.php?t=15792

==Non-Bugs==
Yes, those are tabs in the indents; I like tabs so don't go changing them to spaces please. Also, yes I like my opening braces on their own line most of the time, what's the point of brackets that don't line up?

Everything else that isn't definitely broken is probably deliberate, or was once anyway.

==License==
ZoneMinder is released under the GPL, see below.

Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009 Philip Coombes

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the [http://www.gnu.org/copyleft/gpl.html GNU General Public License] for more details.

Fedora

2015-05-14T01:59:14Z

Knnniggett: /* Installation */

The Fedora Project is a Red Hat sponsored, community-supported open source project. Its stated goal is to promote the rapid progress of free (as in freedom) and open source software and content, and its rapid innovation is possible using open processes and public forums.
'''

The project is led by the Fedora Project Board, which is comprised of community leaders and Red Hat members, and this group steers the direction of the project and of Fedora Core, the Linux distribution it develops. Red Hat employees work with the code alongside community members, and many Fedora Project innovations make their way into new releases of Red Hat Enterprise Linux.

ZoneMinder is developed on the Fedora distribution and no special actions are usually required for installation.

== Zmrepo - A ZoneMinder repository for RPM based distros ==
The ZoneMinder development team would like to introduce you to a new, easier way to install ZoneMinder on Fedora. Zmrepo is meant to be a turn-key solution. There is no compiling, no installing modules from CPAN, and no more complicated repository instructions.

This repository brings together a ZoneMinder rpm built by the development team, with all features enabled. This is in comparison to past ZoneMinder rpm's found in the Fedora repositories, which do not have ffmpeg support built-in. Zmrepo includes all dependencies that are not found in the default Fedora repositories. A few Perl modules are built by us, but all the rest of the dependencies are mirrored from popular sites such as EPEL and RPMFusion. There is no longer a need to add these additional repositories to your system. Zmrepo takes care of that for you.

==== Purpose ====
The primary purpose for developing ZoneMinder rpms for Fedora is to get an idea of how well ZoneMinder works on the bleeding edge of software development. We don't use Fedora in our production systems and consequently these rpms do not get the same share of testing that the ZoneMinder rpms for RHEL/CentOS do. However, they do give us the unique opportunity to solve any problems caused by new software widgets (looking at you systemd) before they trickle down to RHEL/CentOS.

==== Who Should Use ====
Those that want to use the latest and greatest packages available should use this repository over the RHEL/CentOS repository. Keep in mind that this comes with the real possibility Fedora may throw in something new, which might cause a problem with ZoneMinder.

==== Supported Versions ====
Fedora distributions have a relatively short life cycle. A new version of Fedora is scheduled to be released [https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle every 6 months]. It is the goal of the ZoneMinder development team to provide and support ZoneMinder rpms for the two most recent versions of Fedora. Today, those two versions are Fedora 21 and 20. Rpms built for older versions of Fedora may exist in zmrepo, but they will not be maintained and may be deleted at some point in the future.

==== Installation====

* Installation Instructions for i386 or x86_64 architectures on Fedora 20:
wget http://zmrepo.zoneminder.com/f/20/i386/zmrepo-20-3.fc20.noarch.rpm
sudo yum install --nogpgcheck zmrepo-20-3.fc20.noarch.rpm
sudo yum install zoneminder
less /usr/share/doc/zoneminder/README.Fedora

You must complete the steps documented in README.Fedora before ZoneMinder will function correctly.

* Installation Instructions for i386, x86_64, or armv7fl architectures on Fedora 21:
wget http://zmrepo.zoneminder.com/f/21/i386/zmrepo-21-1.fc21.noarch.rpm
sudo yum install --nogpgcheck zmrepo-21-1.fc21.noarch.rpm
sudo yum install zoneminder
less /usr/share/doc/zoneminder/README.Fedora

You must complete the steps documented in README.Fedora before ZoneMinder will function correctly.

==Fedora 18 (alpha)==
*FIXED: ''if you get problems with Live Video not working'' due to a problem with the sockets. 
**ERROR: socket_sendto permission errors.
*Make sure your cgi-bin ScriptAlias is correct as shown below. 
*''ffmpeg libraries from Fedora rpms do not work'' with zm. You have to install from source (yuck).

This is how I got it installed... 

Do all the following as sudo (or root) 
'''install packages''' 
yum install mysql mysql-server zoneminder 

''' disable selinux 
vi /etc/selinux/config 
*change the word 'enforcing' to 'disabled' 

'''REBOOT'''

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf
* in the section - <Directory "/usr/share/zoneminder/www">
**remove the line "Deny from all # DELETE THIS LINE"
**remove the '-Indexes' on the Options line on Line 17 )I don't think the '-' is supposed to be there
**Comment out the Order and Allow lines and insert the new syntax 'Require all granted' as a new line
* I also got a ScriptAlias error for the cgi-bin/zm alias so I commented the cgi-bin scriptAlias in the /etc/httpd/conf/httpd.conf

#F18 /etc/httpd/conf.d.zoneminder.conf
Alias /zm "/usr/share/zoneminder/www"
<Directory "/usr/share/zoneminder/www">
Options FollowSymLinks
AllowOverride All
# NEW format
Require all granted
# The code unfortunately uses short tags in many places
php_value short_open_tag 1
#Deny from all # DELETE THIS LINE
</Directory>
ScriptAlias /cgi-bin "/usr/libexec/zoneminder/cgi-bin"
<Directory "/usr/libexec/zoneminder/cgi-bin">
Options +ExecCGI +MultiViews +SymLinksIfOwnerMatch
AllowOverride All
# NEW format
Require all granted
php_value short_open_tag 1
</Directory>
 
'''start httpd:''' 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 17==
'''install packages''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 14==
'''install packages:''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
/etc/init.d/mysqld start 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
/etc/init.d/httpd start 

'''start zoneminder''' 
/etc/init.d/zoneminder start 

==Fedora 11, 12 and 13==
'''The Easy Way''' Adapted from a forum post by "hiredguntech" or just search the forum for "flowers for candy"

Step-by-step installation of ZM v1.24.2 on Fedora-12.

(1) load fc12 using the netinstall ISO (the CD wants to use dhcp and doesn't work well with an assigned fixed IP) - turn off 'office' and turn on 'server' and 'development'. Besure to include a large /var partition through custom partitioning and use localhost instead of what it suggests (domain.localhost ?). Also, if you're using a capture card install it (them) in the system before starting the netinstall CD. Save these steps as a .txt file so the code can be cut and paste into the terminal with ease.

[2] Remove evolution from task bar (right click... (not a requirement)).

[3] Set screensaver to NOT require password and set it to 20 minutes or more (menu-system::preferences::screensaver).

(4) Disable SELinux. (menu-system::Admin::SELinux Mgmnt; change system default enforcing mode to disabled).

[5] Enable sudo for yourself. From a terminal (menu-Application::System Tools::Terminal),
Code:

su

(enter root password)

echo ''''YourUserName''' ALL=(ALL) ALL' >> /etc/sudoers (put YOUR user name from FC12 installation in place of '''YourUserName''')

(6) Set up the RPM Fusion Repository (in open terminal).

Code:

rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm

rpm -ivh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

exit

exit (closes terminal window)

(7) Install the pre-requisites, (menu-System::Administration::Add/Remove Software) type in the search field the following package names and select each of the closest match (there will be 'other' packages related or similar named - look for the right one, and check-it.)

mysql-server

mysql-devel

pcre-devel

ffmpeg

ffmpeg-devel

Hit the 'Apply' button, accept any added packages, type root password, and let this stuff load.

[8] Install any updates that are available, its the yellow icon up by the time.

(9) Enable the services: web and db. (menu-System::Administration::Services) and find the following:

httpd

mysqld

for each of them hit the 'enable button' so you can start them later.

(10) Reboot. This allows all the services to start and settle in.

(11) Now add Zoneminder (menu-System::Administration::Add/Remove Software) Type Zoneminder in the search field select it and apply.

[13] '''Note:''' To edit as root: open a terminal (menu-Application::System Tools::Terminal), su to root, type 'gedit <path/filename>'. Now you have sufficient permissions to edit & save as root.

(14) Edit as root /etc/httpd/conf.d/zoneminder.conf to remove the 'Deny from All' line. It even says 'DELETE THIS LINE', so it should be easy to find. Save it.

(15) As root, [or with sudo] build the zm database (menu-Application::System Tools::Terminal).

Code:

su

(enter root password)

mysql mysql < /usr/share/zoneminder/db/zm_create.sql

mysqladmin reload

mysql mysql

grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass';

\q

exit

exit

(16) Enable zoneminder. (menu-System::Administration::Services) and find zoneminder. Enable it. You can start the service hear also, Or in a terminal:

Code:

service zoneminder start

[18] Last thing - edit the SECOND entry of short_open_tag down at line 229. Again as root (menu-Application::System Tools::Terminal), gedit /etc/php.ini

Change short_open_tag from 'off' to 'on'

[19] reboot. open browser, type 'localhost/zm'

[20] It may be necessary to change the ffmpeg path in options::images to get ffmpeg to make videos. Generally removing the /local from the existing path will fix this issue

'''Or (the original wiki walk through)'''

You should be able to just do "yum install zoneminder", create the zm database, find the zm_create.sql file (rpm -ql zoneminder) and import it to mysql, then start zoneminder. Plus allow web access. Edit /etc/httpd/conf.d/zoneminder.conf and comment out (#) or delete this line :-

Deny from all # DELETE THIS LINE

Restart/reload apache

sudo service httpd restart

This didn't work for me due to 2 problems. First was php.ini section short_open_tag = Off, set to on

short_open_tag = On

Restart/reload apache

sudo service httpd restart

The other problem was zm_create.sql had duplicate indexes reported using phpMyAdmin. Removed all "INSERT INTO MonitorPresets" and "INSERT INTO MonitorPresets" in zm_create.sql and that imported cleanly. Alternatively just import from the command line mysql -u zmuser -p < zm_create.sql

http://www.zoneminder.com/forums/viewtopic.php?p=50242

'''Manual Install Version 1.24.2 with ffmpeg enabled'''

Version 1.23.3 has always compiled ok on Fedora 9/10/11 but I had problems with version 1.24.2.

Problems with compiling fixed by adding #include <cstdio> to all .cpp files in src directory and removing ccache package (yum remove ccache)

http://www.zoneminder.com/forums/viewtopic.php?p=55152

http://www.zoneminder.com/forums/viewtopic.php?t=12515&sid=0da85eb2fc78917d7a78cf788603a320

If using ffmpeg and ffmpeg-devel packages you may see problem compiling with libavutil.a . I could not get ffmpeg to compile so downloaded the Fedora source package and compiled it manually.

yumdownloader --source ffmpeg

sudo rpm -Uvh ffmpeg-0.5-5.20091026svn.fc12.src.rpm

Needed the following packages

sudo yum install dirac-devel faad2-devel gsm-devel imlib2-devel lame-devel libdc1394-devel libtheora-devel libvdpau-devel openjpeg-devel \
schroedinger-devel speex-devel texi2html x264-devel xvidcore-devel yasm

See http://fozzolog.fozzilinymoo.org/tech/2009/11/recompiling-ffmpeg-for-fedora-12-to-add-faac-support.html (don't need to add faac support, just follow procedure)

My rpmbuild failed so from the BUILD/ffmpeg-20091026

make
sudo make install
sudo make install-libs

and configured ZoneMinder to use /usr/local for FFMPEG

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost \
ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr -L/usr/lib/mysql" ZM_SSL_LIB=openssl --with-ffmpeg=/usr/local

==Fedora 8==
* Have packages for Apache and MySQL installed on the system.
* Install the zoneminder RPM package on the system
: Fedora Information for package zoneminder
: * http://koji.fedoraproject.org/koji/packageinfo?packageID=4691
* Configure zoneminder
* Make sure Apache and MySQL services are running
* Edit the zoneminder.conf apache configuration file to allow web connections
vi /etc/httpd/conf.d/zoneminder.conf
* Build the MySQL database table for zoneminder
mysql -p -u root mysql < /usr/share/zoneminder/db/zm_create.sql > mysqladmin -p -u root reload

The Fedora RPM creates /var/log/zoneminder, but the database scripts point logs to /tmp, rather than the new directory.
* Click '''Options''', '''Paths''' tab, and change
ZM_PATH_LOGS = /var/log/zoneminder
* Click '''Options''', '''Debug''' tab, and change
ZM_EXTRA_DEBUG_LOG = /var/log/zoneminder/zm_debug.log+

* Install ffmpeg on Fedora.
Due to licensing the ffmpeg package is absent from Fedora. It can be added from [[Fedora_Linux_Distribution_Reference#Livna:_Get_Important_Packages_Missing_From_Fedora|Livna]].
wget http://rpm.livna.org/livna-release-8.rpm
rpm -ih livna-release-8.rpm
yum install ffmpeg
yum install ffmpeg-devel
Which provides the following: ffmpeg-libs-0.4.9-0.41.20071011.lvn8, ffmpeg-0.4.9-0.41.20071011.lvn8, ffmpeg-devel-0.4.9-0.41.20071011.lvn8

* Test ffmpeg
ffmpeg -f image2 -i %03d-capture.jpg /tmp/movie.mpg

==Fedora 7==
* Builds From source - see [[Fedora Core 6 Step-by-Step]] '''AS WELL AS''' [http://www.zoneminder.com/forums/viewtopic.php?t=9414 Fedora 7 forum topic]
*RPMs are Available in the '''main Fedora 7 distribution''', and in the development 'rawhide' tree.
**Its as easy as running: yum install zoneminder
**Take a look at [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 6==
*Build from source [[Fedora Core 6 Step-by-Step]]

* RPMs are also available right now in '''Fedora Extras''' for Fedora Core 6.
** [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 4==
* http://www.zoneminder.com/forums/viewtopic.php?t=5991 
Set web user and group correctly and set the log dir to a writeable location.
With FC4 there are three things that must be done to get ZM running,:
#is in the /etc/ld.so.conf.d/ dir created a file with 775 perm called zm.conf and add the line '/usr/local/lib' to it and type 'ldconfig' once it is added, also with a fresh install of FC4 make sure SE linux is disabled if you are not using it. Check your log path in options under the paths tab. This will tell you were the log are going to be put.
#Second make sure the path exists.
#Third create the log files if they do not exist and make sure that they have the correct permissions. '''If zm can not open and write the log files, it will not start. '''

CentOS

2015-04-22T17:49:54Z

Knnniggett: /* Installation */

The intent of this walk through is to install a very base/bare bones installation of CentOS that runs only ZoneMinder. This would be for a dedicated ZoneMinder server with no GUI or any unnecessary services running. The reason for the very light-weight installation is to make the majority of system resources available to ZoneMinder, not the OS. With this installation, memory is reduced to around 140-160MB, and CPU usage is practically nonexistent. The CentOS base installation is very easy to install and doesn’t take too much time as long as you have some type of broadband connection. There are many ways to install CentOS, but this article covers only two, because they are related.

''All CLI operations/commands in this How-To are done as root, in the /root directory. The reasoning is that this system would be in a secure environment to begin with. However, if you need to add a user to run these services to better secure the system, then you can, but keep in mind that some items must run as root.''

== Zmrepo - A ZoneMinder repository for RPM based distros ==
The ZoneMinder development team would like to introduce you to a new, easier way to install ZoneMinder on CentOS. Zmrepo is meant to be a turn-key solution. There is no compiling, no installing modules from CPAN, and no more complicated repository instructions.

This repository brings together a ZoneMinder rpm built by the development team, with all features enabled. It also includes all dependencies that are not found in the default CentOS repositories. A few Perl modules are built by us, but all the rest of the dependencies are mirrored from popular sites such as EPEL and RPMFusion. There is no longer a need to add these additional repositories to your system. Zmrepo takes care of that for you.

==== Who Should Use ====
The development team strictly uses CentOS, but these packages should work on Red Hat Enterprise Linux and Scientific Linux. The rpms in zmrepo are intended to work with ''default installations'' of these Linux distributions. Modified versions are not guaranteed to work. Continue to the Disclaimer below for details.

Please report any issues with RHEL and SL, as we have no way of pro-actively discovering them.

==== Disclaimer ====
This could also be appropriately called '''Who should not Use''' zmrepo.

The goal behind CentOS is that of an enterprise operating system. Stability is prioritized over the latest and greatest version of a particular package. Fortunately, bug fixes are backported. Consequently, you should ''never'' replace the core packages in CentOS! If you truly think that you "have to have" some package that is newer than what is found in the default repository then you should consider using a different Linux distro.

The CentOS maintainers have a great write-up that describes this in much more detail [http://wiki.centos.org/PackageManagement/SourceInstalls here]. Pay close attention to the all the do's, dont's, and "this will break" comments.

Zmrepo extends this same philosophy onto ZoneMinder. While ZoneMinder requires many dependencies to work, zmrepo will not overwrite any core packages. It only adds packages that, otherwise, would not be available.

One other case is worth mentioning. This repository is intended ''only'' for those who have installed RHEL/CentOS/SL using the '''official installation media for that distribution'''! This means that these rpms are not intended to work with third parties that release their own spin of CentOS, which contain their own third party application preinstalled. Third parties are allowed to modify the original distribution in any way, which means we can't guarantee the rpms in zmrepo will be compatible.

For example, if you installed "CentOS" using an installation disk from an Astericks vendor, then the rpms in zmrepo are known not to work.

==== Installation ====

* Installation Instructions for i386 or x86_64 architectures on CentOS 6:
wget http://zmrepo.zoneminder.com/el/6/i386/zmrepo-6-4.el6.noarch.rpm
sudo yum install --nogpgcheck zmrepo-6-4.el6.noarch.rpm
sudo yum install zoneminder
less /usr/share/doc/zoneminder-*/README.CentOS

You must complete the steps documented in README.CentOS before ZoneMinder will function correctly.

NOTE: RHEL users must enable the "rhel-6-server-optional-rpms" repositoy on their system before attempting to install ZoneMinder.

A YouTube video that steps through the installation can be viewed [https://www.youtube.com/watch?v=l2lLvl8WxfU here.]

* Installation Instructions for x86_64 architecture (only) on CentOS 7:
wget http://zmrepo.zoneminder.com/el/7/x86_64/zmrepo-7-4.el7.centos.noarch.rpm
sudo yum install --nogpgcheck zmrepo-7-4.el7.centos.noarch.rpm
sudo yum install zoneminder
less /usr/share/doc/zoneminder-*/README.Centos7

You must complete the steps documented in README.Centos7 before ZoneMinder will function correctly.

== CentOS 5.6 & ZoneMinder 1.25.0 ==
This guide is for CentOS v5.6 (Notes for using this guide with CentOS 6 are in chapter 2.) with ZoneMinder v1.25.0 which are the newest released versions as of this update (Summer 2011). If you are attempting to install newer versions of either using this guide, you will have to adjust file and directory names denoted below.

=== Step One - Get CentOS ===
You can download the “.iso” file(s) for CentOS from http://www.centos.org/ 
Alternatively download the net-install version of CentOS which is basically just the first CD.
Here is one location to download the net-install version: 
Download i386: http://mirror.symnds.com/distributions/CentOS-vault/5.6/isos/i386/CentOS-5.6-i386-netinstall.iso 
Download 64 bit: http://mirror.symnds.com/distributions/CentOS-vault/5.6/isos/x86_64/CentOS-5.6-x86_64-netinstall.iso 
Mirrors List: http://mirror.centos.org/centos/5/isos/

=== Step Two - Installation Source ===
Regardless of which method you use, the next few steps are the same. 
Begin by booting your system up with either cd/dvd. 
Choose the options that best fit your environment until you reach the “Installation Method”.

[[Image:centosnetinstal-http.png]]

Choose '''HTTP''' ONLY if you are using the net-install method. Otherwise, you probably want to choose '''Local CDROM'''. 

If you are using the net-install method then enter: 
Website Name: '''mirror.centos.org''' 
CentOS Directory: (for i386) '''/centos/5.6/os/i386''' 
CentOS Directory: (for 64 bit) '''/centos/5.6/os/x86_64'''

=== Step Three - Installation Packages ===
On the first screen, un-check "Desktop - Gnome" then check "Server" (not Server-GUI) 
Make sure that you have "Customize now" selected at the bottom. (do not check "Packages from CentOS Extras")

[[Image:centosinstall-packages1.png]]

Click "Next" to continue 

Once presented with the custom package selection, un-check/check the following:
Applications = Check only "Editors" and "Text Based Internet"
Development = Check only "Development Libraries" and "Development Tools"
Servers = Un-check everything
Base System = Check only "Base" (you can check Administration Tools and System Tools if you need them, but they are not necessary)

[[Image:Centosinstall-packages2.png]]

Now let the system finish the installation.

[[Image:centosisntall-end.png]]

=== Step Four - Configuration ===
After the first reboot, the setup screen should appear. If not, log into the system and type "setup"

[[Image:centosinstall-setup1.png]]

Select "Firewall Configuration" and set the "Security Level" and "SELinux" to "Disabled."

[[Image:centosinstall-setup2.png]]

Next, we are going to disable a number of system services. Go back to the setup screen and select "System Services" 
Un-Check:
apmd
bluetooth
cups
hidd
ip6tables
iptables
netfs
nfslock
pcscd
portmap
After disabling the services, select "Disable Now and On Boot", exit the setup tool, and log into the system if you haven't already.
*Screen is a simple program that allows you to run commands from a "Hosted" command line interface. This helps if you loose your connection to the server for any reason in that it enables you to resume (screen -r) right where you left off. Often times, I will start a large update/upgrade, leave it for the day, then come back and see where it's at later. Screen allows you to do that without having to be connected.
*Install Screen
yum install screen
*To start a screen session just type
screen
*If you get disconnected and need to resume your session of screen simply type
screen -r

=== Step Five - Installing ZoneMinder 1.25.0 ===
First, we need to download files and prepare the system
*Add the RPM Forge repository to CentOS. This will allow the installation of a number of services/applications later without having to manually install them.
<pre># For i386 CentOS 5.x run:
rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm

# For 64 bit CentOS 5.x run:
rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm</pre>
*Download the needed files, ZoneMinder 1.25.0 and the Cambozola addon
wget http://www2.zoneminder.com/downloads/ZoneMinder-1.25.0.tar.gz
wget http://www.zoneminder.com/sites/zoneminder.com/downloads/cambozola.jar
*Now let's install all the services and programs that will be needed (''If you encounter any dependency errors using yum, try running '''yum clean all''' then re-try the install command(s).'')

*tip: Copy/paste two lines at a time

<pre>
yum -y install mysql mysql-server mysql-devel php php-gd php-mysql httpd gcc \
pcre-devel gd mod_ssl glib2-devel gcc-c++ ntp gnutls-devel ImageMagick

yum -y install libjpeg-devel perl-Archive-Tar perl-MIME-Lite perl-MIME-tools \
perl-Date-Manip perl-LWP-UserAgent-Determined

yum -y install perl-PHP-Serialization perl-Device-SerialPort perl-Archive-Zip perl-Sys-Mmap \
perl-Module-Load subversion git yasm bzip2 bzip2-devel bzip2-libs lbzip2</pre>
*Now let's update everything within the new CentOS install
yum -y update
*At this point, it might be useful to reboot your system. Oddly, sometimes things don't work right unless you reboot after all the updates
reboot -or- shutdown -r now
*After rebooting, log into your system
==== Install ffmpeg ====
*Now we need to make sure we use the latest "tested" version of "ffmpeg". This is the latest version of ffmpeg that the ZoneMinder developers have tested with. Download, compile and install ffmpeg:
<pre>git clone git://git.videolan.org/ffmpeg.git
cd ffmpeg
./configure --enable-gpl --enable-shared --enable-pthreads
make
</pre>

*The following commands must be done as '''root'''

<pre>
make install
make install-libs
</pre>
edit /etc/ld.so.conf and add the line "/usr/local/lib"
<pre>
ldconfig -v
</pre>

*Next, run 'ffmpeg' from the command line. Make sure you do not get any errors:

<pre>
ffmpeg
</pre>

*If 'ffmpeg' runs correctly, you'll see something similar to this:

<pre>
ffmpeg version N-32260-gaebb56e, Copyright (c) 2000-2011 the FFmpeg developers
built on Aug 31 2011 21:41:49 with gcc 4.1.2 20080704 (Red Hat 4.1.2-50)
configuration: --enable-shared --enable-swscale --enable-gpl --enable-pthreads
libavutil 51. 14. 0 / 51. 14. 0
libavcodec 53. 12. 0 / 53. 12. 0
libavformat 53. 10. 0 / 53. 10. 0
libavdevice 53. 3. 0 / 53. 3. 0
libavfilter 2. 37. 0 / 2. 37. 0
libswscale 2. 0. 0 / 2. 0. 0
libpostproc 51. 2. 0 / 51. 2. 0
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'
</pre>

==== Enable services ====
*Turn everything on. These commands must be run as root.

<pre>
chkconfig httpd on
chkconfig mysqld on
chkconfig ntpd on
service httpd start
service mysqld start
service ntpd start
</pre>
==== Install Zoneminder ====
*Next, we need to extract the contents of the ZoneMinder "tar" file, then jump into its directory.
<pre>
cd /root/ # Or your work directory for this installation
tar -zxvf ZoneMinder-1.25.0.tar.gz
cd ZoneMinder-1.25.0
</pre>
*Now we are going to configure ZoneMinder with some additional parameters. What is listed are the default CentOS directory locations.
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin

Note: It seems for Zoneminder to build with newer versions of ffmpeg, (certainly 0.6.3) you'll need to append CPPFLAGS="-D__STDC_CONSTANT_MACROS" to the end of the
./configure line thus:

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-ffmpeg=/usr/local/share/ffmpeg CPPFLAGS="-D__STDC_CONSTANT_MACROS"

There is a section in the FAQ ''"When running configure, I get a lot of messages about not being able to compile the ffmpeg libraries"'' about this [[http://www.zoneminder.com/wiki/index.php/FAQ]].

Worth mentioning here is the section in the FAQ under the heading "''My load is too high, how can I reduce it?''" [[http://www.zoneminder.com/wiki/index.php/FAQ]]. This descibes how you can possibly reduce CPU load by half by
changing the system's jpeg libraries and building Zoneminder with processor specific instructions.
Since CentOS 6.4 CentOS now comes with libjpeg_turbo as the standard JPEG library leading to a more optimised Zoneminder.

By default ZM_DB_HOST=localhost, ZM_DB_NAME=zm, ZM_DB_USER=zmuser, and ZM_DB_PASS=zmpass.
*Change "zmuser" (if you want) with the user that you will use within MySQL to access the ZoneMinder database
*Change "zmpass" with the password you will be using with the "zmuser" account
So if you wish to change it, use a command like:
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass

*if you get the configure "error zm requires libmysqlclient.a" with 64 bit CentOS add the following to the end of your configure statement
--with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql"

e.g. For CentOS 5.6 64-bit with support for ffmpeg. The whole command must be executed on one line. Make sure to change the '''zmpass''' to a password that matches your installation.
<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-ffmpeg=/usr/local/share/ffmpeg --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql" CXXFLAGS="-D__STDC_CONSTANT_MACROS"
</pre>
* Run '''make''' and '''make install''' after running the configuration steps above.

make
# Run the next command as root
make install

==== Configure MySQL ====
*Need to add a password for the root user of MySQL
*Create the zm database
*Create the zm database user with permissions and password
mysql
mysql> SET PASSWORD FOR root@localhost=PASSWORD('new_root_password');
>Query OK, 0 rows affected (0.00 sec)
mysql> create database zm;
>Query OK, 1 row affected (0.01 sec)
mysql> CREATE USER 'your_zm_user'@'localhost' IDENTIFIED BY 'your_zm_password_from_above';
Query OK, 0 rows affected (0.01 sec)
mysql> grant CREATE, INSERT, SELECT, DELETE, UPDATE on zm.* to your_zm_user@localhost;
>Query OK, 0 rows affected (0.02 sec)
mysql> exit
>Bye
*Import the tables into the zm database
cd /root/ZoneMinder-1.25.0
mysql -u root -p zm < db/zm_create.sql

==== Finalize Installation of ZoneMinder ====
'''All remaining CLI commands need to be run as root.'''
*Make ZoneMinder startup automatically after a reboot
# from the ZoneMinder-1.25 source directory
cp scripts/zm /etc/init.d/
chmod +x /etc/init.d/zm
chkconfig zm on
*Add the Cambozola Java web interface
cp cambozola.jar /var/www/html/zm/
*Make sure you have permission to view it from apache:
chown apache:apache /var/www/html/zm/cambozola.jar
*Start ZoneMinder
service zm start

Note: You may get an error when you try to start Zoneminder using the 'zm' startup script as per this forum post: [[http://www.zoneminder.com/forums/viewtopic.php?f=21&t=17827]] .
The reason for this was the default 'zm' startup script was formatted with DOS line endings. If you get the errors as detailed in the above post then the fix is to convert the
'zm' file to use UNIX style line endings. You can do this in the Vim text editor whilst editing the 'zm' file thus: ':set fileformat=unix' then save the file ':wq'. You can also
use the utility dos2unix to convert the file.

* tick the box for support for the Cambozola addon within your ZoneMinder installation: http://ip-address/zm (Options->Images tab->OPT_CAMBOZOLA)

Now have fun and add your cameras to ZoneMinder knowing you now have a very stable and streamlined OS to run it on.

== CentOS 6 Notes ==

The installation for CentOS 6 is pretty much the same.
Download CentOS 6 minimal installation ISO (CentOS-6.0-i386-minimal.iso – 257MB). Burn to CD and install. We only want to be running in console text mode not GUI graphics mode. During installation configure network and tick to enable network adapter.
* Login as root and update the base install:
<pre>yum -y update</pre>
* Install required packages, other useful packages, and their dependencies
<pre>
yum groupinstall core
yum groupinstall base
yum install gcc gcc-c++ wget bison mysql-devel mysql-server php php-mysql php-pear php-pear-DB php-mbstring \
nano tftp-server httpd make ncurses-devel libtermcap-devel sendmail sendmail-cf caching-nameserver \
sox newt-devel libxml2-devel libtiff-devel php-gd audiofile-devel gtk2-devel subversion nano kernel-devel \
bison-devel ncurses zlib zlib-devel openssl openssl-devel gnutls-devel php-process perl-Time-HiRes
</pre>

Suggestion:
To remove various configure/make errors in Centos 6.2, you may also want to install:<pre>
bzip2-libs ffmpeg-devel ffmpeg-php perl-Net-SFTP-Foreign perl-Expect perl-LWPx-ParanoidAgent.x86_64</pre>

Now we continue from step four (4).
==== Installation of ZoneMinder ====
* In step five (5) the correct RPM Forge repository is:
<pre># For i686 CentOS 6.x run:
rpm -Uhv http://apt.sw.be/redhat/el6/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.i686.rpm

# For 64 bit CentOS 6.x run:
rpm -Uhv http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm</pre>

* In step five (5) the command that seems to configure zoneminder correctly is:
<pre>
CXXFLAGS=-D__STDC_CONSTANT_MACROS ./configure --with-webdir=/var/www/html/zm \
--with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache \
ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=your_zm_user ZM_DB_PASS=your_zm_password ZM_SSL_LIB=openssl
</pre>

Suggestion:
For Centos 6.2, I used the following configure string for success:<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=<zm user> ZM_DB_PASS=<zm user passwd> ZM_SSL_LIB=openssl --with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql" --with-ffmpeg=/usr/share/ffmpeg CXXFLAGS="-D__STDC_CONSTANT_MACROS" </pre>

==== Troubleshooting FFmpeg Errors Building ZoneMinder ====
Using the git version of FFmpeg can cause the ZoneMinder make process to fail with unresolved symbols in ffmpeg. To remedy this, use version 0.6.5 of FFmpeg with the same configure instructions as the normal install above.
FFmpeg 0.6.5: http://ffmpeg.org/releases/ffmpeg-0.6.5.tar.bz2
==== Troubleshooting Blank Page ====
If everything went ok but when accessing zoneminder's web page at http://localhost/zm, the page is blank this means that there is a problem with PHP short tags. Edit setting short_open_tag in php.ini (/etc/php.ini) and change it to On.
* Restart apache server with:
<pre>service httpd restart</pre> and you should be up and running.
==== Trouble shooting full drive with CentOS 6 ====
The default drive structure has chaned from that of CentOS 5 having the full drive allocated to the /root partition. CentOS 6 by default makes a logical volume 'LVM' of 10% your drives space for the /root partition and the remaining drive as the /home partion with the exception of the swap and boot partitions.

The will cause Zoneminder to fill the /root partition as the /var/www/html/zm/events directory is by default located here, you can use the system-config-lvm utility to re-adjust this partition balance if your system has been installed with the default partition structure.

It is best to install CentOS 6 with a custom partition layout that is the same as CentOS 5 structure, you can also if using a single physical had drive do with out the LVM drives and create an EXT4 /root partion along with the standard /boot and /swap partitions.

----

[[== '''P.S.''' ==]] aspcicc@jumpy.it
(Update: This does not appear to be required any more.)

Hi! and thanks for your guide.. i want to add a little correction that have made me crazy to resolve, when I poweroff or reboot system i obtain an error related to mysql database and i have understood that the problem was because mysqld is stopped before zoneminder to be more specific there isn't a link under rc0.d (halt) and rc6.d (reboot) to zoneminder that for this lack is simply killed by killall. To resolve this problem you need to add at the start of zm (under /etc/init.d) the line

' # chkconfig: 345 99 01 ' (without ' of course)

and then run
chkconfig --level 345 zm on
chkconfig --level 06 zm off

So the link to shutdown zm is created under rc0.d and rc6.d and zoneminder is started at the end of poweron and stopped at the beginning of the poweroff

For information about priority starting and stopping processes see: http://www.netadmintools.com/art94.html

----

Added Dependency: ImageMagick

Removed Dependency: perl-Time-HiRes, which causes a conflict with the default perl package.

Also, mysql seems to install with no password for the root user, and the zm DB create script creates the database on the fly, which means that the database create command needs to have the "-p zm" removed from the command line.

Could someone verify that this is correct, to make sure it's not just something I missed?

Thanks!
terry@cnysupport.com

----
Struggling to get x264 and ffmpeg working? I used the latest SVN versions not the Centos packages. But I was getting

''ffmpeg: error while loading shared libraries: libavdevice.so.53: cannot open shared object file: No such file or directory''

I followed these instructions:

<pre>cd /etc/ld.so.conf.d</pre>

* add another file: custom-libs.conf
* inside, put :

<pre>/usr/local/lib</pre>

* save the file
* run ldconfig
<pre>ldconfig</pre>

BeeryGaz

----

==== Failed monitors or ZM refusing to start ====
A problem that took me some time to figure out on two installations was SElinux.
SElinux stops Zoneminder from accessing some system parts or doing some functions so will cause various errors or simply drive you nuts trying to figure out.

Look at the following page on how to disable SElinux or use permissive mode.

<pre>http://www.centos.org/docs/5/html/5.2/Deployment_Guide/sec-sel-enable-disable.html</pre>

Some of the errors that I was getting with a fresh install on CentOS 6 was
<pre>
2013-02-16 16:13:10.828590 zmwatch 14898 ERR Can't open memory map file '/dev/shm/zm.mmap.1': No such file or directory zmwatch.pl
2013-02-16 16:13:10.736988 zmfix 15317 ERR Can't stat /dev/video0: Permission denied zmfix.cpp
</pre>

----
== ZoneMinder 1.26.x ==

Zoneminder after a long period of none development is now being developed by the community, these notes are to try and help with the installation of the new release on CentOS 5 and CentOS 6.
All testing has been done on a CentOS 6.4 fresh install server.

=== Cmake installation notes ===

Compiling of Zoneminder can now be done with the 'Cmake' command in replacement of the ./configure command this should automatically configure the build with the minimum of parameters. The 'Cmake' command at time of writing produced a partially working installation with the main files installed into /usr/local/bin/zoneminder and associated folders, different from the above guides.

The webfiles require to be linked via a zoneminder.conf file located with in the /disto/redhat directory inside the build directory that requires to be coped to the /etc/httpd/conf.d directory, this will need to be edited to the correct location of the webfiles and remove the local only command as indicated with in the file.

The Cmake install failed to use my BTTV capture card producing various errors with a potential solution given here <pre>http://www.zoneminder.com/forums/viewtopic.php?f=30&t=21709</pre>

=== ./configure compile ===

To install via the traditional ./configure method you first need to run the ./bootstrap.sh file to generate the required configure file, the install can then progress as the above installation guides.

This method has produced a fully working installation at time of writing.

== pt_BR Instructions ==

Here is a good walkthrough install of zoneminder in CentOS using the rpm package method. It is intended to Portuguese (pt or pt_BR) audience.

<pre>http://dulimind.blogspot.com.br/2015/02/zoneminder-no-centos-6-metodo-facil-com.html</pre>
----

[[Categories: Linux distributions]]

Using a dedicated Hard Drive

2015-04-10T00:29:06Z

Knnniggett:

On many installs you may wish to dedicate a hard drive or partition for Zoneminder events. There are many reasons why you may want to change the storage location - security, data segregation, preventing encroachment onto OS partition by zoneminder etc.

It's not terribly difficult to do, but may be non-obvious to the untaught so here's a brief guide.

Some commands here are based on Debian/Ubuntu installs

1. Become root or "sudo -s" to gain root privs.

2. Stop Zoneminder. "service zoneminder stop", "/usr/bin/zmpkg.pl stop", or "systemctl stop zoneminder"

3. Mount your new partition onto the root filesystem, ensuring it is automatically remounted at boot time by editing /etc/fstab -- For the benefit of this guide, I'm calling my new partition /newdrive

''Note this new partition can be a local drive, raid partition, lvm/md device, external NAS, SAN, NFS share or SMB share. The only condition is that the I/O throughput should be up to handling what Zoneminder will throw at it. For that speed reason, some favour non-journalled filesystems and accept the extra risk of data protection''

4. Locate Zoneminder's "events" and "images" directories. In Debian and Ubuntu, these are under /var/cache/zoneminder. In CentOS and Fedora, these are under /var/lib/zoneminder.

''If you wish to copy the data across, MOVE the events and images directories to /newdrive ''(Note this will take a long time on systems with many events). Also, DO NOT restart zoneminder until this entire process is completed. Doing so will cause all your events to be lost!''

If you don't wish to preserve the data, it is MUCH faster to simply delete or rename the original events and images dirs and create new directories in /newdrive. There is no need to remove the "orphaned" entries in the database, zmaudit will take care of those.

Eg:

mkdir /newdrive/events

mv /var/lib/zoneminder/events /var/lib/zoneminder/events_old
-- or --
rm -rf /var/lib/zoneminder/events

Add these lines in fstab to bind-mount an alternate location:

/dev/sdX1 /otherdrive ext3 defaults 0 2
/otherdrive/zoneminder/images /var/cache/zoneminder/images none defaults,bind 0 2
/otherdrive/zoneminder/events /var/cache/zoneminder/events none defaults,bind 0 2

or in some cases,

/otherdrive/zoneminder/images /var/lib/zoneminder/images none defaults,bind 0 2
/otherdrive/zoneminder/events /var/lib/zoneminder/events none defaults,bind 0 2

or if you have a separate partition for each:

/dev/sdX1 /var/cache/zoneminder/images ext3 defaults 0 2
/dev/sdX2 /var/cache/zoneminder/events ext3 defaults 0 2
(Repeat for images)

5. Ensure ZoneMinder can write to the new destination by changing the owner and group to that of the web server user account. Debian based distros typically use "www-data" as the web server user account while many rpm based distros use "apache".

chown -R apache:apache /otherdrive/zoneminder

6. Finally, restart zoneminder ( "service zoneminder start", "/usr/bin/zmpkg.pl start", or "systemctl start zoneminder") Monitor its operation and ensure new events are being created normally and are viewable. Zoneminder should also update the "Disk: %%" on its Console screen to reflect the disk space on its new partition.

FREQUENTLY ASKED QUESTIONS

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!

Question:
I noticed that there is an events folder under /usr/share/zoneminder/www, can I mount my newdrive to that folder?
Answer:
This will not work in every case either and should be avoided. The events and images folders under /usr/share/zoneminder/www are actually symbolic links that point to the real folders under /var/lib/zoneminder (or /var/cache/zoneminder). Altering this in any way has the same affect as the answer to the first question.

Using a dedicated Hard Drive

2015-04-10T00:24:29Z

Knnniggett:

On many installs you may wish to dedicate a hard drive or partition for Zoneminder events. There are many reasons why you may want to change the storage location - security, data segregation, preventing encroachment onto OS partition by zoneminder etc.

It's not terribly difficult to do, but may be non-obvious to the untaught so here's a brief guide.

Some commands here are based on Debian/Ubuntu installs

1. Become root or "sudo -s" to gain root privs.

2. Stop Zoneminder. "service zoneminder stop", "/usr/bin/zmpkg.pl stop", or "systemctl stop zoneminder"

3. Mount your new partition onto the root filesystem, ensuring it is automatically remounted at boot time by editing /etc/fstab -- For the benefit of this guide, I'm calling my new partition /newdrive

''Note this new partition can be a local drive, raid partition, lvm/md device, external NAS, SAN, NFS share or SMB share. The only condition is that the I/O throughput should be up to handling what Zoneminder will throw at it. For that speed reason, some favour non-journalled filesystems and accept the extra risk of data protection''

4. Locate Zoneminder's "events" and "images" directories. In Debian and Ubuntu, these are in /var/cache/zoneminder. In CentOS and Fedora, these are under /var/lib/zoneminder.

If you wish to copy the data across, MOVE the events and images directories to /newdrive ''(Note this will take a long time on systems with many events). Also, DO NOT restart zoneminder if it cannot locate these files as zmaudit.pl will delete the database entries for any events it cannot match files to''

If you don't wish to preserve the data, it is MUCH faster to simply delete or rename the original events and images dirs and create new directories in /newdrive. There is no need to remove the "orphaned" entries in the database, zmaudit will take care of those.

Eg:

mkdir /newdrive/events

mv /var/lib/zoneminder/events /var/lib/zoneminder/events_old

Add these lines in fstab to bind-mount an alternate location:

/dev/sdX1 /otherdrive ext3 defaults 0 2
/otherdrive/zoneminder/images /var/cache/zoneminder/images none defaults,bind 0 2
/otherdrive/zoneminder/events /var/cache/zoneminder/events none defaults,bind 0 2

or in some cases,

/otherdrive/zoneminder/images /var/lib/zoneminder/images none defaults,bind 0 2
/otherdrive/zoneminder/events /var/lib/zoneminder/events none defaults,bind 0 2

or if you have a separate partition for each:

/dev/sdX1 /var/cache/zoneminder/images ext3 defaults 0 2
/dev/sdX2 /var/cache/zoneminder/events ext3 defaults 0 2
(Repeat for images)

5. Ensure ZoneMinder can write to the new destination by changing the owner and group to that of the web server user account. Debian based distros typically use "www-data" as the web server user account while many rpm based distros use "apache".

chown -R apache:apache /otherdrive/zoneminder

6. Finally, restart zoneminder ( "service zonemidner start", "/usr/bin/zmpkg.pl start", or "systemctl start zoneminder") Monitor its operation and ensure new events are being created normally and are viewable. Zoneminder should also update the "Disk: %%" on its Console screen to reflect the disk space on its new partition.

FREQUENTLY ASKED QUESTIONS

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!

Question:
I noticed that there is an events folder under /usr/share/zoneminder/www, can I mount my newdrive to that folder?
Answer:
This will not work in every case either and should be avoided. The events and images folders under /usr/share/zoneminder/www are actually symbolic links that point to the real folders under /var/lib/zoneminder (or /var/cache/zoneminder). Altering this in any way has the same affect as the answer to the first question.

CentOS

2015-04-06T15:39:05Z

Knnniggett: /* Installation */

The intent of this walk through is to install a very base/bare bones installation of CentOS that runs only ZoneMinder. This would be for a dedicated ZoneMinder server with no GUI or any unnecessary services running. The reason for the very light-weight installation is to make the majority of system resources available to ZoneMinder, not the OS. With this installation, memory is reduced to around 140-160MB, and CPU usage is practically nonexistent. The CentOS base installation is very easy to install and doesn’t take too much time as long as you have some type of broadband connection. There are many ways to install CentOS, but this article covers only two, because they are related.

''All CLI operations/commands in this How-To are done as root, in the /root directory. The reasoning is that this system would be in a secure environment to begin with. However, if you need to add a user to run these services to better secure the system, then you can, but keep in mind that some items must run as root.''

== Zmrepo - A ZoneMinder repository for RPM based distros ==
The ZoneMinder development team would like to introduce you to a new, easier way to install ZoneMinder on CentOS. Zmrepo is meant to be a turn-key solution. There is no compiling, no installing modules from CPAN, and no more complicated repository instructions.

This repository brings together a ZoneMinder rpm built by the development team, with all features enabled. It also includes all dependencies that are not found in the default CentOS repositories. A few Perl modules are built by us, but all the rest of the dependencies are mirrored from popular sites such as EPEL and RPMFusion. There is no longer a need to add these additional repositories to your system. Zmrepo takes care of that for you.

==== Who Should Use ====
The development team strictly uses CentOS, but these packages should work on Red Hat Enterprise Linux and Scientific Linux. The rpms in zmrepo are intended to work with ''default installations'' of these Linux distributions. Modified versions are not guaranteed to work. Continue to the Disclaimer below for details.

Please report any issues with RHEL and SL, as we have no way of pro-actively discovering them.

==== Disclaimer ====
This could also be appropriately called '''Who should not Use''' zmrepo.

The goal behind CentOS is that of an enterprise operating system. Stability is prioritized over the latest and greatest version of a particular package. Fortunately, bug fixes are backported. Consequently, you should ''never'' replace the core packages in CentOS! If you truly think that you "have to have" some package that is newer than what is found in the default repository then you should consider using a different Linux distro.

The CentOS maintainers have a great write-up that describes this in much more detail [http://wiki.centos.org/PackageManagement/SourceInstalls here]. Pay close attention to the all the do's, dont's, and "this will break" comments.

Zmrepo extends this same philosophy onto ZoneMinder. While ZoneMinder requires many dependencies to work, zmrepo will not overwrite any core packages. It only adds packages that, otherwise, would not be available.

One other case is worth mentioning. This repository is intended ''only'' for those who have installed RHEL/CentOS/SL using the '''official installation media for that distribution'''! This means that these rpms are not intended to work with third parties that release their own spin of CentOS, which contain their own third party application preinstalled. Third parties are allowed to modify the original distribution in any way, which means we can't guarantee the rpms in zmrepo will be compatible.

For example, if you installed "CentOS" using an installation disk from an Astericks vendor, then the rpms in zmrepo are known not to work.

==== Installation ====

* Installation Instructions for i386 or x86_64 architectures on CentOS 6:
wget http://zmrepo.zoneminder.com/el/6/i386/zmrepo-6-4.el6.noarch.rpm
sudo yum install --nogpgcheck zmrepo-6-4.el6.noarch.rpm
sudo yum install zoneminder
less /usr/share/doc/zoneminder-*/README.CentOS

You must complete the steps documented in README.CentOS before ZoneMinder will function correctly.

NOTE: RHEL users must enable the "rhel-6-server-optional-rpms" repositoy on their system before attempting to install ZoneMinder.

A YouTube video that steps through the installation can be viewed [https://www.youtube.com/watch?v=l2lLvl8WxfU here.]

* Installation Instructions for x86_64 architecture (only) on CentOS 7:
wget http://zmrepo.zoneminder.com/el/7/x86_64/zmrepo-7-3.el7.centos.noarch.rpm
sudo yum install --nogpgcheck zmrepo-7-3.el7.centos.noarch.rpm
sudo yum install zoneminder
less /usr/share/doc/zoneminder-*/README.Centos7

You must complete the steps documented in README.Centos7 before ZoneMinder will function correctly.

== CentOS 5.6 & ZoneMinder 1.25.0 ==
This guide is for CentOS v5.6 (Notes for using this guide with CentOS 6 are in chapter 2.) with ZoneMinder v1.25.0 which are the newest released versions as of this update (Summer 2011). If you are attempting to install newer versions of either using this guide, you will have to adjust file and directory names denoted below.

=== Step One - Get CentOS ===
You can download the “.iso” file(s) for CentOS from http://www.centos.org/ 
Alternatively download the net-install version of CentOS which is basically just the first CD.
Here is one location to download the net-install version: 
Download i386: http://mirror.symnds.com/distributions/CentOS-vault/5.6/isos/i386/CentOS-5.6-i386-netinstall.iso 
Download 64 bit: http://mirror.symnds.com/distributions/CentOS-vault/5.6/isos/x86_64/CentOS-5.6-x86_64-netinstall.iso 
Mirrors List: http://mirror.centos.org/centos/5/isos/

=== Step Two - Installation Source ===
Regardless of which method you use, the next few steps are the same. 
Begin by booting your system up with either cd/dvd. 
Choose the options that best fit your environment until you reach the “Installation Method”.

[[Image:centosnetinstal-http.png]]

Choose '''HTTP''' ONLY if you are using the net-install method. Otherwise, you probably want to choose '''Local CDROM'''. 

If you are using the net-install method then enter: 
Website Name: '''mirror.centos.org''' 
CentOS Directory: (for i386) '''/centos/5.6/os/i386''' 
CentOS Directory: (for 64 bit) '''/centos/5.6/os/x86_64'''

=== Step Three - Installation Packages ===
On the first screen, un-check "Desktop - Gnome" then check "Server" (not Server-GUI) 
Make sure that you have "Customize now" selected at the bottom. (do not check "Packages from CentOS Extras")

[[Image:centosinstall-packages1.png]]

Click "Next" to continue 

Once presented with the custom package selection, un-check/check the following:
Applications = Check only "Editors" and "Text Based Internet"
Development = Check only "Development Libraries" and "Development Tools"
Servers = Un-check everything
Base System = Check only "Base" (you can check Administration Tools and System Tools if you need them, but they are not necessary)

[[Image:Centosinstall-packages2.png]]

Now let the system finish the installation.

[[Image:centosisntall-end.png]]

=== Step Four - Configuration ===
After the first reboot, the setup screen should appear. If not, log into the system and type "setup"

[[Image:centosinstall-setup1.png]]

Select "Firewall Configuration" and set the "Security Level" and "SELinux" to "Disabled."

[[Image:centosinstall-setup2.png]]

Next, we are going to disable a number of system services. Go back to the setup screen and select "System Services" 
Un-Check:
apmd
bluetooth
cups
hidd
ip6tables
iptables
netfs
nfslock
pcscd
portmap
After disabling the services, select "Disable Now and On Boot", exit the setup tool, and log into the system if you haven't already.
*Screen is a simple program that allows you to run commands from a "Hosted" command line interface. This helps if you loose your connection to the server for any reason in that it enables you to resume (screen -r) right where you left off. Often times, I will start a large update/upgrade, leave it for the day, then come back and see where it's at later. Screen allows you to do that without having to be connected.
*Install Screen
yum install screen
*To start a screen session just type
screen
*If you get disconnected and need to resume your session of screen simply type
screen -r

=== Step Five - Installing ZoneMinder 1.25.0 ===
First, we need to download files and prepare the system
*Add the RPM Forge repository to CentOS. This will allow the installation of a number of services/applications later without having to manually install them.
<pre># For i386 CentOS 5.x run:
rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm

# For 64 bit CentOS 5.x run:
rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm</pre>
*Download the needed files, ZoneMinder 1.25.0 and the Cambozola addon
wget http://www2.zoneminder.com/downloads/ZoneMinder-1.25.0.tar.gz
wget http://www.zoneminder.com/sites/zoneminder.com/downloads/cambozola.jar
*Now let's install all the services and programs that will be needed (''If you encounter any dependency errors using yum, try running '''yum clean all''' then re-try the install command(s).'')

*tip: Copy/paste two lines at a time

<pre>
yum -y install mysql mysql-server mysql-devel php php-gd php-mysql httpd gcc \
pcre-devel gd mod_ssl glib2-devel gcc-c++ ntp gnutls-devel ImageMagick

yum -y install libjpeg-devel perl-Archive-Tar perl-MIME-Lite perl-MIME-tools \
perl-Date-Manip perl-LWP-UserAgent-Determined

yum -y install perl-PHP-Serialization perl-Device-SerialPort perl-Archive-Zip perl-Sys-Mmap \
perl-Module-Load subversion git yasm bzip2 bzip2-devel bzip2-libs lbzip2</pre>
*Now let's update everything within the new CentOS install
yum -y update
*At this point, it might be useful to reboot your system. Oddly, sometimes things don't work right unless you reboot after all the updates
reboot -or- shutdown -r now
*After rebooting, log into your system
==== Install ffmpeg ====
*Now we need to make sure we use the latest "tested" version of "ffmpeg". This is the latest version of ffmpeg that the ZoneMinder developers have tested with. Download, compile and install ffmpeg:
<pre>git clone git://git.videolan.org/ffmpeg.git
cd ffmpeg
./configure --enable-gpl --enable-shared --enable-pthreads
make
</pre>

*The following commands must be done as '''root'''

<pre>
make install
make install-libs
</pre>
edit /etc/ld.so.conf and add the line "/usr/local/lib"
<pre>
ldconfig -v
</pre>

*Next, run 'ffmpeg' from the command line. Make sure you do not get any errors:

<pre>
ffmpeg
</pre>

*If 'ffmpeg' runs correctly, you'll see something similar to this:

<pre>
ffmpeg version N-32260-gaebb56e, Copyright (c) 2000-2011 the FFmpeg developers
built on Aug 31 2011 21:41:49 with gcc 4.1.2 20080704 (Red Hat 4.1.2-50)
configuration: --enable-shared --enable-swscale --enable-gpl --enable-pthreads
libavutil 51. 14. 0 / 51. 14. 0
libavcodec 53. 12. 0 / 53. 12. 0
libavformat 53. 10. 0 / 53. 10. 0
libavdevice 53. 3. 0 / 53. 3. 0
libavfilter 2. 37. 0 / 2. 37. 0
libswscale 2. 0. 0 / 2. 0. 0
libpostproc 51. 2. 0 / 51. 2. 0
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'
</pre>

==== Enable services ====
*Turn everything on. These commands must be run as root.

<pre>
chkconfig httpd on
chkconfig mysqld on
chkconfig ntpd on
service httpd start
service mysqld start
service ntpd start
</pre>
==== Install Zoneminder ====
*Next, we need to extract the contents of the ZoneMinder "tar" file, then jump into its directory.
<pre>
cd /root/ # Or your work directory for this installation
tar -zxvf ZoneMinder-1.25.0.tar.gz
cd ZoneMinder-1.25.0
</pre>
*Now we are going to configure ZoneMinder with some additional parameters. What is listed are the default CentOS directory locations.
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin

Note: It seems for Zoneminder to build with newer versions of ffmpeg, (certainly 0.6.3) you'll need to append CPPFLAGS="-D__STDC_CONSTANT_MACROS" to the end of the
./configure line thus:

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-ffmpeg=/usr/local/share/ffmpeg CPPFLAGS="-D__STDC_CONSTANT_MACROS"

There is a section in the FAQ ''"When running configure, I get a lot of messages about not being able to compile the ffmpeg libraries"'' about this [[http://www.zoneminder.com/wiki/index.php/FAQ]].

Worth mentioning here is the section in the FAQ under the heading "''My load is too high, how can I reduce it?''" [[http://www.zoneminder.com/wiki/index.php/FAQ]]. This descibes how you can possibly reduce CPU load by half by
changing the system's jpeg libraries and building Zoneminder with processor specific instructions.
Since CentOS 6.4 CentOS now comes with libjpeg_turbo as the standard JPEG library leading to a more optimised Zoneminder.

By default ZM_DB_HOST=localhost, ZM_DB_NAME=zm, ZM_DB_USER=zmuser, and ZM_DB_PASS=zmpass.
*Change "zmuser" (if you want) with the user that you will use within MySQL to access the ZoneMinder database
*Change "zmpass" with the password you will be using with the "zmuser" account
So if you wish to change it, use a command like:
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass

*if you get the configure "error zm requires libmysqlclient.a" with 64 bit CentOS add the following to the end of your configure statement
--with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql"

e.g. For CentOS 5.6 64-bit with support for ffmpeg. The whole command must be executed on one line. Make sure to change the '''zmpass''' to a password that matches your installation.
<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-ffmpeg=/usr/local/share/ffmpeg --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql" CXXFLAGS="-D__STDC_CONSTANT_MACROS"
</pre>
* Run '''make''' and '''make install''' after running the configuration steps above.

make
# Run the next command as root
make install

==== Configure MySQL ====
*Need to add a password for the root user of MySQL
*Create the zm database
*Create the zm database user with permissions and password
mysql
mysql> SET PASSWORD FOR root@localhost=PASSWORD('new_root_password');
>Query OK, 0 rows affected (0.00 sec)
mysql> create database zm;
>Query OK, 1 row affected (0.01 sec)
mysql> CREATE USER 'your_zm_user'@'localhost' IDENTIFIED BY 'your_zm_password_from_above';
Query OK, 0 rows affected (0.01 sec)
mysql> grant CREATE, INSERT, SELECT, DELETE, UPDATE on zm.* to your_zm_user@localhost;
>Query OK, 0 rows affected (0.02 sec)
mysql> exit
>Bye
*Import the tables into the zm database
cd /root/ZoneMinder-1.25.0
mysql -u root -p zm < db/zm_create.sql

==== Finalize Installation of ZoneMinder ====
'''All remaining CLI commands need to be run as root.'''
*Make ZoneMinder startup automatically after a reboot
# from the ZoneMinder-1.25 source directory
cp scripts/zm /etc/init.d/
chmod +x /etc/init.d/zm
chkconfig zm on
*Add the Cambozola Java web interface
cp cambozola.jar /var/www/html/zm/
*Make sure you have permission to view it from apache:
chown apache:apache /var/www/html/zm/cambozola.jar
*Start ZoneMinder
service zm start

Note: You may get an error when you try to start Zoneminder using the 'zm' startup script as per this forum post: [[http://www.zoneminder.com/forums/viewtopic.php?f=21&t=17827]] .
The reason for this was the default 'zm' startup script was formatted with DOS line endings. If you get the errors as detailed in the above post then the fix is to convert the
'zm' file to use UNIX style line endings. You can do this in the Vim text editor whilst editing the 'zm' file thus: ':set fileformat=unix' then save the file ':wq'. You can also
use the utility dos2unix to convert the file.

* tick the box for support for the Cambozola addon within your ZoneMinder installation: http://ip-address/zm (Options->Images tab->OPT_CAMBOZOLA)

Now have fun and add your cameras to ZoneMinder knowing you now have a very stable and streamlined OS to run it on.

== CentOS 6 Notes ==

The installation for CentOS 6 is pretty much the same.
Download CentOS 6 minimal installation ISO (CentOS-6.0-i386-minimal.iso – 257MB). Burn to CD and install. We only want to be running in console text mode not GUI graphics mode. During installation configure network and tick to enable network adapter.
* Login as root and update the base install:
<pre>yum -y update</pre>
* Install required packages, other useful packages, and their dependencies
<pre>
yum groupinstall core
yum groupinstall base
yum install gcc gcc-c++ wget bison mysql-devel mysql-server php php-mysql php-pear php-pear-DB php-mbstring \
nano tftp-server httpd make ncurses-devel libtermcap-devel sendmail sendmail-cf caching-nameserver \
sox newt-devel libxml2-devel libtiff-devel php-gd audiofile-devel gtk2-devel subversion nano kernel-devel \
bison-devel ncurses zlib zlib-devel openssl openssl-devel gnutls-devel php-process perl-Time-HiRes
</pre>

Suggestion:
To remove various configure/make errors in Centos 6.2, you may also want to install:<pre>
bzip2-libs ffmpeg-devel ffmpeg-php perl-Net-SFTP-Foreign perl-Expect perl-LWPx-ParanoidAgent.x86_64</pre>

Now we continue from step four (4).
==== Installation of ZoneMinder ====
* In step five (5) the correct RPM Forge repository is:
<pre># For i686 CentOS 6.x run:
rpm -Uhv http://apt.sw.be/redhat/el6/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.i686.rpm

# For 64 bit CentOS 6.x run:
rpm -Uhv http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm</pre>

* In step five (5) the command that seems to configure zoneminder correctly is:
<pre>
CXXFLAGS=-D__STDC_CONSTANT_MACROS ./configure --with-webdir=/var/www/html/zm \
--with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache \
ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=your_zm_user ZM_DB_PASS=your_zm_password ZM_SSL_LIB=openssl
</pre>

Suggestion:
For Centos 6.2, I used the following configure string for success:<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=<zm user> ZM_DB_PASS=<zm user passwd> ZM_SSL_LIB=openssl --with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql" --with-ffmpeg=/usr/share/ffmpeg CXXFLAGS="-D__STDC_CONSTANT_MACROS" </pre>

==== Troubleshooting FFmpeg Errors Building ZoneMinder ====
Using the git version of FFmpeg can cause the ZoneMinder make process to fail with unresolved symbols in ffmpeg. To remedy this, use version 0.6.5 of FFmpeg with the same configure instructions as the normal install above.
FFmpeg 0.6.5: http://ffmpeg.org/releases/ffmpeg-0.6.5.tar.bz2
==== Troubleshooting Blank Page ====
If everything went ok but when accessing zoneminder's web page at http://localhost/zm, the page is blank this means that there is a problem with PHP short tags. Edit setting short_open_tag in php.ini (/etc/php.ini) and change it to On.
* Restart apache server with:
<pre>service httpd restart</pre> and you should be up and running.
==== Trouble shooting full drive with CentOS 6 ====
The default drive structure has chaned from that of CentOS 5 having the full drive allocated to the /root partition. CentOS 6 by default makes a logical volume 'LVM' of 10% your drives space for the /root partition and the remaining drive as the /home partion with the exception of the swap and boot partitions.

The will cause Zoneminder to fill the /root partition as the /var/www/html/zm/events directory is by default located here, you can use the system-config-lvm utility to re-adjust this partition balance if your system has been installed with the default partition structure.

It is best to install CentOS 6 with a custom partition layout that is the same as CentOS 5 structure, you can also if using a single physical had drive do with out the LVM drives and create an EXT4 /root partion along with the standard /boot and /swap partitions.

----

[[== '''P.S.''' ==]] aspcicc@jumpy.it
(Update: This does not appear to be required any more.)

Hi! and thanks for your guide.. i want to add a little correction that have made me crazy to resolve, when I poweroff or reboot system i obtain an error related to mysql database and i have understood that the problem was because mysqld is stopped before zoneminder to be more specific there isn't a link under rc0.d (halt) and rc6.d (reboot) to zoneminder that for this lack is simply killed by killall. To resolve this problem you need to add at the start of zm (under /etc/init.d) the line

' # chkconfig: 345 99 01 ' (without ' of course)

and then run
chkconfig --level 345 zm on
chkconfig --level 06 zm off

So the link to shutdown zm is created under rc0.d and rc6.d and zoneminder is started at the end of poweron and stopped at the beginning of the poweroff

For information about priority starting and stopping processes see: http://www.netadmintools.com/art94.html

----

Added Dependency: ImageMagick

Removed Dependency: perl-Time-HiRes, which causes a conflict with the default perl package.

Also, mysql seems to install with no password for the root user, and the zm DB create script creates the database on the fly, which means that the database create command needs to have the "-p zm" removed from the command line.

Could someone verify that this is correct, to make sure it's not just something I missed?

Thanks!
terry@cnysupport.com

----
Struggling to get x264 and ffmpeg working? I used the latest SVN versions not the Centos packages. But I was getting

''ffmpeg: error while loading shared libraries: libavdevice.so.53: cannot open shared object file: No such file or directory''

I followed these instructions:

<pre>cd /etc/ld.so.conf.d</pre>

* add another file: custom-libs.conf
* inside, put :

<pre>/usr/local/lib</pre>

* save the file
* run ldconfig
<pre>ldconfig</pre>

BeeryGaz

----

==== Failed monitors or ZM refusing to start ====
A problem that took me some time to figure out on two installations was SElinux.
SElinux stops Zoneminder from accessing some system parts or doing some functions so will cause various errors or simply drive you nuts trying to figure out.

Look at the following page on how to disable SElinux or use permissive mode.

<pre>http://www.centos.org/docs/5/html/5.2/Deployment_Guide/sec-sel-enable-disable.html</pre>

Some of the errors that I was getting with a fresh install on CentOS 6 was
<pre>
2013-02-16 16:13:10.828590 zmwatch 14898 ERR Can't open memory map file '/dev/shm/zm.mmap.1': No such file or directory zmwatch.pl
2013-02-16 16:13:10.736988 zmfix 15317 ERR Can't stat /dev/video0: Permission denied zmfix.cpp
</pre>

----
== ZoneMinder 1.26.x ==

Zoneminder after a long period of none development is now being developed by the community, these notes are to try and help with the installation of the new release on CentOS 5 and CentOS 6.
All testing has been done on a CentOS 6.4 fresh install server.

=== Cmake installation notes ===

Compiling of Zoneminder can now be done with the 'Cmake' command in replacement of the ./configure command this should automatically configure the build with the minimum of parameters. The 'Cmake' command at time of writing produced a partially working installation with the main files installed into /usr/local/bin/zoneminder and associated folders, different from the above guides.

The webfiles require to be linked via a zoneminder.conf file located with in the /disto/redhat directory inside the build directory that requires to be coped to the /etc/httpd/conf.d directory, this will need to be edited to the correct location of the webfiles and remove the local only command as indicated with in the file.

The Cmake install failed to use my BTTV capture card producing various errors with a potential solution given here <pre>http://www.zoneminder.com/forums/viewtopic.php?f=30&t=21709</pre>

=== ./configure compile ===

To install via the traditional ./configure method you first need to run the ./bootstrap.sh file to generate the required configure file, the install can then progress as the above installation guides.

This method has produced a fully working installation at time of writing.

== pt_BR Instructions ==

Here is a good walkthrough install of zoneminder in CentOS using the rpm package method. It is intended to Portuguese (pt or pt_BR) audience.

<pre>http://dulimind.blogspot.com.br/2015/02/zoneminder-no-centos-6-metodo-facil-com.html</pre>
----

[[Categories: Linux distributions]]

FAQ

2015-04-04T14:41:05Z

Knnniggett: /* Why does ZM stop recording once I have 32000 events for my monitor? */

== ZoneMinder Frequently Asked Questions ==

This is the FAQ page. Feel free to contribute any FAQs that you think are missing.

===How can I stop ZoneMinder filling up my disk?===

Recent versions of ZoneMinder come with a filter you can use for this purpose already included. However '''by default it is not enabled for event deletion'''.

The filter is called ''PurgeWhenFull'' and to find it, choose one of the event counts from the console page, for instance events in the last hour, for one of your monitors.

This will bring up an event listing and a filter window.

In the filter window there is a drop down select box labeled 'Use Filter', that lets your select a saved filter. Select 'PurgeWhenFull' and it will load that filter.

Make any modifications you might want, such as the percentage full you want it to kick in, or how many events to delete at a time (it will repeat the filter as many times as needed to clear the space, but will only delete this many events each time to get there).

Then click on 'Save' which will bring up a new window. Make sure the 'Automatically delete' box is checked and press save to save your filter. This will then run in the background to keep your disk within those limits.

After you've done that, you changes will automatically be loaded into zmfilter within a few minutes.

Check the <tt>zmfilter.log</tt> file to make sure it is running as sometimes missing perl modules mean that it never runs but people don't always realize.

PURGE BY AGE

To delete events that are older than 7 days, create a new filter with "Date" set to "less than" and a value of "-7 days", sort by "date/time" in "asc"ending order, then enable the checkbox "delete all matches". You can also use a value of week or week and days: "-2 week" or "-2 week 4 day"

Save with 'Run Filter In Background' enabled to have it run automatically.

Optional skip archived events: click on the plus sign next to -7 days to add another condition. "and" "archive status" equal to "unarchived only".

Optional slow delete: limit the number of results to 3. If you have a large backlog of events that would be deleted, this can hard spike the CPU usage for a long time. Limiting the number of results to only the first three each time the filter is run spreads out the delete processes over time, dramatically lessening the CPU load.

There are two methods for ZM to remove files when they are deleted that can be found in Options under the System tab ZM_OPT_FAST_DELETE and ZM_RUN_AUDIT.

ZM_OPT_FAST_DELETE:

Normally an event created as the result of an alarm consists of entries in one or more database tables plus the various files associated with it. When deleting events in the browser it can take a long time to remove all of this if your are trying to do a lot of events at once. It is recommended that you set this option which means that the browser client only deletes the key entries in the events table, which means the events will no longer appear in the listing, and leaves the zmaudit daemon to clear up the rest later.

ZM_RUN_AUDIT:

The zmaudit daemon exists to check that the saved information in the database and on the file system match and are consistent with each other. If an error occurs or if you are using 'fast deletes' it may be that database records are deleted but files remain. In this case, and similar, zmaudit will remove redundant information to synchronize the two data stores. This option controls whether zmaudit is run in the background and performs these checks and fixes continuously. This is recommended for most systems however if you have a very large number of events the process of scanning the database and file system may take a long time and impact performance. In this case you may prefer to not have zmaudit running unconditionally and schedule occasional checks at other, more convenient, times.

ZM_AUDIT_CHECK_INTERVAL:

The zmaudit daemon exists to check that the saved information in the database and on the files system match and are consistent with each other. If an error occurs or if you are using 'fast deletes' it may be that database records are deleted but files remain. In this case, and similar, zmaudit will remove redundant information to synchronize the two data stores. The default check interval of 900 seconds (15 minutes) is fine for most systems however if you have a very large number of events the process of scanning the database and file system may take a long time and impact performance. In this case you may prefer to make this interval much larger to reduce the impact on your system. This option determines how often these checks are performed.

===What does a 'Can't shmget: Invalid argument' error in my logs mean? and my cameras won't display video at higher resolutions.===

This error is discussed in the README in the following excerpt:-
''...this is caused by an attempt to allocate an amount of shared memory greater than your system can handle. The size it requests is based on the following formula, <tt>ring buffer size x image width x image height x 3 (for 24 bit images) + a bit of overhead</tt>.

So, for example:
<pre>384x288 capture resolution, that makes: 110 592 pixels
in 24 bit color that's x24 = 2 654 208 bits per frame
by 80 frames ring buffer x80 = 212 336 640 bits per camera
by 4 cameras x4 = 849 346 560 bits.
Plus 10% overhead = 934 281 216 bits
That's 116 785 152 bytes, and
= 114 048 kB, respectively 111.38 MB.
If my shared memory is set to 134 217 728, which is exactly 128MB,
that means I shouldn't have any problem.
(Note that 1 byte = 8 bits and 1kbyte = 1024bytes, 1MB = 1024 kB)</pre>

If for instance you were using 24bit 640x480 then this would come to about 92Mb if you are using the default buffer size of 100. If this is too large then you can either reduce the image or buffer sizes or increase the maximum amount of shared memory available. If you are using RedHat then you can get details on how to change these settings at http://www.redhat.com/docs/manuals/database/RHDB-2.1-Manual/admin_user/kernel-resources.html .

You should be able to use a similar procedure with other distributions to modify the shared memory pool without kernel recompilations though in some cases this may be necessary. Note, this error also sometimes occurs if you have an old shared memory segment lying around from a previous run that is too small. Use the ipcs and ipcrm system commands to check and remove it if necessary.'"

You can often find out how many 4KB shared memory pages are available by typing the following :-
<pre># cat /proc/sys/kernel/shmall
2097152</pre>

In recent kernels the shmall is set to 2097152 memory pages multiplied by 4096 bytes per page for a total of 8 GB of shared memory available. You only need to increase the shmall value if you have a computer with more than 8GB of memory and wish to use more of it for shared memory usage, such as large databases.

The most shared memory bytes you can allocate in one go :-
<pre># cat /proc/sys/kernel/shmmax
33554432</pre>

In recent kernels the shmmax is set to 33554432 bytes for only 32 MB of maximum shared memory allocatable at a time, hardly enough for ZoneMinder to go above 320 x 240 x 24-bit resolution at 40 frames in the buffer if it is using the /dev/shm shared memory device, so this value needs to be increased. If you are using ZoneMinder with the memory mapped (mmap) compile time option then this doesn't affect you.

To change the value to 128 MB temporarily during this kernel execution type (for example) :-
<pre>echo 536870912 >/proc/sys/kernel/shmmax</pre>

'''Be sure to restart ZoneMinder after this.'''
However be aware that sometimes you will only need to change the shmmax value as shmall is often large enough. Also changing these values in this way is only effective until your machine is rebooted.

To change them permanently you will need to edit <tt>/etc/sysctl.conf</tt> and add the following lines (for example) :-
<pre>kernel.shmmax = 536870912</pre>

Or if your distribution has the <tt>/etc/sysctl.d/</tt> folder you can create a file in this folder without modifying the <tt>/etc/sysctl.d</tt> so you won't lose the changes during distro upgrades :-
<pre>echo kernel.shmmax = 536870912 >/etc/sysctl.d/60-kernel-shm.conf</pre>

To load these settings in the sysctl.conf file type:
<pre>sysctl -p</pre>

To check your shared memory settings type:
<pre>ipcs -l</pre>

Note that with Megapixel cameras like the Axis 207mw becoming cheaper and more attractive, the above memory settings are not adequate. To get Zoneminder working with a full 1280x1024 resolution camera in full color, increase <tt>134217728</tt> (128 MB) to, for example, <tt>268435456</tt> (256 MB) and multiple this value by each camera.

These changes will now also be set the next time your machine is restarted.

Versions 1.24.x of ZoneMinder also allows you to use an alternate method of shared memory allocation, [http://en.wikipedia.org/wiki/Mmap mapped memory]. This requires less configuration and can be simpler to use. Mapped memory allows you to use a special type of file as the placeholder for your memory and this file is 'mapped' into memory space for easy and fast access.

To enable mapped memory in ZoneMinder you need add add the --enable--mmap=yes switch to your configure line. By default mapped memory files are created in /dev/shm which on most distributions is a dedicated pseudo-partition containing memory formatted as a filesystem. If your system uses a different path then this can be changed in ZoneMinder in Options->paths->PATH_MAP. It uses a filesystem type called [http://en.wikipedia.org/wiki/Tmpfs tmpfs]. If you type 'df -h' you should see this area and the size of memory it currently allows. To increase size for tmpfs you need to edit /etc/default/tmpfs. Search for:
<pre>SHM_SIZE=128M</pre>
and change to something like
<pre>SHM_SIZE=1G</pre>
then reboot the system. You could possibly need to change RUN_SIZE, too.

It is important that you do not use a disk based filesystem for your memory mapped files as this will cause memory access to be extremely slow. ZoneMinder creates files called .zm.mmap.<monitor id> in the mapped memory filesystem.

Mapped memory is subject to the same limitations in terms of total memory as using more traditional shared memory but does not require any configuration per allocation or chunk. In future versions of ZoneMinder this will be the default shared memory storage method.

<div id="AlternateSharedMemory" style="width:80%; border:2px solid #8a8588; background:#faf5ff; vertical-align:top; margin-top: 6px; padding: 4px;">
Another good article about shared memory settings http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.uprun.doc/doc/t0008238.htm .
It made a statement that conflicted with those in the Redhat article but they fixed a [http://www.zoneminder.com/forums/viewtopic.php?t=9692 long standing memory issue on FC6], so give them a try.

'''The essential difference was that the kernel.shmall setting is NOT in a direct memory setting in KB but in pages of memory. it is Max Pages of memory'''

'''For example:''' If you want to allocate a maximum memory setting to 8GB you have to convert it to the number of pages (or segments).
with a page size of 4096.
*kernel.shmall = 8000x1024x1024/4096
<pre>kernel.shmall = 2097152</pre>
NOT 8388608000 as would be suggested in the RedHat article linked above.

shmmax is the max amount to allocate in one request -
this is is an actual memory size (as opposed to pages) set to 4GB
<pre>kernel.shmmax = 4294967296</pre>

The <tt>/etc/sysctl.conf</tt> would have these lines
<pre>kernel.shmall = 2097152
kernel.shmmax = 4294967296</pre>

As above, reload your sysctl.conf with <tt>sysctl -p</tt> and check that the settings are correct with <tt>ipcs -l</tt>.
</div>

===I have enabled motion detection but it is not always being triggered when things happen in the camera view===

ZoneMinder uses zones to examine images for motion detection. When you create the initial zones you can choose from a number of preset values for sensitivity etc. Whilst these are usually a good starting point they are not always suitable for all situations and you will probably need to tweak the values for your specific circumstances. The meanings of the various settings are described in the documentation (http://www.zoneminder.com/wiki/index.php/Documentation#Defining_Zones) however if you believe you have sensible settings configured then there are two diagnostic approaches you can use.

====Event Statistics====
The first technique is to use event statistics. Firstly you should ensure they are switched on in Options->Logging->RECORD_EVENT_STATS. This will then cause the raw motion detection statistics for any subsequently generated events to be written to the DB. These can then be accessed by first clicking on the Frames or Alarm Frames values of the event from any event list view in the web gui. Then click on the score value to see the actual values that caused the event. Alternatively the stats can be accessed by clicking on the 'Stats' link when viewing any individual frame. The values displayed there correspond with the values that are used in the zone configuration and give you an idea of what 'real world' values are being generated.

Note that if you are investigating why events 'do not' happen then these will not be saved and so won't be accessible. The best thing to do in that circumstance is to make your zone more sensitive so that it captures all events (perhap even ones you don't want) so you can get an idea of what values are being generated and then start to adjust back to less sensitive settings if necessary. You should make sure you test your settings under a variety of lighting conditions (e.g. day and night, sunny or dull) to get the best feel for that works and what doesn't.

Using statistics will slow your system down to a small degree and use a little extra disk space in the DB so once you are happy you can switch them off again. However it is perfectly feasible to keep them permanently on if your system is able to cope which will allow you to review your setting periodically.

====Diagnostic Images====
The second approach is to use diagnostic images which are saved copies of the intermediate images that ZM uses when determining motion detection. These are switched on and off using Options->Logging->RECORD_DIAG_IMAGES.

There are two kinds of diagnostic images which are and are written (and continuously overwritten) to the top level monitor event directory. If an event occurs then the files are additionally copied to the event directory and renamed with the appropriate frame number as a prefix.

The first set are produced by the monitor on the image as a whole. The diag-r.jpg image is the current reference image against which all individual frames are compared and the diag-d.jpg image is the delta image highlighting the difference between the reference image and the last analysed image. In this images identicial pixels will be black and the more different a pixel is the whiter it will be. Viewing this image and determining the colour of the pixels is a good way of getting a feel for the pixel differences you might expect (often more than you think).

The second set of diag images are labelled as diag-<zoneid>-<stage>.jpg where zoneid is the id of the zone in question (Smile) and the stage is where in the alarm check process the image is generated from. So if you have several zones you can expect to see multiple files. Also these files are only interested in what is happening in their zone only and will ignore anything else outside of the zone. The stages that each number represents are as follows,

# Alarmed Pixels - This image shows all pixels in the zone that are considered to be alarmed as white pixels and all other pixels as black.
# Filtered Pixels - This is as stage one except that all pixels removed by the filters are now black. The white pixels represent the pixels that are candidates to generate an event.
# Raw Blobs - This image contains all alarmed pixels from stage 2 but aggrageted into blobs. Each blob will have a different greyscale value (between 1 and 254) so they can be difficult to spot with the naked eye but using a colour picker or photoshop will make it easier to see what blob is what.
# Filtered Blobs - This image is as stage 3 but under (or over) sized blobs have been removed. This is the final step before determining if an event has occurred, just prior to the number of blobs being counted. Thus this image forms the basis for determining whether an event is generated and outlining on alarmed images is done from the blobs in this image.

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.

===Why can't ZoneMinder capture images (either at all or just particularly fast) when I can see my camera just fine in xawtv or similar?===

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 6-10fps for two, 1-4fps for three and 1-2 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.

When using xawtv etc to view the stream you are not looking at an image captured using the frame grabber but the card's video memory mapped onto your screen. 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.

===Why can't I see streamed images when I can see stills in the Zone window etc?===

This issue is normally down to one of two causes

1) You are using Internet Explorer and are trying to view multi-part jpeg streams. IE does not support these streams directly, unlike most other browsers. You will need to install Cambozola or another multi-part jpeg aware pluging to view them. To do this you will need to obtain the applet from the Downloads page and install the cambozola.jar file in the same directly as the ZoneMinder php files. Then find the ZoneMinder Options->Images page and enable ZM_OPT_CAMBOZOLA and enter the web path to the .jar file in ZM_PATH_CAMBOZOLA. This will ordinarily just be cambozola.jar. Provided (Options / B/W tabs) WEB_H_CAN_STREAM is set to auto and WEB_H_STREAM_METHOD is set to jpeg then Cambozola should be loaded next time you try and view a stream.

'''NOTE''': If you find that the Cambozola applet loads in IE but the applet just displays the version # of Cambozola and the author's name (as opposed to seeing the streaming images), you may need to chmod (''-rwxrwxr-x'') your (''usr/share/zoneminder/'') cambozola.jar:

$ sudo chmod 775 cambozola.jar

Once I did this, images started to stream for me.

2) The other common cause for being unable to view streams is that you have installed the ZoneMinder cgi binaries (zms and nph-zms) in a different directory than your web server is expecting. Make sure that the --with-cgidir option you use to the ZoneMinder configure script is the same as the CGI directory configure for your web server. If you are using Apache, which is the most common one, then in your httpd.conf file there should be a line like <pre>ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"</pre> where the last directory in the quotes is the one you have specified. If not then change one or the other to match. Be warned that configuring apache can be complex so changing the one passed to the ZoneMinder configure (and then rebuilding and reinstalling) is recommended in the first instance. If you change the apache config you will need to restart apache for the changes to take effect. If you still cannot see stream reliably then try changing Options->Paths->ZM_PATH_ZMS to just use zms if nph-zms is specified, or vice versa. Also check in your apache error logs.

===I have several monitors configured but when I load the Montage view in FireFox why can I only see two? or, Why don't all my cameras display when I use the Montage view in FireFox?===

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.

To resolve this situation, follow the instructions below:

<pre>Enter about:config in the address bar

scroll down to
browser.cache.check_doc_frequency 3
change the 3 to a 1

browser.cache.disk.enable True -> False
network.http.max-connections-per-server -> put a value of 100
network.http.max-persistent-connections-per-proxy -> 100 again
network.http.max-persistent-connections-per-server -> 100 again
</pre>

===Why is ZoneMinder using so much CPU?===

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.

The main causes are.

# Using a video palette other than greyscale or RGB24. This can cause a relatively minor performace hit, though still significant. Although some cameras and cards require using planar palettes ZM currently doesn't support this format internally and each frame is converted to an RGB representation prior to processing. Unless you have compelling reasons for using YUV or reduced RGB type palettes such as hitting USB transfer limits I would experiment to see if RGB24 or greyscale is quicker. Put your monitors into 'Monitor' mode so that only the capture daemons are running and monitor the process load of these (the 'zmc' processes) using top. Try it with various palettes to see if it makes a difference.
# Big image sizes. A image of 640x480 requires at least four times the processing of a 320x240 image. Experiment with different sizes to see what effect it may have. Sometimes a large image is just two interlaced smaller frames so has no real benefit anyway. This is especially true for analog cameras/cards as image height over 320 (NTSC) or 352 PAL) are invariably interlaced.
# Capture frame rates. Unless there's a compelling reason in your case there is often little benefit in running cameras at 25fps when 5-10fps would often get you results just as good. Try changing your monitor settings to limit your cameras to lower frame rates. You can still configure ZM to ignore these limits and capture as fast as possible when motion is detected.
# Run function. Obviously running in Record or Mocord modes or in Modect with lots of events generates a lot of DB and file activity and so CPU and load will increase.
# Basic default detection zones. By default when a camera is added one detection zone is added which covers the whole image with a default set of parameters. If your camera covers a view in which various regions are unlikely to generate a valid alarm (ie the sky) then I would experiment with reducing the zone sizes or adding inactive zones to blank out areas you don't want to monitor. Additionally the actual settings of the zone themselves may not be optimal. When doing motion detection the number of changed pixels above a threshold is examined, then this is filter, then contiguous regions are calculated to see if an alarm is generated. If any maximum or minimum threshold is exceeded according to your zone settings at any time the calculation stops. If your settings always result in the calculations going through to the last stage before being failed then additional CPU time is used unnecessarily. Make sure your maximum and minimumzone thresholds are set to sensible values and experiment by switching RECORD_EVENT_STATS on and seeing what the actual values of alarmed pixels etc are during sample events.
# Optimise your settings. After you've got some settings you're happy with then switching off RECORD_EVENT_STATS will prevent the statistics being written to the database which saves some time. Other settings which might make a difference are ZM_FAST_RGB_DIFFS, ZM_OPT_FRAME_SERVER and the JPEG_xxx_QUALITY ones.

I'm sure there are other things which might make a difference such as what else you have running on the box and memory sizes (make sure there's no swapping going on). 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. Having said that I also don't always know why you get certains results from 'top'. For instance if I have a 'zma' daemon running for a monitor that is capturing an image. I've commented out the actual analysis so all it's doing is blending the image with the previous one. In colour mode this takes ~11 milliseconds per frame on my system and the camera is capturing at ~10fps. Using 'top' this reports the process as using ~5% of CPU and permanently in R(un) state. Changing to greyscale mode the blending takes ~4msec (as you would expect as this is roughly a third of 11) but top reports the process as now with 0% CPU and permanently in S(leep) state. So an actual CPU resource usage change of a factor of 3 causes huge differences in reported CPU usage. I have yet to get to the bottom of this but I suspect it's to do with scheduling somewhere along the line and that maybe the greyscale processing will fit into one scheduling time slice whereas the colour one won't but I have no evidence of this yet!

===Why is the timeline view all messed up?===

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.

===How much Hard Disk Space / Bandwidth do I need for ZM?===
Please see [http://www.jpwilson.eu/ZM_Utils/ZM%20storage%20calc%20sheet.xls Storage Calc] in excel format

Or go to [http://www.axis.com/products/video/design_tool/index.htm 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 320x240 storing 1 fps except during alarm events. After 1 week 60GB of space in the volume where the events are stored (/var/www/html/zm) has been used.

===When I try and run ZoneMinder I get lots of audit permission errors in the logs and it won't start===
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 ([http://en.wikipedia.org/wiki/Selinux]).
If you are seeing entries in your system log like:

Jun 11 20:44:02 kernel: audit(1150033442.443:226): avc: denied { read } for pid=5068
comm="uptime" name="utmp" dev=dm-0 ino=16908345 scontext=user_u:system_r:httpd_sys_script_t
tcontext=user_u:object_r:initrc_var_run_t tclass=file

then it is likely that your system has SELinux enabled and it is preventing ZoneMinder from performaing certain activities. You then have two choices. You can either tune SELinux to permit the required operations or you can disable SELinux entirely which will permit ZoneMinder to run unhindered. Disabling SELinux is usually performed by editing its configuration file (e.g., <tt>/etc/selinux/config</tt>) and then rebooting. 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.

=== How do I enable ZoneMinder's security? ===
In the console, click on Options. Check the box next to "ZM_OPT_USE_AUTH". You will immediately be asked to login. The username is 'admin' and the password is 'admin'.

'''To Manage Users:''' 
In main console, go to '''Options->Users'''.

* You may also consider to use the web server security, for example, htaccess files under Apache scope; You may even use this as an additional/redundant security on top of Zoneminders built-in security features;

=== Why does ZM stop recording once I have 32000 events for my monitor? ===
Storing more than 32k files in a single folder is a limitation of some filesystems. To avoid this, enable USE_DEEP_STORAGE under Options.

USE_DEEP_STORAGE is now the default for new ZoneMinder systems so this limitation should only apply to users upgrading from a previous version of ZoneMinder.

Versions of ZM from 1.23.0 onwards allow you to have a deeper filesystem with fewer files per individual directory. As well as not being susceptible to the 32k limit, this is also somewhat faster.

If you have upgraded from a previous version of ZoneMinder and this option is not already enabled, it is very important to follow the steps below to enable it on an existing system. Failure to properly follow these steps WILL RESULT IN LOSS OF YOUR DATA!

# Stop ZoneMinder
# Backup your event data and the dB if you have the available storage
# Enable USE_DEEP_STORAGE under Options.
# From the command line, run "sudo zmupdate.pl --migrate-events"
# Monitor the output for any events that fail to convert.
# After the conversion completes, you can restart ZoneMinder

Note that you can re-run the migrate-events command if any error messages scroll off the screen.

You can read about the lack of a limit in the number of sub-directories in the ext4 filesystem at:
http://kernelnewbies.org/Ext4
and see what tools may assist in your use of this filesystem in:
http://ext4.wiki.kernel.org/index.php/Ext4_Howto
If you search for ext3 or reiserfs on the forums you will find various threads on this issue with guidance on
how to convert.

== Managing system load ''(with IP Cameras in mind)'' ==

=== Introduction ===
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.
3. Comparing the zoned selections to the previous image or images and applying rules.
4. If in alarm state, writing that image to the disk and updating the mysql database.

If you're capturing at five frames per second, the above is repeated five times every second, multiplied by the number of cameras. 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.

=== How do I know if my computer is overloaded? ===
If your CPU is running at 100% all the time, it's probably overloaded (or running at exact optimisation). If the load is consistently high (over 10.0 for a single processor) then Bad Things happen - like lost frames, unrecorded events etc. Occasional peaks are fine, normal and nothing to worry about.

Zoneminder runs on Linux, Linux measures system load using "load", which is complicated but gives a rough guide on what the computer is doing at any given time. Zoneminder shows Load on the main page (top right) as well as disk space. Typing "uptime" on the command line will give a similar guide, but with three figures to give a fuller measure of what's happening over a period of time but for the best guide to see what's happening, install "htop" - which gives easy to read graphs for load, memory and cpu usage.

A load of 1.0 means the processor has "just enough to do right now". Also worth noting that a load of 4.0 means exactly the same for a quad processor machine - each number equals a single processor's workload. A very high load can be fine on a computer that has a stacked workload - such as a machine sending out bulk emails, or working its way through a knotty problem; it'll just keep churning away until it's done. However - Zoneminder needs to process information in real time so it can't afford to stack its jobs, it needs to deal with them right away.

For a better and full explanation of Load: http://en.wikipedia.org/wiki/Load_%28computing%29

=== My load is too high, how can I reduce it? ===
Zoneminder is /very/ tweakable and it's possible to tune it to compromise. The following are good things to try, in no particular order;

Change the jpeg libraries. In most distributions Linux uses standard jpeg libraries which although fine for most things, don't use the MMX functions in nearly all modern processors. Check whether your cpu supports mmx by running "cpuid |grep MMX" which should give you a line or two along the lines of "MMX instructions". If so, give the libs a try. Most people report their load halves simply by using these libs. You may be able to experience substantial Zoneminder performance boosts now by merely upgrading your operating system, without having to download libraries and compile your own binaries, etc. as described in the forum thread linked below. Some distributions, e.g. Fedora 14 now include library code to utilize the instruction set extensions available in your processor:

http://fedoraproject.org/wiki/Fedora_14_Alpha_release_notes#Faster_JPEG_Compression.2FDecompression

"The replacement of libjpeg with libjpeg-turbo brings speed improvements to a wide range of applications when handling images in JPEG format ..."

http://fedoraproject.org/wiki/Releases/14/Schedule

still states "2010-11-02 final release".

CentOS 6.4 now has libjpeg-turbo built in as the default jpeg library allowing the best results out of the box.

http://libjpeg-turbo.virtualgl.org/

provides some history on its project page. If you seek confirmation for which library is in use, you may consider querying e.g. while running on a prior distribution:
<pre>
[u@who ~]$ rpm -q --whatprovides libjpeg
libjpeg-6b-46.fc12.i686
[u@who ~]$
</pre>
and comparing the response to querying when the higher-performance library is available:
<pre>
[u@who ~]$ rpm -q --whatprovides libjpeg
libjpeg-turbo-1.0.1-1.fc14.x86_64
[u@who ~]$
</pre>
As noted in other forum postings, some zoneminder camera and usage configurations may not make much use of jpeg processing (e.g. some webcams), and thus obtain little performance benefit. Otherwise, you should be able to select one or more of:
* running more cameras,
* running existing cameras at higher image resolutions,
* running cameras at a faster frame rate,
* saving MoDect images with higher quality,
* having more CPU cycles available for any non-Zoneminder workload, etc.

http://www.zoneminder.com/forums/viewtopic.php?t=6419 gives more info on the download-the-library-yourself, compile-your-own-Zoneminder binary, etc. approach if needed. Nobody's posted there to say it broke their system... Yet.

If your camera allows you to change image size, think whether you can get away with smaller images. Smaller pics = less load. 320x240 is usually ok for close-up corridor shots.

Go Black and White. Colour pictures use twice to three times the CPU, memory and diskspace but give little benefit to identification.

Reduce frames per second. Halve the fps, halve the workload. If your camera supports fps throttling (Axis do), try that - saves ZM having to drop frames from a stream. 2-5 fps seems to be widely used.

Experiment with using jpeg instead of mjpeg. Some users have reported it gives better performance, but YMMV.

Tweak the zones. Keep them as small and as few as possible. Stick to one zone unless you really need more.

Schedule. If you are running a linux system at near capacity, you'll need to think carefully about things like backups and scheduled tasks. updatedb - the process which maintains a file database so that 'locate' works quickly, is normally scheduled to run once a day and if on a busy system can create a heavy increase on the load. The same is true for scheduled backups, especially those which compress the files. Re-schedule these tasks to a time when the cpu is less likely to be busy, if possible - and also use the "nice" command to reduce their priority. (crontab and /etc/cron.daily/ are good places to start)

Reduce clutter on your PC. Don't run X unless you really need it, the GUI is a huge overhead in both memory and cpu.

More expensive options:

Increase RAM. If your system is having to use disk swap it will HUGELY impact performance in all areas. Again, htop is a good monitor - but first you need to understand that because Linux is using all the memory, it doesn't mean it needs it all - linux handles ram very differently to Windows/DOS and caches stuff. htop will show cached ram as a different colour in the memory graph. Also check that you're actually using a high memory capable kernel - many kernels don't enable high memory by default.

Faster CPU. Simple but effective. Zoneminder also works very well with multiple processor systems out of the box (if SMP is enabled in your kernel). The load of different cameras is spread across the processors.

Try building Zoneminder with processor specific instructions that are optimised to the system it will be running on, also increasing the optimisation level of GCC beyond -O2 will help.
<pre>
./configure CFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp" CXXFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp"
</pre>
The above command is optimised for an Athlon XP cpu so you will need to use the specific processor tag for your cpu, also the compiler optimisation has been increased to -O3.

You also need to put in your normal ./configure commands as if you were compiling with out this optimisation.

A further note is that the compile must be performed on the system that Zoneminder will be running on as this optimisation will make it hardware specific code.

Processor specific commands can be found in the GCC manual along with some more options that may increase performanc.
<pre>
http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
</pre>

The below command has been used to compile Zoneminder on a Athlon XP system running CentOS 5.5 and along with the libjpeg-turbo modification to reduce the CPU load in half, libjpeg-turbo reduced the load by 1/3 before the processor optimisation.
<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin CFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp" CXXFLAGS="-D__STDC_CONSTANT_MACROS -g -O3 -march=athlon-xp -mtune=athlon-xp" --enable-mmap --sysconfdir=/etc/zm
</pre>

The following command has been used to compile Zoneminder 1.25 on a CentOS 6.0 system, the native command should choose the processor automatically during compile time, this needs to be performed on the actual system!!.

<pre>
CFLAGS="-g -O3 -march=native -mtune=native" CXXFLAGS="-D__STDC_CONSTANT_MACROS -g -O3 -march=native -mtune=native" ./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=your_zm_user ZM_DB_PASS=your_zm_password ZM_SSL_LIB=openssl
</pre>

=== What about disks and bandwidth? ===

In most modern pc-based servers, disk I/O is more than adequate for the speeds involved in capturing from multiple cameras in most scenarios.

A typical 100mbit LAN will cope with most setups easily. If you're feeding from cameras over smaller or internet links, obviously fps will be much lower.

Disk and Bandwidth calculators are referenced on the Zoneminder wiki here: http://www.zoneminder.com/wiki/index.php/FAQ#How_much_Hard_Disk_Space_.2F_Bandwidth_do_I_need_for_ZM.3F

== Building ZoneMinder ==

=== When running configure I am getting a lot of messages about not being able to compile the ffmpeg libraries ===

If you see output from configure that looks like this

<pre>checking libavcodec/avcodec.h usability... no
checking libavcodec/avcodec.h presence... yes
configure: WARNING: libavcodec/avcodec.h: present but cannot be compiled
configure: WARNING: libavcodec/avcodec.h: check for missing
prerequisite headers?
configure: WARNING: libavcodec/avcodec.h: see the Autoconf documentation
configure: WARNING: libavcodec/avcodec.h: section "Present But
Cannot Be Compiled"
configure: WARNING: libavcodec/avcodec.h: proceeding with the compiler's
result
configure: WARNING: ## ------------------------------------- ##
configure: WARNING: ## Report this to support@zoneminder.com ##
configure: WARNING: ## ------------------------------------- ##</pre>

then it is caused not by the ZoneMinder build system but ffmpeg itself. However there is a workaround you can use which is to add

CPPFLAGS=-D__STDC_CONSTANT_MACROS

to the ZoneMinder ./configure command which should solve the issue. However this is not a proper 'fix' as such, which can only come from the ffmpeg project itself.

=== I cannot build ZoneMinder and am getting lots of undefined C++ template errors===

This is almost certainly due to the 'ccache' package which attempts to speed up compilation by caching compiled objects. Unfortunately one of the side effects is that it breaks the GNU g++ template resolution method that ZoneMinder uses in building by prevent files getting recompiled. The simplest way around this is to remove the ccache package using your distros package manager.

=== How do I build for X10 support? ===

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. Installing the perl module is covered in the README amongst other places but in summary, do:

perl -MCPAN -eshell
install X10::ActiveHome
quit

== Extending ZoneMinder ==

=== How can I get ZM to do different things at different times of day or week? ===
If you want to configure ZoneMinder to do motion detection during the day and just record at night, for example, you will need to use ZoneMinder 'run states'. 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. This will usually say 'Running' or 'Stopped'. You will then be able to save the current state and give it a name, 'Daytime' for example. Now configure your monitors how you would want them during other times of day and save that, for instance as 'Nighttime'.

Now you can switch between these two states by selecting them from the same dialog you saved them, or from the command line from issue the command ''zmpkg.pl <run state>'', for example ''zmpkg.pl Daytime''.

The final step you need to take, is scheduling the time the changes take effect. For this you can use [http://en.wikipedia.org/wiki/Cron cron]. A simple entry to change to the Daylight state at at 8am and to the nighttime state at 8pm would be as follows,
<pre>0 8 * * * root /usr/local/bin/zmpkg.pl Daytime
0 20 * * * root /usr/local/bin/zmpkg.pl Nighttime</pre>

On Ubuntu 7.04 and possibly others, look in /usr/bin not just /usr/local/bin for the zmpkg.pl file.

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.

For an alternative method of time controlling ZoneMinder, forum user 'voronwe' has created a more interactive calendar style integration. Details of this can be found in this [http://www.zoneminder.com/forums/viewtopic.php?t=6519 forum thread]. If you would like to find out more about this contribution please post on this thread.

=== How can I use ZoneMinder to trigger something else when there is an alarm? ===
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. Full details are in the README or by doing 'perldoc ZoneMinder', 'perldoc ZoneMinder::SharedMem' etc.
Below is an example script that checks all monitors for alarms and when one occurs, prints a message to the screen. You can add in your own code to make this reaction a little more useful.

<pre>#!/usr/bin/perl -w

use strict;

use ZoneMinder;

$| = 1;

zmDbgInit( "myscript", level=>0, to_log=>0, to_syslog=>0, to_term=>1 );

my $dbh = DBI->connect( "DBI:mysql:database=".ZM_DB_NAME.";host=".ZM_DB_HOST, ZM_DB_USER, ZM_DB_PASS );

my $sql = "select M.*, max(E.Id) as LastEventId from Monitors as M left join Events as E on M.Id = E.MonitorId where M.Function != 'None' group by (M.Id)";
my $sth = $dbh->prepare_cached( $sql ) or die( "Can't prepare '$sql': ".$dbh->errstr() );

my $res = $sth->execute() or die( "Can't execute '$sql': ".$sth->errstr() );
my @monitors;
while ( my $monitor = $sth->fetchrow_hashref() )
{
push( @monitors, $monitor );
}

while( 1 )
{
foreach my $monitor ( @monitors )
{
next if ( !zmMemVerify( $monitor ) );

if ( my $last_event_id = zmHasAlarmed( $monitor, $monitor->{LastEventId} ) )
{
$monitor->{LastEventId} = $last_event_id;
print( "Monitor ".$monitor->{Name}." has alarmed\n" );
#
# Do your stuff here
#
}
}
sleep( 1 );
}</pre>

==Trouble Shooting==
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.

===What logs should I check for errors?===
ZoneMinder creates its own logs and are usually located in the <tt>/tmp</tt> directory.

The ZoneMinder logs for the RPM packages are located in <tt>/var/log/zm</tt>.

Depending on your problem errors can show up in any of these logs but, usually the logs of interest are <tt>zmdc.log</tt> and <tt>zmpkg.log</tt> if ZM is not able to start.

Now since ZM is dependent on other components to work, you might not find errors in ZM but in the other components.
Other logs of interest are:<tt>
*/var/log/messages and/or /var/log/syslog
*/var/log/dmesg
*/var/log/httpd/error_log</tt> (RedHat/Fedora) or <tt>/var/log/apache2/error_log
*/var/log/mysqld.log</tt> (Errors here don't happen very often but just in case)

If ZM is not functioning, you should always be able to find an error in at least one of these logs. Use the [[tail]] command to get info from the logs. This can be done like so:

tail -f /var/log/messages /var/log/httpd/error_log /var/log/zm/zm*.log

This will append any data entered to any of these logs to your console screen (<tt>-f</tt>). To exit, hit [ctrl -c].

More verbose logging for the ZoneMinder binaries is available by enabling the debug option from the control panel and will be placed in the path you have configured for the debug logs. Output can be limited to a specific binary as described in the Debug options page under the "?" marks.

===How can I trouble shoot the hardware and/or software?===
Here are some commands to get information about your hardware. Some commands are distribution dependent.
* <tt>[[lspci]] -vv</tt> -- Returns lots of detailed info. Check for conflicting interrupts or port assignments. You can sometimes alter interrupts/ ports in bios. Try a different pci slot to get a clue if it is HW conflict (comand provided by the pciutils package).
* <tt>[[scanpci]] -v</tt> -- Gives you information from your hardware EPROM
* <tt>[[lsusb]] -vv</tt> -- Returns lots of detail about USB devices (camand provided by usbutils package).
* <tt>[[dmesg]]</tt> -- Shows you how your hardware initialized (or didn't) on boot-up. You will get the most use of this.
* <tt>[[v4l-info]]</tt> -- to see how driver is talking to card. look for unusual values.
* <tt>[[modinfo bttv]]</tt> -- some bttv driver stats.
* <tt>[[zmu]] -m 0 -q -v</tt> -- Returns various information regarding a monitor configuration.
* <tt>[[ipcs]] </tt> -- Provides information on the ipc facilities for which the calling process has read acccess.
* <tt>[[ipcrm]] </tt> -- The ipcrm command can be used to remove an IPC object from the kernel.
* <tt>cat /proc/interrupts</tt> -- This will dispaly what interrupts your hardware is using.

===Why is it that when monitoring a camera, the top portion of the image is cutoff and appears at the bottom of the image, with a line seperating the top from the bottom?===

=== Why am I getting a 403 access error with my web browser when trying to access http //localhost/zm? ===

The apache web server needs to have the right permissions and configuration to be able to read the Zoneminder files. Check the forums for solution, and edit the apache configuration and change directory permissions to give apache the right to read the Zoneminder files. Depending on your Zoneminder configuration, you would use the zm user and group that Zoneminder was built with, such as wwwuser and www.

=== Why am I getting broken images when trying to view events? ===

Zoneminder and the Apache web server need to have the right permissions. Check this forum topic and similar ones:
http://www.zoneminder.com/forums/viewtopic.php?p=48754#48754

===Why is the image from my color camera appearing in black and white?===
If you recently upgraded to zoneminder 1.26, there is a per camera option that defaults to black and white and can be mis-set if your upgrade didn't happen right. See this thread: http://www.zoneminder.com/forums/viewtopic.php?f=30&t=21344

This may occur if you have a NTSC analog camera but have configured the source in ZoneMinder as PAL for the Device Format under the source tab. You may also be mislead because zmu can report the video port as being PAL when the camera is actually NTSC. Confirm the format of your analog camera by checking it's technical specifications, possibly found with the packaging it came in, on the manufacturers website, or even on the retail website where you purchased the camera. Change the Device Format setting to NTSC and set it to the lowest resolution of 320 x 240. If you have confirmed that the camera itself is NTSC format, but don't get a picture using the NTSC setting, consider increasing the shared memory '''kernel.shmall''' and '''kernel.shmmax''' settings in /etc/sysctl.conf to a larger value such as 268435456. This is also the reason you should start with the 320x240 resolution, so as to minimize the potential of memory problems which would interfere with your attempts to troubleshoot the device format issue. Once you have obtained a picture in the monitor using the NTSC format, then you can experiment with raising the resolution.

===Why do I only see blue screens with a timestamp when monitoring my camera?===
If this camera is attached to a capture card, then you may have selected the wrong Device Source or Channel when configuring the monitor in the ZoneMinder console. If you have a capture card with 2 D-sub style inputs(looks like a VGA port) to which you attach a provided splitter that splits off multiple cables, then the splitter may be attached to the wrong port. For example, PV-149 capture cards have two D-sub style ports labeled as DB1 and DB2, and come packaged with a connector for one of these ports that splits into 4 BNC connecters. The initial four video ports are available with the splitter attached to DB1.

===Why do I only see black screens with a timestamp when monitoring my camera?===
In the monitor windows where you see the black screen with a timestamp, select settings and enter the Brightness, Contrast, Hue, and Color settings reported for the device by '''zmu -d <device_path> -q -v'''. 32768 may be appropriate values to try for these settings. After saving the settings, select Settings again to confirm they saved successfully.

===I am getting messages about a backtrace in my logs, what do I do?===
If you are seeing entries in your log like the following
<pre>Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6 [0x3347230210]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6(memset+0xce) [0x334727684e]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x40ee9a]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x419946]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x4213cf]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma(cos+0x35c) [0x404674]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6(__libc_start_main+0xf4) [0x334721da44]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma(cos+0xd1) [0x4043e9]]
Jan 11 20:25:22 localhost zma_m2[19051]: INF [Backtrace complete]</pre>
then you can help diagnose the problem by running a special command to translate the hex addresses into helpful information. This command is called addr2line and you can type 'man addr2line' for more information.
Basically addr2line takes two sets of parameters, the first is the name of the binary file, and the second is a list of addresses. Both of these pieces of information are displayed in the logs. The filename is the first part after the 'Backtrace:' tag, in this case /usr/local/bin/zma, though it may well be different in your case. Some of the lines refer to libraries rather than the zma executable but those can be ignored for now, the important part is noting which ZM binary is involved. The binary file is passed in following the -e flag. The addresses to pass to addr2line are those contained in the '[]' pairs. Again you can ignore those that are on a line that refers to a library but it will not hurt if you include them.
So in the example above, the command would be <pre>addr2line -e /usr/local/bin/zma 0x40ee9a 0x419946 0x4213cf 0x404674 0x4043e9</pre>
This should then dump out a more symbolic list containing source file names and line numbers, and it is this information which will be helpful if posted to the forums. Sometimes addr2line fails to produce useful output. This is usually because either the problem is so severe that it has corrupted the stack and prevented useful information from being displayed, or that you have either compiled ZM without the -g flag for debug, or you have stripped the binaries of symbol information after installation. This this case you would need to rebuild temporarily with debug enabled for the information to be useful.

This error some times happens when a linked camera looses its link or it is corrupted by the user or some other system event, try deleting the affected cameras and recreating them in the Zoneminder console.

===How do I repair the MySQL Database?===
There is two ways to go about this. In most cases you can run from the command prompt ->
* mysqlcheck --all-databases --auto-repair -p'''your_database_password''' -u '''your_databse_user'''

If that does not work then you will have to make sure that ZoneMinder is stopped then run the following (nothing should be using the database while running this and you will have to adjust for your correct path if it is different). ->
* myisamchk --silent --force --fast --update-state -O key_buffer=64M -O sort_buffer=64M -O read_buffer=1M -O write_buffer=1M /var/lib/mysql/*/*.MYI

===How do I repair the MySQL Database when the cli fails?===
In Ubuntu, the commands listed above do not seem to work. However, actually doing it by hand from within MySQL does. (But that is beyond the scope of this document) But that got me thinking... And phpmyadmin does work. Bring up a terminal.
sudo apt-get install phpmyadmin

Now go to http://zoneminder_IP/ and stop the ZM service. Continue to http://zoneminder_IP/phpmyadmin and select the zoneminder database. Select and tables marked 'in use' and pick the action 'repare' to fix. Restart the zoneminder service from the web browser. Remove or disable the phpmyadmin tool, as it is not always the most secure thing around, and opens your database wide to any skilled hacker.
sudo apt-get remove phpmyadmin

===I upgraded by distribution and ZM stopped working===
Some possibilties (Incomplete list and subject to correction)
#[[/usr/local/bin/zmfix: /usr/lib/libmysqlclient.so.15: version `MYSQL_5.0' not found (required by /usr/local/bin/zmfix)]] :: Solution: Recompile and reinstall Zoneminder.
Any time you update a major version that ZoneMinder depends on, you need to recompile ZoneMinder.

===Zoneminder doesn't start automatically on boot===
Check the list for log entries like "zmfix[766]: ERR [Can't connect to server: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)] ".
What can happen is that zoneminder is started too quickly after Mysql and tries to contact the database server before it's ready. Zoneminder gets no answer and aborts.
August 2010 - Ubuntu upgrades seem to be leaving several systems in this state. One way around this is to add a delay to the zoneminder startup script allowing Mysql to finish starting.
"Simply adding 'sleep 15' in the line above 'zmfix -a' in the /etc/init.d/zoneminder file fixed my ZoneMinder startup problems!" - credit to Pada.

=== Remote Path setup for Panasonic and other Camera ===
On adding or editing the source you can select the preset link for the parameters for the specified camera . In version 1.23.3 presets for BTTV,Axis,Panasonic,GadSpot,VEO, and BlueNet are available . Selecting the presets ZM fills up the required value for the remote path variable

=== Why do I get repeated/ mixed/unstable/ blank monitors on bt878-like cards (a.k.a. PICO 2000) ===

Please have a check at [[Pico2000]];

===What causes "Invalid JPEG file structure: two SOI markers" from zmc (1.24.x)===

Some settings that used to be global only are now per camera. On the Monitor Source tab, if you are using Remote Protocol "HTTP" and Remote Method "Simple", try changing Remote Method to "Regexp".

== Miscellaneous ==
=== I see ZoneMinder is licensed under the GPL. What does that allow or restrict me in doing with ZoneMinder? ===

The ZoneMinder license is described at the end of the documentation and consists of the following section

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty
of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

This means that ZoneMinder is licensed under the terms described [http://www.gnu.org/copyleft/gpl.html here]. There is a comprehensive FAQ covering the GPL at http://www.gnu.org/licenses/gpl-faq.html but in essence you are allowed to redistribute or modify GPL licensed software provided that you release your distribution or modifications freely under the same terms. You are allowed to sell systems based on GPL software. You are not allowed to restrict or reduce the rights of GPL software in your distribution however. Of course if you are just making modifications for your system locally you are not releasing changes so you have no obligations in this case. I recommend reading the GPL FAQ for more in-depth coverage of this issue.

=== Can I use ZoneMinder as part of my commercial product? ===

The GPL license allows you produce systems based on GPL software provided your systems also adhere to that license and any modifications you make are also released under the same terms. The GPL does not permit you to include ZoneMinder in proprietary systems (see http://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem for details). If you wish to include ZoneMinder in this kind of system then you will need to license ZoneMinder under different terms. This is sometimes possible and you will need to contact me for further details in these circumstances.

FAQ

2015-04-04T14:36:56Z

Knnniggett: /* Why does ZM stop recording once I have 32000 events for my monitor? */

== ZoneMinder Frequently Asked Questions ==

This is the FAQ page. Feel free to contribute any FAQs that you think are missing.

===How can I stop ZoneMinder filling up my disk?===

Recent versions of ZoneMinder come with a filter you can use for this purpose already included. However '''by default it is not enabled for event deletion'''.

The filter is called ''PurgeWhenFull'' and to find it, choose one of the event counts from the console page, for instance events in the last hour, for one of your monitors.

This will bring up an event listing and a filter window.

In the filter window there is a drop down select box labeled 'Use Filter', that lets your select a saved filter. Select 'PurgeWhenFull' and it will load that filter.

Make any modifications you might want, such as the percentage full you want it to kick in, or how many events to delete at a time (it will repeat the filter as many times as needed to clear the space, but will only delete this many events each time to get there).

Then click on 'Save' which will bring up a new window. Make sure the 'Automatically delete' box is checked and press save to save your filter. This will then run in the background to keep your disk within those limits.

After you've done that, you changes will automatically be loaded into zmfilter within a few minutes.

Check the <tt>zmfilter.log</tt> file to make sure it is running as sometimes missing perl modules mean that it never runs but people don't always realize.

PURGE BY AGE

To delete events that are older than 7 days, create a new filter with "Date" set to "less than" and a value of "-7 days", sort by "date/time" in "asc"ending order, then enable the checkbox "delete all matches". You can also use a value of week or week and days: "-2 week" or "-2 week 4 day"

Save with 'Run Filter In Background' enabled to have it run automatically.

Optional skip archived events: click on the plus sign next to -7 days to add another condition. "and" "archive status" equal to "unarchived only".

Optional slow delete: limit the number of results to 3. If you have a large backlog of events that would be deleted, this can hard spike the CPU usage for a long time. Limiting the number of results to only the first three each time the filter is run spreads out the delete processes over time, dramatically lessening the CPU load.

There are two methods for ZM to remove files when they are deleted that can be found in Options under the System tab ZM_OPT_FAST_DELETE and ZM_RUN_AUDIT.

ZM_OPT_FAST_DELETE:

Normally an event created as the result of an alarm consists of entries in one or more database tables plus the various files associated with it. When deleting events in the browser it can take a long time to remove all of this if your are trying to do a lot of events at once. It is recommended that you set this option which means that the browser client only deletes the key entries in the events table, which means the events will no longer appear in the listing, and leaves the zmaudit daemon to clear up the rest later.

ZM_RUN_AUDIT:

The zmaudit daemon exists to check that the saved information in the database and on the file system match and are consistent with each other. If an error occurs or if you are using 'fast deletes' it may be that database records are deleted but files remain. In this case, and similar, zmaudit will remove redundant information to synchronize the two data stores. This option controls whether zmaudit is run in the background and performs these checks and fixes continuously. This is recommended for most systems however if you have a very large number of events the process of scanning the database and file system may take a long time and impact performance. In this case you may prefer to not have zmaudit running unconditionally and schedule occasional checks at other, more convenient, times.

ZM_AUDIT_CHECK_INTERVAL:

The zmaudit daemon exists to check that the saved information in the database and on the files system match and are consistent with each other. If an error occurs or if you are using 'fast deletes' it may be that database records are deleted but files remain. In this case, and similar, zmaudit will remove redundant information to synchronize the two data stores. The default check interval of 900 seconds (15 minutes) is fine for most systems however if you have a very large number of events the process of scanning the database and file system may take a long time and impact performance. In this case you may prefer to make this interval much larger to reduce the impact on your system. This option determines how often these checks are performed.

===What does a 'Can't shmget: Invalid argument' error in my logs mean? and my cameras won't display video at higher resolutions.===

This error is discussed in the README in the following excerpt:-
''...this is caused by an attempt to allocate an amount of shared memory greater than your system can handle. The size it requests is based on the following formula, <tt>ring buffer size x image width x image height x 3 (for 24 bit images) + a bit of overhead</tt>.

So, for example:
<pre>384x288 capture resolution, that makes: 110 592 pixels
in 24 bit color that's x24 = 2 654 208 bits per frame
by 80 frames ring buffer x80 = 212 336 640 bits per camera
by 4 cameras x4 = 849 346 560 bits.
Plus 10% overhead = 934 281 216 bits
That's 116 785 152 bytes, and
= 114 048 kB, respectively 111.38 MB.
If my shared memory is set to 134 217 728, which is exactly 128MB,
that means I shouldn't have any problem.
(Note that 1 byte = 8 bits and 1kbyte = 1024bytes, 1MB = 1024 kB)</pre>

If for instance you were using 24bit 640x480 then this would come to about 92Mb if you are using the default buffer size of 100. If this is too large then you can either reduce the image or buffer sizes or increase the maximum amount of shared memory available. If you are using RedHat then you can get details on how to change these settings at http://www.redhat.com/docs/manuals/database/RHDB-2.1-Manual/admin_user/kernel-resources.html .

You should be able to use a similar procedure with other distributions to modify the shared memory pool without kernel recompilations though in some cases this may be necessary. Note, this error also sometimes occurs if you have an old shared memory segment lying around from a previous run that is too small. Use the ipcs and ipcrm system commands to check and remove it if necessary.'"

You can often find out how many 4KB shared memory pages are available by typing the following :-
<pre># cat /proc/sys/kernel/shmall
2097152</pre>

In recent kernels the shmall is set to 2097152 memory pages multiplied by 4096 bytes per page for a total of 8 GB of shared memory available. You only need to increase the shmall value if you have a computer with more than 8GB of memory and wish to use more of it for shared memory usage, such as large databases.

The most shared memory bytes you can allocate in one go :-
<pre># cat /proc/sys/kernel/shmmax
33554432</pre>

In recent kernels the shmmax is set to 33554432 bytes for only 32 MB of maximum shared memory allocatable at a time, hardly enough for ZoneMinder to go above 320 x 240 x 24-bit resolution at 40 frames in the buffer if it is using the /dev/shm shared memory device, so this value needs to be increased. If you are using ZoneMinder with the memory mapped (mmap) compile time option then this doesn't affect you.

To change the value to 128 MB temporarily during this kernel execution type (for example) :-
<pre>echo 536870912 >/proc/sys/kernel/shmmax</pre>

'''Be sure to restart ZoneMinder after this.'''
However be aware that sometimes you will only need to change the shmmax value as shmall is often large enough. Also changing these values in this way is only effective until your machine is rebooted.

To change them permanently you will need to edit <tt>/etc/sysctl.conf</tt> and add the following lines (for example) :-
<pre>kernel.shmmax = 536870912</pre>

Or if your distribution has the <tt>/etc/sysctl.d/</tt> folder you can create a file in this folder without modifying the <tt>/etc/sysctl.d</tt> so you won't lose the changes during distro upgrades :-
<pre>echo kernel.shmmax = 536870912 >/etc/sysctl.d/60-kernel-shm.conf</pre>

To load these settings in the sysctl.conf file type:
<pre>sysctl -p</pre>

To check your shared memory settings type:
<pre>ipcs -l</pre>

Note that with Megapixel cameras like the Axis 207mw becoming cheaper and more attractive, the above memory settings are not adequate. To get Zoneminder working with a full 1280x1024 resolution camera in full color, increase <tt>134217728</tt> (128 MB) to, for example, <tt>268435456</tt> (256 MB) and multiple this value by each camera.

These changes will now also be set the next time your machine is restarted.

Versions 1.24.x of ZoneMinder also allows you to use an alternate method of shared memory allocation, [http://en.wikipedia.org/wiki/Mmap mapped memory]. This requires less configuration and can be simpler to use. Mapped memory allows you to use a special type of file as the placeholder for your memory and this file is 'mapped' into memory space for easy and fast access.

To enable mapped memory in ZoneMinder you need add add the --enable--mmap=yes switch to your configure line. By default mapped memory files are created in /dev/shm which on most distributions is a dedicated pseudo-partition containing memory formatted as a filesystem. If your system uses a different path then this can be changed in ZoneMinder in Options->paths->PATH_MAP. It uses a filesystem type called [http://en.wikipedia.org/wiki/Tmpfs tmpfs]. If you type 'df -h' you should see this area and the size of memory it currently allows. To increase size for tmpfs you need to edit /etc/default/tmpfs. Search for:
<pre>SHM_SIZE=128M</pre>
and change to something like
<pre>SHM_SIZE=1G</pre>
then reboot the system. You could possibly need to change RUN_SIZE, too.

It is important that you do not use a disk based filesystem for your memory mapped files as this will cause memory access to be extremely slow. ZoneMinder creates files called .zm.mmap.<monitor id> in the mapped memory filesystem.

Mapped memory is subject to the same limitations in terms of total memory as using more traditional shared memory but does not require any configuration per allocation or chunk. In future versions of ZoneMinder this will be the default shared memory storage method.

<div id="AlternateSharedMemory" style="width:80%; border:2px solid #8a8588; background:#faf5ff; vertical-align:top; margin-top: 6px; padding: 4px;">
Another good article about shared memory settings http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.uprun.doc/doc/t0008238.htm .
It made a statement that conflicted with those in the Redhat article but they fixed a [http://www.zoneminder.com/forums/viewtopic.php?t=9692 long standing memory issue on FC6], so give them a try.

'''The essential difference was that the kernel.shmall setting is NOT in a direct memory setting in KB but in pages of memory. it is Max Pages of memory'''

'''For example:''' If you want to allocate a maximum memory setting to 8GB you have to convert it to the number of pages (or segments).
with a page size of 4096.
*kernel.shmall = 8000x1024x1024/4096
<pre>kernel.shmall = 2097152</pre>
NOT 8388608000 as would be suggested in the RedHat article linked above.

shmmax is the max amount to allocate in one request -
this is is an actual memory size (as opposed to pages) set to 4GB
<pre>kernel.shmmax = 4294967296</pre>

The <tt>/etc/sysctl.conf</tt> would have these lines
<pre>kernel.shmall = 2097152
kernel.shmmax = 4294967296</pre>

As above, reload your sysctl.conf with <tt>sysctl -p</tt> and check that the settings are correct with <tt>ipcs -l</tt>.
</div>

===I have enabled motion detection but it is not always being triggered when things happen in the camera view===

ZoneMinder uses zones to examine images for motion detection. When you create the initial zones you can choose from a number of preset values for sensitivity etc. Whilst these are usually a good starting point they are not always suitable for all situations and you will probably need to tweak the values for your specific circumstances. The meanings of the various settings are described in the documentation (http://www.zoneminder.com/wiki/index.php/Documentation#Defining_Zones) however if you believe you have sensible settings configured then there are two diagnostic approaches you can use.

====Event Statistics====
The first technique is to use event statistics. Firstly you should ensure they are switched on in Options->Logging->RECORD_EVENT_STATS. This will then cause the raw motion detection statistics for any subsequently generated events to be written to the DB. These can then be accessed by first clicking on the Frames or Alarm Frames values of the event from any event list view in the web gui. Then click on the score value to see the actual values that caused the event. Alternatively the stats can be accessed by clicking on the 'Stats' link when viewing any individual frame. The values displayed there correspond with the values that are used in the zone configuration and give you an idea of what 'real world' values are being generated.

Note that if you are investigating why events 'do not' happen then these will not be saved and so won't be accessible. The best thing to do in that circumstance is to make your zone more sensitive so that it captures all events (perhap even ones you don't want) so you can get an idea of what values are being generated and then start to adjust back to less sensitive settings if necessary. You should make sure you test your settings under a variety of lighting conditions (e.g. day and night, sunny or dull) to get the best feel for that works and what doesn't.

Using statistics will slow your system down to a small degree and use a little extra disk space in the DB so once you are happy you can switch them off again. However it is perfectly feasible to keep them permanently on if your system is able to cope which will allow you to review your setting periodically.

====Diagnostic Images====
The second approach is to use diagnostic images which are saved copies of the intermediate images that ZM uses when determining motion detection. These are switched on and off using Options->Logging->RECORD_DIAG_IMAGES.

There are two kinds of diagnostic images which are and are written (and continuously overwritten) to the top level monitor event directory. If an event occurs then the files are additionally copied to the event directory and renamed with the appropriate frame number as a prefix.

The first set are produced by the monitor on the image as a whole. The diag-r.jpg image is the current reference image against which all individual frames are compared and the diag-d.jpg image is the delta image highlighting the difference between the reference image and the last analysed image. In this images identicial pixels will be black and the more different a pixel is the whiter it will be. Viewing this image and determining the colour of the pixels is a good way of getting a feel for the pixel differences you might expect (often more than you think).

The second set of diag images are labelled as diag-<zoneid>-<stage>.jpg where zoneid is the id of the zone in question (Smile) and the stage is where in the alarm check process the image is generated from. So if you have several zones you can expect to see multiple files. Also these files are only interested in what is happening in their zone only and will ignore anything else outside of the zone. The stages that each number represents are as follows,

# Alarmed Pixels - This image shows all pixels in the zone that are considered to be alarmed as white pixels and all other pixels as black.
# Filtered Pixels - This is as stage one except that all pixels removed by the filters are now black. The white pixels represent the pixels that are candidates to generate an event.
# Raw Blobs - This image contains all alarmed pixels from stage 2 but aggrageted into blobs. Each blob will have a different greyscale value (between 1 and 254) so they can be difficult to spot with the naked eye but using a colour picker or photoshop will make it easier to see what blob is what.
# Filtered Blobs - This image is as stage 3 but under (or over) sized blobs have been removed. This is the final step before determining if an event has occurred, just prior to the number of blobs being counted. Thus this image forms the basis for determining whether an event is generated and outlining on alarmed images is done from the blobs in this image.

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.

===Why can't ZoneMinder capture images (either at all or just particularly fast) when I can see my camera just fine in xawtv or similar?===

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 6-10fps for two, 1-4fps for three and 1-2 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.

When using xawtv etc to view the stream you are not looking at an image captured using the frame grabber but the card's video memory mapped onto your screen. 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.

===Why can't I see streamed images when I can see stills in the Zone window etc?===

This issue is normally down to one of two causes

1) You are using Internet Explorer and are trying to view multi-part jpeg streams. IE does not support these streams directly, unlike most other browsers. You will need to install Cambozola or another multi-part jpeg aware pluging to view them. To do this you will need to obtain the applet from the Downloads page and install the cambozola.jar file in the same directly as the ZoneMinder php files. Then find the ZoneMinder Options->Images page and enable ZM_OPT_CAMBOZOLA and enter the web path to the .jar file in ZM_PATH_CAMBOZOLA. This will ordinarily just be cambozola.jar. Provided (Options / B/W tabs) WEB_H_CAN_STREAM is set to auto and WEB_H_STREAM_METHOD is set to jpeg then Cambozola should be loaded next time you try and view a stream.

'''NOTE''': If you find that the Cambozola applet loads in IE but the applet just displays the version # of Cambozola and the author's name (as opposed to seeing the streaming images), you may need to chmod (''-rwxrwxr-x'') your (''usr/share/zoneminder/'') cambozola.jar:

$ sudo chmod 775 cambozola.jar

Once I did this, images started to stream for me.

2) The other common cause for being unable to view streams is that you have installed the ZoneMinder cgi binaries (zms and nph-zms) in a different directory than your web server is expecting. Make sure that the --with-cgidir option you use to the ZoneMinder configure script is the same as the CGI directory configure for your web server. If you are using Apache, which is the most common one, then in your httpd.conf file there should be a line like <pre>ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"</pre> where the last directory in the quotes is the one you have specified. If not then change one or the other to match. Be warned that configuring apache can be complex so changing the one passed to the ZoneMinder configure (and then rebuilding and reinstalling) is recommended in the first instance. If you change the apache config you will need to restart apache for the changes to take effect. If you still cannot see stream reliably then try changing Options->Paths->ZM_PATH_ZMS to just use zms if nph-zms is specified, or vice versa. Also check in your apache error logs.

===I have several monitors configured but when I load the Montage view in FireFox why can I only see two? or, Why don't all my cameras display when I use the Montage view in FireFox?===

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.

To resolve this situation, follow the instructions below:

<pre>Enter about:config in the address bar

scroll down to
browser.cache.check_doc_frequency 3
change the 3 to a 1

browser.cache.disk.enable True -> False
network.http.max-connections-per-server -> put a value of 100
network.http.max-persistent-connections-per-proxy -> 100 again
network.http.max-persistent-connections-per-server -> 100 again
</pre>

===Why is ZoneMinder using so much CPU?===

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.

The main causes are.

# Using a video palette other than greyscale or RGB24. This can cause a relatively minor performace hit, though still significant. Although some cameras and cards require using planar palettes ZM currently doesn't support this format internally and each frame is converted to an RGB representation prior to processing. Unless you have compelling reasons for using YUV or reduced RGB type palettes such as hitting USB transfer limits I would experiment to see if RGB24 or greyscale is quicker. Put your monitors into 'Monitor' mode so that only the capture daemons are running and monitor the process load of these (the 'zmc' processes) using top. Try it with various palettes to see if it makes a difference.
# Big image sizes. A image of 640x480 requires at least four times the processing of a 320x240 image. Experiment with different sizes to see what effect it may have. Sometimes a large image is just two interlaced smaller frames so has no real benefit anyway. This is especially true for analog cameras/cards as image height over 320 (NTSC) or 352 PAL) are invariably interlaced.
# Capture frame rates. Unless there's a compelling reason in your case there is often little benefit in running cameras at 25fps when 5-10fps would often get you results just as good. Try changing your monitor settings to limit your cameras to lower frame rates. You can still configure ZM to ignore these limits and capture as fast as possible when motion is detected.
# Run function. Obviously running in Record or Mocord modes or in Modect with lots of events generates a lot of DB and file activity and so CPU and load will increase.
# Basic default detection zones. By default when a camera is added one detection zone is added which covers the whole image with a default set of parameters. If your camera covers a view in which various regions are unlikely to generate a valid alarm (ie the sky) then I would experiment with reducing the zone sizes or adding inactive zones to blank out areas you don't want to monitor. Additionally the actual settings of the zone themselves may not be optimal. When doing motion detection the number of changed pixels above a threshold is examined, then this is filter, then contiguous regions are calculated to see if an alarm is generated. If any maximum or minimum threshold is exceeded according to your zone settings at any time the calculation stops. If your settings always result in the calculations going through to the last stage before being failed then additional CPU time is used unnecessarily. Make sure your maximum and minimumzone thresholds are set to sensible values and experiment by switching RECORD_EVENT_STATS on and seeing what the actual values of alarmed pixels etc are during sample events.
# Optimise your settings. After you've got some settings you're happy with then switching off RECORD_EVENT_STATS will prevent the statistics being written to the database which saves some time. Other settings which might make a difference are ZM_FAST_RGB_DIFFS, ZM_OPT_FRAME_SERVER and the JPEG_xxx_QUALITY ones.

I'm sure there are other things which might make a difference such as what else you have running on the box and memory sizes (make sure there's no swapping going on). 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. Having said that I also don't always know why you get certains results from 'top'. For instance if I have a 'zma' daemon running for a monitor that is capturing an image. I've commented out the actual analysis so all it's doing is blending the image with the previous one. In colour mode this takes ~11 milliseconds per frame on my system and the camera is capturing at ~10fps. Using 'top' this reports the process as using ~5% of CPU and permanently in R(un) state. Changing to greyscale mode the blending takes ~4msec (as you would expect as this is roughly a third of 11) but top reports the process as now with 0% CPU and permanently in S(leep) state. So an actual CPU resource usage change of a factor of 3 causes huge differences in reported CPU usage. I have yet to get to the bottom of this but I suspect it's to do with scheduling somewhere along the line and that maybe the greyscale processing will fit into one scheduling time slice whereas the colour one won't but I have no evidence of this yet!

===Why is the timeline view all messed up?===

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.

===How much Hard Disk Space / Bandwidth do I need for ZM?===
Please see [http://www.jpwilson.eu/ZM_Utils/ZM%20storage%20calc%20sheet.xls Storage Calc] in excel format

Or go to [http://www.axis.com/products/video/design_tool/index.htm 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 320x240 storing 1 fps except during alarm events. After 1 week 60GB of space in the volume where the events are stored (/var/www/html/zm) has been used.

===When I try and run ZoneMinder I get lots of audit permission errors in the logs and it won't start===
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 ([http://en.wikipedia.org/wiki/Selinux]).
If you are seeing entries in your system log like:

Jun 11 20:44:02 kernel: audit(1150033442.443:226): avc: denied { read } for pid=5068
comm="uptime" name="utmp" dev=dm-0 ino=16908345 scontext=user_u:system_r:httpd_sys_script_t
tcontext=user_u:object_r:initrc_var_run_t tclass=file

then it is likely that your system has SELinux enabled and it is preventing ZoneMinder from performaing certain activities. You then have two choices. You can either tune SELinux to permit the required operations or you can disable SELinux entirely which will permit ZoneMinder to run unhindered. Disabling SELinux is usually performed by editing its configuration file (e.g., <tt>/etc/selinux/config</tt>) and then rebooting. 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.

=== How do I enable ZoneMinder's security? ===
In the console, click on Options. Check the box next to "ZM_OPT_USE_AUTH". You will immediately be asked to login. The username is 'admin' and the password is 'admin'.

'''To Manage Users:''' 
In main console, go to '''Options->Users'''.

* You may also consider to use the web server security, for example, htaccess files under Apache scope; You may even use this as an additional/redundant security on top of Zoneminders built-in security features;

=== Why does ZM stop recording once I have 32000 events for my monitor? ===
ZM_USE_DEEP_STORAGE is now the default for new ZoneMinder systems so this limitation should only apply to users upgrading from a previous version of ZoneMinder.

This is a limitation of the ext3 filesystem that most Linux distributions use. One directory cannot hold more than 32k approx files.

Version of ZM from 1.23.0 onwards allow you to have a deeper filesystem with fewer files per individual directory. As well as not being susceptible to the 32k limit this is also somewhat faster.

If you have upgraded from a previous version of ZoneMinder and are considering enabling this option, it is very important to follow the steps below. Failure to properly follow these steps WILL RESULT IN LOSS OF YOUR DATA!

# Stop ZoneMinder
# Backup your event data and the dB if you have the available storage
# Enable USE_DEEP_STORAGE under Options.
# From the command line, run "sudo zmupdate.pl --migrate-events"
# Monitor the output for any events that fail to convert.
# After the conversion completes, you can restart ZoneMinder

Note that you can re-run the migrate-events command if any error messages scroll off the screen.

You can read about the lack of a limit in the number of
sub-directories in the ext4 filesystem at:
http://kernelnewbies.org/Ext4
and see what tools may assist in your use of this filesystem in:
http://ext4.wiki.kernel.org/index.php/Ext4_Howto
Note that while GParted 0.5.2 recognizes ext4 partitions, at least in
some circumstances it does not succeed in formatting a partition for
the ext4 filesystem. Also, if you search for ext3 or reiserfs on the
forums you will find various threads on this issue with guidance on
how to convert.

== Managing system load ''(with IP Cameras in mind)'' ==

=== Introduction ===
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.
3. Comparing the zoned selections to the previous image or images and applying rules.
4. If in alarm state, writing that image to the disk and updating the mysql database.

If you're capturing at five frames per second, the above is repeated five times every second, multiplied by the number of cameras. 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.

=== How do I know if my computer is overloaded? ===
If your CPU is running at 100% all the time, it's probably overloaded (or running at exact optimisation). If the load is consistently high (over 10.0 for a single processor) then Bad Things happen - like lost frames, unrecorded events etc. Occasional peaks are fine, normal and nothing to worry about.

Zoneminder runs on Linux, Linux measures system load using "load", which is complicated but gives a rough guide on what the computer is doing at any given time. Zoneminder shows Load on the main page (top right) as well as disk space. Typing "uptime" on the command line will give a similar guide, but with three figures to give a fuller measure of what's happening over a period of time but for the best guide to see what's happening, install "htop" - which gives easy to read graphs for load, memory and cpu usage.

A load of 1.0 means the processor has "just enough to do right now". Also worth noting that a load of 4.0 means exactly the same for a quad processor machine - each number equals a single processor's workload. A very high load can be fine on a computer that has a stacked workload - such as a machine sending out bulk emails, or working its way through a knotty problem; it'll just keep churning away until it's done. However - Zoneminder needs to process information in real time so it can't afford to stack its jobs, it needs to deal with them right away.

For a better and full explanation of Load: http://en.wikipedia.org/wiki/Load_%28computing%29

=== My load is too high, how can I reduce it? ===
Zoneminder is /very/ tweakable and it's possible to tune it to compromise. The following are good things to try, in no particular order;

Change the jpeg libraries. In most distributions Linux uses standard jpeg libraries which although fine for most things, don't use the MMX functions in nearly all modern processors. Check whether your cpu supports mmx by running "cpuid |grep MMX" which should give you a line or two along the lines of "MMX instructions". If so, give the libs a try. Most people report their load halves simply by using these libs. You may be able to experience substantial Zoneminder performance boosts now by merely upgrading your operating system, without having to download libraries and compile your own binaries, etc. as described in the forum thread linked below. Some distributions, e.g. Fedora 14 now include library code to utilize the instruction set extensions available in your processor:

http://fedoraproject.org/wiki/Fedora_14_Alpha_release_notes#Faster_JPEG_Compression.2FDecompression

"The replacement of libjpeg with libjpeg-turbo brings speed improvements to a wide range of applications when handling images in JPEG format ..."

http://fedoraproject.org/wiki/Releases/14/Schedule

still states "2010-11-02 final release".

CentOS 6.4 now has libjpeg-turbo built in as the default jpeg library allowing the best results out of the box.

http://libjpeg-turbo.virtualgl.org/

provides some history on its project page. If you seek confirmation for which library is in use, you may consider querying e.g. while running on a prior distribution:
<pre>
[u@who ~]$ rpm -q --whatprovides libjpeg
libjpeg-6b-46.fc12.i686
[u@who ~]$
</pre>
and comparing the response to querying when the higher-performance library is available:
<pre>
[u@who ~]$ rpm -q --whatprovides libjpeg
libjpeg-turbo-1.0.1-1.fc14.x86_64
[u@who ~]$
</pre>
As noted in other forum postings, some zoneminder camera and usage configurations may not make much use of jpeg processing (e.g. some webcams), and thus obtain little performance benefit. Otherwise, you should be able to select one or more of:
* running more cameras,
* running existing cameras at higher image resolutions,
* running cameras at a faster frame rate,
* saving MoDect images with higher quality,
* having more CPU cycles available for any non-Zoneminder workload, etc.

http://www.zoneminder.com/forums/viewtopic.php?t=6419 gives more info on the download-the-library-yourself, compile-your-own-Zoneminder binary, etc. approach if needed. Nobody's posted there to say it broke their system... Yet.

If your camera allows you to change image size, think whether you can get away with smaller images. Smaller pics = less load. 320x240 is usually ok for close-up corridor shots.

Go Black and White. Colour pictures use twice to three times the CPU, memory and diskspace but give little benefit to identification.

Reduce frames per second. Halve the fps, halve the workload. If your camera supports fps throttling (Axis do), try that - saves ZM having to drop frames from a stream. 2-5 fps seems to be widely used.

Experiment with using jpeg instead of mjpeg. Some users have reported it gives better performance, but YMMV.

Tweak the zones. Keep them as small and as few as possible. Stick to one zone unless you really need more.

Schedule. If you are running a linux system at near capacity, you'll need to think carefully about things like backups and scheduled tasks. updatedb - the process which maintains a file database so that 'locate' works quickly, is normally scheduled to run once a day and if on a busy system can create a heavy increase on the load. The same is true for scheduled backups, especially those which compress the files. Re-schedule these tasks to a time when the cpu is less likely to be busy, if possible - and also use the "nice" command to reduce their priority. (crontab and /etc/cron.daily/ are good places to start)

Reduce clutter on your PC. Don't run X unless you really need it, the GUI is a huge overhead in both memory and cpu.

More expensive options:

Increase RAM. If your system is having to use disk swap it will HUGELY impact performance in all areas. Again, htop is a good monitor - but first you need to understand that because Linux is using all the memory, it doesn't mean it needs it all - linux handles ram very differently to Windows/DOS and caches stuff. htop will show cached ram as a different colour in the memory graph. Also check that you're actually using a high memory capable kernel - many kernels don't enable high memory by default.

Faster CPU. Simple but effective. Zoneminder also works very well with multiple processor systems out of the box (if SMP is enabled in your kernel). The load of different cameras is spread across the processors.

Try building Zoneminder with processor specific instructions that are optimised to the system it will be running on, also increasing the optimisation level of GCC beyond -O2 will help.
<pre>
./configure CFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp" CXXFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp"
</pre>
The above command is optimised for an Athlon XP cpu so you will need to use the specific processor tag for your cpu, also the compiler optimisation has been increased to -O3.

You also need to put in your normal ./configure commands as if you were compiling with out this optimisation.

A further note is that the compile must be performed on the system that Zoneminder will be running on as this optimisation will make it hardware specific code.

Processor specific commands can be found in the GCC manual along with some more options that may increase performanc.
<pre>
http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
</pre>

The below command has been used to compile Zoneminder on a Athlon XP system running CentOS 5.5 and along with the libjpeg-turbo modification to reduce the CPU load in half, libjpeg-turbo reduced the load by 1/3 before the processor optimisation.
<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin CFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp" CXXFLAGS="-D__STDC_CONSTANT_MACROS -g -O3 -march=athlon-xp -mtune=athlon-xp" --enable-mmap --sysconfdir=/etc/zm
</pre>

The following command has been used to compile Zoneminder 1.25 on a CentOS 6.0 system, the native command should choose the processor automatically during compile time, this needs to be performed on the actual system!!.

<pre>
CFLAGS="-g -O3 -march=native -mtune=native" CXXFLAGS="-D__STDC_CONSTANT_MACROS -g -O3 -march=native -mtune=native" ./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=your_zm_user ZM_DB_PASS=your_zm_password ZM_SSL_LIB=openssl
</pre>

=== What about disks and bandwidth? ===

In most modern pc-based servers, disk I/O is more than adequate for the speeds involved in capturing from multiple cameras in most scenarios.

A typical 100mbit LAN will cope with most setups easily. If you're feeding from cameras over smaller or internet links, obviously fps will be much lower.

Disk and Bandwidth calculators are referenced on the Zoneminder wiki here: http://www.zoneminder.com/wiki/index.php/FAQ#How_much_Hard_Disk_Space_.2F_Bandwidth_do_I_need_for_ZM.3F

== Building ZoneMinder ==

=== When running configure I am getting a lot of messages about not being able to compile the ffmpeg libraries ===

If you see output from configure that looks like this

<pre>checking libavcodec/avcodec.h usability... no
checking libavcodec/avcodec.h presence... yes
configure: WARNING: libavcodec/avcodec.h: present but cannot be compiled
configure: WARNING: libavcodec/avcodec.h: check for missing
prerequisite headers?
configure: WARNING: libavcodec/avcodec.h: see the Autoconf documentation
configure: WARNING: libavcodec/avcodec.h: section "Present But
Cannot Be Compiled"
configure: WARNING: libavcodec/avcodec.h: proceeding with the compiler's
result
configure: WARNING: ## ------------------------------------- ##
configure: WARNING: ## Report this to support@zoneminder.com ##
configure: WARNING: ## ------------------------------------- ##</pre>

then it is caused not by the ZoneMinder build system but ffmpeg itself. However there is a workaround you can use which is to add

CPPFLAGS=-D__STDC_CONSTANT_MACROS

to the ZoneMinder ./configure command which should solve the issue. However this is not a proper 'fix' as such, which can only come from the ffmpeg project itself.

=== I cannot build ZoneMinder and am getting lots of undefined C++ template errors===

This is almost certainly due to the 'ccache' package which attempts to speed up compilation by caching compiled objects. Unfortunately one of the side effects is that it breaks the GNU g++ template resolution method that ZoneMinder uses in building by prevent files getting recompiled. The simplest way around this is to remove the ccache package using your distros package manager.

=== How do I build for X10 support? ===

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. Installing the perl module is covered in the README amongst other places but in summary, do:

perl -MCPAN -eshell
install X10::ActiveHome
quit

== Extending ZoneMinder ==

=== How can I get ZM to do different things at different times of day or week? ===
If you want to configure ZoneMinder to do motion detection during the day and just record at night, for example, you will need to use ZoneMinder 'run states'. 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. This will usually say 'Running' or 'Stopped'. You will then be able to save the current state and give it a name, 'Daytime' for example. Now configure your monitors how you would want them during other times of day and save that, for instance as 'Nighttime'.

Now you can switch between these two states by selecting them from the same dialog you saved them, or from the command line from issue the command ''zmpkg.pl <run state>'', for example ''zmpkg.pl Daytime''.

The final step you need to take, is scheduling the time the changes take effect. For this you can use [http://en.wikipedia.org/wiki/Cron cron]. A simple entry to change to the Daylight state at at 8am and to the nighttime state at 8pm would be as follows,
<pre>0 8 * * * root /usr/local/bin/zmpkg.pl Daytime
0 20 * * * root /usr/local/bin/zmpkg.pl Nighttime</pre>

On Ubuntu 7.04 and possibly others, look in /usr/bin not just /usr/local/bin for the zmpkg.pl file.

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.

For an alternative method of time controlling ZoneMinder, forum user 'voronwe' has created a more interactive calendar style integration. Details of this can be found in this [http://www.zoneminder.com/forums/viewtopic.php?t=6519 forum thread]. If you would like to find out more about this contribution please post on this thread.

=== How can I use ZoneMinder to trigger something else when there is an alarm? ===
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. Full details are in the README or by doing 'perldoc ZoneMinder', 'perldoc ZoneMinder::SharedMem' etc.
Below is an example script that checks all monitors for alarms and when one occurs, prints a message to the screen. You can add in your own code to make this reaction a little more useful.

<pre>#!/usr/bin/perl -w

use strict;

use ZoneMinder;

$| = 1;

zmDbgInit( "myscript", level=>0, to_log=>0, to_syslog=>0, to_term=>1 );

my $dbh = DBI->connect( "DBI:mysql:database=".ZM_DB_NAME.";host=".ZM_DB_HOST, ZM_DB_USER, ZM_DB_PASS );

my $sql = "select M.*, max(E.Id) as LastEventId from Monitors as M left join Events as E on M.Id = E.MonitorId where M.Function != 'None' group by (M.Id)";
my $sth = $dbh->prepare_cached( $sql ) or die( "Can't prepare '$sql': ".$dbh->errstr() );

my $res = $sth->execute() or die( "Can't execute '$sql': ".$sth->errstr() );
my @monitors;
while ( my $monitor = $sth->fetchrow_hashref() )
{
push( @monitors, $monitor );
}

while( 1 )
{
foreach my $monitor ( @monitors )
{
next if ( !zmMemVerify( $monitor ) );

if ( my $last_event_id = zmHasAlarmed( $monitor, $monitor->{LastEventId} ) )
{
$monitor->{LastEventId} = $last_event_id;
print( "Monitor ".$monitor->{Name}." has alarmed\n" );
#
# Do your stuff here
#
}
}
sleep( 1 );
}</pre>

==Trouble Shooting==
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.

===What logs should I check for errors?===
ZoneMinder creates its own logs and are usually located in the <tt>/tmp</tt> directory.

The ZoneMinder logs for the RPM packages are located in <tt>/var/log/zm</tt>.

Depending on your problem errors can show up in any of these logs but, usually the logs of interest are <tt>zmdc.log</tt> and <tt>zmpkg.log</tt> if ZM is not able to start.

Now since ZM is dependent on other components to work, you might not find errors in ZM but in the other components.
Other logs of interest are:<tt>
*/var/log/messages and/or /var/log/syslog
*/var/log/dmesg
*/var/log/httpd/error_log</tt> (RedHat/Fedora) or <tt>/var/log/apache2/error_log
*/var/log/mysqld.log</tt> (Errors here don't happen very often but just in case)

If ZM is not functioning, you should always be able to find an error in at least one of these logs. Use the [[tail]] command to get info from the logs. This can be done like so:

tail -f /var/log/messages /var/log/httpd/error_log /var/log/zm/zm*.log

This will append any data entered to any of these logs to your console screen (<tt>-f</tt>). To exit, hit [ctrl -c].

More verbose logging for the ZoneMinder binaries is available by enabling the debug option from the control panel and will be placed in the path you have configured for the debug logs. Output can be limited to a specific binary as described in the Debug options page under the "?" marks.

===How can I trouble shoot the hardware and/or software?===
Here are some commands to get information about your hardware. Some commands are distribution dependent.
* <tt>[[lspci]] -vv</tt> -- Returns lots of detailed info. Check for conflicting interrupts or port assignments. You can sometimes alter interrupts/ ports in bios. Try a different pci slot to get a clue if it is HW conflict (comand provided by the pciutils package).
* <tt>[[scanpci]] -v</tt> -- Gives you information from your hardware EPROM
* <tt>[[lsusb]] -vv</tt> -- Returns lots of detail about USB devices (camand provided by usbutils package).
* <tt>[[dmesg]]</tt> -- Shows you how your hardware initialized (or didn't) on boot-up. You will get the most use of this.
* <tt>[[v4l-info]]</tt> -- to see how driver is talking to card. look for unusual values.
* <tt>[[modinfo bttv]]</tt> -- some bttv driver stats.
* <tt>[[zmu]] -m 0 -q -v</tt> -- Returns various information regarding a monitor configuration.
* <tt>[[ipcs]] </tt> -- Provides information on the ipc facilities for which the calling process has read acccess.
* <tt>[[ipcrm]] </tt> -- The ipcrm command can be used to remove an IPC object from the kernel.
* <tt>cat /proc/interrupts</tt> -- This will dispaly what interrupts your hardware is using.

===Why is it that when monitoring a camera, the top portion of the image is cutoff and appears at the bottom of the image, with a line seperating the top from the bottom?===

=== Why am I getting a 403 access error with my web browser when trying to access http //localhost/zm? ===

The apache web server needs to have the right permissions and configuration to be able to read the Zoneminder files. Check the forums for solution, and edit the apache configuration and change directory permissions to give apache the right to read the Zoneminder files. Depending on your Zoneminder configuration, you would use the zm user and group that Zoneminder was built with, such as wwwuser and www.

=== Why am I getting broken images when trying to view events? ===

Zoneminder and the Apache web server need to have the right permissions. Check this forum topic and similar ones:
http://www.zoneminder.com/forums/viewtopic.php?p=48754#48754

===Why is the image from my color camera appearing in black and white?===
If you recently upgraded to zoneminder 1.26, there is a per camera option that defaults to black and white and can be mis-set if your upgrade didn't happen right. See this thread: http://www.zoneminder.com/forums/viewtopic.php?f=30&t=21344

This may occur if you have a NTSC analog camera but have configured the source in ZoneMinder as PAL for the Device Format under the source tab. You may also be mislead because zmu can report the video port as being PAL when the camera is actually NTSC. Confirm the format of your analog camera by checking it's technical specifications, possibly found with the packaging it came in, on the manufacturers website, or even on the retail website where you purchased the camera. Change the Device Format setting to NTSC and set it to the lowest resolution of 320 x 240. If you have confirmed that the camera itself is NTSC format, but don't get a picture using the NTSC setting, consider increasing the shared memory '''kernel.shmall''' and '''kernel.shmmax''' settings in /etc/sysctl.conf to a larger value such as 268435456. This is also the reason you should start with the 320x240 resolution, so as to minimize the potential of memory problems which would interfere with your attempts to troubleshoot the device format issue. Once you have obtained a picture in the monitor using the NTSC format, then you can experiment with raising the resolution.

===Why do I only see blue screens with a timestamp when monitoring my camera?===
If this camera is attached to a capture card, then you may have selected the wrong Device Source or Channel when configuring the monitor in the ZoneMinder console. If you have a capture card with 2 D-sub style inputs(looks like a VGA port) to which you attach a provided splitter that splits off multiple cables, then the splitter may be attached to the wrong port. For example, PV-149 capture cards have two D-sub style ports labeled as DB1 and DB2, and come packaged with a connector for one of these ports that splits into 4 BNC connecters. The initial four video ports are available with the splitter attached to DB1.

===Why do I only see black screens with a timestamp when monitoring my camera?===
In the monitor windows where you see the black screen with a timestamp, select settings and enter the Brightness, Contrast, Hue, and Color settings reported for the device by '''zmu -d <device_path> -q -v'''. 32768 may be appropriate values to try for these settings. After saving the settings, select Settings again to confirm they saved successfully.

===I am getting messages about a backtrace in my logs, what do I do?===
If you are seeing entries in your log like the following
<pre>Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6 [0x3347230210]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6(memset+0xce) [0x334727684e]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x40ee9a]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x419946]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x4213cf]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma(cos+0x35c) [0x404674]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6(__libc_start_main+0xf4) [0x334721da44]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma(cos+0xd1) [0x4043e9]]
Jan 11 20:25:22 localhost zma_m2[19051]: INF [Backtrace complete]</pre>
then you can help diagnose the problem by running a special command to translate the hex addresses into helpful information. This command is called addr2line and you can type 'man addr2line' for more information.
Basically addr2line takes two sets of parameters, the first is the name of the binary file, and the second is a list of addresses. Both of these pieces of information are displayed in the logs. The filename is the first part after the 'Backtrace:' tag, in this case /usr/local/bin/zma, though it may well be different in your case. Some of the lines refer to libraries rather than the zma executable but those can be ignored for now, the important part is noting which ZM binary is involved. The binary file is passed in following the -e flag. The addresses to pass to addr2line are those contained in the '[]' pairs. Again you can ignore those that are on a line that refers to a library but it will not hurt if you include them.
So in the example above, the command would be <pre>addr2line -e /usr/local/bin/zma 0x40ee9a 0x419946 0x4213cf 0x404674 0x4043e9</pre>
This should then dump out a more symbolic list containing source file names and line numbers, and it is this information which will be helpful if posted to the forums. Sometimes addr2line fails to produce useful output. This is usually because either the problem is so severe that it has corrupted the stack and prevented useful information from being displayed, or that you have either compiled ZM without the -g flag for debug, or you have stripped the binaries of symbol information after installation. This this case you would need to rebuild temporarily with debug enabled for the information to be useful.

This error some times happens when a linked camera looses its link or it is corrupted by the user or some other system event, try deleting the affected cameras and recreating them in the Zoneminder console.

===How do I repair the MySQL Database?===
There is two ways to go about this. In most cases you can run from the command prompt ->
* mysqlcheck --all-databases --auto-repair -p'''your_database_password''' -u '''your_databse_user'''

If that does not work then you will have to make sure that ZoneMinder is stopped then run the following (nothing should be using the database while running this and you will have to adjust for your correct path if it is different). ->
* myisamchk --silent --force --fast --update-state -O key_buffer=64M -O sort_buffer=64M -O read_buffer=1M -O write_buffer=1M /var/lib/mysql/*/*.MYI

===How do I repair the MySQL Database when the cli fails?===
In Ubuntu, the commands listed above do not seem to work. However, actually doing it by hand from within MySQL does. (But that is beyond the scope of this document) But that got me thinking... And phpmyadmin does work. Bring up a terminal.
sudo apt-get install phpmyadmin

Now go to http://zoneminder_IP/ and stop the ZM service. Continue to http://zoneminder_IP/phpmyadmin and select the zoneminder database. Select and tables marked 'in use' and pick the action 'repare' to fix. Restart the zoneminder service from the web browser. Remove or disable the phpmyadmin tool, as it is not always the most secure thing around, and opens your database wide to any skilled hacker.
sudo apt-get remove phpmyadmin

===I upgraded by distribution and ZM stopped working===
Some possibilties (Incomplete list and subject to correction)
#[[/usr/local/bin/zmfix: /usr/lib/libmysqlclient.so.15: version `MYSQL_5.0' not found (required by /usr/local/bin/zmfix)]] :: Solution: Recompile and reinstall Zoneminder.
Any time you update a major version that ZoneMinder depends on, you need to recompile ZoneMinder.

===Zoneminder doesn't start automatically on boot===
Check the list for log entries like "zmfix[766]: ERR [Can't connect to server: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)] ".
What can happen is that zoneminder is started too quickly after Mysql and tries to contact the database server before it's ready. Zoneminder gets no answer and aborts.
August 2010 - Ubuntu upgrades seem to be leaving several systems in this state. One way around this is to add a delay to the zoneminder startup script allowing Mysql to finish starting.
"Simply adding 'sleep 15' in the line above 'zmfix -a' in the /etc/init.d/zoneminder file fixed my ZoneMinder startup problems!" - credit to Pada.

=== Remote Path setup for Panasonic and other Camera ===
On adding or editing the source you can select the preset link for the parameters for the specified camera . In version 1.23.3 presets for BTTV,Axis,Panasonic,GadSpot,VEO, and BlueNet are available . Selecting the presets ZM fills up the required value for the remote path variable

=== Why do I get repeated/ mixed/unstable/ blank monitors on bt878-like cards (a.k.a. PICO 2000) ===

Please have a check at [[Pico2000]];

===What causes "Invalid JPEG file structure: two SOI markers" from zmc (1.24.x)===

Some settings that used to be global only are now per camera. On the Monitor Source tab, if you are using Remote Protocol "HTTP" and Remote Method "Simple", try changing Remote Method to "Regexp".

== Miscellaneous ==
=== I see ZoneMinder is licensed under the GPL. What does that allow or restrict me in doing with ZoneMinder? ===

The ZoneMinder license is described at the end of the documentation and consists of the following section

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty
of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

This means that ZoneMinder is licensed under the terms described [http://www.gnu.org/copyleft/gpl.html here]. There is a comprehensive FAQ covering the GPL at http://www.gnu.org/licenses/gpl-faq.html but in essence you are allowed to redistribute or modify GPL licensed software provided that you release your distribution or modifications freely under the same terms. You are allowed to sell systems based on GPL software. You are not allowed to restrict or reduce the rights of GPL software in your distribution however. Of course if you are just making modifications for your system locally you are not releasing changes so you have no obligations in this case. I recommend reading the GPL FAQ for more in-depth coverage of this issue.

=== Can I use ZoneMinder as part of my commercial product? ===

The GPL license allows you produce systems based on GPL software provided your systems also adhere to that license and any modifications you make are also released under the same terms. The GPL does not permit you to include ZoneMinder in proprietary systems (see http://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem for details). If you wish to include ZoneMinder in this kind of system then you will need to license ZoneMinder under different terms. This is sometimes possible and you will need to contact me for further details in these circumstances.

FAQ

2015-04-04T14:29:20Z

Knnniggett: /* Why does ZM stop recording once I have 32000 events for my monitor? */

== ZoneMinder Frequently Asked Questions ==

This is the FAQ page. Feel free to contribute any FAQs that you think are missing.

===How can I stop ZoneMinder filling up my disk?===

Recent versions of ZoneMinder come with a filter you can use for this purpose already included. However '''by default it is not enabled for event deletion'''.

The filter is called ''PurgeWhenFull'' and to find it, choose one of the event counts from the console page, for instance events in the last hour, for one of your monitors.

This will bring up an event listing and a filter window.

In the filter window there is a drop down select box labeled 'Use Filter', that lets your select a saved filter. Select 'PurgeWhenFull' and it will load that filter.

Make any modifications you might want, such as the percentage full you want it to kick in, or how many events to delete at a time (it will repeat the filter as many times as needed to clear the space, but will only delete this many events each time to get there).

Then click on 'Save' which will bring up a new window. Make sure the 'Automatically delete' box is checked and press save to save your filter. This will then run in the background to keep your disk within those limits.

After you've done that, you changes will automatically be loaded into zmfilter within a few minutes.

Check the <tt>zmfilter.log</tt> file to make sure it is running as sometimes missing perl modules mean that it never runs but people don't always realize.

PURGE BY AGE

To delete events that are older than 7 days, create a new filter with "Date" set to "less than" and a value of "-7 days", sort by "date/time" in "asc"ending order, then enable the checkbox "delete all matches". You can also use a value of week or week and days: "-2 week" or "-2 week 4 day"

Save with 'Run Filter In Background' enabled to have it run automatically.

Optional skip archived events: click on the plus sign next to -7 days to add another condition. "and" "archive status" equal to "unarchived only".

Optional slow delete: limit the number of results to 3. If you have a large backlog of events that would be deleted, this can hard spike the CPU usage for a long time. Limiting the number of results to only the first three each time the filter is run spreads out the delete processes over time, dramatically lessening the CPU load.

There are two methods for ZM to remove files when they are deleted that can be found in Options under the System tab ZM_OPT_FAST_DELETE and ZM_RUN_AUDIT.

ZM_OPT_FAST_DELETE:

Normally an event created as the result of an alarm consists of entries in one or more database tables plus the various files associated with it. When deleting events in the browser it can take a long time to remove all of this if your are trying to do a lot of events at once. It is recommended that you set this option which means that the browser client only deletes the key entries in the events table, which means the events will no longer appear in the listing, and leaves the zmaudit daemon to clear up the rest later.

ZM_RUN_AUDIT:

The zmaudit daemon exists to check that the saved information in the database and on the file system match and are consistent with each other. If an error occurs or if you are using 'fast deletes' it may be that database records are deleted but files remain. In this case, and similar, zmaudit will remove redundant information to synchronize the two data stores. This option controls whether zmaudit is run in the background and performs these checks and fixes continuously. This is recommended for most systems however if you have a very large number of events the process of scanning the database and file system may take a long time and impact performance. In this case you may prefer to not have zmaudit running unconditionally and schedule occasional checks at other, more convenient, times.

ZM_AUDIT_CHECK_INTERVAL:

The zmaudit daemon exists to check that the saved information in the database and on the files system match and are consistent with each other. If an error occurs or if you are using 'fast deletes' it may be that database records are deleted but files remain. In this case, and similar, zmaudit will remove redundant information to synchronize the two data stores. The default check interval of 900 seconds (15 minutes) is fine for most systems however if you have a very large number of events the process of scanning the database and file system may take a long time and impact performance. In this case you may prefer to make this interval much larger to reduce the impact on your system. This option determines how often these checks are performed.

===What does a 'Can't shmget: Invalid argument' error in my logs mean? and my cameras won't display video at higher resolutions.===

This error is discussed in the README in the following excerpt:-
''...this is caused by an attempt to allocate an amount of shared memory greater than your system can handle. The size it requests is based on the following formula, <tt>ring buffer size x image width x image height x 3 (for 24 bit images) + a bit of overhead</tt>.

So, for example:
<pre>384x288 capture resolution, that makes: 110 592 pixels
in 24 bit color that's x24 = 2 654 208 bits per frame
by 80 frames ring buffer x80 = 212 336 640 bits per camera
by 4 cameras x4 = 849 346 560 bits.
Plus 10% overhead = 934 281 216 bits
That's 116 785 152 bytes, and
= 114 048 kB, respectively 111.38 MB.
If my shared memory is set to 134 217 728, which is exactly 128MB,
that means I shouldn't have any problem.
(Note that 1 byte = 8 bits and 1kbyte = 1024bytes, 1MB = 1024 kB)</pre>

If for instance you were using 24bit 640x480 then this would come to about 92Mb if you are using the default buffer size of 100. If this is too large then you can either reduce the image or buffer sizes or increase the maximum amount of shared memory available. If you are using RedHat then you can get details on how to change these settings at http://www.redhat.com/docs/manuals/database/RHDB-2.1-Manual/admin_user/kernel-resources.html .

You should be able to use a similar procedure with other distributions to modify the shared memory pool without kernel recompilations though in some cases this may be necessary. Note, this error also sometimes occurs if you have an old shared memory segment lying around from a previous run that is too small. Use the ipcs and ipcrm system commands to check and remove it if necessary.'"

You can often find out how many 4KB shared memory pages are available by typing the following :-
<pre># cat /proc/sys/kernel/shmall
2097152</pre>

In recent kernels the shmall is set to 2097152 memory pages multiplied by 4096 bytes per page for a total of 8 GB of shared memory available. You only need to increase the shmall value if you have a computer with more than 8GB of memory and wish to use more of it for shared memory usage, such as large databases.

The most shared memory bytes you can allocate in one go :-
<pre># cat /proc/sys/kernel/shmmax
33554432</pre>

In recent kernels the shmmax is set to 33554432 bytes for only 32 MB of maximum shared memory allocatable at a time, hardly enough for ZoneMinder to go above 320 x 240 x 24-bit resolution at 40 frames in the buffer if it is using the /dev/shm shared memory device, so this value needs to be increased. If you are using ZoneMinder with the memory mapped (mmap) compile time option then this doesn't affect you.

To change the value to 128 MB temporarily during this kernel execution type (for example) :-
<pre>echo 536870912 >/proc/sys/kernel/shmmax</pre>

'''Be sure to restart ZoneMinder after this.'''
However be aware that sometimes you will only need to change the shmmax value as shmall is often large enough. Also changing these values in this way is only effective until your machine is rebooted.

To change them permanently you will need to edit <tt>/etc/sysctl.conf</tt> and add the following lines (for example) :-
<pre>kernel.shmmax = 536870912</pre>

Or if your distribution has the <tt>/etc/sysctl.d/</tt> folder you can create a file in this folder without modifying the <tt>/etc/sysctl.d</tt> so you won't lose the changes during distro upgrades :-
<pre>echo kernel.shmmax = 536870912 >/etc/sysctl.d/60-kernel-shm.conf</pre>

To load these settings in the sysctl.conf file type:
<pre>sysctl -p</pre>

To check your shared memory settings type:
<pre>ipcs -l</pre>

Note that with Megapixel cameras like the Axis 207mw becoming cheaper and more attractive, the above memory settings are not adequate. To get Zoneminder working with a full 1280x1024 resolution camera in full color, increase <tt>134217728</tt> (128 MB) to, for example, <tt>268435456</tt> (256 MB) and multiple this value by each camera.

These changes will now also be set the next time your machine is restarted.

Versions 1.24.x of ZoneMinder also allows you to use an alternate method of shared memory allocation, [http://en.wikipedia.org/wiki/Mmap mapped memory]. This requires less configuration and can be simpler to use. Mapped memory allows you to use a special type of file as the placeholder for your memory and this file is 'mapped' into memory space for easy and fast access.

To enable mapped memory in ZoneMinder you need add add the --enable--mmap=yes switch to your configure line. By default mapped memory files are created in /dev/shm which on most distributions is a dedicated pseudo-partition containing memory formatted as a filesystem. If your system uses a different path then this can be changed in ZoneMinder in Options->paths->PATH_MAP. It uses a filesystem type called [http://en.wikipedia.org/wiki/Tmpfs tmpfs]. If you type 'df -h' you should see this area and the size of memory it currently allows. To increase size for tmpfs you need to edit /etc/default/tmpfs. Search for:
<pre>SHM_SIZE=128M</pre>
and change to something like
<pre>SHM_SIZE=1G</pre>
then reboot the system. You could possibly need to change RUN_SIZE, too.

It is important that you do not use a disk based filesystem for your memory mapped files as this will cause memory access to be extremely slow. ZoneMinder creates files called .zm.mmap.<monitor id> in the mapped memory filesystem.

Mapped memory is subject to the same limitations in terms of total memory as using more traditional shared memory but does not require any configuration per allocation or chunk. In future versions of ZoneMinder this will be the default shared memory storage method.

<div id="AlternateSharedMemory" style="width:80%; border:2px solid #8a8588; background:#faf5ff; vertical-align:top; margin-top: 6px; padding: 4px;">
Another good article about shared memory settings http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.uprun.doc/doc/t0008238.htm .
It made a statement that conflicted with those in the Redhat article but they fixed a [http://www.zoneminder.com/forums/viewtopic.php?t=9692 long standing memory issue on FC6], so give them a try.

'''The essential difference was that the kernel.shmall setting is NOT in a direct memory setting in KB but in pages of memory. it is Max Pages of memory'''

'''For example:''' If you want to allocate a maximum memory setting to 8GB you have to convert it to the number of pages (or segments).
with a page size of 4096.
*kernel.shmall = 8000x1024x1024/4096
<pre>kernel.shmall = 2097152</pre>
NOT 8388608000 as would be suggested in the RedHat article linked above.

shmmax is the max amount to allocate in one request -
this is is an actual memory size (as opposed to pages) set to 4GB
<pre>kernel.shmmax = 4294967296</pre>

The <tt>/etc/sysctl.conf</tt> would have these lines
<pre>kernel.shmall = 2097152
kernel.shmmax = 4294967296</pre>

As above, reload your sysctl.conf with <tt>sysctl -p</tt> and check that the settings are correct with <tt>ipcs -l</tt>.
</div>

===I have enabled motion detection but it is not always being triggered when things happen in the camera view===

ZoneMinder uses zones to examine images for motion detection. When you create the initial zones you can choose from a number of preset values for sensitivity etc. Whilst these are usually a good starting point they are not always suitable for all situations and you will probably need to tweak the values for your specific circumstances. The meanings of the various settings are described in the documentation (http://www.zoneminder.com/wiki/index.php/Documentation#Defining_Zones) however if you believe you have sensible settings configured then there are two diagnostic approaches you can use.

====Event Statistics====
The first technique is to use event statistics. Firstly you should ensure they are switched on in Options->Logging->RECORD_EVENT_STATS. This will then cause the raw motion detection statistics for any subsequently generated events to be written to the DB. These can then be accessed by first clicking on the Frames or Alarm Frames values of the event from any event list view in the web gui. Then click on the score value to see the actual values that caused the event. Alternatively the stats can be accessed by clicking on the 'Stats' link when viewing any individual frame. The values displayed there correspond with the values that are used in the zone configuration and give you an idea of what 'real world' values are being generated.

Note that if you are investigating why events 'do not' happen then these will not be saved and so won't be accessible. The best thing to do in that circumstance is to make your zone more sensitive so that it captures all events (perhap even ones you don't want) so you can get an idea of what values are being generated and then start to adjust back to less sensitive settings if necessary. You should make sure you test your settings under a variety of lighting conditions (e.g. day and night, sunny or dull) to get the best feel for that works and what doesn't.

Using statistics will slow your system down to a small degree and use a little extra disk space in the DB so once you are happy you can switch them off again. However it is perfectly feasible to keep them permanently on if your system is able to cope which will allow you to review your setting periodically.

====Diagnostic Images====
The second approach is to use diagnostic images which are saved copies of the intermediate images that ZM uses when determining motion detection. These are switched on and off using Options->Logging->RECORD_DIAG_IMAGES.

There are two kinds of diagnostic images which are and are written (and continuously overwritten) to the top level monitor event directory. If an event occurs then the files are additionally copied to the event directory and renamed with the appropriate frame number as a prefix.

The first set are produced by the monitor on the image as a whole. The diag-r.jpg image is the current reference image against which all individual frames are compared and the diag-d.jpg image is the delta image highlighting the difference between the reference image and the last analysed image. In this images identicial pixels will be black and the more different a pixel is the whiter it will be. Viewing this image and determining the colour of the pixels is a good way of getting a feel for the pixel differences you might expect (often more than you think).

The second set of diag images are labelled as diag-<zoneid>-<stage>.jpg where zoneid is the id of the zone in question (Smile) and the stage is where in the alarm check process the image is generated from. So if you have several zones you can expect to see multiple files. Also these files are only interested in what is happening in their zone only and will ignore anything else outside of the zone. The stages that each number represents are as follows,

# Alarmed Pixels - This image shows all pixels in the zone that are considered to be alarmed as white pixels and all other pixels as black.
# Filtered Pixels - This is as stage one except that all pixels removed by the filters are now black. The white pixels represent the pixels that are candidates to generate an event.
# Raw Blobs - This image contains all alarmed pixels from stage 2 but aggrageted into blobs. Each blob will have a different greyscale value (between 1 and 254) so they can be difficult to spot with the naked eye but using a colour picker or photoshop will make it easier to see what blob is what.
# Filtered Blobs - This image is as stage 3 but under (or over) sized blobs have been removed. This is the final step before determining if an event has occurred, just prior to the number of blobs being counted. Thus this image forms the basis for determining whether an event is generated and outlining on alarmed images is done from the blobs in this image.

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.

===Why can't ZoneMinder capture images (either at all or just particularly fast) when I can see my camera just fine in xawtv or similar?===

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 6-10fps for two, 1-4fps for three and 1-2 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.

When using xawtv etc to view the stream you are not looking at an image captured using the frame grabber but the card's video memory mapped onto your screen. 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.

===Why can't I see streamed images when I can see stills in the Zone window etc?===

This issue is normally down to one of two causes

1) You are using Internet Explorer and are trying to view multi-part jpeg streams. IE does not support these streams directly, unlike most other browsers. You will need to install Cambozola or another multi-part jpeg aware pluging to view them. To do this you will need to obtain the applet from the Downloads page and install the cambozola.jar file in the same directly as the ZoneMinder php files. Then find the ZoneMinder Options->Images page and enable ZM_OPT_CAMBOZOLA and enter the web path to the .jar file in ZM_PATH_CAMBOZOLA. This will ordinarily just be cambozola.jar. Provided (Options / B/W tabs) WEB_H_CAN_STREAM is set to auto and WEB_H_STREAM_METHOD is set to jpeg then Cambozola should be loaded next time you try and view a stream.

'''NOTE''': If you find that the Cambozola applet loads in IE but the applet just displays the version # of Cambozola and the author's name (as opposed to seeing the streaming images), you may need to chmod (''-rwxrwxr-x'') your (''usr/share/zoneminder/'') cambozola.jar:

$ sudo chmod 775 cambozola.jar

Once I did this, images started to stream for me.

2) The other common cause for being unable to view streams is that you have installed the ZoneMinder cgi binaries (zms and nph-zms) in a different directory than your web server is expecting. Make sure that the --with-cgidir option you use to the ZoneMinder configure script is the same as the CGI directory configure for your web server. If you are using Apache, which is the most common one, then in your httpd.conf file there should be a line like <pre>ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"</pre> where the last directory in the quotes is the one you have specified. If not then change one or the other to match. Be warned that configuring apache can be complex so changing the one passed to the ZoneMinder configure (and then rebuilding and reinstalling) is recommended in the first instance. If you change the apache config you will need to restart apache for the changes to take effect. If you still cannot see stream reliably then try changing Options->Paths->ZM_PATH_ZMS to just use zms if nph-zms is specified, or vice versa. Also check in your apache error logs.

===I have several monitors configured but when I load the Montage view in FireFox why can I only see two? or, Why don't all my cameras display when I use the Montage view in FireFox?===

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.

To resolve this situation, follow the instructions below:

<pre>Enter about:config in the address bar

scroll down to
browser.cache.check_doc_frequency 3
change the 3 to a 1

browser.cache.disk.enable True -> False
network.http.max-connections-per-server -> put a value of 100
network.http.max-persistent-connections-per-proxy -> 100 again
network.http.max-persistent-connections-per-server -> 100 again
</pre>

===Why is ZoneMinder using so much CPU?===

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.

The main causes are.

# Using a video palette other than greyscale or RGB24. This can cause a relatively minor performace hit, though still significant. Although some cameras and cards require using planar palettes ZM currently doesn't support this format internally and each frame is converted to an RGB representation prior to processing. Unless you have compelling reasons for using YUV or reduced RGB type palettes such as hitting USB transfer limits I would experiment to see if RGB24 or greyscale is quicker. Put your monitors into 'Monitor' mode so that only the capture daemons are running and monitor the process load of these (the 'zmc' processes) using top. Try it with various palettes to see if it makes a difference.
# Big image sizes. A image of 640x480 requires at least four times the processing of a 320x240 image. Experiment with different sizes to see what effect it may have. Sometimes a large image is just two interlaced smaller frames so has no real benefit anyway. This is especially true for analog cameras/cards as image height over 320 (NTSC) or 352 PAL) are invariably interlaced.
# Capture frame rates. Unless there's a compelling reason in your case there is often little benefit in running cameras at 25fps when 5-10fps would often get you results just as good. Try changing your monitor settings to limit your cameras to lower frame rates. You can still configure ZM to ignore these limits and capture as fast as possible when motion is detected.
# Run function. Obviously running in Record or Mocord modes or in Modect with lots of events generates a lot of DB and file activity and so CPU and load will increase.
# Basic default detection zones. By default when a camera is added one detection zone is added which covers the whole image with a default set of parameters. If your camera covers a view in which various regions are unlikely to generate a valid alarm (ie the sky) then I would experiment with reducing the zone sizes or adding inactive zones to blank out areas you don't want to monitor. Additionally the actual settings of the zone themselves may not be optimal. When doing motion detection the number of changed pixels above a threshold is examined, then this is filter, then contiguous regions are calculated to see if an alarm is generated. If any maximum or minimum threshold is exceeded according to your zone settings at any time the calculation stops. If your settings always result in the calculations going through to the last stage before being failed then additional CPU time is used unnecessarily. Make sure your maximum and minimumzone thresholds are set to sensible values and experiment by switching RECORD_EVENT_STATS on and seeing what the actual values of alarmed pixels etc are during sample events.
# Optimise your settings. After you've got some settings you're happy with then switching off RECORD_EVENT_STATS will prevent the statistics being written to the database which saves some time. Other settings which might make a difference are ZM_FAST_RGB_DIFFS, ZM_OPT_FRAME_SERVER and the JPEG_xxx_QUALITY ones.

I'm sure there are other things which might make a difference such as what else you have running on the box and memory sizes (make sure there's no swapping going on). 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. Having said that I also don't always know why you get certains results from 'top'. For instance if I have a 'zma' daemon running for a monitor that is capturing an image. I've commented out the actual analysis so all it's doing is blending the image with the previous one. In colour mode this takes ~11 milliseconds per frame on my system and the camera is capturing at ~10fps. Using 'top' this reports the process as using ~5% of CPU and permanently in R(un) state. Changing to greyscale mode the blending takes ~4msec (as you would expect as this is roughly a third of 11) but top reports the process as now with 0% CPU and permanently in S(leep) state. So an actual CPU resource usage change of a factor of 3 causes huge differences in reported CPU usage. I have yet to get to the bottom of this but I suspect it's to do with scheduling somewhere along the line and that maybe the greyscale processing will fit into one scheduling time slice whereas the colour one won't but I have no evidence of this yet!

===Why is the timeline view all messed up?===

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.

===How much Hard Disk Space / Bandwidth do I need for ZM?===
Please see [http://www.jpwilson.eu/ZM_Utils/ZM%20storage%20calc%20sheet.xls Storage Calc] in excel format

Or go to [http://www.axis.com/products/video/design_tool/index.htm 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 320x240 storing 1 fps except during alarm events. After 1 week 60GB of space in the volume where the events are stored (/var/www/html/zm) has been used.

===When I try and run ZoneMinder I get lots of audit permission errors in the logs and it won't start===
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 ([http://en.wikipedia.org/wiki/Selinux]).
If you are seeing entries in your system log like:

Jun 11 20:44:02 kernel: audit(1150033442.443:226): avc: denied { read } for pid=5068
comm="uptime" name="utmp" dev=dm-0 ino=16908345 scontext=user_u:system_r:httpd_sys_script_t
tcontext=user_u:object_r:initrc_var_run_t tclass=file

then it is likely that your system has SELinux enabled and it is preventing ZoneMinder from performaing certain activities. You then have two choices. You can either tune SELinux to permit the required operations or you can disable SELinux entirely which will permit ZoneMinder to run unhindered. Disabling SELinux is usually performed by editing its configuration file (e.g., <tt>/etc/selinux/config</tt>) and then rebooting. 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.

=== How do I enable ZoneMinder's security? ===
In the console, click on Options. Check the box next to "ZM_OPT_USE_AUTH". You will immediately be asked to login. The username is 'admin' and the password is 'admin'.

'''To Manage Users:''' 
In main console, go to '''Options->Users'''.

* You may also consider to use the web server security, for example, htaccess files under Apache scope; You may even use this as an additional/redundant security on top of Zoneminders built-in security features;

=== Why does ZM stop recording once I have 32000 events for my monitor? ===
ZM_USE_DEEP_STORAGE is now the default for new ZoneMinder systems so this limitation should only apply to users upgrading from a previous version of ZoneMinder.

This is a limitation of the ext3 filesystem that most Linux distributions use. One directory cannot hold more than 32k approx files.

Version of ZM from 1.23.0 onwards allow you to have a deeper filesystem with fewer files per individual directory. As well as not being susceptible to the 32k limit this is also somewhat faster.

If you have upgraded from a previous version of ZoneMinder and are considering enabling this option, it is very important to follow the steps below. Failure to properly follow these steps WILL RESULT IN LOSS OF YOUR DATA!

- Stop ZoneMinder
- Backup your event data and the dB if you have the available storage
- Enable USE_DEEP_STORAGE under Options.
- From the command line, run "sudo zmupdate.pl --migrate-events"
- Monitor the output for any events that fail to convert.
- After the conversion completes, you can restart ZoneMinder

Note that you can re-run the migrate-events command if any error messages scroll off the screen.

You can read about the lack of a limit in the number of
sub-directories in the ext4 filesystem at:
http://kernelnewbies.org/Ext4
and see what tools may assist in your use of this filesystem in:
http://ext4.wiki.kernel.org/index.php/Ext4_Howto
Note that while GParted 0.5.2 recognizes ext4 partitions, at least in
some circumstances it does not succeed in formatting a partition for
the ext4 filesystem. Also, if you search for ext3 or reiserfs on the
forums you will find various threads on this issue with guidance on
how to convert.

== Managing system load ''(with IP Cameras in mind)'' ==

=== Introduction ===
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.
3. Comparing the zoned selections to the previous image or images and applying rules.
4. If in alarm state, writing that image to the disk and updating the mysql database.

If you're capturing at five frames per second, the above is repeated five times every second, multiplied by the number of cameras. 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.

=== How do I know if my computer is overloaded? ===
If your CPU is running at 100% all the time, it's probably overloaded (or running at exact optimisation). If the load is consistently high (over 10.0 for a single processor) then Bad Things happen - like lost frames, unrecorded events etc. Occasional peaks are fine, normal and nothing to worry about.

Zoneminder runs on Linux, Linux measures system load using "load", which is complicated but gives a rough guide on what the computer is doing at any given time. Zoneminder shows Load on the main page (top right) as well as disk space. Typing "uptime" on the command line will give a similar guide, but with three figures to give a fuller measure of what's happening over a period of time but for the best guide to see what's happening, install "htop" - which gives easy to read graphs for load, memory and cpu usage.

A load of 1.0 means the processor has "just enough to do right now". Also worth noting that a load of 4.0 means exactly the same for a quad processor machine - each number equals a single processor's workload. A very high load can be fine on a computer that has a stacked workload - such as a machine sending out bulk emails, or working its way through a knotty problem; it'll just keep churning away until it's done. However - Zoneminder needs to process information in real time so it can't afford to stack its jobs, it needs to deal with them right away.

For a better and full explanation of Load: http://en.wikipedia.org/wiki/Load_%28computing%29

=== My load is too high, how can I reduce it? ===
Zoneminder is /very/ tweakable and it's possible to tune it to compromise. The following are good things to try, in no particular order;

Change the jpeg libraries. In most distributions Linux uses standard jpeg libraries which although fine for most things, don't use the MMX functions in nearly all modern processors. Check whether your cpu supports mmx by running "cpuid |grep MMX" which should give you a line or two along the lines of "MMX instructions". If so, give the libs a try. Most people report their load halves simply by using these libs. You may be able to experience substantial Zoneminder performance boosts now by merely upgrading your operating system, without having to download libraries and compile your own binaries, etc. as described in the forum thread linked below. Some distributions, e.g. Fedora 14 now include library code to utilize the instruction set extensions available in your processor:

http://fedoraproject.org/wiki/Fedora_14_Alpha_release_notes#Faster_JPEG_Compression.2FDecompression

"The replacement of libjpeg with libjpeg-turbo brings speed improvements to a wide range of applications when handling images in JPEG format ..."

http://fedoraproject.org/wiki/Releases/14/Schedule

still states "2010-11-02 final release".

CentOS 6.4 now has libjpeg-turbo built in as the default jpeg library allowing the best results out of the box.

http://libjpeg-turbo.virtualgl.org/

provides some history on its project page. If you seek confirmation for which library is in use, you may consider querying e.g. while running on a prior distribution:
<pre>
[u@who ~]$ rpm -q --whatprovides libjpeg
libjpeg-6b-46.fc12.i686
[u@who ~]$
</pre>
and comparing the response to querying when the higher-performance library is available:
<pre>
[u@who ~]$ rpm -q --whatprovides libjpeg
libjpeg-turbo-1.0.1-1.fc14.x86_64
[u@who ~]$
</pre>
As noted in other forum postings, some zoneminder camera and usage configurations may not make much use of jpeg processing (e.g. some webcams), and thus obtain little performance benefit. Otherwise, you should be able to select one or more of:
* running more cameras,
* running existing cameras at higher image resolutions,
* running cameras at a faster frame rate,
* saving MoDect images with higher quality,
* having more CPU cycles available for any non-Zoneminder workload, etc.

http://www.zoneminder.com/forums/viewtopic.php?t=6419 gives more info on the download-the-library-yourself, compile-your-own-Zoneminder binary, etc. approach if needed. Nobody's posted there to say it broke their system... Yet.

If your camera allows you to change image size, think whether you can get away with smaller images. Smaller pics = less load. 320x240 is usually ok for close-up corridor shots.

Go Black and White. Colour pictures use twice to three times the CPU, memory and diskspace but give little benefit to identification.

Reduce frames per second. Halve the fps, halve the workload. If your camera supports fps throttling (Axis do), try that - saves ZM having to drop frames from a stream. 2-5 fps seems to be widely used.

Experiment with using jpeg instead of mjpeg. Some users have reported it gives better performance, but YMMV.

Tweak the zones. Keep them as small and as few as possible. Stick to one zone unless you really need more.

Schedule. If you are running a linux system at near capacity, you'll need to think carefully about things like backups and scheduled tasks. updatedb - the process which maintains a file database so that 'locate' works quickly, is normally scheduled to run once a day and if on a busy system can create a heavy increase on the load. The same is true for scheduled backups, especially those which compress the files. Re-schedule these tasks to a time when the cpu is less likely to be busy, if possible - and also use the "nice" command to reduce their priority. (crontab and /etc/cron.daily/ are good places to start)

Reduce clutter on your PC. Don't run X unless you really need it, the GUI is a huge overhead in both memory and cpu.

More expensive options:

Increase RAM. If your system is having to use disk swap it will HUGELY impact performance in all areas. Again, htop is a good monitor - but first you need to understand that because Linux is using all the memory, it doesn't mean it needs it all - linux handles ram very differently to Windows/DOS and caches stuff. htop will show cached ram as a different colour in the memory graph. Also check that you're actually using a high memory capable kernel - many kernels don't enable high memory by default.

Faster CPU. Simple but effective. Zoneminder also works very well with multiple processor systems out of the box (if SMP is enabled in your kernel). The load of different cameras is spread across the processors.

Try building Zoneminder with processor specific instructions that are optimised to the system it will be running on, also increasing the optimisation level of GCC beyond -O2 will help.
<pre>
./configure CFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp" CXXFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp"
</pre>
The above command is optimised for an Athlon XP cpu so you will need to use the specific processor tag for your cpu, also the compiler optimisation has been increased to -O3.

You also need to put in your normal ./configure commands as if you were compiling with out this optimisation.

A further note is that the compile must be performed on the system that Zoneminder will be running on as this optimisation will make it hardware specific code.

Processor specific commands can be found in the GCC manual along with some more options that may increase performanc.
<pre>
http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
</pre>

The below command has been used to compile Zoneminder on a Athlon XP system running CentOS 5.5 and along with the libjpeg-turbo modification to reduce the CPU load in half, libjpeg-turbo reduced the load by 1/3 before the processor optimisation.
<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin CFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp" CXXFLAGS="-D__STDC_CONSTANT_MACROS -g -O3 -march=athlon-xp -mtune=athlon-xp" --enable-mmap --sysconfdir=/etc/zm
</pre>

The following command has been used to compile Zoneminder 1.25 on a CentOS 6.0 system, the native command should choose the processor automatically during compile time, this needs to be performed on the actual system!!.

<pre>
CFLAGS="-g -O3 -march=native -mtune=native" CXXFLAGS="-D__STDC_CONSTANT_MACROS -g -O3 -march=native -mtune=native" ./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=your_zm_user ZM_DB_PASS=your_zm_password ZM_SSL_LIB=openssl
</pre>

=== What about disks and bandwidth? ===

In most modern pc-based servers, disk I/O is more than adequate for the speeds involved in capturing from multiple cameras in most scenarios.

A typical 100mbit LAN will cope with most setups easily. If you're feeding from cameras over smaller or internet links, obviously fps will be much lower.

Disk and Bandwidth calculators are referenced on the Zoneminder wiki here: http://www.zoneminder.com/wiki/index.php/FAQ#How_much_Hard_Disk_Space_.2F_Bandwidth_do_I_need_for_ZM.3F

== Building ZoneMinder ==

=== When running configure I am getting a lot of messages about not being able to compile the ffmpeg libraries ===

If you see output from configure that looks like this

<pre>checking libavcodec/avcodec.h usability... no
checking libavcodec/avcodec.h presence... yes
configure: WARNING: libavcodec/avcodec.h: present but cannot be compiled
configure: WARNING: libavcodec/avcodec.h: check for missing
prerequisite headers?
configure: WARNING: libavcodec/avcodec.h: see the Autoconf documentation
configure: WARNING: libavcodec/avcodec.h: section "Present But
Cannot Be Compiled"
configure: WARNING: libavcodec/avcodec.h: proceeding with the compiler's
result
configure: WARNING: ## ------------------------------------- ##
configure: WARNING: ## Report this to support@zoneminder.com ##
configure: WARNING: ## ------------------------------------- ##</pre>

then it is caused not by the ZoneMinder build system but ffmpeg itself. However there is a workaround you can use which is to add

CPPFLAGS=-D__STDC_CONSTANT_MACROS

to the ZoneMinder ./configure command which should solve the issue. However this is not a proper 'fix' as such, which can only come from the ffmpeg project itself.

=== I cannot build ZoneMinder and am getting lots of undefined C++ template errors===

This is almost certainly due to the 'ccache' package which attempts to speed up compilation by caching compiled objects. Unfortunately one of the side effects is that it breaks the GNU g++ template resolution method that ZoneMinder uses in building by prevent files getting recompiled. The simplest way around this is to remove the ccache package using your distros package manager.

=== How do I build for X10 support? ===

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. Installing the perl module is covered in the README amongst other places but in summary, do:

perl -MCPAN -eshell
install X10::ActiveHome
quit

== Extending ZoneMinder ==

=== How can I get ZM to do different things at different times of day or week? ===
If you want to configure ZoneMinder to do motion detection during the day and just record at night, for example, you will need to use ZoneMinder 'run states'. 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. This will usually say 'Running' or 'Stopped'. You will then be able to save the current state and give it a name, 'Daytime' for example. Now configure your monitors how you would want them during other times of day and save that, for instance as 'Nighttime'.

Now you can switch between these two states by selecting them from the same dialog you saved them, or from the command line from issue the command ''zmpkg.pl <run state>'', for example ''zmpkg.pl Daytime''.

The final step you need to take, is scheduling the time the changes take effect. For this you can use [http://en.wikipedia.org/wiki/Cron cron]. A simple entry to change to the Daylight state at at 8am and to the nighttime state at 8pm would be as follows,
<pre>0 8 * * * root /usr/local/bin/zmpkg.pl Daytime
0 20 * * * root /usr/local/bin/zmpkg.pl Nighttime</pre>

On Ubuntu 7.04 and possibly others, look in /usr/bin not just /usr/local/bin for the zmpkg.pl file.

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.

For an alternative method of time controlling ZoneMinder, forum user 'voronwe' has created a more interactive calendar style integration. Details of this can be found in this [http://www.zoneminder.com/forums/viewtopic.php?t=6519 forum thread]. If you would like to find out more about this contribution please post on this thread.

=== How can I use ZoneMinder to trigger something else when there is an alarm? ===
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. Full details are in the README or by doing 'perldoc ZoneMinder', 'perldoc ZoneMinder::SharedMem' etc.
Below is an example script that checks all monitors for alarms and when one occurs, prints a message to the screen. You can add in your own code to make this reaction a little more useful.

<pre>#!/usr/bin/perl -w

use strict;

use ZoneMinder;

$| = 1;

zmDbgInit( "myscript", level=>0, to_log=>0, to_syslog=>0, to_term=>1 );

my $dbh = DBI->connect( "DBI:mysql:database=".ZM_DB_NAME.";host=".ZM_DB_HOST, ZM_DB_USER, ZM_DB_PASS );

my $sql = "select M.*, max(E.Id) as LastEventId from Monitors as M left join Events as E on M.Id = E.MonitorId where M.Function != 'None' group by (M.Id)";
my $sth = $dbh->prepare_cached( $sql ) or die( "Can't prepare '$sql': ".$dbh->errstr() );

my $res = $sth->execute() or die( "Can't execute '$sql': ".$sth->errstr() );
my @monitors;
while ( my $monitor = $sth->fetchrow_hashref() )
{
push( @monitors, $monitor );
}

while( 1 )
{
foreach my $monitor ( @monitors )
{
next if ( !zmMemVerify( $monitor ) );

if ( my $last_event_id = zmHasAlarmed( $monitor, $monitor->{LastEventId} ) )
{
$monitor->{LastEventId} = $last_event_id;
print( "Monitor ".$monitor->{Name}." has alarmed\n" );
#
# Do your stuff here
#
}
}
sleep( 1 );
}</pre>

==Trouble Shooting==
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.

===What logs should I check for errors?===
ZoneMinder creates its own logs and are usually located in the <tt>/tmp</tt> directory.

The ZoneMinder logs for the RPM packages are located in <tt>/var/log/zm</tt>.

Depending on your problem errors can show up in any of these logs but, usually the logs of interest are <tt>zmdc.log</tt> and <tt>zmpkg.log</tt> if ZM is not able to start.

Now since ZM is dependent on other components to work, you might not find errors in ZM but in the other components.
Other logs of interest are:<tt>
*/var/log/messages and/or /var/log/syslog
*/var/log/dmesg
*/var/log/httpd/error_log</tt> (RedHat/Fedora) or <tt>/var/log/apache2/error_log
*/var/log/mysqld.log</tt> (Errors here don't happen very often but just in case)

If ZM is not functioning, you should always be able to find an error in at least one of these logs. Use the [[tail]] command to get info from the logs. This can be done like so:

tail -f /var/log/messages /var/log/httpd/error_log /var/log/zm/zm*.log

This will append any data entered to any of these logs to your console screen (<tt>-f</tt>). To exit, hit [ctrl -c].

More verbose logging for the ZoneMinder binaries is available by enabling the debug option from the control panel and will be placed in the path you have configured for the debug logs. Output can be limited to a specific binary as described in the Debug options page under the "?" marks.

===How can I trouble shoot the hardware and/or software?===
Here are some commands to get information about your hardware. Some commands are distribution dependent.
* <tt>[[lspci]] -vv</tt> -- Returns lots of detailed info. Check for conflicting interrupts or port assignments. You can sometimes alter interrupts/ ports in bios. Try a different pci slot to get a clue if it is HW conflict (comand provided by the pciutils package).
* <tt>[[scanpci]] -v</tt> -- Gives you information from your hardware EPROM
* <tt>[[lsusb]] -vv</tt> -- Returns lots of detail about USB devices (camand provided by usbutils package).
* <tt>[[dmesg]]</tt> -- Shows you how your hardware initialized (or didn't) on boot-up. You will get the most use of this.
* <tt>[[v4l-info]]</tt> -- to see how driver is talking to card. look for unusual values.
* <tt>[[modinfo bttv]]</tt> -- some bttv driver stats.
* <tt>[[zmu]] -m 0 -q -v</tt> -- Returns various information regarding a monitor configuration.
* <tt>[[ipcs]] </tt> -- Provides information on the ipc facilities for which the calling process has read acccess.
* <tt>[[ipcrm]] </tt> -- The ipcrm command can be used to remove an IPC object from the kernel.
* <tt>cat /proc/interrupts</tt> -- This will dispaly what interrupts your hardware is using.

===Why is it that when monitoring a camera, the top portion of the image is cutoff and appears at the bottom of the image, with a line seperating the top from the bottom?===

=== Why am I getting a 403 access error with my web browser when trying to access http //localhost/zm? ===

The apache web server needs to have the right permissions and configuration to be able to read the Zoneminder files. Check the forums for solution, and edit the apache configuration and change directory permissions to give apache the right to read the Zoneminder files. Depending on your Zoneminder configuration, you would use the zm user and group that Zoneminder was built with, such as wwwuser and www.

=== Why am I getting broken images when trying to view events? ===

Zoneminder and the Apache web server need to have the right permissions. Check this forum topic and similar ones:
http://www.zoneminder.com/forums/viewtopic.php?p=48754#48754

===Why is the image from my color camera appearing in black and white?===
If you recently upgraded to zoneminder 1.26, there is a per camera option that defaults to black and white and can be mis-set if your upgrade didn't happen right. See this thread: http://www.zoneminder.com/forums/viewtopic.php?f=30&t=21344

This may occur if you have a NTSC analog camera but have configured the source in ZoneMinder as PAL for the Device Format under the source tab. You may also be mislead because zmu can report the video port as being PAL when the camera is actually NTSC. Confirm the format of your analog camera by checking it's technical specifications, possibly found with the packaging it came in, on the manufacturers website, or even on the retail website where you purchased the camera. Change the Device Format setting to NTSC and set it to the lowest resolution of 320 x 240. If you have confirmed that the camera itself is NTSC format, but don't get a picture using the NTSC setting, consider increasing the shared memory '''kernel.shmall''' and '''kernel.shmmax''' settings in /etc/sysctl.conf to a larger value such as 268435456. This is also the reason you should start with the 320x240 resolution, so as to minimize the potential of memory problems which would interfere with your attempts to troubleshoot the device format issue. Once you have obtained a picture in the monitor using the NTSC format, then you can experiment with raising the resolution.

===Why do I only see blue screens with a timestamp when monitoring my camera?===
If this camera is attached to a capture card, then you may have selected the wrong Device Source or Channel when configuring the monitor in the ZoneMinder console. If you have a capture card with 2 D-sub style inputs(looks like a VGA port) to which you attach a provided splitter that splits off multiple cables, then the splitter may be attached to the wrong port. For example, PV-149 capture cards have two D-sub style ports labeled as DB1 and DB2, and come packaged with a connector for one of these ports that splits into 4 BNC connecters. The initial four video ports are available with the splitter attached to DB1.

===Why do I only see black screens with a timestamp when monitoring my camera?===
In the monitor windows where you see the black screen with a timestamp, select settings and enter the Brightness, Contrast, Hue, and Color settings reported for the device by '''zmu -d <device_path> -q -v'''. 32768 may be appropriate values to try for these settings. After saving the settings, select Settings again to confirm they saved successfully.

===I am getting messages about a backtrace in my logs, what do I do?===
If you are seeing entries in your log like the following
<pre>Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6 [0x3347230210]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6(memset+0xce) [0x334727684e]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x40ee9a]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x419946]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x4213cf]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma(cos+0x35c) [0x404674]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6(__libc_start_main+0xf4) [0x334721da44]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma(cos+0xd1) [0x4043e9]]
Jan 11 20:25:22 localhost zma_m2[19051]: INF [Backtrace complete]</pre>
then you can help diagnose the problem by running a special command to translate the hex addresses into helpful information. This command is called addr2line and you can type 'man addr2line' for more information.
Basically addr2line takes two sets of parameters, the first is the name of the binary file, and the second is a list of addresses. Both of these pieces of information are displayed in the logs. The filename is the first part after the 'Backtrace:' tag, in this case /usr/local/bin/zma, though it may well be different in your case. Some of the lines refer to libraries rather than the zma executable but those can be ignored for now, the important part is noting which ZM binary is involved. The binary file is passed in following the -e flag. The addresses to pass to addr2line are those contained in the '[]' pairs. Again you can ignore those that are on a line that refers to a library but it will not hurt if you include them.
So in the example above, the command would be <pre>addr2line -e /usr/local/bin/zma 0x40ee9a 0x419946 0x4213cf 0x404674 0x4043e9</pre>
This should then dump out a more symbolic list containing source file names and line numbers, and it is this information which will be helpful if posted to the forums. Sometimes addr2line fails to produce useful output. This is usually because either the problem is so severe that it has corrupted the stack and prevented useful information from being displayed, or that you have either compiled ZM without the -g flag for debug, or you have stripped the binaries of symbol information after installation. This this case you would need to rebuild temporarily with debug enabled for the information to be useful.

This error some times happens when a linked camera looses its link or it is corrupted by the user or some other system event, try deleting the affected cameras and recreating them in the Zoneminder console.

===How do I repair the MySQL Database?===
There is two ways to go about this. In most cases you can run from the command prompt ->
* mysqlcheck --all-databases --auto-repair -p'''your_database_password''' -u '''your_databse_user'''

If that does not work then you will have to make sure that ZoneMinder is stopped then run the following (nothing should be using the database while running this and you will have to adjust for your correct path if it is different). ->
* myisamchk --silent --force --fast --update-state -O key_buffer=64M -O sort_buffer=64M -O read_buffer=1M -O write_buffer=1M /var/lib/mysql/*/*.MYI

===How do I repair the MySQL Database when the cli fails?===
In Ubuntu, the commands listed above do not seem to work. However, actually doing it by hand from within MySQL does. (But that is beyond the scope of this document) But that got me thinking... And phpmyadmin does work. Bring up a terminal.
sudo apt-get install phpmyadmin

Now go to http://zoneminder_IP/ and stop the ZM service. Continue to http://zoneminder_IP/phpmyadmin and select the zoneminder database. Select and tables marked 'in use' and pick the action 'repare' to fix. Restart the zoneminder service from the web browser. Remove or disable the phpmyadmin tool, as it is not always the most secure thing around, and opens your database wide to any skilled hacker.
sudo apt-get remove phpmyadmin

===I upgraded by distribution and ZM stopped working===
Some possibilties (Incomplete list and subject to correction)
#[[/usr/local/bin/zmfix: /usr/lib/libmysqlclient.so.15: version `MYSQL_5.0' not found (required by /usr/local/bin/zmfix)]] :: Solution: Recompile and reinstall Zoneminder.
Any time you update a major version that ZoneMinder depends on, you need to recompile ZoneMinder.

===Zoneminder doesn't start automatically on boot===
Check the list for log entries like "zmfix[766]: ERR [Can't connect to server: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)] ".
What can happen is that zoneminder is started too quickly after Mysql and tries to contact the database server before it's ready. Zoneminder gets no answer and aborts.
August 2010 - Ubuntu upgrades seem to be leaving several systems in this state. One way around this is to add a delay to the zoneminder startup script allowing Mysql to finish starting.
"Simply adding 'sleep 15' in the line above 'zmfix -a' in the /etc/init.d/zoneminder file fixed my ZoneMinder startup problems!" - credit to Pada.

=== Remote Path setup for Panasonic and other Camera ===
On adding or editing the source you can select the preset link for the parameters for the specified camera . In version 1.23.3 presets for BTTV,Axis,Panasonic,GadSpot,VEO, and BlueNet are available . Selecting the presets ZM fills up the required value for the remote path variable

=== Why do I get repeated/ mixed/unstable/ blank monitors on bt878-like cards (a.k.a. PICO 2000) ===

Please have a check at [[Pico2000]];

===What causes "Invalid JPEG file structure: two SOI markers" from zmc (1.24.x)===

Some settings that used to be global only are now per camera. On the Monitor Source tab, if you are using Remote Protocol "HTTP" and Remote Method "Simple", try changing Remote Method to "Regexp".

== Miscellaneous ==
=== I see ZoneMinder is licensed under the GPL. What does that allow or restrict me in doing with ZoneMinder? ===

The ZoneMinder license is described at the end of the documentation and consists of the following section

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty
of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

This means that ZoneMinder is licensed under the terms described [http://www.gnu.org/copyleft/gpl.html here]. There is a comprehensive FAQ covering the GPL at http://www.gnu.org/licenses/gpl-faq.html but in essence you are allowed to redistribute or modify GPL licensed software provided that you release your distribution or modifications freely under the same terms. You are allowed to sell systems based on GPL software. You are not allowed to restrict or reduce the rights of GPL software in your distribution however. Of course if you are just making modifications for your system locally you are not releasing changes so you have no obligations in this case. I recommend reading the GPL FAQ for more in-depth coverage of this issue.

=== Can I use ZoneMinder as part of my commercial product? ===

The GPL license allows you produce systems based on GPL software provided your systems also adhere to that license and any modifications you make are also released under the same terms. The GPL does not permit you to include ZoneMinder in proprietary systems (see http://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem for details). If you wish to include ZoneMinder in this kind of system then you will need to license ZoneMinder under different terms. This is sometimes possible and you will need to contact me for further details in these circumstances.

Fedora

2015-03-11T14:30:07Z

Knnniggett: /* Installation */

The Fedora Project is a Red Hat sponsored, community-supported open source project. Its stated goal is to promote the rapid progress of free (as in freedom) and open source software and content, and its rapid innovation is possible using open processes and public forums.
'''

The project is led by the Fedora Project Board, which is comprised of community leaders and Red Hat members, and this group steers the direction of the project and of Fedora Core, the Linux distribution it develops. Red Hat employees work with the code alongside community members, and many Fedora Project innovations make their way into new releases of Red Hat Enterprise Linux.

ZoneMinder is developed on the Fedora distribution and no special actions are usually required for installation.

== Zmrepo - A ZoneMinder repository for RPM based distros ==
The ZoneMinder development team would like to introduce you to a new, easier way to install ZoneMinder on Fedora. Zmrepo is meant to be a turn-key solution. There is no compiling, no installing modules from CPAN, and no more complicated repository instructions.

This repository brings together a ZoneMinder rpm built by the development team, with all features enabled. This is in comparison to past ZoneMinder rpm's found in the Fedora repositories, which do not have ffmpeg support built-in. Zmrepo includes all dependencies that are not found in the default Fedora repositories. A few Perl modules are built by us, but all the rest of the dependencies are mirrored from popular sites such as EPEL and RPMFusion. There is no longer a need to add these additional repositories to your system. Zmrepo takes care of that for you.

==== Purpose ====
The primary purpose for developing ZoneMinder rpms for Fedora is to get an idea of how well ZoneMinder works on the bleeding edge of software development. We don't use Fedora in our production systems and consequently these rpms do not get the same share of testing that the ZoneMinder rpms for RHEL/CentOS do. However, they do give us the unique opportunity to solve any problems caused by new software widgets (looking at you systemd) before they trickle down to RHEL/CentOS.

==== Who Should Use ====
Those that want to use the latest and greatest packages available should use this repository over the RHEL/CentOS repository. Keep in mind that this comes with the real possibility Fedora may throw in something new, which might cause a problem with ZoneMinder.

==== Supported Versions ====
Fedora distributions have a relatively short life cycle. A new version of Fedora is scheduled to be released [https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle every 6 months]. It is the goal of the ZoneMinder development team to provide and support ZoneMinder rpms for the two most recent versions of Fedora. Today, those two versions are Fedora 21 and 20. Rpms built for older versions of Fedora may exist in zmrepo, but they will not be maintained and may be deleted at some point in the future.

==== Installation====

* Installation Instructions for i386 or x86_64 architectures on Fedora 20:
wget http://zmrepo.zoneminder.com/f/20/i386/zmrepo-20-3.fc20.noarch.rpm
sudo yum install --nogpgcheck zmrepo-20-3.fc20.noarch.rpm
sudo yum install zoneminder
less /usr/share/doc/zoneminder/README.Fedora

You must complete the steps documented in README.Fedora before ZoneMinder will function correctly.

* Installation Instructions for i386 or x86_64 architectures on Fedora 21:
wget http://zmrepo.zoneminder.com/f/21/i386/zmrepo-21-1.fc21.noarch.rpm
sudo yum install --nogpgcheck zmrepo-21-1.fc21.noarch.rpm
sudo yum install zoneminder
less /usr/share/doc/zoneminder/README.Fedora

You must complete the steps documented in README.Fedora before ZoneMinder will function correctly.

==Fedora 18 (alpha)==
*FIXED: ''if you get problems with Live Video not working'' due to a problem with the sockets. 
**ERROR: socket_sendto permission errors.
*Make sure your cgi-bin ScriptAlias is correct as shown below. 
*''ffmpeg libraries from Fedora rpms do not work'' with zm. You have to install from source (yuck).

This is how I got it installed... 

Do all the following as sudo (or root) 
'''install packages''' 
yum install mysql mysql-server zoneminder 

''' disable selinux 
vi /etc/selinux/config 
*change the word 'enforcing' to 'disabled' 

'''REBOOT'''

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf
* in the section - <Directory "/usr/share/zoneminder/www">
**remove the line "Deny from all # DELETE THIS LINE"
**remove the '-Indexes' on the Options line on Line 17 )I don't think the '-' is supposed to be there
**Comment out the Order and Allow lines and insert the new syntax 'Require all granted' as a new line
* I also got a ScriptAlias error for the cgi-bin/zm alias so I commented the cgi-bin scriptAlias in the /etc/httpd/conf/httpd.conf

#F18 /etc/httpd/conf.d.zoneminder.conf
Alias /zm "/usr/share/zoneminder/www"
<Directory "/usr/share/zoneminder/www">
Options FollowSymLinks
AllowOverride All
# NEW format
Require all granted
# The code unfortunately uses short tags in many places
php_value short_open_tag 1
#Deny from all # DELETE THIS LINE
</Directory>
ScriptAlias /cgi-bin "/usr/libexec/zoneminder/cgi-bin"
<Directory "/usr/libexec/zoneminder/cgi-bin">
Options +ExecCGI +MultiViews +SymLinksIfOwnerMatch
AllowOverride All
# NEW format
Require all granted
php_value short_open_tag 1
</Directory>
 
'''start httpd:''' 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 17==
'''install packages''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
systemctl start mysqld.service 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
systemctl start httpd.service 

'''start zoneminder:''' 
systemctl start zoneminder.service 

==Fedora 14==
'''install packages:''' 
yum install mysql mysql-server zoneminder 

'''setup mysql:''' 
/etc/init.d/mysqld start 
mysql_secure_installation # enable root password 
mysql -u root -p < /usr/share/zoneminder/db/zm_create.sql 
mysql -u root -p 
grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass'; 
use zm; 
quit 

'''setup apache web server:''' 
vi /etc/httpd/conf.d/zoneminder.conf # remove the line "Deny from all # DELETE THIS LINE" 
/etc/init.d/httpd start 

'''start zoneminder''' 
/etc/init.d/zoneminder start 

==Fedora 11, 12 and 13==
'''The Easy Way''' Adapted from a forum post by "hiredguntech" or just search the forum for "flowers for candy"

Step-by-step installation of ZM v1.24.2 on Fedora-12.

(1) load fc12 using the netinstall ISO (the CD wants to use dhcp and doesn't work well with an assigned fixed IP) - turn off 'office' and turn on 'server' and 'development'. Besure to include a large /var partition through custom partitioning and use localhost instead of what it suggests (domain.localhost ?). Also, if you're using a capture card install it (them) in the system before starting the netinstall CD. Save these steps as a .txt file so the code can be cut and paste into the terminal with ease.

[2] Remove evolution from task bar (right click... (not a requirement)).

[3] Set screensaver to NOT require password and set it to 20 minutes or more (menu-system::preferences::screensaver).

(4) Disable SELinux. (menu-system::Admin::SELinux Mgmnt; change system default enforcing mode to disabled).

[5] Enable sudo for yourself. From a terminal (menu-Application::System Tools::Terminal),
Code:

su

(enter root password)

echo ''''YourUserName''' ALL=(ALL) ALL' >> /etc/sudoers (put YOUR user name from FC12 installation in place of '''YourUserName''')

(6) Set up the RPM Fusion Repository (in open terminal).

Code:

rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm

rpm -ivh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

exit

exit (closes terminal window)

(7) Install the pre-requisites, (menu-System::Administration::Add/Remove Software) type in the search field the following package names and select each of the closest match (there will be 'other' packages related or similar named - look for the right one, and check-it.)

mysql-server

mysql-devel

pcre-devel

ffmpeg

ffmpeg-devel

Hit the 'Apply' button, accept any added packages, type root password, and let this stuff load.

[8] Install any updates that are available, its the yellow icon up by the time.

(9) Enable the services: web and db. (menu-System::Administration::Services) and find the following:

httpd

mysqld

for each of them hit the 'enable button' so you can start them later.

(10) Reboot. This allows all the services to start and settle in.

(11) Now add Zoneminder (menu-System::Administration::Add/Remove Software) Type Zoneminder in the search field select it and apply.

[13] '''Note:''' To edit as root: open a terminal (menu-Application::System Tools::Terminal), su to root, type 'gedit <path/filename>'. Now you have sufficient permissions to edit & save as root.

(14) Edit as root /etc/httpd/conf.d/zoneminder.conf to remove the 'Deny from All' line. It even says 'DELETE THIS LINE', so it should be easy to find. Save it.

(15) As root, [or with sudo] build the zm database (menu-Application::System Tools::Terminal).

Code:

su

(enter root password)

mysql mysql < /usr/share/zoneminder/db/zm_create.sql

mysqladmin reload

mysql mysql

grant select,insert,update,delete on zm.* to 'zmuser'@localhost identified by 'zmpass';

\q

exit

exit

(16) Enable zoneminder. (menu-System::Administration::Services) and find zoneminder. Enable it. You can start the service hear also, Or in a terminal:

Code:

service zoneminder start

[18] Last thing - edit the SECOND entry of short_open_tag down at line 229. Again as root (menu-Application::System Tools::Terminal), gedit /etc/php.ini

Change short_open_tag from 'off' to 'on'

[19] reboot. open browser, type 'localhost/zm'

[20] It may be necessary to change the ffmpeg path in options::images to get ffmpeg to make videos. Generally removing the /local from the existing path will fix this issue

'''Or (the original wiki walk through)'''

You should be able to just do "yum install zoneminder", create the zm database, find the zm_create.sql file (rpm -ql zoneminder) and import it to mysql, then start zoneminder. Plus allow web access. Edit /etc/httpd/conf.d/zoneminder.conf and comment out (#) or delete this line :-

Deny from all # DELETE THIS LINE

Restart/reload apache

sudo service httpd restart

This didn't work for me due to 2 problems. First was php.ini section short_open_tag = Off, set to on

short_open_tag = On

Restart/reload apache

sudo service httpd restart

The other problem was zm_create.sql had duplicate indexes reported using phpMyAdmin. Removed all "INSERT INTO MonitorPresets" and "INSERT INTO MonitorPresets" in zm_create.sql and that imported cleanly. Alternatively just import from the command line mysql -u zmuser -p < zm_create.sql

http://www.zoneminder.com/forums/viewtopic.php?p=50242

'''Manual Install Version 1.24.2 with ffmpeg enabled'''

Version 1.23.3 has always compiled ok on Fedora 9/10/11 but I had problems with version 1.24.2.

Problems with compiling fixed by adding #include <cstdio> to all .cpp files in src directory and removing ccache package (yum remove ccache)

http://www.zoneminder.com/forums/viewtopic.php?p=55152

http://www.zoneminder.com/forums/viewtopic.php?t=12515&sid=0da85eb2fc78917d7a78cf788603a320

If using ffmpeg and ffmpeg-devel packages you may see problem compiling with libavutil.a . I could not get ffmpeg to compile so downloaded the Fedora source package and compiled it manually.

yumdownloader --source ffmpeg

sudo rpm -Uvh ffmpeg-0.5-5.20091026svn.fc12.src.rpm

Needed the following packages

sudo yum install dirac-devel faad2-devel gsm-devel imlib2-devel lame-devel libdc1394-devel libtheora-devel libvdpau-devel openjpeg-devel \
schroedinger-devel speex-devel texi2html x264-devel xvidcore-devel yasm

See http://fozzolog.fozzilinymoo.org/tech/2009/11/recompiling-ffmpeg-for-fedora-12-to-add-faac-support.html (don't need to add faac support, just follow procedure)

My rpmbuild failed so from the BUILD/ffmpeg-20091026

make
sudo make install
sudo make install-libs

and configured ZoneMinder to use /usr/local for FFMPEG

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost \
ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr -L/usr/lib/mysql" ZM_SSL_LIB=openssl --with-ffmpeg=/usr/local

==Fedora 8==
* Have packages for Apache and MySQL installed on the system.
* Install the zoneminder RPM package on the system
: Fedora Information for package zoneminder
: * http://koji.fedoraproject.org/koji/packageinfo?packageID=4691
* Configure zoneminder
* Make sure Apache and MySQL services are running
* Edit the zoneminder.conf apache configuration file to allow web connections
vi /etc/httpd/conf.d/zoneminder.conf
* Build the MySQL database table for zoneminder
mysql -p -u root mysql < /usr/share/zoneminder/db/zm_create.sql > mysqladmin -p -u root reload

The Fedora RPM creates /var/log/zoneminder, but the database scripts point logs to /tmp, rather than the new directory.
* Click '''Options''', '''Paths''' tab, and change
ZM_PATH_LOGS = /var/log/zoneminder
* Click '''Options''', '''Debug''' tab, and change
ZM_EXTRA_DEBUG_LOG = /var/log/zoneminder/zm_debug.log+

* Install ffmpeg on Fedora.
Due to licensing the ffmpeg package is absent from Fedora. It can be added from [[Fedora_Linux_Distribution_Reference#Livna:_Get_Important_Packages_Missing_From_Fedora|Livna]].
wget http://rpm.livna.org/livna-release-8.rpm
rpm -ih livna-release-8.rpm
yum install ffmpeg
yum install ffmpeg-devel
Which provides the following: ffmpeg-libs-0.4.9-0.41.20071011.lvn8, ffmpeg-0.4.9-0.41.20071011.lvn8, ffmpeg-devel-0.4.9-0.41.20071011.lvn8

* Test ffmpeg
ffmpeg -f image2 -i %03d-capture.jpg /tmp/movie.mpg

==Fedora 7==
* Builds From source - see [[Fedora Core 6 Step-by-Step]] '''AS WELL AS''' [http://www.zoneminder.com/forums/viewtopic.php?t=9414 Fedora 7 forum topic]
*RPMs are Available in the '''main Fedora 7 distribution''', and in the development 'rawhide' tree.
**Its as easy as running: yum install zoneminder
**Take a look at [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 6==
*Build from source [[Fedora Core 6 Step-by-Step]]

* RPMs are also available right now in '''Fedora Extras''' for Fedora Core 6.
** [http://www.zoneminder.com/forums/viewtopic.php?t=9674 The Announcement post in the forums]

==Fedora Core 4==
* http://www.zoneminder.com/forums/viewtopic.php?t=5991 
Set web user and group correctly and set the log dir to a writeable location.
With FC4 there are three things that must be done to get ZM running,:
#is in the /etc/ld.so.conf.d/ dir created a file with 775 perm called zm.conf and add the line '/usr/local/lib' to it and type 'ldconfig' once it is added, also with a fresh install of FC4 make sure SE linux is disabled if you are not using it. Check your log path in options under the paths tab. This will tell you were the log are going to be put.
#Second make sure the path exists.
#Third create the log files if they do not exist and make sure that they have the correct permissions. '''If zm can not open and write the log files, it will not start. '''

CentOS

2015-03-11T14:29:23Z

Knnniggett: /* Installation */

The intent of this walk through is to install a very base/bare bones installation of CentOS that runs only ZoneMinder. This would be for a dedicated ZoneMinder server with no GUI or any unnecessary services running. The reason for the very light-weight installation is to make the majority of system resources available to ZoneMinder, not the OS. With this installation, memory is reduced to around 140-160MB, and CPU usage is practically nonexistent. The CentOS base installation is very easy to install and doesn’t take too much time as long as you have some type of broadband connection. There are many ways to install CentOS, but this article covers only two, because they are related.

''All CLI operations/commands in this How-To are done as root, in the /root directory. The reasoning is that this system would be in a secure environment to begin with. However, if you need to add a user to run these services to better secure the system, then you can, but keep in mind that some items must run as root.''

== Zmrepo - A ZoneMinder repository for RPM based distros ==
The ZoneMinder development team would like to introduce you to a new, easier way to install ZoneMinder on CentOS. Zmrepo is meant to be a turn-key solution. There is no compiling, no installing modules from CPAN, and no more complicated repository instructions.

This repository brings together a ZoneMinder rpm built by the development team, with all features enabled. It also includes all dependencies that are not found in the default CentOS repositories. A few Perl modules are built by us, but all the rest of the dependencies are mirrored from popular sites such as EPEL and RPMFusion. There is no longer a need to add these additional repositories to your system. Zmrepo takes care of that for you.

==== Who Should Use ====
The development team strictly uses CentOS, but these packages should work on Red Hat Enterprise Linux and Scientific Linux. The rpms in zmrepo are intended to work with ''default installations'' of these Linux distributions. Modified versions are not guaranteed to work. Continue to the Disclaimer below for details.

Please report any issues with RHEL and SL, as we have no way of pro-actively discovering them.

==== Disclaimer ====
This could also be appropriately called '''Who should not Use''' zmrepo.

The goal behind CentOS is that of an enterprise operating system. Stability is prioritized over the latest and greatest version of a particular package. Fortunately, bug fixes are backported. Consequently, you should ''never'' replace the core packages in CentOS! If you truly think that you "have to have" some package that is newer than what is found in the default repository then you should consider using a different Linux distro.

The CentOS maintainers have a great write-up that describes this in much more detail [http://wiki.centos.org/PackageManagement/SourceInstalls here]. Pay close attention to the all the do's, dont's, and "this will break" comments.

Zmrepo extends this same philosophy onto ZoneMinder. While ZoneMinder requires many dependencies to work, zmrepo will not overwrite any core packages. It only adds packages that, otherwise, would not be available.

One other case is worth mentioning. This repository is intended ''only'' for those who have installed RHEL/CentOS/SL using the '''official installation media for that distribution'''! This means that these rpms are not intended to work with third parties that release their own spin of CentOS, which contain their own third party application preinstalled. Third parties are allowed to modify the original distribution in any way, which means we can't guarantee the rpms in zmrepo will be compatible.

For example, if you installed "CentOS" using an installation disk from an Astericks vendor, then the rpms in zmrepo are known not to work.

==== Installation ====

* Installation Instructions for i386 or x86_64 architectures on CentOS 6:
wget http://zmrepo.zoneminder.com/el/6/i386/zmrepo-6-4.el6.noarch.rpm
sudo yum install --nogpgcheck zmrepo-6-4.el6.noarch.rpm
sudo yum install zoneminder
less /usr/share/doc/zoneminder-*/README.CentOS

You must complete the steps documented in README.CentOS before ZoneMinder will function correctly.

NOTE: RHEL users must enable the "rhel-6-server-optional-rpms" repositoy on their system before attempting to install ZoneMinder.

A YouTube video that steps through the installation can be viewed [https://www.youtube.com/watch?v=l2lLvl8WxfU here.]

* Installation Instructions for x86_64 architecture (only) on CentOS 7:
wget http://zmrepo.zoneminder.com/el/7/x86_64/zmrepo-7-3.el7.centos.noarch.rpm
sudo yum install --nogpgcheck zmrepo-7-3.el7.centos.noarch.rpm
sudo yum install zoneminder
less /usr/share/doc/zoneminder-*/README.Centos7

You must complete the steps documented in README.Centos7 before ZoneMinder will function correctly.

'''WARNING: CentOS 7 support is still being developed. This repo is currently not for production and might not yet be error free.'''

== CentOS 5.6 & ZoneMinder 1.25.0 ==
This guide is for CentOS v5.6 (Notes for using this guide with CentOS 6 are in chapter 2.) with ZoneMinder v1.25.0 which are the newest released versions as of this update (Summer 2011). If you are attempting to install newer versions of either using this guide, you will have to adjust file and directory names denoted below.

=== Step One - Get CentOS ===
You can download the “.iso” file(s) for CentOS from http://www.centos.org/ 
Alternatively download the net-install version of CentOS which is basically just the first CD.
Here is one location to download the net-install version: 
Download i386: http://mirror.symnds.com/distributions/CentOS-vault/5.6/isos/i386/CentOS-5.6-i386-netinstall.iso 
Download 64 bit: http://mirror.symnds.com/distributions/CentOS-vault/5.6/isos/x86_64/CentOS-5.6-x86_64-netinstall.iso 
Mirrors List: http://mirror.centos.org/centos/5/isos/

=== Step Two - Installation Source ===
Regardless of which method you use, the next few steps are the same. 
Begin by booting your system up with either cd/dvd. 
Choose the options that best fit your environment until you reach the “Installation Method”.

[[Image:centosnetinstal-http.png]]

Choose '''HTTP''' ONLY if you are using the net-install method. Otherwise, you probably want to choose '''Local CDROM'''. 

If you are using the net-install method then enter: 
Website Name: '''mirror.centos.org''' 
CentOS Directory: (for i386) '''/centos/5.6/os/i386''' 
CentOS Directory: (for 64 bit) '''/centos/5.6/os/x86_64'''

=== Step Three - Installation Packages ===
On the first screen, un-check "Desktop - Gnome" then check "Server" (not Server-GUI) 
Make sure that you have "Customize now" selected at the bottom. (do not check "Packages from CentOS Extras")

[[Image:centosinstall-packages1.png]]

Click "Next" to continue 

Once presented with the custom package selection, un-check/check the following:
Applications = Check only "Editors" and "Text Based Internet"
Development = Check only "Development Libraries" and "Development Tools"
Servers = Un-check everything
Base System = Check only "Base" (you can check Administration Tools and System Tools if you need them, but they are not necessary)

[[Image:Centosinstall-packages2.png]]

Now let the system finish the installation.

[[Image:centosisntall-end.png]]

=== Step Four - Configuration ===
After the first reboot, the setup screen should appear. If not, log into the system and type "setup"

[[Image:centosinstall-setup1.png]]

Select "Firewall Configuration" and set the "Security Level" and "SELinux" to "Disabled."

[[Image:centosinstall-setup2.png]]

Next, we are going to disable a number of system services. Go back to the setup screen and select "System Services" 
Un-Check:
apmd
bluetooth
cups
hidd
ip6tables
iptables
netfs
nfslock
pcscd
portmap
After disabling the services, select "Disable Now and On Boot", exit the setup tool, and log into the system if you haven't already.
*Screen is a simple program that allows you to run commands from a "Hosted" command line interface. This helps if you loose your connection to the server for any reason in that it enables you to resume (screen -r) right where you left off. Often times, I will start a large update/upgrade, leave it for the day, then come back and see where it's at later. Screen allows you to do that without having to be connected.
*Install Screen
yum install screen
*To start a screen session just type
screen
*If you get disconnected and need to resume your session of screen simply type
screen -r

=== Step Five - Installing ZoneMinder 1.25.0 ===
First, we need to download files and prepare the system
*Add the RPM Forge repository to CentOS. This will allow the installation of a number of services/applications later without having to manually install them.
<pre># For i386 CentOS 5.x run:
rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm

# For 64 bit CentOS 5.x run:
rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm</pre>
*Download the needed files, ZoneMinder 1.25.0 and the Cambozola addon
wget http://www2.zoneminder.com/downloads/ZoneMinder-1.25.0.tar.gz
wget http://www.zoneminder.com/sites/zoneminder.com/downloads/cambozola.jar
*Now let's install all the services and programs that will be needed (''If you encounter any dependency errors using yum, try running '''yum clean all''' then re-try the install command(s).'')

*tip: Copy/paste two lines at a time

<pre>
yum -y install mysql mysql-server mysql-devel php php-gd php-mysql httpd gcc \
pcre-devel gd mod_ssl glib2-devel gcc-c++ ntp gnutls-devel ImageMagick

yum -y install libjpeg-devel perl-Archive-Tar perl-MIME-Lite perl-MIME-tools \
perl-Date-Manip perl-LWP-UserAgent-Determined

yum -y install perl-PHP-Serialization perl-Device-SerialPort perl-Archive-Zip perl-Sys-Mmap \
perl-Module-Load subversion git yasm bzip2 bzip2-devel bzip2-libs lbzip2</pre>
*Now let's update everything within the new CentOS install
yum -y update
*At this point, it might be useful to reboot your system. Oddly, sometimes things don't work right unless you reboot after all the updates
reboot -or- shutdown -r now
*After rebooting, log into your system
==== Install ffmpeg ====
*Now we need to make sure we use the latest "tested" version of "ffmpeg". This is the latest version of ffmpeg that the ZoneMinder developers have tested with. Download, compile and install ffmpeg:
<pre>git clone git://git.videolan.org/ffmpeg.git
cd ffmpeg
./configure --enable-gpl --enable-shared --enable-pthreads
make
</pre>

*The following commands must be done as '''root'''

<pre>
make install
make install-libs
</pre>
edit /etc/ld.so.conf and add the line "/usr/local/lib"
<pre>
ldconfig -v
</pre>

*Next, run 'ffmpeg' from the command line. Make sure you do not get any errors:

<pre>
ffmpeg
</pre>

*If 'ffmpeg' runs correctly, you'll see something similar to this:

<pre>
ffmpeg version N-32260-gaebb56e, Copyright (c) 2000-2011 the FFmpeg developers
built on Aug 31 2011 21:41:49 with gcc 4.1.2 20080704 (Red Hat 4.1.2-50)
configuration: --enable-shared --enable-swscale --enable-gpl --enable-pthreads
libavutil 51. 14. 0 / 51. 14. 0
libavcodec 53. 12. 0 / 53. 12. 0
libavformat 53. 10. 0 / 53. 10. 0
libavdevice 53. 3. 0 / 53. 3. 0
libavfilter 2. 37. 0 / 2. 37. 0
libswscale 2. 0. 0 / 2. 0. 0
libpostproc 51. 2. 0 / 51. 2. 0
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'
</pre>

==== Enable services ====
*Turn everything on. These commands must be run as root.

<pre>
chkconfig httpd on
chkconfig mysqld on
chkconfig ntpd on
service httpd start
service mysqld start
service ntpd start
</pre>
==== Install Zoneminder ====
*Next, we need to extract the contents of the ZoneMinder "tar" file, then jump into its directory.
<pre>
cd /root/ # Or your work directory for this installation
tar -zxvf ZoneMinder-1.25.0.tar.gz
cd ZoneMinder-1.25.0
</pre>
*Now we are going to configure ZoneMinder with some additional parameters. What is listed are the default CentOS directory locations.
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin

Note: It seems for Zoneminder to build with newer versions of ffmpeg, (certainly 0.6.3) you'll need to append CPPFLAGS="-D__STDC_CONSTANT_MACROS" to the end of the
./configure line thus:

./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-ffmpeg=/usr/local/share/ffmpeg CPPFLAGS="-D__STDC_CONSTANT_MACROS"

There is a section in the FAQ ''"When running configure, I get a lot of messages about not being able to compile the ffmpeg libraries"'' about this [[http://www.zoneminder.com/wiki/index.php/FAQ]].

Worth mentioning here is the section in the FAQ under the heading "''My load is too high, how can I reduce it?''" [[http://www.zoneminder.com/wiki/index.php/FAQ]]. This descibes how you can possibly reduce CPU load by half by
changing the system's jpeg libraries and building Zoneminder with processor specific instructions.
Since CentOS 6.4 CentOS now comes with libjpeg_turbo as the standard JPEG library leading to a more optimised Zoneminder.

By default ZM_DB_HOST=localhost, ZM_DB_NAME=zm, ZM_DB_USER=zmuser, and ZM_DB_PASS=zmpass.
*Change "zmuser" (if you want) with the user that you will use within MySQL to access the ZoneMinder database
*Change "zmpass" with the password you will be using with the "zmuser" account
So if you wish to change it, use a command like:
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass

*if you get the configure "error zm requires libmysqlclient.a" with 64 bit CentOS add the following to the end of your configure statement
--with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql"

e.g. For CentOS 5.6 64-bit with support for ffmpeg. The whole command must be executed on one line. Make sure to change the '''zmpass''' to a password that matches your installation.
<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-ffmpeg=/usr/local/share/ffmpeg --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser ZM_DB_PASS=zmpass --with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql" CXXFLAGS="-D__STDC_CONSTANT_MACROS"
</pre>
* Run '''make''' and '''make install''' after running the configuration steps above.

make
# Run the next command as root
make install

==== Configure MySQL ====
*Need to add a password for the root user of MySQL
*Create the zm database
*Create the zm database user with permissions and password
mysql
mysql> SET PASSWORD FOR root@localhost=PASSWORD('new_root_password');
>Query OK, 0 rows affected (0.00 sec)
mysql> create database zm;
>Query OK, 1 row affected (0.01 sec)
mysql> CREATE USER 'your_zm_user'@'localhost' IDENTIFIED BY 'your_zm_password_from_above';
Query OK, 0 rows affected (0.01 sec)
mysql> grant CREATE, INSERT, SELECT, DELETE, UPDATE on zm.* to your_zm_user@localhost;
>Query OK, 0 rows affected (0.02 sec)
mysql> exit
>Bye
*Import the tables into the zm database
cd /root/ZoneMinder-1.25.0
mysql -u root -p zm < db/zm_create.sql

==== Finalize Installation of ZoneMinder ====
'''All remaining CLI commands need to be run as root.'''
*Make ZoneMinder startup automatically after a reboot
# from the ZoneMinder-1.25 source directory
cp scripts/zm /etc/init.d/
chmod +x /etc/init.d/zm
chkconfig zm on
*Add the Cambozola Java web interface
cp cambozola.jar /var/www/html/zm/
*Make sure you have permission to view it from apache:
chown apache:apache /var/www/html/zm/cambozola.jar
*Start ZoneMinder
service zm start

Note: You may get an error when you try to start Zoneminder using the 'zm' startup script as per this forum post: [[http://www.zoneminder.com/forums/viewtopic.php?f=21&t=17827]] .
The reason for this was the default 'zm' startup script was formatted with DOS line endings. If you get the errors as detailed in the above post then the fix is to convert the
'zm' file to use UNIX style line endings. You can do this in the Vim text editor whilst editing the 'zm' file thus: ':set fileformat=unix' then save the file ':wq'. You can also
use the utility dos2unix to convert the file.

* tick the box for support for the Cambozola addon within your ZoneMinder installation: http://ip-address/zm (Options->Images tab->OPT_CAMBOZOLA)

Now have fun and add your cameras to ZoneMinder knowing you now have a very stable and streamlined OS to run it on.

== CentOS 6 Notes ==

The installation for CentOS 6 is pretty much the same.
Download CentOS 6 minimal installation ISO (CentOS-6.0-i386-minimal.iso – 257MB). Burn to CD and install. We only want to be running in console text mode not GUI graphics mode. During installation configure network and tick to enable network adapter.
* Login as root and update the base install:
<pre>yum -y update</pre>
* Install required packages, other useful packages, and their dependencies
<pre>
yum groupinstall core
yum groupinstall base
yum install gcc gcc-c++ wget bison mysql-devel mysql-server php php-mysql php-pear php-pear-DB php-mbstring \
nano tftp-server httpd make ncurses-devel libtermcap-devel sendmail sendmail-cf caching-nameserver \
sox newt-devel libxml2-devel libtiff-devel php-gd audiofile-devel gtk2-devel subversion nano kernel-devel \
bison-devel ncurses zlib zlib-devel openssl openssl-devel gnutls-devel php-process perl-Time-HiRes
</pre>

Suggestion:
To remove various configure/make errors in Centos 6.2, you may also want to install:<pre>
bzip2-libs ffmpeg-devel ffmpeg-php perl-Net-SFTP-Foreign perl-Expect perl-LWPx-ParanoidAgent.x86_64</pre>

Now we continue from step four (4).
==== Installation of ZoneMinder ====
* In step five (5) the correct RPM Forge repository is:
<pre># For i686 CentOS 6.x run:
rpm -Uhv http://apt.sw.be/redhat/el6/en/i386/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.i686.rpm

# For 64 bit CentOS 6.x run:
rpm -Uhv http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm</pre>

* In step five (5) the command that seems to configure zoneminder correctly is:
<pre>
CXXFLAGS=-D__STDC_CONSTANT_MACROS ./configure --with-webdir=/var/www/html/zm \
--with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache \
ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=your_zm_user ZM_DB_PASS=your_zm_password ZM_SSL_LIB=openssl
</pre>

Suggestion:
For Centos 6.2, I used the following configure string for success:<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=<zm user> ZM_DB_PASS=<zm user passwd> ZM_SSL_LIB=openssl --with-extralibs="-L/usr/lib64 -L/usr/lib64/mysql" --with-ffmpeg=/usr/share/ffmpeg CXXFLAGS="-D__STDC_CONSTANT_MACROS" </pre>

==== Troubleshooting FFmpeg Errors Building ZoneMinder ====
Using the git version of FFmpeg can cause the ZoneMinder make process to fail with unresolved symbols in ffmpeg. To remedy this, use version 0.6.5 of FFmpeg with the same configure instructions as the normal install above.
FFmpeg 0.6.5: http://ffmpeg.org/releases/ffmpeg-0.6.5.tar.bz2
==== Troubleshooting Blank Page ====
If everything went ok but when accessing zoneminder's web page at http://localhost/zm, the page is blank this means that there is a problem with PHP short tags. Edit setting short_open_tag in php.ini (/etc/php.ini) and change it to On.
* Restart apache server with:
<pre>service httpd restart</pre> and you should be up and running.
==== Trouble shooting full drive with CentOS 6 ====
The default drive structure has chaned from that of CentOS 5 having the full drive allocated to the /root partition. CentOS 6 by default makes a logical volume 'LVM' of 10% your drives space for the /root partition and the remaining drive as the /home partion with the exception of the swap and boot partitions.

The will cause Zoneminder to fill the /root partition as the /var/www/html/zm/events directory is by default located here, you can use the system-config-lvm utility to re-adjust this partition balance if your system has been installed with the default partition structure.

It is best to install CentOS 6 with a custom partition layout that is the same as CentOS 5 structure, you can also if using a single physical had drive do with out the LVM drives and create an EXT4 /root partion along with the standard /boot and /swap partitions.

----

[[== '''P.S.''' ==]] aspcicc@jumpy.it
(Update: This does not appear to be required any more.)

Hi! and thanks for your guide.. i want to add a little correction that have made me crazy to resolve, when I poweroff or reboot system i obtain an error related to mysql database and i have understood that the problem was because mysqld is stopped before zoneminder to be more specific there isn't a link under rc0.d (halt) and rc6.d (reboot) to zoneminder that for this lack is simply killed by killall. To resolve this problem you need to add at the start of zm (under /etc/init.d) the line

' # chkconfig: 345 99 01 ' (without ' of course)

and then run
chkconfig --level 345 zm on
chkconfig --level 06 zm off

So the link to shutdown zm is created under rc0.d and rc6.d and zoneminder is started at the end of poweron and stopped at the beginning of the poweroff

For information about priority starting and stopping processes see: http://www.netadmintools.com/art94.html

----

Added Dependency: ImageMagick

Removed Dependency: perl-Time-HiRes, which causes a conflict with the default perl package.

Also, mysql seems to install with no password for the root user, and the zm DB create script creates the database on the fly, which means that the database create command needs to have the "-p zm" removed from the command line.

Could someone verify that this is correct, to make sure it's not just something I missed?

Thanks!
terry@cnysupport.com

----
Struggling to get x264 and ffmpeg working? I used the latest SVN versions not the Centos packages. But I was getting

''ffmpeg: error while loading shared libraries: libavdevice.so.53: cannot open shared object file: No such file or directory''

I followed these instructions:

<pre>cd /etc/ld.so.conf.d</pre>

* add another file: custom-libs.conf
* inside, put :

<pre>/usr/local/lib</pre>

* save the file
* run ldconfig
<pre>ldconfig</pre>

BeeryGaz

----

==== Failed monitors or ZM refusing to start ====
A problem that took me some time to figure out on two installations was SElinux.
SElinux stops Zoneminder from accessing some system parts or doing some functions so will cause various errors or simply drive you nuts trying to figure out.

Look at the following page on how to disable SElinux or use permissive mode.

<pre>http://www.centos.org/docs/5/html/5.2/Deployment_Guide/sec-sel-enable-disable.html</pre>

Some of the errors that I was getting with a fresh install on CentOS 6 was
<pre>
2013-02-16 16:13:10.828590 zmwatch 14898 ERR Can't open memory map file '/dev/shm/zm.mmap.1': No such file or directory zmwatch.pl
2013-02-16 16:13:10.736988 zmfix 15317 ERR Can't stat /dev/video0: Permission denied zmfix.cpp
</pre>

----
== ZoneMinder 1.26.x ==

Zoneminder after a long period of none development is now being developed by the community, these notes are to try and help with the installation of the new release on CentOS 5 and CentOS 6.
All testing has been done on a CentOS 6.4 fresh install server.

=== Cmake installation notes ===

Compiling of Zoneminder can now be done with the 'Cmake' command in replacement of the ./configure command this should automatically configure the build with the minimum of parameters. The 'Cmake' command at time of writing produced a partially working installation with the main files installed into /usr/local/bin/zoneminder and associated folders, different from the above guides.

The webfiles require to be linked via a zoneminder.conf file located with in the /disto/redhat directory inside the build directory that requires to be coped to the /etc/httpd/conf.d directory, this will need to be edited to the correct location of the webfiles and remove the local only command as indicated with in the file.

The Cmake install failed to use my BTTV capture card producing various errors with a potential solution given here <pre>http://www.zoneminder.com/forums/viewtopic.php?f=30&t=21709</pre>

=== ./configure compile ===

To install via the traditional ./configure method you first need to run the ./bootstrap.sh file to generate the required configure file, the install can then progress as the above installation guides.

This method has produced a fully working installation at time of writing.

== pt_BR Instructions ==

Here is a good walkthrough install of zoneminder in CentOS using the rpm package method. It is intended to Portuguese (pt or pt_BR) audience.

<pre>http://dulimind.blogspot.com.br/2015/02/zoneminder-no-centos-6-metodo-facil-com.html</pre>
----

[[Categories: Linux distributions]]