techforce
08-31-2001, 12:28 PM
Hi,
I am with pegasus and I have a dedicated server with them. I have had it for 1 week. Last night at 3 AM my server would not respond. I sent them a email. Its now 12 PM and my server is still not responding. So I called them. Someone told me they were not aware of the problem and that he is not in the unix dedicated support dept. I asked him if someone was at the center 24/7 and he said NO :eek: huh? so if a dedicated server goes down we have to wait till the open the next morning?
Is the average business practise of most companies?
on a average server how often can I expect it to go down?
A server shouldn't stop responding unless, there has been network connectivity loss... or for some reason it crashed.
kryps
08-31-2001, 01:44 PM
how about...
[root@rs /root]# uptime
1:38pm up 152 days, 2:09, 1 user, load average: 0.00, 0.00, 0.00
...for server at rackspace.com ;)
-- kryps
If a domain or IP didn't respond it is possible that Apache or BIND were down, but there is a program that restarts them.
Did you get any reports?
what downtime can I expect from my server?
Yikes -- is it really that bad these days that we expect downtime? Unless you're talking about a Windows box, I would certainly say that you shouldn't expect any downtime.
Network connectivity OTOH may go down from time to time, but unless you're getting a really good deal, I would also expect no downtime there either.
As for RackSpace, I second the motion. I had one problem with them in the beginning though: First, I disabled their access to the box completely, Then, I set up ipchains to drop ICMP (Ping) packets.
Their 'RackWatch' system thought my box was down, and after unsuccessfully trying to log in, they pushed the magical Reset button...
Once I asked them to please not do that, I've had a solid 100% uptime since. Not one network outage that I'm aware of (and I monitor externally), and of course the boxes themselves just run and run :)
Anyway, my advice is to first determine if it's a network-related outage or something on your own box. From there, if it's the box, find out if it's a hardware problem, software problem, or even a user problem (all it takes is a typo sometimes)...
Originally posted by kryps
how about...
[root@rs /root]# uptime
1:38pm up 152 days, 2:09, 1 user, load average: 0.00, 0.00, 0.00
...for server at rackspace.com ;)
-- kryps
All that means is the server has not powered down or been rebooted in 152 days. It does not mean it has been available to the world for 152 days. I think rackspace.com does not have much downtime though so it is very possible.
I have FreeBSD servers that have been up 216 days but the network has been down a few times for a few minutes so it does not mean it has been 100% up for 216 days...