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 burn a new BootImage to 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 Thank you for your help,
40 -- PlanetLab Central (support@planet-lab.org)
43 #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.
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 Thank you for your help,
118 -- PlanetLab Central (support@planet-lab.org)
120 #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.
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 pcuthankyou_one=("""Thank you for correcting your PlanetLab node PCU - %(loginbase)s""",
168 While monitoring your site, we noticed that the following PCU *improved* their states:
171 Often, system administration is a thankless job, but not today. :-)
174 -- PlanetLab Central (support@planet-lab.org)
177 thankyou=("""Thank you for helping maintain your PlanetLab nodes - %(loginbase)s""",
179 While monitoring your site, we noticed that the following nodes *improved*
183 Often, system administration is a thankless job, but not today. :-)
186 -- PlanetLab Central (support@planet-lab.org)
189 PROD- This state is the production state where the node can contact PlanetLab,
190 and install slices from users.
191 DEBUG- This state designates a node that could not boot successfully.
192 OLDBOOTCD- This state corresponds to the situation where an oldbootcd prevented
193 the normal operation of the node.
194 ERROR- This is an error state, where there is absolutely no contact
198 nmreset =("""NM Reset at %(loginbase)s""",
200 Monitor restarted NM on the following machines:
205 pcudown_one =("""Could not use PCU to reboot %(hostname)s""",
207 """As part of our machine monitoring and maintenance, we tried to use the PCU
208 registered below, but could not for the following reason at the link below:
210 https://monitor.planet-lab.org/cgi-bin/printbadpcus.php?id=%(pcu_id)s
212 We need your help resolving this issue in two ways:
214 * First, we need your help rebooting %(hostname)s. Because we cannot leverage
215 the above PCU, please manually reboot this machine and we can help you
216 resolve any configuration errors with the PCU independently.
218 * Second, if it is possible, please correcct the above PCU problem.
219 By enabling us to take administrative actions automatically from
220 PlanetLab Central without local intervention, you can trade a small
221 amount of time now for a time savings in the future.
223 If the PCU is up and running, but behind a firewall, please make it accessible
224 from address block 128.112.139.0/25. You can confirm that this is the address
225 space from which the PlanetLab Central servers run.
227 If the above PCU is no longer in service, please delete it by visiting:
229 https://www.planet-lab.org/db/sites/pcu.php?id=%(pcu_id)s
231 and selecting 'Delete PCU'. You may then register a new PCU for your nodes.
233 Thank you very much for your help,
234 -- PlanetLab Central (support@planet-lab.org)
236 pcutonodemapping_one =("""PCU to Node mapping is incorrect for %(hostname)s""",
238 As part of our machine monitoring and maintenance, we tried to use the PCU
239 registered below, and though it appears to succeed, we do not subsequently
240 observe the associated nodes rebooting:
242 https://monitor.planet-lab.org/cgi-bin/printbadpcus.php?id=%(pcu_id)s
246 We need your help resolving this issue in two ways:
248 * First, we need your help rebooting %(hostname)s. Because the above PCU
249 does not appear to actually control the above Nodes, we cannot use it to
250 reboot these machines. So, please manually reboot the machine and we can
251 help you resolve any configuration errors with the PCU independently.
253 * Second, please check the configuration of the above PCU. Check that the
254 PCU is physically connected to the servers that it should be able to
255 control. A common mistake is that the PCU is registered for a machine,
256 but not actually connected physically to the machine.
258 By enabling us to take administrative actions automatically from PlanetLab
259 Central without local intervention, you can trade a small amount of time now
260 for a time savings in the future.
262 If the above PCU is no longer in service, please delete it by visiting:
264 https://www.planet-lab.org/db/sites/pcu.php?id=%(pcu_id)s
266 and selecting 'Delete PCU'. You may then register a new PCU for your nodes.
268 Alternately, if the machines listed above are no longer in service, please
269 delete them by visiting your sites page at:
271 https://www.planet-lab.org/
273 Thank you very much for your help,
274 -- PlanetLab Central (support@planet-lab.org)
277 newalphacd_one=(""" Planetlab nodes need a new BootCD: %(loginbase)s""",
278 """As part of PlanetLab node monitoring, we noticed that your machines needs a new BootCD to fully support your hardware:
282 To make this process as simple as possible, we have created All-in-One boot images that include the node configuration file.
284 The only step that you need to take is to choose which media you prefer, either CD ISO, or USB image for each host.
288 Instructions to burn or copy these All-in-One images to the appropriate media are available in the Technical Contact's Guide.
290 https://www.planet-lab.org/doc/guides/bootcdsetup
292 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.
294 Thank you for your help,
295 -- PlanetLab Central (support@planet-lab.org)
298 # TODO: need reminder versions for repeats...
299 newdown=[newdown_one, newdown_two, newdown_three]
300 newbootcd=[newbootcd_one, newbootcd_two, newbootcd_three]
301 newalphacd=[newalphacd_one, newalphacd_one, newalphacd_one]
302 newthankyou=[thankyou,thankyou,thankyou]
303 pcuthankyou=[pcuthankyou_one,pcuthankyou_one,pcuthankyou_one]
304 NMReset=[nmreset,nmreset,nmreset]
305 pcutonodemapping=[pcutonodemapping_one, pcutonodemapping_one, pcutonodemapping_one]
306 pcudown=[pcudown_one, pcudown_one, pcudown_one]
308 unknownsequence = ("""Unrecognized Error on PlanetLab host %(hostname)s""",
310 While trying to automatically recover this machine:
312 http://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
314 We encountered an unknown situation. Please re-code to handle, or manually intervene to repair this host.
316 Abbreviated BootManager Sequence:
320 BootManager.log output follows:
321 ---------------------------------------------------------
324 donation_down_one=("""PlanetLab node donation setup: %(hostname)s""",
328 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.
331 We are writing because we need your help completing the setup to ensure its full operation.
333 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:
335 https://svn.planet-lab.org/wiki/DC7800Configuration
337 It is essential that the AMT feature be configured to enable PlanetLab staff to remotely manage the machine. The basic steps are:
339 Configure the DC7800 AMT feature : https://www.planet-lab.org/AMT
340 Add a PCU to your site : https://www.planet-lab.org/db/sites/pcu.php
341 Associate your node with the PCU : Follow the 'My Site' link
342 Finally, download the Boot Image : https://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
343 Burn Boot Image to media & Reboot your node
345 You can confirm that your machine's PCU is correctly configured by visiting the AMT
346 port using your browser, such as:
348 http://%(hostname)s:16992/
350 If you need any clarification about the steps mentioned here, please feel free
351 to contact us at PlanetLab Support (support@planet-lab.org).
353 Thank you for your help,
354 -- PlanetLab Central (support@planet-lab.org)
357 donation_nopcu_one=("""PlanetLab node donation, PCU setup: %(hostname)s""",
361 As part of PlanetLab node monitoring, we noticed the following node was not completely setup at your site:
364 We are writing because we need your help completing the setup to ensure its full operation.
366 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.
368 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:
370 https://svn.planet-lab.org/wiki/DC7800Configuration
372 It is essential that the PCU be configured. The basic steps are:
374 Configure the DC7800 AMT feature : https://www.planet-lab.org/AMT
375 Add a PCU to your site : https://www.planet-lab.org/db/sites/pcu.php
376 Associate your node with the PCU : Follow the 'My Site' link
378 You can confirm that your machine is correctly configured by visiting the AMT
379 port using your browser, such as:
381 http://%(hostname)s:16992/
383 If you need any clarification about the steps mentioned here, please feel free
384 to contact us at PlanetLab Support (support@planet-lab.org).
386 Thank you for your help,
387 -- PlanetLab Central (support@planet-lab.org)
390 donation_nopcu = [ donation_nopcu_one, donation_nopcu_one, donation_nopcu_one ]
391 donation_down = [ donation_down_one, donation_down_one, donation_down_one ]
394 minimalhardware = ("""Hardware requirements not met on PlanetLab host %(hostname)s""",
396 While trying to automatically recover this machine:
398 http://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
400 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.
402 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.
404 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.
409 BootManager.log output follows:
410 ---------------------------------------------------------
414 baddisk = ("""Bad Disk on PlanetLab node %(hostname)s""",
415 """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.
417 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.
421 -- PlanetLab Central (support@planet-lab.org)
423 The output of `dmesg` follows:
424 -------------------------------------------------------------------------
429 down=("""PlanetLab node %(hostname)s down.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s has been down for %(days)s days.
431 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.
433 http://summer.cs.princeton.edu/status/tabulator.cgi?table=table_nodeviewshort&select='address==%(hostbyteorder)s'
435 http://www.planet-lab.org/db/sites/index.php?id=%(site_id)d
437 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.
442 -- PlanetLab Central (support@planet-lab.org)
445 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.
447 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.
449 http://summer.cs.princeton.edu/status/tabulator.cgi?table=table_nodeviewshort&select='address==%(hostbyteorder)s'
451 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.
453 Thank you for your help,
454 -- PlanetLab Central (support@planet-lab.org)
457 plnode_cfg=(""" Please Verify Network Configuration for PlanetLab node %(hostname)s""",
460 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:
462 https://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
464 Find the primary node network entry and confirm that the settings are correct.
466 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.
468 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.
470 Please let us know if you need any assistance.
472 Thank you for your help,
473 -- PlanetLab Central (support@planet-lab.org)
475 BootManager.log output follows:
476 ---------------------------------------------------------
480 plnode_cfg=(""" Please Update Configuration file for PlanetLab node %(hostname)s""",
481 """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:
483 https://www.planet-lab.org/db/nodes/index.php?nodepattern=%(hostname)s
485 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.
487 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.
489 Thank you for your help,
490 -- PlanetLab Central (support@planet-lab.org)
493 bootcd=(""" Planetlab node %(hostname)s needs a new BootCD""",
494 """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).
496 Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact Guide.
497 https://www.planet-lab.org/doc/guides/tech#NodeInstallation
499 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.
501 Thanks you for your help,
502 -- PlanetLab Central (support@planet-lab.org)
505 ssh=("""Planetlab node %(hostname)s down.""", """As part of PlanetLab node monitoring, we noticed node %(hostname)s is not available for ssh.
507 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.
509 http://summer.cs.princeton.edu/status/tabulator.cgi?table=table_nodeviewshort&select='address==%(hostbyteorder)s'
511 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.
516 -- PlanetLab Central (support@planet-lab.org)
520 baddns=("""Planetlab node down: broken DNS configuration for %(hostname)s""",
521 """As part of PlanetLab node monitoring, we noticed the DNS servers used by the following machine(s) are not responding to queries.
525 The conseuqnece of this is that the node cannot boot correctly, and is not a functioning part of the PlanetLab network.
527 To help us return this machine to running order, please verify that the registered DNS servers in the node network configuration are correct.
531 You may update the node's network information at the link below:
533 https://www.planet-lab.org/db/nodes/node_networks.php?id=%(nodenetwork_id)s
535 If you have any questions, please feel free to contact us at PlanetLab Support (support@planet-lab.org).
537 Thank you for your help,
538 -- PlanetLab Central (support@planet-lab.org)
542 filerw=("""Planetlab node %(hostname)s has a bad disk.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s has a read-only filesystem.
544 Please verify the integrity of the disk and email the site if a replacement is needed.
548 -- PlanetLab Central (support@planet-lab.org)
552 clock_drift=("""Planetlab node %(hostname)s and NTP.""", """As part of PlanetLab node monitoring, we noticed %(hostname)s cannot reach our NTP server.
554 Please verify that the NTP port (tcp/123) is not blocked by your site.
558 -- PlanetLab Central (support@planet-lab.org)
563 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.
565 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.
568 -- PlanetLab Central (support@planet-lab.org)
572 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.
574 All %(loginbase)s slices are now suspended.
577 -- PlanetLab Central (support@planet-lab.org)
581 pcu_broken=("""%(hostname)s failed to reinstall""","""Hello,
583 %(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?
588 -- PlanetLab Central (support@planet-lab.org)
594 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
598 -- PlanetLab Central (support@planet-lab.org)