<div dir="ltr">Thank you Michel. I checked my amazon ec2 account. I found it's just my fault, node001 seems was terminated by the spot price policy.<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 3, 2013 at 3:22 PM, François-Michel L'Heureux <span dir="ltr"><<a href="mailto:fmlheureux@datacratic.com" target="_blank">fmlheureux@datacratic.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Kai<div><br></div><div>About your 20 nodes cluster, was node001 up all the time or did it stop/restart at any point? If it did, then the node references need to be cleaned and recreated as the identification does indeed change.</div>
<div><br></div><div>The way to solve this is simple: run "<span style="font-family:arial,sans-serif;font-size:13px">ssh-keygen -f "/home/kli/.ssh/known_hosts" -R node001" as it mentions.</span></div><div>
<span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Was a StarCluster load balancer running? I know this error happens from times to times but I haven't spent time over it.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Mich</span></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><span style="color:rgb(136,136,136)">Kai</span></div>
</div></div>