#
# Faiyaz Ahmed <faiyaza@cs.princeton.edu>
#
-# $Id: emailTxt.py,v 1.9 2007/08/08 13:26:46 soltesz Exp $
+# $Id: emailTxt.py,v 1.10 2007/08/29 17:26:50 soltesz Exp $
#
%(hostname_list)s
We're writing because we need your help returning them to their regular operation.
-To help, please confirm that a recent BootCD is installed in the machine (Version 3.0 or greater). Then, after checking that the node is properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we are seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network. It may take several minutes before Comon registers your node. Until that time, visiting the link below will return an 'Internal Server Error'.
+To help, please confirm that a verison 3.0 or greater BootCD is installed in the machine. Then, after checking that the node is properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we are seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network. It may take several minutes before Comon registers your node. Until that time, visiting the link below will return an 'Internal Server Error'.
http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
sudo /usr/sbin/vps ax
-If you have a BootCD older than 3.0, you will need to create a new Boot CD and configuration file. You can find instructions for this at the Technical Contact's Guide:
+If you have a BootCD older than 3.0, you will need to create a new BootCD and configuration file. You can find instructions for this at the Technical Contact's Guide:
- https://www.planet-lab.org/doc/guides/tech#NodeInstallation
+ https://www.planet-lab.org/doc/guides/bootcdsetup
-If after following these directions and finding your machine reported by CoMon, there is no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
+If after following these directions, and either logging in with your site_admin account or seeing the CoMon report of your machine, there is no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
After a week, we will disable your site's ability to create new slices. Because this action will directly affect your site's registered PI, we will also CC the PI for help at that time.
%(hostname_list)s
We're writing again because our previous correspondence, sent only to the registered Technical Contact, has gone unacknowledged for at least a week, and we need your help returning these machines to their regular operation. We understand that machine maintenance can take time. So, while we wait for the machines to return to their regular operation slice creation has been suspended at your site. No new slices may be created, but the existing slices and services running within them will be unaffected.
-To help, please confirm that a recent BootCD is installed in the machine (Version 3.0 or greater). Then, after checking that the node is properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we are seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network. It may take several minutes before Comon registers your node.
+To help, please confirm that a verison 3.0 or greater BootCD is installed in the machine. Then, after checking that the node is properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we are seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network. It may take several minutes before Comon registers your node. Until that time, visiting the link below will return an 'Internal Server Error'.
http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
If you have a BootCD older than 3.0, you will need to create a new Boot CD and configuration file. You can find instructions for this at the Technical Contact's Guide:
- https://www.planet-lab.org/doc/guides/tech#NodeInstallation
+ https://www.planet-lab.org/doc/guides/bootcdsetup
-If after following these directions and finding your machine reported by CoMon, there is no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
+If after following these directions, and either logging in with your site_admin account or seeing the CoMon report of your machine, there is no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
After another week, we will disable all slices currently running on PlanetLab. Because this action will directly affect all users of these slices, these users will also be notified at that time.
%(hostname_list)s
We understand that machine maintenance can take time. We're writing again because our previous correspondences, sent first to the registered Technical Contact then the the Site PI, have gone unacknowledged for at least two weeks, and we need your help returning these machines to their regular operation. This is the third time attempting to contact someone in regard to these machines at your site. So, while we wait for the machines to return to their regular operation all current slice activity will be suspended. Current experiments will be stopped and will not be be able to start again until there is evidence that you have begun to help with the maintenance of these machines.
-To help, please confirm that a recent BootCD is installed in the machine (Version 3.0 or greater). Then, after checking that the node is properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we are seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network. It may take several minutes before Comon registers your node.
+To help, please confirm that a verison 3.0 or greater BootCD is installed in the machine. Then, after checking that the node is properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we are seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network. It may take several minutes before Comon registers your node. Until that time, visiting the link below will return an 'Internal Server Error'.
http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
If you have a BootCD older than 3.0, you will need to create a new Boot CD and configuration file. You can find instructions for this at the Technical Contact's Guide:
- https://www.planet-lab.org/doc/guides/tech#NodeInstallation
+ https://www.planet-lab.org/doc/guides/bootcdsetup
-If after following these directions and finding your machine reported by CoMon, there is no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
+If after following these directions, and either logging in with your site_admin account or seeing the CoMon report of your machine, there is no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
Thank you for your help,
-- PlanetLab Central (support@planet-lab.org)
"""As part of PlanetLab node monitoring, we noticed the following nodes have an out-dated BootCD:
%(hostname_list)s
-This usually implies that you need to update the BootCD and node configuration file stored on the read-only media (Either the all-in-one ISO CD, floppy disk, or write-protected USB stick).
+This usually implies that you need to update the BootCD and node configuration file stored on the read-only media (either the all-in-one ISO CD, floppy disk, or write-protected USB stick).
To check the status of these and any other machines that you manage please visit:
Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
- https://www.planet-lab.org/doc/guides/tech#NodeInstallation
+ https://www.planet-lab.org/doc/guides/bootcdsetup
If your node returns to normal operation after following these directions, then there's no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
- https://www.planet-lab.org/doc/guides/tech#NodeInstallation
+ https://www.planet-lab.org/doc/guides/bootcdsetup
If your node returns to normal operation after following these directions, then there's no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
- https://www.planet-lab.org/doc/guides/tech#NodeInstallation
+ https://www.planet-lab.org/doc/guides/bootcdsetup
If your node returns to normal operation after following these directions, then there's no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
ERROR- This is an error state, where there is absolutely no contact
with PlanetLab.
""")
+
+ nmreset =("""NM Reset at %(loginbase)s""",
+ """
+Monitor restarted NM on the following machines:
+
+%(hostname_list)s
+
+ """)
+ pcudown_one =("""Could not use PCU to reboot %(hostname)s""",
+
+"""As part of our machine monitoring and maintenance, we tried to use the PCU
+registered below, but could not for the following reason at the link below:
+
+ https://pl-virtual-03.cs.princeton.edu/cgi-bin/printbadpcus.php#id%(pcu_id)s
+
+We need your help resolving this issue in two ways:
+
+* First, we need your help rebooting %(hostname)s. Because we cannot leverage
+ the above PCU, please manually reboot this machine and we can help you
+ resolve any configuration errors with the PCU independently.
+
+* Second, if it is possible, please correcct the above PCU problem.
+ By enabling us to take administrative actions automatically from
+ PlanetLab Central without local intervention, you can trade a small
+ amount of time now for a time savings in the future.
+
+If the PCU is up and running, but behind a firewall, please make it accessible
+from address block 128.112.139.0/25. You can confirm that this is the address
+space from which the PlanetLab Central servers run.
+
+If the above PCU is no longer in service, please delete it by visiting:
+
+ https://www.planet-lab.org/db/sites/pcu.php?id=%(pcu_id)s
+
+and selecting 'Delete PCU'. You may then register a new PCU for your nodes.
+
+Thank you very much for your help,
+ -- PlanetLab Central (support@planet-lab.org)
+""")
+ pcutonodemapping_one =("""PCU to Node mapping is incorrect for %(hostname)s""",
+ """
+ As part of our machine monitoring and maintenance, we tried to use the PCU
+registered below, and though it appears to succeed, we do not subsequently
+observe the associated nodes rebooting:
+
+ https://pl-virtual-03.cs.princeton.edu/cgi-bin/printbadpcus.php#id%(pcu_id)s
+
+%(hostname_list)s
+
+We need your help resolving this issue in two ways:
+
+* First, we need your help rebooting %(hostname)s. Because the above PCU
+ does not appear to actually control the above Nodes, we cannot use it to
+ reboot these machines. So, please manually reboot the machine and we can
+ help you resolve any configuration errors with the PCU independently.
+
+* Second, please check the configuration of the above PCU. Check that the
+ PCU is physically connected to the servers that it should be able to
+ control. A common mistake is that the PCU is registered for a machine,
+ but not actually connected physically to the machine.
+
+By enabling us to take administrative actions automatically from PlanetLab
+Central without local intervention, you can trade a small amount of time now
+for a time savings in the future.
+
+If the above PCU is no longer in service, please delete it by visiting:
+
+ https://www.planet-lab.org/db/sites/pcu.php?id=%(pcu_id)s
+
+and selecting 'Delete PCU'. You may then register a new PCU for your nodes.
+
+Alternately, if the machines listed above are no longer in service, please
+delete them by visiting your sites page at:
+
+ https://www.planet-lab.org/
+
+Thank you very much for your help,
+ -- PlanetLab Central (support@planet-lab.org)
+""")
+
# TODO: need reminder versions for repeats...
newdown=[newdown_one, newdown_two, newdown_three]
newbootcd=[newbootcd_one, newbootcd_two, newbootcd_three]
newthankyou=[thankyou,thankyou,thankyou]
+ NMReset=[nmreset,nmreset,nmreset]
+ pcutonodemapping=[pcutonodemapping_one, pcutonodemapping_one, pcutonodemapping_one]
+ pcudown=[pcudown_one, pcudown_one, pcudown_one]
down=("""PlanetLab node %(hostname)s down.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s has been down for %(days)s days.
git://git.onelab.eu / monitor.git / blobdiff