%(hostname_list)s
We're writing because we need your help returning them to their regular operation.
-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'.
+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'.
http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
sudo /usr/sbin/vps ax
-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:
+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:
https://www.planet-lab.org/doc/guides/bootcdsetup
%(hostname_list)s
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.
-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'.
+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'.
http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
%(hostname_list)s
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.
-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'.
+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'.
http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
""")
pcudown_one =("""Could not use PCU to reboot %(hostname)s""",
-"""As part of our machine monitoring and maintenance, we tried to use the PCU
-registered below, but could not for the following reason at the link below:
+"""As part of PlanetLab node monitoring and maintenance, we tried to use the PCU
+registered below, but could not for the reasons at the link below:
https://monitor.planet-lab.org/cgi-bin/printbadpcus.php?id=%(pcu_id)s
-We need your help resolving this issue in two ways:
+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 that
+ there is a problem with the PCU configuration, we can help you
+ resolve that independently.
-* First, we need your help rebooting %(hostname)s. Because we cannot leverage
- the above PCU, please manually reboot this machine and we can help you
- resolve any configuration errors with the PCU independently.
+ 2. 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
+ software on your machine. To help us, please make a note of any text on
+ the console and report it to mailto:support@planet-lab.org . An example
+ might be that the console hangs waiting for a module to unload. The last
+ reported name or any error messages on the screen would be very helpful.
-* Second, if it is possible, please correcct the above PCU problem.
- By enabling us to take administrative actions automatically from
- PlanetLab Central without local intervention, you can trade a small
- amount of time now for a time savings in the future.
+ 3. Alternately, 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 from PlanetLab Central without your intervention, you
+ can trade a small amount of time now for a time savings in the future.
If the PCU is up and running, but behind a firewall, please make it accessible
-from address block 128.112.139.0/25. You can confirm that this is the address
+from address block 128.112.139.0/24. You can confirm that this is the address
space from which the PlanetLab Central servers run.
If the above PCU is no longer in service, please delete it by visiting:
git://git.onelab.eu / monitor.git / blobdiff