#############################################################################
#############################################################################
#############################################################################
#############################################################################
"""We tried to use the PCU registered for %(hostname)s, but for some reason
the host did not come back online. You may be able to learn more by visiting
this link:
"""We tried to use the PCU registered for %(hostname)s, but for some reason
the host did not come back online. You may be able to learn more by visiting
this link:
We need your help resolving this issue in a few ways:
1. First, we need your help rebooting %(hostname)s. Because the above PCU does
not appear to work, please manually reboot this machine. If it turns out
We need your help resolving this issue in a few ways:
1. First, we need your help rebooting %(hostname)s. Because the above PCU does
not appear to work, please manually reboot this machine. If it turns out
resolve that independently.
2. If it is possible, please correcct the above PCU problem, or let us know
resolve that independently.
2. If it is possible, please correcct the above PCU problem, or let us know
- what steps you are taking. By enabling us to take administrative actions
- automatically without your intervention, you will save time in the future
- the next time we need to reboot this machine, because we will be able to
- do so without disturbing you.
+ what steps you are taking. By enabling us to take administrative actions
+ automatically without your intervention, you will save time in the future
+ the next time we need to reboot this machine, because we will be able to
+ do so without disturbing you.
3. If there is nothing apparently wrong with the PCU, or the mapping between
the PCU and the host, then there is likely a problem with our bootstrap
3. If there is nothing apparently wrong with the PCU, or the mapping between
the PCU and the host, then there is likely a problem with our bootstrap
appears stuck in a debug mode. To try to correct this, we're trying to rerun BootManager.py.
If any action is needed from you, you will recieve additional notices. Thank you!
""")
appears stuck in a debug mode. To try to correct this, we're trying to rerun BootManager.py.
If any action is needed from you, you will recieve additional notices. Thank you!
""")
-This notice is to let you know that any penalties previously applied to your
-site have been removed: %(penalty_level)s.
+This notice is to let you know that any privileges previously reduced at your
+site have been restored: %(penalty_level)s.
-This notice is to let you know that the penalty applied to your site has
-increased: %(penalty_level)s.
+This notice is to let you know that the privileges granted to your site as
+a participating member of Planetlab have reduced: %(penalty_level)s.
Your privileges will be reduced corresponding to the legend below. To
restore these privileges, please return at least two machines to working
Your privileges will be reduced corresponding to the legend below. To
restore these privileges, please return at least two machines to working
"""As part of PlanetLab node monitoring, we noticed that we were not able to recognize all the hardware in your machine. This means that it is so new that it needs a new BootCD, or that it is so old that it is no longer supported.
%(hostname)s
"""As part of PlanetLab node monitoring, we noticed that we were not able to recognize all the hardware in your machine. This means that it is so new that it needs a new BootCD, or that it is so old that it is no longer supported.
%(hostname)s
pcutonodemapping=[pcutonodemapping_one, pcutonodemapping_one, pcutonodemapping_one]
pcudown=[pcudown_one, pcudown_one, pcudown_one]
pcutonodemapping=[pcutonodemapping_one, pcutonodemapping_one, pcutonodemapping_one]
pcudown=[pcudown_one, pcudown_one, pcudown_one]
Configure the DC7800 AMT feature : https://www.planet-lab.org/AMT
Add a PCU to your site : https://www.planet-lab.org/db/sites/pcu.php
Associate your node with the PCU : Follow the 'My Site' link
Configure the DC7800 AMT feature : https://www.planet-lab.org/AMT
Add a PCU to your site : https://www.planet-lab.org/db/sites/pcu.php
Associate your node with the PCU : Follow the 'My Site' link
Burn Boot Image to media & Reboot your node
You can confirm that your machine's PCU is correctly configured by visiting the AMT
Burn Boot Image to media & Reboot your node
You can confirm that your machine's PCU is correctly configured by visiting the AMT
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.
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.
"""As part of PlanetLab node monitoring, we noticed %(hostname)s has a number of disk or media related I/O errors, that prevent it from either booting or reliably running as a PlanetLab node.
Please verify the integrity of the disk, and order a replacement if needed. If you need to schedule downtime for the node, please let us know at support@planet-lab.org.
"""As part of PlanetLab node monitoring, we noticed %(hostname)s has a number of disk or media related I/O errors, that prevent it from either booting or reliably running as a PlanetLab node.
Please verify the integrity of the disk, and order a replacement if needed. If you need to schedule downtime for the node, please let us know at support@planet-lab.org.
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:
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:
"""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:
"""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:
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.
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.
git://git.onelab.eu / monitor.git / blobdiff