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 the message 'could not find requested table - probably empty'.
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 BootImage on CD or USB. 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 Finally, you can track the current status of your machines using this Google Gadget:
41 http://fusion.google.com/add?source=atgs&moduleurl=http://monitor.planet-lab.org/monitor/sitemonitor.xml
43 Thank you for your help,
44 -- PlanetLab Central (support@planet-lab.org)
47 #If no one responds, then 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.
49 newdown_two=("""PlanetLab node(s) down: %(loginbase)s""",
53 As part of PlanetLab node monitoring, we noticed the following nodes were down at your site:
56 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.
58 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 the message 'could not find requested table - probably empty'.
60 http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
62 If the machine has booted successfully, you may check it more quickly by logging in with your site_admin account, and running:
66 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:
68 https://www.planet-lab.org/doc/guides/bootcdsetup
70 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.
72 Finally, you can track the current status of your machines using this Google Gadget:
74 http://fusion.google.com/add?source=atgs&moduleurl=http://monitor.planet-lab.org/monitor/sitemonitor.xml
76 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.
78 Thank you for your help,
79 -- PlanetLab Central (support@planet-lab.org)
82 newdown_three=("""PlanetLab node(s) down: %(loginbase)s""",
86 As part of PlanetLab node monitoring, we noticed the following nodes were down at your site:
89 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.
91 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 the message 'could not find requested table - probably empty'.
93 http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
95 If the machine has booted successfully, you may check it more quickly by logging in with your site_admin account, and running:
99 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:
101 https://www.planet-lab.org/doc/guides/bootcdsetup
103 Finally, you can track the current status of your machines using this Google Gadget:
105 http://fusion.google.com/add?source=atgs&moduleurl=http://monitor.planet-lab.org/monitor/sitemonitor.xml
107 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.
109 Thank you for your help,
110 -- PlanetLab Central (support@planet-lab.org)
113 newbootcd_one=(""" Planetlab nodes need a new BootCD: %(loginbase)s""", # : %(hostname)s""",
114 """As part of PlanetLab node monitoring, we noticed the following nodes have an out-dated BootCD:
117 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).
119 To check the status of these and any other machines that you manage please visit:
121 http://comon.cs.princeton.edu/status
123 Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
125 https://www.planet-lab.org/doc/guides/bootcdsetup
127 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.
129 Thank you for your help,
130 -- PlanetLab Central (support@planet-lab.org)
132 #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.
134 newbootcd_two=(""" Planetlab nodes need a new BootCD: %(loginbase)s""", # : %(hostname)s""",
135 """As part of PlanetLab node monitoring, we noticed the following nodes have an out-dated BootCD:
138 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).
140 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.
142 To check the status of these and any other machines that you manage please visit:
144 http://comon.cs.princeton.edu/status
146 Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
148 https://www.planet-lab.org/doc/guides/bootcdsetup
150 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.
152 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.
154 Thank you for your help,
155 -- PlanetLab Central (support@planet-lab.org)
157 newbootcd_three=(""" Planetlab nodes need a new BootCD: %(loginbase)s""", # : %(hostname)s""",
158 """As part of PlanetLab node monitoring, we noticed the following nodes have an out-dated BootCD:
161 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).
163 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.
165 To check the status of these and any other machines that you manage please visit:
167 http://comon.cs.princeton.edu/status
169 Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
171 https://www.planet-lab.org/doc/guides/bootcdsetup
173 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.
175 Thank you for your help,
176 -- PlanetLab Central (support@planet-lab.org)
178 pcuthankyou_one=("""Thank you for correcting your PlanetLab node PCU - %(loginbase)s""",
180 While monitoring your site, we noticed that the following PCU *improved* their states:
183 Often, system administration is a thankless job, but not today. :-)
186 -- PlanetLab Central (support@planet-lab.org)
189 thankyou=("""Thank you for helping maintain your PlanetLab nodes - %(loginbase)s""",
191 While monitoring your site, we noticed that the following nodes *improved*
195 Often, system administration is a thankless job, but not today. :-)
198 -- PlanetLab Central (support@planet-lab.org)
201 PROD- This state is the production state where the node can contact PlanetLab,
202 and install slices from users.
203 DEBUG- This state designates a node that could not boot successfully.
204 OLDBOOTCD- This state corresponds to the situation where an oldbootcd prevented
205 the normal operation of the node.
206 ERROR- This is an error state, where there is absolutely no contact
210 pcufailed_notice =("""Could not use PCU to reboot %(hostname)s""",
212 """As part of PlanetLab node monitoring and maintenance, we tried to use the PCU
213 registered for %(hostname)s, but could not for some reason.
217 Thank you very much for your help,
218 -- PlanetLab Central (support@planet-lab.org)
220 online_notice=("""Host %(hostname)s is online""",
222 This notice is simply to let you know that:
225 is online and operational. Thank you very much for your help!
227 test_notice=("""Host %(hostname)s is testing""",
229 This notice is simply to test whether notices work.
232 Thank you very much for your help!
234 retry_bootman=("""Running BootManager on %(hostname)s""",
236 This notice is simply to let you know that:
239 appears stuck in a debug mode. To try to correct this, we're trying to rerun BootManager.py.
240 If any action is needed from you, you will recieve additional notices. Thank you!
242 down_notice=("""Host %(hostname)s is down""",
244 This notice is simply to let you know that:
247 is down, disconnected from the network and/or non-operational. Please investigate, thank you very much for your help!
250 clear_penalty=("""All penalties have been cleared from site %(loginbase)s""",
252 This notice is to let you know that any penalties previously applied to your site have
253 been removed: %(penalty_level)s.
255 All privileges have been restored. If your slices were disabled, please allow
256 up to 30 minutes for them to return to enabled.
260 0 - no penalties applied
261 1 - site is disabled. no new slices can be created.
262 2+ - all existing slices will be disabled.
265 increase_penalty=("""Penalty increased for site %(loginbase)s""",
267 This notice is to let you know that the penalty applied to your site has
268 increased: %(penalty_level)s.
272 0 - no penalty applied
273 1 - site is disabled. no new slices can be created.
274 2+ - all existing slices will be disabled.
277 nmreset =("""NM Reset at %(loginbase)s""",
279 Monitor restarted NM on the following machines:
284 pcudown_one =("""Could not use PCU to reboot %(hostname)s""",
286 """As part of PlanetLab node monitoring and maintenance, we tried to use the PCU
287 registered below, but could not for the reasons at the link below:
289 https://monitor.planet-lab.org/cgi-bin/printbadpcus.php?id=%(pcu_id)s
291 We need your help resolving this issue in a few ways:
293 1. First, we need your help rebooting %(hostname)s. Because the above PCU does
294 not appear to work, please manually reboot this machine. If it turns out that
295 there is a problem with the PCU configuration, we can help you
296 resolve that independently.
298 2. If there is nothing apparently wrong with the PCU, or the mapping between
299 the PCU and the host, then there is likely a problem with our bootstrap
300 software on your machine. To help us, please make a note of any text on
301 the console and report it to mailto:support@planet-lab.org . An example
302 might be that the console hangs waiting for a module to unload. The last
303 reported name or any error messages on the screen would be very helpful.
305 3. Alternately, if it is possible, please correcct the above PCU problem, or
306 let us know what steps you are taking. By enabling us to take administrative
307 actions automatically from PlanetLab Central without your intervention, you
308 can trade a small amount of time now for a time savings in the future.
310 If the PCU is up and running, but behind a firewall, please make it accessible
311 from address block 128.112.139.0/24. You can confirm that this is the address
312 space from which the PlanetLab Central servers run.
314 If the above PCU is no longer in service, please delete it by visiting:
316 https://www.planet-lab.org/db/sites/pcu.php?id=%(pcu_id)s
318 and selecting 'Delete PCU'. You may then register a new PCU for your nodes.
320 Thank you very much for your help,
321 -- PlanetLab Central (support@planet-lab.org)
323 pcutonodemapping_one =("""PCU to Node mapping is incorrect for %(hostname)s""",
325 As part of our machine monitoring and maintenance, we tried to use the PCU
326 registered below, and though it appears to succeed, we do not subsequently
327 observe the associated nodes rebooting:
329 https://monitor.planet-lab.org/cgi-bin/printbadpcus.php?id=%(pcu_id)s
333 We need your help resolving this issue in two ways:
335 * First, we need your help rebooting %(hostname)s. Because the above PCU
336 does not appear to actually control the above Nodes, we cannot use it to
337 reboot these machines. So, please manually reboot the machine and we can
338 help you resolve any configuration errors with the PCU independently.
340 * Second, please check the configuration of the above PCU. Check that the
341 PCU is physically connected to the servers that it should be able to
342 control. A common mistake is that the PCU is registered for a machine,
343 but not actually connected physically to the machine.
345 By enabling us to take administrative actions automatically from PlanetLab
346 Central without local intervention, you can trade a small amount of time now
347 for a time savings in the future.
349 If the above PCU is no longer in service, please delete it by visiting:
351 https://www.planet-lab.org/db/sites/pcu.php?id=%(pcu_id)s
353 and selecting 'Delete PCU'. You may then register a new PCU for your nodes.
355 Alternately, if the machines listed above are no longer in service, please
356 delete them by visiting your sites page at:
358 https://www.planet-lab.org/
360 Thank you very much for your help,
361 -- PlanetLab Central (support@planet-lab.org)
364 newalphacd_one=(""" Planetlab nodes need a new BootCD: %(loginbase)s""",
365 """As part of PlanetLab node monitoring, we noticed that your machines needs a new BootCD to fully support your hardware:
369 To make this process as simple as possible, we have created All-in-One boot images that include the node configuration file.
371 The only step that you need to take is to choose which media you prefer, either CD ISO, or USB image for each host.
375 Instructions to burn or copy these All-in-One images to the appropriate media are available in the Technical Contact's Guide.
377 https://www.planet-lab.org/doc/guides/bootcdsetup
379 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.
381 Thank you for your help,
382 -- PlanetLab Central (support@planet-lab.org)
385 # TODO: need reminder versions for repeats...
386 newdown=[newdown_one, newdown_two, newdown_three]
387 newbootcd=[newbootcd_one, newbootcd_two, newbootcd_three]
388 newalphacd=[newalphacd_one, newalphacd_one, newalphacd_one]
389 newthankyou=[thankyou,thankyou,thankyou]
390 pcuthankyou=[pcuthankyou_one,pcuthankyou_one,pcuthankyou_one]
391 NMReset=[nmreset,nmreset,nmreset]
392 pcutonodemapping=[pcutonodemapping_one, pcutonodemapping_one, pcutonodemapping_one]
393 pcudown=[pcudown_one, pcudown_one, pcudown_one]
395 unknownsequence = ("""Unrecognized Error on PlanetLab host %(hostname)s""",
397 While trying to automatically recover this machine:
399 http://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
401 We encountered an unknown situation. Please re-code to handle, or manually intervene to repair this host.
403 Abbreviated BootManager Sequence:
407 BootManager.log output follows:
408 ---------------------------------------------------------
411 donation_down_one=("""PlanetLab node donation setup: %(hostname)s""",
415 As part of PlanetLab node monitoring, we noticed the following node is registered in the PlanetLab database, but it is not completly setup and running.
418 We are writing because we need your help completing the setup to ensure its full operation.
420 You should have received directions for the complete configuration when you contacted the donation program coordinator at PlanetLab. For review, or if you did not receive them, you can find the latest version here:
422 https://svn.planet-lab.org/wiki/DC7800Configuration
424 It is essential that the AMT feature be configured to enable PlanetLab staff to remotely manage the machine. The basic steps are:
426 Configure the DC7800 AMT feature : https://www.planet-lab.org/AMT
427 Add a PCU to your site : https://www.planet-lab.org/db/sites/pcu.php
428 Associate your node with the PCU : Follow the 'My Site' link
429 Finally, download the Boot Image : https://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
430 Burn Boot Image to media & Reboot your node
432 You can confirm that your machine's PCU is correctly configured by visiting the AMT
433 port using your browser, such as:
435 http://%(hostname)s:16992/
437 If you need any clarification about the steps mentioned here, please feel free
438 to contact us at PlanetLab Support (support@planet-lab.org).
440 Thank you for your help,
441 -- PlanetLab Central (support@planet-lab.org)
444 donation_nopcu_one=("""PlanetLab node donation, PCU setup: %(hostname)s""",
448 As part of PlanetLab node monitoring, we noticed the following node was not completely setup at your site:
451 We are writing because we need your help completing the setup to ensure its full operation.
453 The DC7800 comes with a built-in remote management feature. The PCU functionality on your node is not configured. The result of this is that we are unable to remotely administer this machine.
455 You should have received directions for the complete configuration when you contacted the donation program coordinator at PlanetLab. For review, or if you did not receive them, you can find the latest version here:
457 https://svn.planet-lab.org/wiki/DC7800Configuration
459 It is essential that the PCU be configured. The basic steps are:
461 Configure the DC7800 AMT feature : https://www.planet-lab.org/AMT
462 Add a PCU to your site : https://www.planet-lab.org/db/sites/pcu.php
463 Associate your node with the PCU : Follow the 'My Site' link
465 You can confirm that your machine is correctly configured by visiting the AMT
466 port using your browser, such as:
468 http://%(hostname)s:16992/
470 If you need any clarification about the steps mentioned here, please feel free
471 to contact us at PlanetLab Support (support@planet-lab.org).
473 Thank you for your help,
474 -- PlanetLab Central (support@planet-lab.org)
477 donation_nopcu = [ donation_nopcu_one, donation_nopcu_one, donation_nopcu_one ]
478 donation_down = [ donation_down_one, donation_down_one, donation_down_one ]
481 minimalhardware = ("""Hardware requirements not met on PlanetLab host %(hostname)s""",
483 While trying to automatically recover this machine:
485 http://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
487 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.
489 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.
491 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.
496 BootManager.log output follows:
497 ---------------------------------------------------------
501 baddisk = ("""Bad Disk on PlanetLab node %(hostname)s""",
502 """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.
504 Please verify the integrity of the disk, and order a replacement if needed. If you need to schedule downtime for the node, please let us know at support@planet-lab.org.
508 -- PlanetLab Central (support@planet-lab.org)
510 The output of `dmesg` follows:
511 -------------------------------------------------------------------------
516 down=("""PlanetLab node %(hostname)s down.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s has been down for %(days)s days.
518 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.
520 http://summer.cs.princeton.edu/status/tabulator.cgi?table=table_nodeviewshort&select='address==%(hostbyteorder)s'
522 http://www.planet-lab.org/db/sites/index.php?id=%(site_id)d
524 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.
529 -- PlanetLab Central (support@planet-lab.org)
532 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.
534 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.
536 http://summer.cs.princeton.edu/status/tabulator.cgi?table=table_nodeviewshort&select='address==%(hostbyteorder)s'
538 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.
540 Thank you for your help,
541 -- PlanetLab Central (support@planet-lab.org)
544 plnode_cfg=(""" Please Verify Network Configuration for PlanetLab node %(hostname)s""",
547 As part of PlanetLab node monitoring, we noticed that %(hostname)s has a network configuration error related to DNS or hostname lookups. Often this can happen either due local configuraiton changes, or a misconfiguration of the node's DNS servers. To resolve the issue we require your assistance. All that is needed is to visit:
549 https://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
551 Find the primary node network entry and confirm that the settings are correct.
553 If you use 'static' network configuration, verify that the DNS servers are correct. If you are using 'dhcp' then you will need to confirm that the information returned for the node will allow it to perform lookups on it's own hostname.
555 If you change the network settings, 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. If you are using an All-in-One boot image, then you will need to download the All-in-One image instead, burn it to the appropriate media (CD or USB) and reboot.
557 Please let us know if you need any assistance.
559 Thank you for your help,
560 -- PlanetLab Central (support@planet-lab.org)
562 BootManager.log output follows:
563 ---------------------------------------------------------
567 plnode_cfg=(""" Please Update Configuration file for PlanetLab node %(hostname)s""",
568 """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:
570 https://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
572 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.
574 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.
576 Thank you for your help,
577 -- PlanetLab Central (support@planet-lab.org)
580 bootcd=(""" Planetlab node %(hostname)s needs a new BootCD""",
581 """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).
583 Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact Guide.
584 https://www.planet-lab.org/doc/guides/tech#NodeInstallation
586 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.
588 Thanks you for your help,
589 -- PlanetLab Central (support@planet-lab.org)
592 ssh=("""Planetlab node %(hostname)s down.""", """As part of PlanetLab node monitoring, we noticed node %(hostname)s is not available for ssh.
594 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.
596 http://summer.cs.princeton.edu/status/tabulator.cgi?table=table_nodeviewshort&select='address==%(hostbyteorder)s'
598 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.
603 -- PlanetLab Central (support@planet-lab.org)
607 baddns=("""Planetlab node down: broken DNS configuration for %(hostname)s""",
608 """As part of PlanetLab node monitoring, we noticed the DNS servers used by the following machine(s) are not responding to queries.
612 The conseuqnece of this is that the node cannot boot correctly, and is not a functioning part of the PlanetLab network.
614 To help us return this machine to running order, please verify that the registered DNS servers in the node network configuration are correct.
618 You may update the node's network information at the link below:
620 https://www.planet-lab.org/db/nodes/node_networks.php?id=%(nodenetwork_id)s
622 If you have any questions, please feel free to contact us at PlanetLab Support (support@planet-lab.org).
624 Thank you for your help,
625 -- PlanetLab Central (support@planet-lab.org)
629 filerw=("""Planetlab node %(hostname)s has a bad disk.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s has a read-only filesystem.
631 Please verify the integrity of the disk and email the site if a replacement is needed.
635 -- PlanetLab Central (support@planet-lab.org)
639 clock_drift=("""Planetlab node %(hostname)s and NTP.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s cannot reach our NTP server.
641 Please verify that the NTP port (tcp/123) is not blocked by your site.
645 -- PlanetLab Central (support@planet-lab.org)
650 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.
652 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.
655 -- PlanetLab Central (support@planet-lab.org)
659 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.
661 All %(loginbase)s slices are now suspended.
664 -- PlanetLab Central (support@planet-lab.org)
668 pcu_broken=("""%(hostname)s failed to reinstall""","""Hello,
670 %(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?
675 -- PlanetLab Central (support@planet-lab.org)
681 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
685 -- PlanetLab Central (support@planet-lab.org)