m1.medium
The agent doesn't seem to be able to report vitals and we cannot log in.
Comments are currently closed for this discussion. You can start a new one.
The agent doesn't seem to be able to report vitals and we cannot log in.
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Jonathan Weiss on 19 Mar, 2012 06:48 PM
which instance?
3 Posted by till on 19 Mar, 2012 07:11 PM
Had to take it down: gearman-worker1.
Setup and configure ran, but no CPU/memory reported anywhere. No ssh access. Something went wrong.
Support Staff 4 Posted by Jonathan Weiss on 19 Mar, 2012 07:37 PM
I just successfully booted a m1.medium instance in my cloud and can login normally.
I also don't see any stats yet, we will investigate this.
5 Posted by till on 17 Apr, 2012 03:35 PM
I just had the same problem again.
Setup broke on an instance (
m1.medium) even though it should have the resources required and it's 64bit too, etc.. I was unable to log into it to check out what's wrong.Support Staff 6 Posted by Jonathan Weiss on 17 Apr, 2012 09:53 PM
I don't think that this is related to
m1.medium- did Thomas solve your problem?7 Posted by till on 18 Apr, 2012 02:57 PM
Thomas replied and Daniel helped figure out the issue!
I agree, they are probably not related. Or most likely.
I think whenever the setup breaks, it looks like an instance is basically rendered useless. Which is not too bad because it shouldn't break anyway, but it makes debugging harder. I'm not sure how I can give more feedback on this.
My guess is – because I noticed that with chef-solo a lot – is that chef-solo hogs resources like crazy when things don't go according to plan or just take longer. And then it's downhill from there.
till closed this discussion on 02 May, 2012 04:30 PM.