2 # Copyright (c) 2004 The Trustees of Princeton University (Trustees).
4 # Faiyaz Ahmed <faiyaza@cs.princeton.edu>
6 # $Id: emailTxt.py,v 1.10 2007/08/29 17:26:50 soltesz Exp $
10 # This file contains the texts of the automatically generated
11 # emails sent to techs and PIs
16 newdown_one=("""PlanetLab node(s) down: %(loginbase)s""",
20 As part of PlanetLab node monitoring, we noticed the following nodes were down at your site:
23 We're writing because we need your help returning them to their regular operation.
25 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'.
27 http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
29 If the machine has booted successfully, you may check it more quickly by logging in with your site_admin account, and running:
33 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:
35 https://www.planet-lab.org/doc/guides/bootcdsetup
37 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.
39 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.
41 Thank you for your help,
42 -- PlanetLab Central (support@planet-lab.org)
45 newdown_two=("""PlanetLab node(s) down: %(loginbase)s""",
49 As part of PlanetLab node monitoring, we noticed the following nodes were down at your site:
52 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.
54 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'.
56 http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
58 If the machine has booted successfully, you may check it more quickly by logging in with your site_admin account, and running:
62 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:
64 https://www.planet-lab.org/doc/guides/bootcdsetup
66 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.
68 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.
70 Thank you for your help,
71 -- PlanetLab Central (support@planet-lab.org)
74 newdown_three=("""PlanetLab node(s) down: %(loginbase)s""",
78 As part of PlanetLab node monitoring, we noticed the following nodes were down at your site:
81 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.
83 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'.
85 http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
87 If the machine has booted successfully, you may check it more quickly by logging in with your site_admin account, and running:
91 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:
93 https://www.planet-lab.org/doc/guides/bootcdsetup
95 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.
97 Thank you for your help,
98 -- PlanetLab Central (support@planet-lab.org)
101 newbootcd_one=(""" Planetlab nodes need a new BootCD: %(loginbase)s""", # : %(hostname)s""",
102 """As part of PlanetLab node monitoring, we noticed the following nodes have an out-dated BootCD:
105 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).
107 To check the status of these and any other machines that you manage please visit:
109 http://comon.cs.princeton.edu/status
111 Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
113 https://www.planet-lab.org/doc/guides/bootcdsetup
115 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.
117 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.
119 Thank you for your help,
120 -- PlanetLab Central (support@planet-lab.org)
122 newbootcd_two=(""" Planetlab nodes need a new BootCD: %(loginbase)s""", # : %(hostname)s""",
123 """As part of PlanetLab node monitoring, we noticed the following nodes have an out-dated BootCD:
126 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).
128 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.
130 To check the status of these and any other machines that you manage please visit:
132 http://comon.cs.princeton.edu/status
134 Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
136 https://www.planet-lab.org/doc/guides/bootcdsetup
138 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.
140 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.
142 Thank you for your help,
143 -- PlanetLab Central (support@planet-lab.org)
145 newbootcd_three=(""" Planetlab nodes need a new BootCD: %(loginbase)s""", # : %(hostname)s""",
146 """As part of PlanetLab node monitoring, we noticed the following nodes have an out-dated BootCD:
149 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).
151 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.
153 To check the status of these and any other machines that you manage please visit:
155 http://comon.cs.princeton.edu/status
157 Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
159 https://www.planet-lab.org/doc/guides/bootcdsetup
161 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.
163 Thank you for your help,
164 -- PlanetLab Central (support@planet-lab.org)
166 thankyou=("""Thank you for helping maintain your PlanetLab nodes - %(loginbase)s""",
168 While monitoring your site, we noticed that the following nodes *improved*
172 Often, system administration is a thankless job, but not today. :-)
175 -- PlanetLab Central (support@planet-lab.org)
178 PROD- This state is the production state where the node can contact PlanetLab,
179 and install slices from users.
180 DEBUG- This state designates a node that could not boot successfully.
181 OLDBOOTCD- This state corresponds to the situation where an oldbootcd prevented
182 the normal operation of the node.
183 ERROR- This is an error state, where there is absolutely no contact
187 nmreset =("""NM Reset at %(loginbase)s""",
189 Monitor restarted NM on the following machines:
194 pcudown_one =("""Could not use PCU to reboot %(hostname)s""",
196 """As part of our machine monitoring and maintenance, we tried to use the PCU
197 registered below, but could not for the following reason at the link below:
199 https://pl-virtual-03.cs.princeton.edu/cgi-bin/printbadpcus.php#id%(pcu_id)s
201 We need your help resolving this issue in two ways:
203 * First, we need your help rebooting %(hostname)s. Because we cannot leverage
204 the above PCU, please manually reboot this machine and we can help you
205 resolve any configuration errors with the PCU independently.
207 * Second, if it is possible, please correcct the above PCU problem.
208 By enabling us to take administrative actions automatically from
209 PlanetLab Central without local intervention, you can trade a small
210 amount of time now for a time savings in the future.
212 If the PCU is up and running, but behind a firewall, please make it accessible
213 from address block 128.112.139.0/25. You can confirm that this is the address
214 space from which the PlanetLab Central servers run.
216 If the above PCU is no longer in service, please delete it by visiting:
218 https://www.planet-lab.org/db/sites/pcu.php?id=%(pcu_id)s
220 and selecting 'Delete PCU'. You may then register a new PCU for your nodes.
222 Thank you very much for your help,
223 -- PlanetLab Central (support@planet-lab.org)
225 pcutonodemapping_one =("""PCU to Node mapping is incorrect for %(hostname)s""",
227 As part of our machine monitoring and maintenance, we tried to use the PCU
228 registered below, and though it appears to succeed, we do not subsequently
229 observe the associated nodes rebooting:
231 https://pl-virtual-03.cs.princeton.edu/cgi-bin/printbadpcus.php#id%(pcu_id)s
235 We need your help resolving this issue in two ways:
237 * First, we need your help rebooting %(hostname)s. Because the above PCU
238 does not appear to actually control the above Nodes, we cannot use it to
239 reboot these machines. So, please manually reboot the machine and we can
240 help you resolve any configuration errors with the PCU independently.
242 * Second, please check the configuration of the above PCU. Check that the
243 PCU is physically connected to the servers that it should be able to
244 control. A common mistake is that the PCU is registered for a machine,
245 but not actually connected physically to the machine.
247 By enabling us to take administrative actions automatically from PlanetLab
248 Central without local intervention, you can trade a small amount of time now
249 for a time savings in the future.
251 If the above PCU is no longer in service, please delete it by visiting:
253 https://www.planet-lab.org/db/sites/pcu.php?id=%(pcu_id)s
255 and selecting 'Delete PCU'. You may then register a new PCU for your nodes.
257 Alternately, if the machines listed above are no longer in service, please
258 delete them by visiting your sites page at:
260 https://www.planet-lab.org/
262 Thank you very much for your help,
263 -- PlanetLab Central (support@planet-lab.org)
266 newalphacd_one=(""" Planetlab nodes need a new BootCD: %(loginbase)s""",
267 """As part of PlanetLab node monitoring, we noticed that your machines needs a new BootCD to fully support your hardware:
271 To make this process as simple as possible, we have created All-in-One boot images that include the node configuration file.
273 The only step that you need to take is to choose which media you prefer, either CD ISO, or USB image for each host.
277 Instructions to burn or copy these All-in-One images to the appropriate media are available in the Technical Contact's Guide.
279 https://www.planet-lab.org/doc/guides/bootcdsetup
281 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.
283 Thank you for your help,
284 -- PlanetLab Central (support@planet-lab.org)
287 # TODO: need reminder versions for repeats...
288 newdown=[newdown_one, newdown_two, newdown_three]
289 newbootcd=[newbootcd_one, newbootcd_two, newbootcd_three]
290 newalphacd=[newalphacd_one, newalphacd_one, newalphacd_one]
291 newthankyou=[thankyou,thankyou,thankyou]
292 NMReset=[nmreset,nmreset,nmreset]
293 pcutonodemapping=[pcutonodemapping_one, pcutonodemapping_one, pcutonodemapping_one]
294 pcudown=[pcudown_one, pcudown_one, pcudown_one]
296 unknownsequence = ("""Unrecognized Error on PlanetLab host %(hostname)s""",
298 While trying to automatically recover this machine:
300 http://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
302 We encountered an unknown situation. Please re-code to handle, or manually intervene to repair this host.
304 Abbreviated BootManager Sequence:
308 BootManager.log output follows:
309 ---------------------------------------------------------
313 minimalhardware = ("""Hardware requirements not met on PlanetLab host %(hostname)s""",
315 While trying to automatically recover this machine:
317 http://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
319 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.
321 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.
323 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.
328 BootManager.log output follows:
329 ---------------------------------------------------------
333 baddisk = ("""Bad Disk on PlanetLab node %(hostname)s""",
334 """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.
336 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.
340 -- PlanetLab Central (support@planet-lab.org)
342 The output of `dmesg` follows:
343 -------------------------------------------------------------------------
348 down=("""PlanetLab node %(hostname)s down.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s has been down for %(days)s days.
350 Please check the node's connectivity and, if properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we're seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network.
352 http://summer.cs.princeton.edu/status/tabulator.cgi?table=table_nodeviewshort&select='address==%(hostbyteorder)s'
354 http://www.planet-lab.org/db/sites/index.php?id=%(site_id)d
356 There's no need to respond to this message if CoMon reports that your machine is accessible. 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 resolve the issue.
361 -- PlanetLab Central (support@planet-lab.org)
364 dbg=("""Planetlab node %(hostname)s requires reboot.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s is in debug mode. This usually implies the node was rebooted unexpectedly and could not come up cleanly.
366 Please check the node's connectivity and, if properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we're seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network.
368 http://summer.cs.princeton.edu/status/tabulator.cgi?table=table_nodeviewshort&select='address==%(hostbyteorder)s'
370 There's no need to respond to this message if CoMon reports that your machine is accessible. 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 resolve the issue.
372 Thank you for your help,
373 -- PlanetLab Central (support@planet-lab.org)
376 plnode_cfg=(""" Please Update Configuration file for PlanetLab node %(hostname)s""",
377 """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:
379 https://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
381 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.
383 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.
385 Thank you for your help,
386 -- PlanetLab Central (support@planet-lab.org)
389 bootcd=(""" Planetlab node %(hostname)s needs a new BootCD""",
390 """As part of PlanetLab node monitoring, we noticed %(hostname)s has an out-dated BootCD: "%(version)". This usually implies that you need to update both the BootCD and regenerate the planet.cnf file stored on the read-only floppy (Or read-only USB stick that stores the content of BootCD and planet.cnf).
392 Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact Guide.
393 https://www.planet-lab.org/doc/guides/tech#NodeInstallation
395 There's no need to respond to this message if you're able to follow the directions 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.
397 Thanks you for your help,
398 -- PlanetLab Central (support@planet-lab.org)
401 ssh=("""Planetlab node %(hostname)s down.""", """As part of PlanetLab node monitoring, we noticed node %(hostname)s is not available for ssh.
403 Please check the node's connectivity and, if properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we're seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network.
405 http://summer.cs.princeton.edu/status/tabulator.cgi?table=table_nodeviewshort&select='address==%(hostbyteorder)s'
407 There's no need to respond to this message if CoMon reports that your machine is accessible. 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 resolve the issue.
412 -- PlanetLab Central (support@planet-lab.org)
416 dns=("""Planetlab node %(hostname)s down.""", """As part of PlanetLab node monitoring, we noticed the DNS servers used by %(hostname)s are not responding to queries.
418 Please verify the DNS information used by the node is correct. You can find directions on how to update the node's network information on the PlanetLab Technical Contacts Guid (http://www.planet-lab.org/doc/TechsGuide.php#id268898).
422 -- PlanetLab Central (support@planet-lab.org)
426 filerw=("""Planetlab node %(hostname)s has a bad disk.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s has a read-only filesystem.
428 Please verify the integrity of the disk and email the site if a replacement is needed.
432 -- PlanetLab Central (support@planet-lab.org)
436 clock_drift=("""Planetlab node %(hostname)s and NTP.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s cannot reach our NTP server.
438 Please verify that the NTP port (tcp/123) is not blocked by your site.
442 -- PlanetLab Central (support@planet-lab.org)
447 removedSliceCreation=("""PlanetLab slice creation/renewal suspension.""","""As part of PlanetLab node monitoring, we noticed the %(loginbase)s site has less than 2 nodes up. We have attempted to contact the PI and Technical contacts %(times)s times and have not received a response.
449 Slice creation and renewal are now suspended for the %(loginbase)s site. Please be aware that failure to respond will result in the automatic suspension of all running slices on PlanetLab.
452 -- PlanetLab Central (support@planet-lab.org)
456 suspendSlices=("""PlanetLab slices suspended.""","""As part of PlanetLab node monitoring, we noticed the %(loginbase)s site has less than 2 nodes up. We have attempted to contact the PI and Technical contacts %(times)s times and have not received a response.
458 All %(loginbase)s slices are now suspended.
461 -- PlanetLab Central (support@planet-lab.org)
465 pcu_broken=("""%(hostname)s failed to reinstall""","""Hello,
467 %(hostname)s was remotely rebooted via your power control unit but has not contacted PlanetLab since. It should contact upon every boot, hence we believe that either the node has some hardware problems, is not properly connected to the power control unit, or has network connectivity issues. Could you please reboot the node and watch the console for error messages?
472 -- PlanetLab Central (support@planet-lab.org)
478 We have set %(hostname)s to reinstall, but because your site does not have a power control unit, we are unable to powercycle the node. Please
482 -- PlanetLab Central (support@planet-lab.org)