System-generated Notifications - Revision history

Support: /* "Bandwidth limit notification" */

2013-02-28T22:56:20Z

"Bandwidth limit notification"

@@ Line 617: / Line 617: @@
 = "Bandwidth limit notification" =
-<pre>customer        #       usage   level   b/w option
+A process on mail ([[Infrastructure_Machines#Cronjobs|top20customer.pl]]) periodically looks for customers who are nearing or at their bandwidth limit (which varies based on the package and # of systems), and emails support@johncompanies.com & sales@johncompanies.com when they’re getting close.  Customers have 3 options for how to handle bandwidth overage:
-col00174        1       770.50G overage limit   limit to $20</pre>
+#	stop – they want traffic to be stopped (we cap, not stop actually) when they reach their allotment
 '''Action to take:''' After reviewing whether to contact the customer or limit bandwidth, you can send them a notice via the 'Send Notice' link in the bandwidth section of their mgmt page. The notice will be tailored to the current situation (warning vs over). The email can be deleted.

Support: /* "IMPORTANT REMINDER - SYSTEM SHUT DOWN TODAY" */

2013-02-28T22:51:59Z

"IMPORTANT REMINDER - SYSTEM SHUT DOWN TODAY"

← Older revision		Revision as of 15:51, 28 February 2013
Line 17:		Line 17:
	= "IMPORTANT REMINDER - SYSTEM SHUT DOWN TODAY" =		= "IMPORTANT REMINDER - SYSTEM SHUT DOWN TODAY" =

	~~We send out automated notices to customers who have~~ a ~~cancel date~~ (<tt>~~jc:systems.~~cancel_date</tt>) of the ~~present~~ date or a ~~date~~ in the ~~future~~ (at the ~~time~~ the ~~<tt>/usr/local/www/cronjobs/shutdownreminder~~.~~pl</tt> script runs)~~. A series of these go out at the cancel date gets closer, until the day of the cancel at which point the subject switches from "SHUT DOWN IN X DAYS" to "SHUT DOWN TODAY"		Every night at midnight, a script ([[Infrastructure_Machines#Cronjobs\|shutdownreminder.pl]]) runs which looks for systems (in [[Management_System_/_Public_Website_/_Signup_/_Account_Manager#jc:systems\|jc:systems]]) which are marked with a <tt>cancel_date</tt> (but no stop date – i.e. they’re pending shutdown). If the cancel date is equal to the current date or current date + 10, 5, 2, or 1 days, it will send them a shutdown reminder email (cc’ing support@johncompanies.com). All emails are logged so there’s no need to save these cc’s. Typically, we keep the “shutdown today” reminder in the queue as a reminder that it needs to be shut down (manually, typically at the end of the day). The list of systems set to be shutdown is also listed on the main page in Mgmt.

			A series of these go out at the cancel date gets closer, until the day of the cancel at which point the subject switches from "SHUT DOWN IN X DAYS" to "SHUT DOWN TODAY"

	'''Action to take:''' delete these emails, but when you get the notice about "SHUT DOWN TODAY", that is your reminder to actually stop the system today.		'''Action to take:''' delete these emails, but when you get the notice about "SHUT DOWN TODAY", that is your reminder to actually stop the system today.

70.230.212.110: /* "Bandwidth Overage Report for March 2010" */

2012-12-18T00:21:58Z

"Bandwidth Overage Report for March 2010"

← Older revision		Revision as of 17:21, 17 December 2012
Line 635:		Line 635:

	'''Action to take:''' Use this report to decide if and how much to bill a customer for bandwidth usage. Save/archive the report email.		'''Action to take:''' Use this report to decide if and how much to bill a customer for bandwidth usage. Save/archive the report email.

			= Backup failures =

			<pre>jail1 at 2012-12-12 : rsync.backup attempted to backup /mnt/data1/69.55.233.233-col01243/asd but that directory is non-existent.</pre>

			This is an automated email sent out by the vps backup scripts when they run into a problem. It means a directory was removed by a customer or perhaps the vps was cancelled and directories were not removed from the nightly backup script, or perhaps we moved their mount vps point/location and didn't update the backup config.

			'''Action to take:''' Rectify the problem by removing or renaming the dir to backup (contact the customer if this was not cause we moved the customer due to cancellation or other reason). Delete the email notice.

70.230.212.110: /* Bandwidth limit notification */

2012-12-18T00:16:15Z

Bandwidth limit notification

@@ Line 613: / Line 613: @@
 '''Action to take:''' None, assuming you initiated the verify.
-= Bandwidth limit notification =
+= "Bandwidth limit notification" =
 <pre>customer        #       usage   level   b/w option
@@ Line 621: / Line 621: @@
 '''Action to take:''' After reviewing whether to contact the customer or limit bandwidth, you can send them a notice via the 'Send Notice' link in the bandwidth section of their mgmt page. The notice will be tailored to the current situation (warning vs over). The email can be deleted.

70.230.212.110: /* "RAID controller problem on newbackup3" */

2012-12-18T00:14:34Z

"RAID controller problem on newbackup3"

← Older revision		Revision as of 17:14, 17 December 2012
Line 612:		Line 612:

	'''Action to take:''' None, assuming you initiated the verify.		'''Action to take:''' None, assuming you initiated the verify.

			= Bandwidth limit notification =

			<pre>customer # usage level b/w option
			col00174 1 770.50G overage limit limit to $20</pre>

			This indicates that a customer is either near their bandwidth limit (@ 90% under level it will say 'warn'), or at/over their limit (@ 100%+ it will say 'limit').

			'''Action to take:''' After reviewing whether to contact the customer or limit bandwidth, you can send them a notice via the 'Send Notice' link in the bandwidth section of their mgmt page. The notice will be tailored to the current situation (warning vs over). The email can be deleted.

70.230.212.110: /* "snapshot rotation done on backup1" */

2012-12-18T00:06:38Z

"snapshot rotation done on backup1"

← Older revision		Revision as of 17:06, 17 December 2012
Line 8:		Line 8:

	'''Action to take:''' Confirm that this was received before midnight (or whenever backups start from virts/jails -> backup server). Delete email.		'''Action to take:''' Confirm that this was received before midnight (or whenever backups start from virts/jails -> backup server). Delete email.

			= "!BB - 9638010! jail1.johncompanies.com.conn - 600082197184218" =

			These are generated by [[BigBrother]] and the content will depend on the server and problem

			'''Action to take:''' You will want to look into the cause/reason for the notice and you may delete these emails.

	= "IMPORTANT REMINDER - SYSTEM SHUT DOWN TODAY" =		= "IMPORTANT REMINDER - SYSTEM SHUT DOWN TODAY" =

70.230.212.110: /* "snapshot rotation done on backup1" */

2012-12-18T00:02:38Z

"snapshot rotation done on backup1"

← Older revision		Revision as of 17:02, 17 December 2012
Line 8:		Line 8:

	'''Action to take:''' Confirm that this was received before midnight (or whenever backups start from virts/jails -> backup server). Delete email.		'''Action to take:''' Confirm that this was received before midnight (or whenever backups start from virts/jails -> backup server). Delete email.

			= "IMPORTANT REMINDER - SYSTEM SHUT DOWN TODAY" =

			We send out automated notices to customers who have a cancel date (<tt>jc:systems.cancel_date</tt>) of the present date or a date in the future (at the time the <tt>/usr/local/www/cronjobs/shutdownreminder.pl</tt> script runs). A series of these go out at the cancel date gets closer, until the day of the cancel at which point the subject switches from "SHUT DOWN IN X DAYS" to "SHUT DOWN TODAY"

			'''Action to take:''' delete these emails, but when you get the notice about "SHUT DOWN TODAY", that is your reminder to actually stop the system today.

	= "RAID controller problem on backup1.johncompanies.com" =		= "RAID controller problem on backup1.johncompanies.com" =

70.230.212.110 at 22:46, 10 December 2012

2012-12-10T22:46:34Z

← Older revision		Revision as of 15:46, 10 December 2012
Line 595:		Line 595:

	'''Action to take:''' None if you get just a couple/few of these, and it was due to an explained outage.		'''Action to take:''' None if you get just a couple/few of these, and it was due to an explained outage.
			= "RAID controller problem on newbackup3" =

			1 ARC-1160-VOL#00 Raid Set # 00 Raid5 5000.0GB 00/00/00 Checking(77%)

			'''Action to take:''' None, assuming you initiated the verify.

70.230.212.110 at 00:47, 6 December 2012

2012-12-06T00:47:01Z

← Older revision		Revision as of 17:47, 5 December 2012
Line 1:		Line 1:

			= Payment-related emails =
	Also see [[Payment_System#Payment-related_emails\|Payment-related emails]]		Also see [[Payment_System#Payment-related_emails\|Payment-related emails]]

70.230.212.110 at 00:46, 6 December 2012

2012-12-06T00:46:32Z

← Older revision		Revision as of 17:46, 5 December 2012
Line 1:		Line 1:

			Also see [[Payment_System#Payment-related_emails\|Payment-related emails]]

	= "snapshot rotation done on backup1" =		= "snapshot rotation done on backup1" =