> Well I have logs for the slave that used ami instance ami-b5ea34dc and
> failed to start with the 404 failure in the morning.
> Now the same slaves using ami-b5ea34dc instance are able to start without
> the problem.
> I am not an EC2 expert so am not sure why that failure occurred when I
> tried earlier.
> Anyways will keep a watch and inform if I see the problem again.
I did not mean to imply that you had not seen these, only that I could not
reproduce. Do you have a link to the logs you have where it failed?
On Tue, 24 Apr 2012, Deepti B. Kalakeri wrote:
> Well I have logs for the slave that used ami instance ami-b5ea34dc and
> failed to start with the 404 failure in the morning.
> Now the same slaves using ami-b5ea34dc instance are able to start without
> the problem.
> I am not an EC2 expert so am not sure why that failure occurred when I
> tried earlier.
> Anyways will keep a watch and inform if I see the problem again.
I did not mean to imply that you had not seen these, only that I could not
reproduce. Do you have a link to the logs you have where it failed?