NM not running after this error is seen

[choksi81]

Several nodes exhibit this behavior and after this, the NM has not been observed running.

1247549568.05:PID-26778:[INFO]:Loading config
1247549568.11:PID-26778:Traceback (most recent call last):
  File "nmmain.py", line 410, in <module>
  File "nmmain.py", line 349, in main
KeyError: 'publickey'

Sample node:
onelab1.info.ucl.ac.be (See http://blackbox.cs.washington.edu:4444/detailed/onelab1.info.ucl.ac.be/1247816135 for more information about the node. Ignore the mismatch on file hashes - it was compared to an older version file dict).

[choksi81]

Author: justinc
I'm not sure what it happening here. The node looks relatively normal except the nodeman.cfg file is missing the publickey and privatekey for the node. I don't know what is happening.

[choksi81]

Author: justinc
I think this might be related to #320. What puzzles me is that the node has obviously transitioned into a different state in the meantime. How did this happen without the node manager running? Was the node uninstalled and reinstalled?

[choksi81]

Author: justinc
This seems to be the cause of our current crisis. We need to fix this ASAP.

[choksi81]

Author: cemeyer
Kon figured out his scripts were causing this and we think it has been fixed.