From: Stephen Soltesz <soltesz@cs.princeton.edu> Date: Thu, 25 Sep 2008 18:56:07 +0000 (+0000) Subject: clarified 'failed to authenticate' message. X-Git-Tag: MyPLC-4.2-19~9 X-Git-Url: http://git.onelab.eu/?a=commitdiff_plain;h=e4eeb5b8807092dab86938eda515f09e2e0c7622;p=myplc.git clarified 'failed to authenticate' message. --- diff --git a/db-config b/db-config index 76688c1..419fbae 100755 --- a/db-config +++ b/db-config @@ -789,24 +789,18 @@ requirements. The most common reason for authentication failure is that the authentication key stored in the node configuration file, does not -match the key on record. - -There are two possible steps to resolve the problem. - -1. If you have used an All-in-one BootCD that includes the plnode.txt file, - then please check your machine for any old boot media, either in the - floppy drive, or on a USB stick. It is likely that an old configuration - is being used instead of the new configuration stored on the BootCD. -Or, -2. If you are using Generic BootCD image, then regenerate the node - configuration file by visiting: - - https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d - - Under 'Download', follow the 'Download plnode.txt file for %(hostname)s' - option, and save the downloaded file as plnode.txt on either a floppy - disk or a USB flash drive. Be sure the 'Boot State' is set to 'Boot', - and, then reboot the node. +match the key stored in our database. These keys must match in order to +authenticate the node successfully. + +Each time the configuration file is downloaded, either as part of an All-in-One +BootImage or by downloading the plnode.txt file, the authentication key is +RECREATED. So, which ever file was downloaded most recently is the one we +have in our database. Often, users will download both the All-in-One image as +well as the plnode.txt file, and inadvertently break the boot image. + +To repair this problem, simply download your All-in-One BootImage again, and +copy it to the appropriate read-only boot media (write-protected USB or +CD-ROM). If you have already performed this step and are still receiving this message, please reply so that we can help investigate the problem.