Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Thu Oct 15, 2009 10:55 am 
Offline
Senior Newbie

Joined: Thu Oct 15, 2009 3:53 am
Posts: 6
This should be a simple question: why could a gentoo vps (stock image, 32bit) shutdown and never come up when i run 'reboot'?
--
Oct 15 14:30:09 ln shutdown[17350]: shutting down for system reboot
--


Top
   
 Post subject:
PostPosted: Thu Oct 15, 2009 12:00 pm 
Offline
Senior Member
User avatar

Joined: Tue May 26, 2009 3:29 pm
Posts: 1691
Location: Montreal, QC
Do it from lish and see if any error messages are produced.


Top
   
 Post subject:
PostPosted: Thu Oct 15, 2009 12:05 pm 
Offline
Senior Member

Joined: Fri Dec 07, 2007 1:37 am
Posts: 385
Location: NC, USA
If you wait a minute or two, you should get a Lassie initiated boot anytime you shutdown from within your linode. I just checked and it works fine on my gentoo system (running 2.6.30.5-x86_64-linode8). Check the "Settings and Utilities" tab of the Linode Manager to see if it is enabled for you. In fact, Lassie is so aggressive that she will restart you even if you do a "shutdown -h".

If you don't want to wait for Lassie, you can initiate the reboot from the Linode Manager or within a Lish session.


Top
   
 Post subject:
PostPosted: Tue Oct 20, 2009 10:06 pm 
Offline
Senior Newbie

Joined: Thu Oct 15, 2009 3:53 am
Posts: 6
Yeah, Lassie does it's job but here's what I've noticed:
newark18 - works as expected
newark35, newark65 - doesn't start after reboot.
The same Gentoo image. So I guess it has smth to do with newer server configs.
Will be getting to lish later.


Top
   
 Post subject:
PostPosted: Wed Oct 21, 2009 4:33 pm 
Offline
Senior Member

Joined: Thu Dec 04, 2008 10:55 am
Posts: 57
Location: New Jersey
mispost


Top
   
 Post subject:
PostPosted: Wed Oct 21, 2009 8:48 pm 
Offline
Senior Newbie

Joined: Thu Oct 15, 2009 3:53 am
Posts: 6
OK, tried rebooting via lish.
The last message I see before screen terminates is that the system will be rebooted.


Top
   
 Post subject:
PostPosted: Wed Oct 21, 2009 9:06 pm 
Offline
Senior Member

Joined: Sat Mar 28, 2009 4:23 pm
Posts: 415
Website: http://jedsmith.org/
Location: Out of his depth and job-hopping without a clue about network security fundamentals
I could be emitting complete hot air here, and if so caker will correct me --

'reboot' and such in Linux will communicate to the kernel that a warm reboot is to be attempted. In our environment, there's no such thing. When you issue 'reboot', your guest domain goes away, and Lassie will jump in and issue a boot job to your Linode.

It's all the same to our system. Your domU was there, and then it wasn't. I don't think we know if you issued a 'reboot' from your Linode, because it probably tries to fire ACPI commands for a warm reset...which Xen might completely ignore.

These are all guesses, but educated ones. My suspicion is that 'reboot' is blindly saying "warm reset, please", Xen is ignoring it, and destroying the domain. This is probably why when you issue a reboot to your Linode from the Linode Manager, you get a "shutdown" job and a "boot" job.

(Aside: Higher host numbers aren't necessarily indicative of newer software. In this particular case, newark18 actually has "newer" software than newark35. We probably rebooted it at some point. Edit: Yep.)

_________________
Disclaimer: I am no longer employed by Linode; opinions are my own alone.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group