Shutting Down Service - Revision history

Support: /* VPS */

2013-02-28T22:41:25Z

VPS

← Older revision		Revision as of 15:41, 28 February 2013
Line 21:		Line 21:
	# use the "stop" link in mgmt to set him as down/done.		# use the "stop" link in mgmt to set him as down/done.
	# if his pp subscription is still active- take action to get that cancelled (email billing person at JC or tell customer to cancel it)		# if his pp subscription is still active- take action to get that cancelled (email billing person at JC or tell customer to cancel it)


	FreeBSD:		FreeBSD:

	# canceljail <hostname>		Automated method:<br>
	# you will be reminded to remove domains (<tt>rmdomains <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC		1. <tt>g <customerID></tt><br>
	# you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)		2. <tt>canceljail <hostname></tt><br>
	# you will be prompted to remove backups, if any		3. you will be reminded to remove domains (<tt>rmdomains CID</tt>) (if any domains are listed, must also be removed from named.conf: <tt>vi ../named.conf; rr</tt>)<br>
	# you will be reminded to ptr(s), if any: <tt>ptr <ip></tt>		NOTE- only remove them if the customer if after shutting down his jail he will no longer have any services with JC<br>
	# use the "stop" link in mgmt to set him as down/done.		4. you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)<br>
	# if ~~his~~ pp subscription is still active- take action to get that cancelled (email ~~billing person at JC or tell customer to cancel it~~)		5. you will be prompted to remove backups, if any<br>
			6. you will be reminded to ptr(s), if any: <tt>ptr <ip></tt> on ns1c<br>
			7. use the "stop" link in mgmt to set him as down/done.<br>
			8. if their pp subscription is still active- take action to get that cancelled (email payments@johncompanies.com)<br>

	Manual method:
			Manual method:<br>
	1. <tt>g <customerID></tt><br>		1. <tt>g <customerID></tt><br>
	2. <tt>jailkill <hostname></tt><br>		2. <tt>jailkill <hostname></tt><br>
Line 55:		Line 60:
	12. remove any firewall rules: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)<br>		12. remove any firewall rules: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)<br>
	13. remove ptr(s), if any: <tt>ptr <ip></tt> on ns1c<br>		13. remove ptr(s), if any: <tt>ptr <ip></tt> on ns1c<br>


	~~Automated method:<br>~~
	~~1. <tt>g <customerID></tt><br>~~
	~~2. <tt>canceljail <hostname></tt><br>~~
	~~3. you will be reminded to remove domains (<tt>rmdomains CID</tt>) (if any domains are listed, must also be removed from named.conf: <tt>vi ../named.conf; rr</tt>)<br>~~
	~~NOTE- only remove them if the customer if after shutting down his jail he will no longer have any services with JC<br>~~
	4. you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)<br>
	~~5. you will be prompted to remove backups, if any<br>~~
	~~6. you will be reminded to ptr(s), if any: <tt>ptr <ip></tt> on ns1c<br>~~
	~~7. use the "stop" link in mgmt to set him as down/done.<br>~~
	~~8. if their pp subscription is still active- take action to get that cancelled (email payments@johncompanies.com)<br>~~

	~~Colos:~~
	~~1. contact the appropriate data center to request they power off the server. Do not use the ATS switch to power it down.<br>~~
	~~2. leave the customer cancelled but NOT stopped in mgmt- this state reminds us it needs to be removed. Once we remove it we will mark it as stopped<br>~~
	~~2. IF no longer going to be a customer, remove zones from ns1c: rmdomains col00241 (if any domains are listed, must also be removed from named.conf)<br>~~
	3. check for firewall rules on the firewall machine - note which data center you're at- check firewall1/firewall2 as approp. g <ip>, ipfw del <rule id> <rule id> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)
	~~4. check to see if they had nfs-mounted backup space on backup1/backup2/backup3~~
	~~5. if they are paying via cc, and since we're not stopping them, their sub will have to be cancelled to stop future billing~~
	~~6. remove ptr(s), if any: ptr <ip>~~

	= Dedicated Server =		= Dedicated Server =

Support: /* VPS */

2013-02-28T22:40:02Z

VPS

← Older revision		Revision as of 15:40, 28 February 2013
Line 33:		Line 33:

	Manual method:		Manual method:
	# g <customerID>		1. <tt>g <customerID></tt><br>
	# jailkill <hostname>		2. <tt>jailkill <hostname></tt><br>
	# unmount /mnt/dataX/1.1.1.1-col0XXXX		3. <tt>unmount /mnt/dataX/1.1.1.1-col0XXXX</tt><br>
	# vnconfig –u /dev/vnN		On >=6.x: <tt>unmount /mnt/dataX/1.1.1.1-col0XXXX/dev</tt><br>
	or <br>		4. On 4.x: <tt>vnconfig –u /dev/vnN</tt><br>
	mdconfig –d –u N<br>		On >=7.x: <tt>mdconfig –d –u N</tt><br>
	or <br>		On 6.x:
	gconcat list /dev/concat/vX-vY<br>		gconcat volume:<br>
	gconcat stop /dev/concat/vX-vY<br>		<tt>gconcat list /dev/concat/vX-vY</tt><br>
	gconcat clear /dev/gvinum/vX /dev/gvinum/vX<br>		<tt>gconcat stop /dev/concat/vX-vY</tt><br>
	# rename vn/md file (include date!), ex: mv /mnt/data1/1.2.3.4-col00241 /mnt/data1/old-col00241-vnfile-cxld-20041220		<tt>gconcat clear /dev/gvinum/vX /dev/gvinum/vX</tt><br>
	# edit quad, comment out jail config entries and note, ex: # cancelled col00241		gvinum single volume:<br>
	# run buildsafe (copies changes made to quad into safe file)		<tt>cleargv 12</tt> (if you want to clear /dev/gvinum/v12)
	# check backups, gb <customerID>, if any listed edit backup config (vb) and remove backups from ~~backup2~~ (or run mvbackups)		5. rename vn/md file (include date!), ex: <tt>mv /mnt/data1/1.2.3.4-col00241 /mnt/data1/old-col00241-vnfile-cxld-20041220</tt><br>
	# remove ~~his~~ dir: rm –fr /mnt/data1/1.2.3.4-col00241-DIR		6. edit quad, comment out jail config entries and note, ex: # cancelled col00241<br>
	# stop in mgmt ~~screen~~		7. run <tt>buildsafe</tt> (copies changes made to quad into safe file)<br>
	# IF no longer going to be a customer, remove zones from ns1c: rmdomains col00241 (if any domains are listed, must also be removed from named.conf)		8. check backups, <tt>gb <customerID></tt>, if any listed edit backup config (<tt>vb</tt>) and remove backups from backup1 (or run <tt>mvbackups</tt> if moving to another server)<br>
	# remove any firewall rules: g <ip>, ipfw del <rule id> <rule id> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)		9. remove the mountpoint dir: <tt>rm –fr /mnt/data1/1.2.3.4-col00241-DIR</tt><br>
	# remove ptr(s), if any: ptr <ip>		10. use the "stop" link in mgmt to set him as down/done.<br>
			11. IF no longer going to be a customer, remove zones from ns1c: <tt>rmdomains col00241</tt> (if any domains are listed, must also be removed from named.conf and the nameserver should be HUP'd: <tt>vi ../named.conf; rr</tt>)<br>
			12. remove any firewall rules: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)<br>
			13. remove ptr(s), if any: <tt>ptr <ip></tt> on ns1c<br>


	~~Jails:~~		Automated method:<br>
	Automated method:		1. <tt>g <customerID></tt><br>
	1. g <customerID>		2. <tt>canceljail <hostname></tt><br>
	2. canceljail <hostname>		3. you will be reminded to remove domains (<tt>rmdomains CID</tt>) (if any domains are listed, must also be removed from named.conf: <tt>vi ../named.conf; rr</tt>)<br>
	3. you will be reminded to remove domains (rmdomains CID) (if any domains are listed, must also be removed from named.conf)		NOTE- only remove them if the customer if after shutting down his jail he will no longer have any services with JC<br>
	NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC		4. you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)<br>
	4. you will be reminded to check for firewall rules on the firewall machine: g <ip>, ipfw del <rule id> <rule id> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)		5. you will be prompted to remove backups, if any<br>
	5. you will be prompted to remove backups, if any		6. you will be reminded to ptr(s), if any: <tt>ptr <ip></tt> on ns1c<br>
	6. you will be reminded to ptr(s), if any: ptr <ip>		7. use the "stop" link in mgmt to set him as down/done.<br>
	7. use the "stop" link in mgmt to set him as down/done.		8. if their pp subscription is still active- take action to get that cancelled (email payments@johncompanies.com)<br>
	8. if ~~his~~ pp subscription is still active- take action to get that cancelled (email ~~Dave or tell customer to cancel it)~~

	~~Manual method:~~
	~~1. g <customerID>~~
	~~2. jailkill <hostname>~~
	~~3. unmount /mnt/dataX/1.1.1.1-col0XXXX~~
	~~4. vnconfig –u /dev/vnN~~
	or
	~~mdconfig –d –u N~~
	or
	~~gconcat list /dev/concat/vX-vY~~
	~~gconcat stop /dev/concat/vX-vY~~
	~~gconcat clear /dev/gvinum/vX /dev/gvinum/vX~~
	5. ~~rename vn/md file (include date!~~)~~, ex: mv /mnt/data1/1.2.3.4-col00241 /mnt/data1/old-col00241-vnfile-cxld-20041220~~
	~~6. edit quad, comment out jail config entries and note, ex: # cancelled col00241~~
	~~7. run buildsafe (copies changes made to quad into safe file)~~
	~~8. check backups, gb~~ <~~customerID>, if any listed edit backup config (vb) and remove backups from backup2 (or run mvbackups)~~
	~~9. remove his dir: rm –fr /mnt/data1/1.2.3.4-col00241-DIR~~
	~~10. stop in mgmt screen~~
	~~11. IF no longer going to be a customer, remove zones from ns1c: rmdomains col00241 (if any domains are listed, must also be removed from named.conf)~~
	~~12. remove any firewall rules: g <ip>, ipfw del <rule id> <rule id> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)~~
	~~13. remove ptr(s), if any: ptr <ip~~>

	Colos:		Colos:
	1. contact the appropriate data center to request they power off the server. Do not use the ATS switch to power it down.		1. contact the appropriate data center to request they power off the server. Do not use the ATS switch to power it down.<br>
	2. leave the customer cancelled but NOT stopped in mgmt- this state reminds us it needs to be removed. Once we remove it we will mark it as stopped		2. leave the customer cancelled but NOT stopped in mgmt- this state reminds us it needs to be removed. Once we remove it we will mark it as stopped<br>
	2. IF no longer going to be a customer, remove zones from ns1c: rmdomains col00241 (if any domains are listed, must also be removed from named.conf)		2. IF no longer going to be a customer, remove zones from ns1c: rmdomains col00241 (if any domains are listed, must also be removed from named.conf)<br>
	3. check for firewall rules on the firewall machine - note which data center you're at- check firewall1/firewall2 as approp. g <ip>, ipfw del <rule id> <rule id> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)		3. check for firewall rules on the firewall machine - note which data center you're at- check firewall1/firewall2 as approp. g <ip>, ipfw del <rule id> <rule id> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)
	4. check to see if they had nfs-mounted backup space on backup1/backup2/backup3		4. check to see if they had nfs-mounted backup space on backup1/backup2/backup3

Support: /* VPS */

2013-02-28T22:27:06Z

VPS

← Older revision		Revision as of 15:27, 28 February 2013
Line 33:		Line 33:

	Manual method:		Manual method:
	1. g <customerID>		# g <customerID>
	2. jailkill <hostname>		# jailkill <hostname>
	3. unmount /mnt/dataX/1.1.1.1-col0XXXX		# unmount /mnt/dataX/1.1.1.1-col0XXXX
	4. vnconfig –u /dev/vnN		# vnconfig –u /dev/vnN
	or		or <br>
	mdconfig –d –u N		mdconfig –d –u N<br>
	or		or <br>
	gconcat list /dev/concat/vX-vY		gconcat list /dev/concat/vX-vY<br>
	gconcat stop /dev/concat/vX-vY		gconcat stop /dev/concat/vX-vY<br>
	gconcat clear /dev/gvinum/vX /dev/gvinum/vX		gconcat clear /dev/gvinum/vX /dev/gvinum/vX<br>
	5. rename vn/md file (include date!), ex: mv /mnt/data1/1.2.3.4-col00241 /mnt/data1/old-col00241-vnfile-cxld-20041220		# rename vn/md file (include date!), ex: mv /mnt/data1/1.2.3.4-col00241 /mnt/data1/old-col00241-vnfile-cxld-20041220
	6. edit quad, comment out jail config entries and note, ex: # cancelled col00241		# edit quad, comment out jail config entries and note, ex: # cancelled col00241
	7. run buildsafe (copies changes made to quad into safe file)		# run buildsafe (copies changes made to quad into safe file)
	8. check backups, gb <customerID>, if any listed edit backup config (vb) and remove backups from backup2 (or run mvbackups)		# check backups, gb <customerID>, if any listed edit backup config (vb) and remove backups from backup2 (or run mvbackups)
	9. remove his dir: rm –fr /mnt/data1/1.2.3.4-col00241-DIR		# remove his dir: rm –fr /mnt/data1/1.2.3.4-col00241-DIR
	~~10.~~ stop in mgmt screen		# stop in mgmt screen
	~~11.~~ IF no longer going to be a customer, remove zones from ns1c: rmdomains col00241 (if any domains are listed, must also be removed from named.conf)		# IF no longer going to be a customer, remove zones from ns1c: rmdomains col00241 (if any domains are listed, must also be removed from named.conf)
	~~12.~~ remove any firewall rules: g <ip>, ipfw del <rule id> <rule id> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)		# remove any firewall rules: g <ip>, ipfw del <rule id> <rule id> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)
	~~13.~~ remove ptr(s), if any: ptr <ip>		# remove ptr(s), if any: ptr <ip>

70.230.212.110: /* VPS */

2013-01-18T01:39:41Z

VPS

← Older revision		Revision as of 18:39, 17 January 2013
Line 15:		Line 15:

	# <tt>[[VPS_Management#cancelve\|cancelve]] <VEID></tt>		# <tt>[[VPS_Management#cancelve\|cancelve]] <VEID></tt>
	# you will be reminded to remove domains (<tt>rmdomains <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC		# you will be reminded to remove domains (<tt>[[DNS#DNS_Management_and_Operations\|rmdomains]] <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC
	# you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)		# you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)
	# you will be prompted to remove backups, if any		# you will be prompted to remove backups, if any
	# you will be reminded to ptr(s), if any: <tt>ptr <ip></tt>		# you will be reminded to ptr(s), if any: <tt>[[DNS#DNS_Management_and_Operations\|ptr]] <ip></tt>
	# use the "stop" link in mgmt to set him as down/done.		# use the "stop" link in mgmt to set him as down/done.
	# if his pp subscription is still active- take action to get that cancelled (email billing person at JC or tell customer to cancel it)		# if his pp subscription is still active- take action to get that cancelled (email billing person at JC or tell customer to cancel it)

70.230.212.110: /* VPS */

2013-01-18T01:38:33Z

VPS

← Older revision		Revision as of 18:38, 17 January 2013
Line 6:		Line 6:

	In response to the authorized cancellation request, we send them the paste for "cancel". You will need to edit it to reflect,		In response to the authorized cancellation request, we send them the paste for "cancel". You will need to edit it to reflect,
	# any domains we may be hosting for them (<tt>listdomains <CID></tt>), if they have none remove the line.		# any domains we may be hosting for them (<tt>[[DNS#DNS_Management_and_Operations\|listdomains]] <CID></tt>), if they have none remove the line.
	# if they are not paying via pp sub, remove the line referring to a cancelled payment and email confirmation (their credit card or paypal billing agreement will simply stop billing).		# if they are not paying via pp sub, remove the line referring to a cancelled payment and email confirmation (their credit card or paypal billing agreement will simply stop billing).

70.230.212.110: /* VPS */

2013-01-18T01:34:54Z

VPS

← Older revision		Revision as of 18:34, 17 January 2013
Line 10:		Line 10:

	Once you receive the "Shutdown Today" email or if you see their shutdown date has come (seen in green on the mgmt main/login screen) or if they reply at any point saying you can shut down their server now, you may proceed with actually stopping their server.		Once you receive the "Shutdown Today" email or if you see their shutdown date has come (seen in green on the mgmt main/login screen) or if they reply at any point saying you can shut down their server now, you may proceed with actually stopping their server.


	Linux:		Linux:

	~~Automated method~~:		# <tt>[[VPS_Management#cancelve\|cancelve]] <VEID></tt>
	# ~~cancelve VEID~~		# you will be reminded to remove domains (<tt>rmdomains <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC
			# you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)
			# you will be prompted to remove backups, if any
			# you will be reminded to ptr(s), if any: <tt>ptr <ip></tt>
			# use the "stop" link in mgmt to set him as down/done.
			# if his pp subscription is still active- take action to get that cancelled (email billing person at JC or tell customer to cancel it)

			FreeBSD:

			# canceljail <hostname>
	# you will be reminded to remove domains (<tt>rmdomains <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC		# you will be reminded to remove domains (<tt>rmdomains <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC
	# you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)		# you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)

70.230.212.110: /* VPS */

2013-01-18T01:33:14Z

VPS

70.230.212.110: /* VPS */

2013-01-18T01:32:19Z

VPS

70.230.212.110: /* VPS */

2013-01-18T01:31:58Z

VPS

← Older revision		Revision as of 18:31, 17 January 2013
Line 5:		Line 5:
	Once you have an authorized request from an authorized contact, setup the server for shutdown on the day before the next bill is due- use the "cancel" link adjacent to their system in mgmt. Assuming the cancel date is at least 1 day in the future, the customer will receive shutdown notices at: 10 5 2 1 days before shutdown, as well as the day of shutdown ("Shutown Today"). If they are paying via paypal subscription, you should email the billing handler (sales@johncompanies.com) to cancel their paypal subscription to prevent future/further payments. If they are paying via cc or paypal billing agreement, as long as we shut their system down before the next bill date, their billing will cease- no more service charges on the ledger = no more payments taken from payment sources on file. It's also possible to cancel the sub associated with their account or set the next bill date into the future, but this is only recommended if there is an exception where their shutdown date is after the next billing date.		Once you have an authorized request from an authorized contact, setup the server for shutdown on the day before the next bill is due- use the "cancel" link adjacent to their system in mgmt. Assuming the cancel date is at least 1 day in the future, the customer will receive shutdown notices at: 10 5 2 1 days before shutdown, as well as the day of shutdown ("Shutown Today"). If they are paying via paypal subscription, you should email the billing handler (sales@johncompanies.com) to cancel their paypal subscription to prevent future/further payments. If they are paying via cc or paypal billing agreement, as long as we shut their system down before the next bill date, their billing will cease- no more service charges on the ledger = no more payments taken from payment sources on file. It's also possible to cancel the sub associated with their account or set the next bill date into the future, but this is only recommended if there is an exception where their shutdown date is after the next billing date.

	In response to the authorized cancellation request, we send them the paste for "cancel". You will need to edit it to reflect, 1. any domains we may be hosting for them (<tt>listdomains <CID></tt>), if they have none remove the line. 2. if they are not paying via pp, remove the line referring to a cancelled payment and email confirmation (their credit card will simply stop billing).		In response to the authorized cancellation request, we send them the paste for "cancel". You will need to edit it to reflect,
			1. any domains we may be hosting for them (<tt>listdomains <CID></tt>), if they have none remove the line.
			1. if they are not paying via pp sub, remove the line referring to a cancelled payment and email confirmation (their credit card or paypal billing agreement will simply stop billing).

	Once you receive the "Shutdown Today" email or if you see their shutdown date has come (seen in green on the mgmt main/login screen) or if they reply at any point saying you can shut down their server now, you may proceed with actually stopping their server.		Once you receive the "Shutdown Today" email or if you see their shutdown date has come (seen in green on the mgmt main/login screen) or if they reply at any point saying you can shut down their server now, you may proceed with actually stopping their server.

	~~Virts~~:		Linux:

	Automated method:		Automated method:
	1. cancelve VEID		1. cancelve VEID
	3. you will be reminded to remove domains (rmdomains CID) (if any domains are listed, must also be removed from named.conf)		1. you will be reminded to remove domains (<tt>rmdomains <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC
	NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC		1. you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)
	4. you will be reminded to check for firewall rules on the firewall machine: g <ip>, ipfw del <rule id> <rule id> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)		1. you will be prompted to remove backups, if any
	5. you will be prompted to remove backups, if any		1. you will be reminded to ptr(s), if any: <tt>ptr <ip></tt>
	6. you will be reminded to ptr(s), if any: ptr <ip>		1. use the "stop" link in mgmt to set him as down/done.
	7. use the "stop" link in mgmt to set him as down/done.		1. if his pp subscription is still active- take action to get that cancelled (email billing person at JC or tell customer to cancel it)
	8. if his pp subscription is still active- take action to get that cancelled (email ~~Dave~~ or tell customer to cancel it)

	Manual method:		Manual method:

70.230.212.110: /* VPS */

2013-01-18T01:28:50Z

VPS

← Older revision		Revision as of 18:28, 17 January 2013
Line 3:		Line 3:
	When someone cancels, they must be authorized to do so. The request must come from the owner or an admin contact. If not, email the owner to confirm.		When someone cancels, they must be authorized to do so. The request must come from the owner or an admin contact. If not, email the owner to confirm.

	~~Assuming~~ you have ~~a good~~ request from an authorized contact, setup the server for shutdown on the day before the next bill is due- use the "cancel" link adjacent to their system in mgmt. Assuming the cancel date is at least 1 day in the future, the customer will receive shutdown notices at: 10 5 2 1 days before shutdown, as well as the day of shutdown "Shutown Today". ~~As you're setting the customer up for shutdown~~, you should ~~take action to~~ (~~email Dave~~) cancel their paypal subscription to prevent future/further ~~billing~~. If they are paying via cc, as long as we shut their system down before the next bill date, their billing will cease. It's also possible to cancel the sub associated with their account or set the next bill date into the future, but this is ~~not~~ recommended.		Once you have an authorized request from an authorized contact, setup the server for shutdown on the day before the next bill is due- use the "cancel" link adjacent to their system in mgmt. Assuming the cancel date is at least 1 day in the future, the customer will receive shutdown notices at: 10 5 2 1 days before shutdown, as well as the day of shutdown ("Shutown Today"). If they are paying via paypal subscription, you should email the billing handler (sales@johncompanies.com) to cancel their paypal subscription to prevent future/further payments. If they are paying via cc or paypal billing agreement, as long as we shut their system down before the next bill date, their billing will cease- no more service charges on the ledger = no more payments taken from payment sources on file. It's also possible to cancel the sub associated with their account or set the next bill date into the future, but this is only recommended if there is an exception where their shutdown date is after the next billing date.

	In response to the authorized cancellation request, we send them the paste for "cancel". You will need to edit it to reflect, 1. any domains we may be hosting for them (~~lsdomains~~ CID), if they have none remove the line. 2. if they are not paying via pp, remove the line referring to a cancelled payment and email confirmation (their credit card will simply stop billing).		In response to the authorized cancellation request, we send them the paste for "cancel". You will need to edit it to reflect, 1. any domains we may be hosting for them (<tt>listdomains <CID></tt>), if they have none remove the line. 2. if they are not paying via pp, remove the line referring to a cancelled payment and email confirmation (their credit card will simply stop billing).

	Once you receive the "Shutdown Today" email or if you see their shutdown date has come (seen in green on the mgmt main/login screen) or if they reply at any point saying you can shut down their server now, you may proceed with actually stopping their server.		Once you receive the "Shutdown Today" email or if you see their shutdown date has come (seen in green on the mgmt main/login screen) or if they reply at any point saying you can shut down their server now, you may proceed with actually stopping their server.
Line 84:		Line 84:
	5. if they are paying via cc, and since we're not stopping them, their sub will have to be cancelled to stop future billing		5. if they are paying via cc, and since we're not stopping them, their sub will have to be cancelled to stop future billing
	6. remove ptr(s), if any: ptr <ip>		6. remove ptr(s), if any: ptr <ip>


	= Dedicated Server =		= Dedicated Server =

← Older revision		Revision as of 18:33, 17 January 2013
Line 6:		Line 6:

	In response to the authorized cancellation request, we send them the paste for "cancel". You will need to edit it to reflect,		In response to the authorized cancellation request, we send them the paste for "cancel". You will need to edit it to reflect,
	1. any domains we may be hosting for them (<tt>listdomains <CID></tt>), if they have none remove the line.		# any domains we may be hosting for them (<tt>listdomains <CID></tt>), if they have none remove the line.
	1. if they are not paying via pp sub, remove the line referring to a cancelled payment and email confirmation (their credit card or paypal billing agreement will simply stop billing).		# if they are not paying via pp sub, remove the line referring to a cancelled payment and email confirmation (their credit card or paypal billing agreement will simply stop billing).

	Once you receive the "Shutdown Today" email or if you see their shutdown date has come (seen in green on the mgmt main/login screen) or if they reply at any point saying you can shut down their server now, you may proceed with actually stopping their server.		Once you receive the "Shutdown Today" email or if you see their shutdown date has come (seen in green on the mgmt main/login screen) or if they reply at any point saying you can shut down their server now, you may proceed with actually stopping their server.
Line 14:		Line 14:

	Automated method:		Automated method:
	1. cancelve VEID		# cancelve VEID
	1. you will be reminded to remove domains (<tt>rmdomains <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC		# you will be reminded to remove domains (<tt>rmdomains <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC
	1. you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)		# you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)
	1. you will be prompted to remove backups, if any		# you will be prompted to remove backups, if any
	1. you will be reminded to ptr(s), if any: <tt>ptr <ip></tt>		# you will be reminded to ptr(s), if any: <tt>ptr <ip></tt>
	1. use the "stop" link in mgmt to set him as down/done.		# use the "stop" link in mgmt to set him as down/done.
	1. if his pp subscription is still active- take action to get that cancelled (email billing person at JC or tell customer to cancel it)		# if his pp subscription is still active- take action to get that cancelled (email billing person at JC or tell customer to cancel it)

	Manual method:		Manual method:

← Older revision		Revision as of 18:32, 17 January 2013
Line 6:		Line 6:

	In response to the authorized cancellation request, we send them the paste for "cancel". You will need to edit it to reflect,		In response to the authorized cancellation request, we send them the paste for "cancel". You will need to edit it to reflect,
	1. any domains we may be hosting for them (<tt>listdomains <CID></tt>), if they have none remove the line.		1. any domains we may be hosting for them (<tt>listdomains <CID></tt>), if they have none remove the line.
	1. if they are not paying via pp sub, remove the line referring to a cancelled payment and email confirmation (their credit card or paypal billing agreement will simply stop billing).		1. if they are not paying via pp sub, remove the line referring to a cancelled payment and email confirmation (their credit card or paypal billing agreement will simply stop billing).

	Once you receive the "Shutdown Today" email or if you see their shutdown date has come (seen in green on the mgmt main/login screen) or if they reply at any point saying you can shut down their server now, you may proceed with actually stopping their server.		Once you receive the "Shutdown Today" email or if you see their shutdown date has come (seen in green on the mgmt main/login screen) or if they reply at any point saying you can shut down their server now, you may proceed with actually stopping their server.
Line 14:		Line 14:

	Automated method:		Automated method:
	1. cancelve VEID		1. cancelve VEID
	1. you will be reminded to remove domains (<tt>rmdomains <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC		1. you will be reminded to remove domains (<tt>rmdomains <CID></tt>) (if any domains are listed, must also be removed from named.conf) NOTE- only remove them if the customer if after shutting down his CT he will no longer have any services with JC
	1. you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)		1. you will be reminded to check for firewall rules on the firewall machine: <tt>g <ip>, ipfw del <rule id> <rule id></tt> (NOTE: make sure to check that only 1 IP is defined by each rule you’re going to delete)
	1. you will be prompted to remove backups, if any		1. you will be prompted to remove backups, if any
	1. you will be reminded to ptr(s), if any: <tt>ptr <ip></tt>		1. you will be reminded to ptr(s), if any: <tt>ptr <ip></tt>
	1. use the "stop" link in mgmt to set him as down/done.		1. use the "stop" link in mgmt to set him as down/done.
	1. if his pp subscription is still active- take action to get that cancelled (email billing person at JC or tell customer to cancel it)		1. if his pp subscription is still active- take action to get that cancelled (email billing person at JC or tell customer to cancel it)

	Manual method:		Manual method: