Rapid Reboot woes!!! HELP!

[tekdev]

Now that I read a bit more, I see that the much-touted rapid-reboot should be a last resort. Well, my site became unresponsive to all web aspects, WHM included. Nothing, nada. Ping was OK. I should have tried putty, so I tried the rapid reboot and now its been sitting at reboot initiated for over an hour! And the supoort ticket hasn't been assigned in the last hour either! HELP! Site IP is: 69.44.157.180

[lkbryant]

i am now also having some sort of same problem.

everything worked fine just couple hours ago, didn't touch at hing.
now, sites are not responding, cant even SSH, i can ping fine, dns seems to resolve fine, but i cant do nothing??

how do i solve this?

do i have to "buy" a support ticket for a problem i dont think i committed?

[DXD]

This has happened to me several times already and I've only had the server a week.

I've found the Rapid Reboot never does anything I usually wait 10-20 minutes and when the server doesn't come back up I submit a reboot request ticket which does not cost anything. Doing this has resovled the issue within an hour normally.

I'm not sure what the Radid Reboot Feature is for as I've never seen it actually work.

[knightfoo]

RapidReboot performs a hardware reset of your server, much like flipping the power switch off then on. However, it does not guarantee that your server will come back online .. if there are hardware or OS issues that prevent the server from booting properly, support is automatically notified to investigate. You do not need to buy a support ticket or use a paid support ticket to check the status on a reboot. :)

-knightfoo

[DXD]

I hear what your saying but I've tried it knowing there was nothing wrong with the server just to see if it works and it doesn't.

Also that auto creating of the support ticket I've seen that take hours before it does not.

I've even seen MY.SERVERBEACH.COM report that the server was up when it's not.

[QT]

The "Online" status in MyServerBeach simply means that your account is active (not suspended).
:)

[DXD]

Ok let me be more clear :)

Where it says "Server Online" on http://my.serverbeach.com I've found that's not always true :)

And I'm not refering to just after a reboot. I've found it that way after a TECH says it's online and it wasn't but it said online.

[knightfoo]

Originally posted by DXD
Ok let me be more clear :)

Where it says "Server Online" on http://my.serverbeach.com I've found that's not always true :)

And I'm not refering to just after a reboot. I've found it that way after a TECH says it's online and it wasn't but it said online.

As QT stated, the "Online" status simply means your account is not suspended and the server is not in the process of being rebooted. Since we do not offer a monitoring solution, MyServerBeach does not have a live status of whether your server is down or up.

-knightfoo

[DXD]

Now I'm getting really confused:

https://secure.serverbeach.com/catalog/rapid_reboot_explain.php

<i>You will be able to view the status of your server as it reboots. Next to your server, you will see one of the following messages to indicate the status of your reboot operation:
• Server online - no reboot in process
• Reboot initiated
• Reboot in process
• Reboot complete
• Contacting support
</i>

So if it's not monitored? How does it know it's in process and when it's complete?
<i>
• Network card check
• IP network traffic test
</i>
That looks like it saying it's checked at reboot as well which would indicate monitoring of the reboot.

<i>Your server will be rebooted immediately, but it takes up to 10 minutes for the RapidReboot™ system to run and complete its tests. You will receive an e-mail notification, confirming that your server was rebooted successfully</i>

Again I say no it does not. As I've tried it multiple times, and never have had any of the results the Rapid Reboot page states.
After I've clicked the Rapid reboot I've waited an hour or more and no ticket, then I created my own ticket to have a tech reboot it since Rapid Reboot obviously didn't work.

So if your saying there is no Monitoring how does Rapid Reboot know that the server was sucessfully rebooted and that a ticket doesn't need to be created.

What checks are done? If someone is running a firewall and blocking all ICMP traffic you couldn't just ping the server and know, you would never know it was rebooted.

Something here doesn't add up or make sense to me.

[lkbryant]

hmm, so no one knows why my server all of a sudden was unable for me to ssh into it letalone work as a webserver?

[canislupusyo]

it could be several reasons why you server will not respond to ssh anything form server load to hardware problems. your best bet is to contact SB via trouble ticket.

[interra]

I had an incident with my server as well.

For some reason server stopped responding to any requests from outside except ICMP packets (ping / traceroute).

I expect there to be internal software problem on my server and I'm monitoring it to find the reason why it happened.

But anyway when I tried to use RapidReboot it helped me not. For almost an hour there was no reaction to RapidReboot request I made. According to http://www.serverbeach.com/catalog/rapid_reboot_explain.php
How long will a RapidReboot™ take?

Your server will be rebooted immediately, but it takes up to 10 minutes...
I even tried to do it another time and yet another time (with appropriate 10-15 minutes delays).

Finally I've seen the message stating the reboot operation on mySB console. Server promptly was available again. And within some time (25 minutes or so) I got e-mail with confirmation that reboot was complete.

If SB is eager to investigate the case 4th of September 2004 was the date and #6559-1 was the server which had the problem.

Regards,

m.

[tekdev]

OK, I'm not sure what's going on, but out of the blue, my server stops responding to anything, no ping, no nothing. tracert stops at 69.44.56.67. I did a rapid-reboot as a last resort and dang if it didn't stay stuck at "reboot initiated" again... going on 20 minutes now. Please somebody from SB assure me that this is not normal to have this same problem occur twice in two weeks! Since I can't connect to the box at all I can't see what's wrong! I need some assurances or causes because this makes me look bad to my clients. Any help is greatly appreciated!

[QT]

Originally posted by tekdev
OK, I'm not sure what's going on, but out of the blue, my server stops responding to anything, no ping, no nothing. tracert stops at 69.44.56.67. I did a rapid-reboot as a last resort and dang if it didn't stay stuck at "reboot initiated" again... going on 20 minutes now. Please somebody from SB assure me that this is not normal to have this same problem occur twice in two weeks! Since I can't connect to the box at all I can't see what's wrong! I need some assurances or causes because this makes me look bad to my clients. Any help is greatly appreciated!
As I stated in my PM, this sounds like it may be a hardware issue. Please submit a support request to have one of our technicians investigate. :)

[RobS]

I've used the Rapid Reboot and it has always worked for me... Except today... :-(