%(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)
+""")
+
+ newalphacd_one=(""" Planetlab nodes need a new BootCD: %(loginbase)s""",
+"""As part of PlanetLab node monitoring, we noticed that your machines needs a new BootCD to fully support your hardware:
+
+%(hostname_list)s
+
+To make this process as simple as possible, we have created All-in-One boot images that include the node configuration file.
+
+The only step that you need to take is to choose which media you prefer, either CD ISO, or USB image for each host.
+
+%(url_list)s
+
+Instructions to burn or copy these All-in-One images to the appropriate media are available in the Technical Contact's Guide.
+
+ 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.
+
+Thank you 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]
+ newalphacd=[newalphacd_one, newalphacd_one, newalphacd_one]
newthankyou=[thankyou,thankyou,thankyou]
NMReset=[nmreset,nmreset,nmreset]
+ pcutonodemapping=[pcutonodemapping_one, pcutonodemapping_one, pcutonodemapping_one]
+ pcudown=[pcudown_one, pcudown_one, pcudown_one]
+
+ unknownsequence = ("""Unrecognized Error on PlanetLab host %(hostname)s""",
+ """
+While trying to automatically recover this machine:
+
+ http://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
+
+We encountered an unknown situation. Please re-code to handle, or manually intervene to repair this host.
+
+Abbreviated BootManager Sequence:
+
+ %(sequence)s
+
+BootManager.log output follows:
+---------------------------------------------------------
+%(bmlog)s
+""" )
+
+ minimalhardware = ("""Hardware requirements not met on PlanetLab host %(hostname)s""",
+ """
+While trying to automatically recover this machine:
+
+ http://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
+
+We encountered an failed hardware requirement. Please look at the log below to determine the exact nature of the failure, either Disk, CPU, Network, or Mimial RAM was not satisfied.
+
+If your machine does not meet the current hardware specifications for a PlanetLab node (http://www.planet-lab.org/hardware), please upgrade it to meet the current recommended configuration.
+
+If you believe this message is an error, please email support@planet-lab.org explaining the problem. You may need to create an updated Boot Image that includes drivers for your hardware.
+
+Thank you,
+ - PlanetLab Support
+
+BootManager.log output follows:
+---------------------------------------------------------
+%(bmlog)s
+""" )
+
+ baddisk = ("""Bad Disk on PlanetLab node %(hostname)s""",
+ """As part of PlanetLab node monitoring, we noticed %(hostname)s has a number of disk or media related I/O errors, that prevent it from either booting or reliably running as a PlanetLab node.
+
+Please verify the integrity of the disk, and order a replacment if needed. If you need to schedule downtime for the node, please let us know at support@planet-lab.org.
+
+Thanks.
+
+ -- PlanetLab Central (support@planet-lab.org)
+
+The output of `dmesg` follows:
+-------------------------------------------------------------------------
+
+%(log)s
+""")
down=("""PlanetLab node %(hostname)s down.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s has been down for %(days)s days.
-- PlanetLab Central (support@planet-lab.org)
""")
- planet_cnf=(""" Planetlab node %(hostname)s needs an updated configuration file""", """As part of PlanetLab node monitoring, we noticed %(hostname)s has an out-dated planet.cnf file with no NODE_ID. This can happen after an upgrade and requires your assistance in correcting. All that is needed is to visit:
+ plnode_cfg=(""" Please Update Configuration file for PlanetLab node %(hostname)s""",
+ """As part of PlanetLab node monitoring, we noticed %(hostname)s has an out-dated plnode.txt file with no NODE_ID or a mis-matched HOSTNAME. This can happen either due to an initial configuration failure at your site, with information entered into our database, or after a software upgrade. To resolve the issue we require your assistance. All that is needed is to visit:
- https://www.planet-lab.org/db/nodes/index.php?id=%(node_id)d
+ https://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
-And follow the "Download conf file" link to generate a new configuration file for each node. Copy this file to the appropriate read-only media, either floppy or USB stick, and reboot the machines.
+Then, select, "Download -> Download plnode.txt file for %(hostname)s" menu. This will generate a new configuration file for your node. Copy this file to the appropriate read-only media, either floppy or USB stick, and reboot the machine.
-There's no need to respond to this message if you're able to update the configuration files without difficulty and your node returns to normal operation. 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.
+There is no need to respond to this message if you're able to update the configuration file without difficulty and your node returns to normal operation. 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.
Thank you for your help,
-- PlanetLab Central (support@planet-lab.org)
git://git.onelab.eu / monitor.git / blobdiff