FAQ - Revision history

Worm6666: /* Sample FAQ Heading */

2021-10-04T09:01:26Z

Sample FAQ Heading

← Older revision		Revision as of 05:01, 4 October 2021
Line 12:		Line 12:
	=== Sample FAQ Heading ===		=== Sample FAQ Heading ===
	Sample FAQ answer.		Sample FAQ answer.

			----

			=== Montage Layout Names duplicity ===

			Problem with Montage Layout naming - using same name <b><i>causes creating new one instead of updating existing one...</i></b><br>
			Ubuntu 20.04.3 LTS Focal Fossa - easy setup - thank You ZoneMinder !<br>
			- but then You need to access the database "zm" - and I searched and found easy solution and modified a little...<br>
			- in this case - I use webui of phpmyadmin to manage the content of database - it is easy for beginners,<br>
			and You cannot harm the database so easy like with bad syntax on command line...<br>

			<b>1./ log-in to terminal as su</b><br>
			sudo su
			(provide password for Your superuser)<br>

			<b>2./ install phpmyadmin</b><br>
			apt-get install phpmyadmin
			- I have used for both apache2 and lighttpd<br>
			- I have created custom password (for example: PASSword123)<br>

			<b>3./ modify access to databases for default user "phpmyadmin"</b><br>
			- enter mysql:<br>
			mysql -u root -pzm
			- pzm is for -p and zm because "-p zm" with space don't work...<br>
			- I have used command for all databases for easy use...<br>
			GRANT ALL ON . TO 'phpmyadmin'@'localhost'
			- this causes that user "phpmyadmin" has all databases on host visible and editable<br>
			- normaly it would look like this - only for "zm" database<br>
			GRANT ALL ON zm.* TO 'phpmyadmin'@'localhost'

			<b>4./ delete or modify unwanted layouts</b><br>
			- connect from browser:
			http://localhost/phpmyadmin
			- username "phpmyadmin"
			- password "PASSword123"
			- open database "zm" and look for table "MontageLayouts"<br>
			- do what You want (study how layout is defined...) :-)<br>
			- or simply delete unwanted or broken layout - after this refresh page with layout and<br>
			in the dropdown menu of layouts is the deleted one (or more) not more available...<br>

			<b><i>Don't forget - MYSQL and PHPMYADMIN are two DIFFERENT things...<br>
			- also take care about usernames and passwords</i></b>

			----

Asker: https://github.com/ZoneMinder/ZoneMinder/issues/1169

2015-12-05T11:17:23Z

https://github.com/ZoneMinder/ZoneMinder/issues/1169

Show changes

Stevegilvarry at 12:59, 13 November 2015

2015-11-13T12:59:13Z

← Older revision		Revision as of 08:59, 13 November 2015
Line 467:		Line 467:
	=== How can I use ZoneMinder to trigger something else when there is an alarm? ===		=== 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.		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.		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. This script will check every second and perform the action so you may want to store the last state and only perform your action on change.

	<pre>#!/usr/bin/perl -w		<pre>#!/usr/bin/perl -w
Line 477:		Line 477:
	$\| = 1;		$\| = 1;

	~~zmDbgInit( "myscript", level=>0, to_log=>0, to_syslog=>0, to_term=>1 );~~		my $dbh = DBI->connect( "DBI:mysql:database=".$Config{ZM_DB_NAME}.";host=".$Config{ZM_DB_HOST}, $Config{ZM_DB_USER}, $Config{ZM_DB_PASS} ) or croak( "Can't connect to db" );

	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 $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)";

Asker at 20:08, 13 August 2015

2015-08-13T20:08:29Z

← Older revision		Revision as of 16:08, 13 August 2015
Line 1:		Line 1:
	~~PP was here~~

	== ZoneMinder Frequently Asked Questions ==		== ZoneMinder Frequently Asked Questions ==

Asker at 20:07, 13 August 2015

2015-08-13T20:07:30Z

← Older revision		Revision as of 16:07, 13 August 2015
Line 1:		Line 1:
			PP was here

	== ZoneMinder Frequently Asked Questions ==		== ZoneMinder Frequently Asked Questions ==

Knnniggett: /* Why does ZM stop recording once I have 32000 events for my monitor? */

2015-04-04T14:41:05Z

Why does ZM stop recording once I have 32000 events for my monitor?

← Older revision		Revision as of 10:41, 4 April 2015
Line 266:		Line 266:

	=== Why does ZM stop recording once I have 32000 events for my monitor? ===		=== 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~~.		Storing more than 32k files in a single folder is a limitation of some filesystems. To avoid this, enable USE_DEEP_STORAGE under Options.

	~~This~~ is a ~~limitation~~ of ~~the ext3 filesystem that most Linux distributions use. One directory cannot hold more than 32k approx files~~.		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.

	~~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.		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 ~~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!		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		# Stop ZoneMinder
Line 283:		Line 283:
	Note that you can re-run the migrate-events command if any error messages scroll off the screen.		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		You can read about the lack of a limit in the number of sub-directories in the ext4 filesystem at:
	sub-directories in the ext4 filesystem at:
	http://kernelnewbies.org/Ext4		http://kernelnewbies.org/Ext4
	and see what tools may assist in your use of this filesystem in:		and see what tools may assist in your use of this filesystem in:
	http://ext4.wiki.kernel.org/index.php/Ext4_Howto		http://ext4.wiki.kernel.org/index.php/Ext4_Howto
	~~Note that while GParted 0.5.2 recognizes ext4 partitions, at least in~~		If you search for ext3 or reiserfs on the forums you will find various threads on this issue with guidance on
	~~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.		how to convert.

Knnniggett: /* Why does ZM stop recording once I have 32000 events for my monitor? */

2015-04-04T14:36:56Z

Why does ZM stop recording once I have 32000 events for my monitor?

← Older revision		Revision as of 10:36, 4 April 2015
Line 274:		Line 274:
	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!		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		# Stop ZoneMinder
	- Backup your event data and the dB if you have the available storage		# Backup your event data and the dB if you have the available storage
	- Enable USE_DEEP_STORAGE under Options.		# Enable USE_DEEP_STORAGE under Options.
	- From the command line, run "sudo zmupdate.pl --migrate-events"		# From the command line, run "sudo zmupdate.pl --migrate-events"
	- Monitor the output for any events that fail to convert.		# Monitor the output for any events that fail to convert.
	- After the conversion completes, you can restart ZoneMinder		# 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.		Note that you can re-run the migrate-events command if any error messages scroll off the screen.

Knnniggett: /* Why does ZM stop recording once I have 32000 events for my monitor? */

2015-04-04T14:29:20Z

Why does ZM stop recording once I have 32000 events for my monitor?

← Older revision		Revision as of 10:29, 4 April 2015
Line 266:		Line 266:

	=== Why does ZM stop recording once I have 32000 events for my monitor? ===		=== Why does ZM stop recording once I have 32000 events for my monitor? ===
	~~This~~ is a ~~limitation~~ of ~~the ext3 filesystem that most Linux distributions use. One directory cannot hold more than 32k approx files~~.		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.

	~~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. However it is relatively and although few issues have been reported thus far it should be considered in beta for now. Also, it is currently not possible to migrate saved events between the different storage formats so is only suitable for new installations or if you do not mind losing saved events.		This is a limitation of the ext3 filesystem that most Linux distributions use. One directory cannot hold more than 32k approx files.

	~~So if~~ you do not ~~want~~ to ~~use~~ the ~~deeper filesystem~~ option		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.
	~~(Options~~-~~>Paths~~-~~>ZM_USE_DEEP_STORAGE), for now~~ you have ~~to reduce~~ the
	~~number of~~ events ~~or store your images (e~~.~~g. /var/lib/zoneminder) on a~~		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!
	~~partition~~ that ~~uses a different filesystem such as ext4 or reiserfs~~.
			- 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		You can read about the lack of a limit in the number of

Unbroken: /* What does a 'Can't shmget: Invalid argument' error in my logs mean? and my cameras won't display video at higher resolutions. */

2014-12-09T10:26:47Z

What does a 'Can't shmget: Invalid argument' error in my logs mean? and my cameras won't display video at higher resolutions.

← Older revision		Revision as of 06:26, 9 December 2014
Line 110:		Line 110:
	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.		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' you should see this area and the size of memory it currently allows. 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.		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.		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.

Bbunge: /* How can I stop ZoneMinder filling up my disk? */

2014-11-11T02:18:01Z

How can I stop ZoneMinder filling up my disk?

← Older revision		Revision as of 22:18, 10 November 2014
Line 25:		Line 25:
	PURGE BY AGE		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".		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.		Save with 'Run Filter In Background' enabled to have it run automatically.