SMS Notifications - Revision history

Burger: /* Tips */

2025-05-09T13:10:34Z

Tips

← Older revision		Revision as of 09:10, 9 May 2025
Line 56:		Line 56:
	</pre>		</pre>

	* ~~make~~ sure email is checked off in filters.		* Make sure email is checked off in filters.

			* Make sure that the path for sendmail points to msmtp (whereis sendmail, and do a symbolic link, ln -s)

	* service zoneminder restart may be needed after changes (depends upon ZM version)		* service zoneminder restart may be needed after changes (depends upon ZM version)

Burger: /* The Simplest Server Monitor */

2025-04-14T04:37:04Z

The Simplest Server Monitor

← Older revision		Revision as of 00:37, 14 April 2025
Line 215:		Line 215:
	</pre>		</pre>

	=== The Simplest ~~Server~~ Monitor ===		=== The Simplest Program Monitor ===
	The use of && or \|\| for either a function that returns 1 or 0 (test via $? or just an echo) is the simplest way to script commands. Put it in cron.		The use of && or \|\| for either a function that returns 1 or 0 (test via $? or just an echo) is the simplest way to script commands. Put it in cron.
	ps x \| grep zmc \| grep -vi grep \|\| echo "zmc is not running..." \| msmtp -a default email@address		ps x \| grep zmc \| grep -vi grep \|\| echo "zmc is not running..." \| msmtp -a default email@address

Burger: /* Basic Server Monitor */

2025-04-14T04:36:31Z

Basic Server Monitor

← Older revision		Revision as of 00:36, 14 April 2025
Line 214:		Line 214:
	5 0 * * 1 root echo "zm server" \| mutt -s "zm server" user@email.com -a /tmp/hdd_report		5 0 * * 1 root echo "zm server" \| mutt -s "zm server" user@email.com -a /tmp/hdd_report
	</pre>		</pre>

			=== The Simplest Server Monitor ===
			The use of && or \|\| for either a function that returns 1 or 0 (test via $? or just an echo) is the simplest way to script commands. Put it in cron.
			ps x \| grep zmc \| grep -vi grep \|\| echo "zmc is not running..." \| msmtp -a default email@address

	==Troubleshooting==		==Troubleshooting==
	===Error sending message, child exited 127 (Exec error.).===		===Error sending message, child exited 127 (Exec error.).===

Burger: /* Send email if MySQL is not running */

2024-12-10T07:54:09Z

Send email if MySQL is not running

← Older revision		Revision as of 03:54, 10 December 2024
Line 112:		Line 112:
	fi		fi
	</pre>		</pre>
	===Send ~~email~~ if MySQL is ~~not running~~===		===Send Email if MySQL is Not Running===
	<pre>		<pre>
	#usage: feed $1 subject		#usage: feed $1 subject

Burger: /* Send Email if ZM is Not Running */

2024-12-10T07:52:22Z

Send Email if ZM is Not Running

← Older revision		Revision as of 03:52, 10 December 2024
Line 103:		Line 103:
	alt.		alt.
	<pre>		<pre>
	#usage: feed $1 ~~company name/~~subject		#usage: feed $1 subject
	zmdc.pl check \| grep stopped		zmdc.pl check \| grep stopped
	if [ $? -eq 0 ]; then		if [ $? -eq 0 ]; then
Line 111:		Line 111:
	echo "do nothing"		echo "do nothing"
	fi		fi
			</pre>
			===Send email if MySQL is not running===
			<pre>
			#usage: feed $1 subject
			mysqladmin processlist \| grep zmuser
			#returns 0 if zmuser detected
			if [ $? -eq 0 ]; then
			#send email
			echo "do nothing"
			else
			echo "mysql is not running" \| mutt -s $1 user@address.com
			fi

	</pre>		</pre>

Burger: /* Send Email if ZM is Not Running */

2024-12-10T07:50:22Z

Send Email if ZM is Not Running

@@ Line 98: / Line 98: @@
 else
          echo "ZM is running, do nothing"
 fi
 </pre>

Burger: /* Error sending message, child exited 127 (Exec error.). */

2024-10-04T17:17:36Z

Error sending message, child exited 127 (Exec error.).

← Older revision		Revision as of 13:17, 4 October 2024
Line 193:		Line 193:
	If when sending something like the following you get the above error:		If when sending something like the following you get the above error:
	echo "message" \| mutt -s "cameras_email" user@email -a /tmp/attachment.txt		echo "message" \| mutt -s "cameras_email" user@email -a /tmp/attachment.txt
			Error sending message, child exited 127 (Exec error.).
	You need to install msmtp-mta.		You need to install msmtp-mta.

Burger: /* Troubleshooting */

2024-10-04T17:17:11Z

Troubleshooting

← Older revision		Revision as of 13:17, 4 October 2024
Line 190:		Line 190:
	</pre>		</pre>
	==Troubleshooting==		==Troubleshooting==
			===Error sending message, child exited 127 (Exec error.).===
			If when sending something like the following you get the above error:
			echo "message" \| mutt -s "cameras_email" user@email -a /tmp/attachment.txt
			You need to install msmtp-mta.

	==Resources==		==Resources==

Burger: /* Examples of Emails for Monitoring */

2024-10-04T17:15:28Z

Examples of Emails for Monitoring

← Older revision		Revision as of 13:15, 4 October 2024
Line 189:		Line 189:
	5 0 * * 1 root echo "zm server" \| mutt -s "zm server" user@email.com -a /tmp/hdd_report		5 0 * * 1 root echo "zm server" \| mutt -s "zm server" user@email.com -a /tmp/hdd_report
	</pre>		</pre>
			==Troubleshooting==

	==Resources==		==Resources==

Burger at 07:13, 14 September 2024

2024-09-14T07:13:10Z

← Older revision		Revision as of 03:13, 14 September 2024
Line 74:		Line 74:
	See [[Filters]]		See [[Filters]]

	== Send email if only on a certain runstate (Filter on Run States) ==		=== Send email if only on a certain runstate (Filter on Run States) ===

	Notifications are easy if you want alarms emailed between a static time, for example between 12AM and 6AM. If you have a situation where you may not want the alarms to send you text messages on occasion, you can filter on run states.		Notifications are easy if you want alarms emailed between a static time, for example between 12AM and 6AM. If you have a situation where you may not want the alarms to send you text messages on occasion, you can filter on run states.
Line 82:		Line 82:
	Note that in the author's opinion, run states can become unwieldy for large installations. It's best used with smaller setups only.		Note that in the author's opinion, run states can become unwieldy for large installations. It's best used with smaller setups only.

	== Send Email if ZM is Not Running ==		== Examples of Emails for Monitoring ==
			=== Send Email if ZM is Not Running ===
	Here is a minimal script to check that Zoneminder is running. Note that this does not check for mysql errors or hard drive errors (which are possible). Do not put any spaces in the subject or email. Also, you may want to monitor that the server is actually powered on, from another computer (as if the server shuts down for any reason, this will obviously not run).		Here is a minimal script to check that Zoneminder is running. Note that this does not check for mysql errors or hard drive errors (which are possible). Do not put any spaces in the subject or email. Also, you may want to monitor that the server is actually powered on, from another computer (as if the server shuts down for any reason, this will obviously not run).
	<pre>		<pre>
Line 100:		Line 101:
	</pre>		</pre>

	== Send Email if HDD Fails ==		=== Send Email if HDD Fails ===
	This script will give you 1 email an hour, if a hdd has an error. This is an alternative way of checking hdd status instead of S.M.A.R.T. .		This script will give you 1 email an hour, if a hdd has an error. This is an alternative way of checking hdd status instead of S.M.A.R.T. .
	<pre>		<pre>
Line 126:		Line 127:
	</pre>		</pre>

	== Send Email if Camera is Offline ==		=== Send Email if Camera is Offline ===
	This script will ping an ip address 10 times, then if there is an error, it will try again 10 more times. If it still cannot connect, an email will be sent. There is a lock file, so that only one email is sent every couple hours.		This script will ping an ip address 10 times, then if there is an error, it will try again 10 more times. If it still cannot connect, an email will be sent. There is a lock file, so that only one email is sent every couple hours.
	<pre>		<pre>
Line 179:		Line 180:
	</pre>		</pre>

	== Basic Server Monitor ==		=== Basic Server Monitor ===
	These would go in /etc/crontab. You might run this once a week, to monitor a server.		These would go in /etc/crontab. You might run this once a week, to monitor a server.
	<pre>		<pre>