ORBIT-USER: Imaging Error

[Thierry Rakotoarivelo]

Dear all,

Indeed, this information is on the tutorial page about imaging nodes
(http://orbit-lab.org/wiki/Tutorial/HowToImage)
As Max said, we will add it to the NH output as well.

Regards,
Thierry.

Max Ott wrote:
> This normally indicates a disk error. I guess we should provide a
> better error message. Just try again and if it fails again, please
> report the machine as it may contain a failing disk.
> 
> -max
> 
> On 7/25/07, Thierry Rakotoarivelo <Thierry.Rakotoarivelo at nicta.com.au> 
> wrote:
>> Hi Sanjit,
>>
>> I had a look at your logfile. The nodeHandler received the following
>> message from the nodeAgent on node1-4 in your one-node imaging process:
>>
>> 2007-07-24 18:07:36 DEBUG
>> nodeHandler::Communicator: commServer(STDOUT):
>> 'n_1_4 APP_EVENT DONE.ERROR builtin:load_image "status: 15"'
>>
>> This means that "something" happened on node1-4 that made the frisbee
>> client on it (in charge of retrieving and writing the image) exit with
>> an error code. For us to know what happened, we need the logfile of
>> node1-4 (/var/log/nodeAgent4.log). However, it has most probably been
>> wiped away since your last email (on the next reboot on node1-4)...
>>
>> Sorry for not being able to provide you more information on this issue,
>> maybe next time if we can get the logfile we will be able to do more.
>>
>> Regards,
>> Thierry.
>>
>>
>> Sanjit Kaul wrote:
>> > Not sure why?
>> >
>> > grid_2007_07_24_17_57_49.log
>> >
>> > Thanks,
>> > Sanjit
>>
>> --