Tuesday, March 24, 2009

Server down at 1and1 hosting for the 22nd time

Unfortunately, the server has been down this time since around 6:30 am. It's around 8:00 am now so it was down for about an hour and a half. Usually I catch it and reboot within a few minutes. This time I was up late programming and didn't wake up when the server monitor running on my laptop went off. I've had to sleep with the laptop next to my bed for the last month and a half (since Feb 2nd) because 1and1 refuses to repair or replace the server. Their support rules don't call for replacing a server that crashes several times a week. For them it's apparently normal for servers to crash that often. That and they play the "blame game". They claim it's the customer's fault the server is crashing. However, they can't explain how it could be my fault the server is crashing.

Fortunately, all of the DNS has been transferred to another server. Also all the email and most of the web sites. I've also transferred all of my domain registrations from 1and1 to goDaddy. The last 10 domains should complete transfer in the next few days. This weekend should see the transfer of the few remaining websites to the new server and then I can abandon this piece of junk server from 1and1.com.

Saturday, March 21, 2009

1and1 hosting server is down for 21st time

The server I rent at 1and1 hosting went down again a few minutes ago. This is the twenty first crash since I started trying to use the server around the 2nd of February.

All of the email accounts and most of the websites have been moved from this unreliable server to a server at goDaddy. I hope to get the remaining sites moved this weekend.

Wednesday, March 18, 2009

1and1 hosting server is down for 20th time

The server that I rent from 1and1 hosting is down again. This is the 20th time it's crashed since February 2nd. It stayed up for 3 1/2 days this time.

1and1 Hosting has refused to repair or replace the server. They claim it's the customer's problem if the server keeps crashing. They say that you have to prove the crashes are their fault before they'll look at the server and consider fixing or replacing it.

I'm about half way through moving from 1and1 hosting to goDaddy. Because of other postings on the web about problems with 1and1 hosting I'm transferring all the domains I have registered through 1and1.com to goDaddy.com. Others have posted stories about 1and1 holding domains registered with them hostage because of other disputes with them. To be safe I'm moving all my domains to goDaddy.com even though it's costing me around $300.00 in transfer/renewal fees.


Once again before rebooting the serial console showed only:

RAID1 conf printout:
--- wd:2 rd:2
disk 0, wo:0, o:1, dev:sda7
disk 1, wo:0, o:1, dev:sdb7

Saturday, March 14, 2009

1and.com server only stayed up 15 hours this time

I hope this isn't a trend, the server crashed again after only 15 hours. It's been going around a week between crashes lately. Much better than the 2 or 3 crashes a day a month ago. Anyway, I had to reboot it just after 8 this morning and now just before 12 at night it locked up again and I had to reboot it.

The 1and1 web server has crashed 19 times since February 2nd. 38 days divided by 19 crashes is an average of 2 days between crashes. 1and1 web servers are really unreliable. The 6 year old server I had at Hostway went for years between reboots and even then it didn't lock up, I just rebooted it because of software upgrades.

The 19 crashes in 38 days figure doesn't count the 6 or 8 crashes before they replaced the hard drive. Since then the logs show the following reboots:

Feb 3 21:09:23
Feb 4 15:49:29
Feb 4 21:24:33
Feb 5 05:05:07
Feb 5 13:05:00
Feb 10 05:46:24
Feb 11 05:59:42
Feb 13 17:20:54
Feb 14 00:53:56
Feb 14 18:01:01
Feb 15 21:37:32
Feb 19 15:54:07
Feb 19 20:26:18
Feb 26 00:41:51
Mar 5 07:53:51
Mar 9 18:14:18
Mar 14 08:14:48
Mar 14 23:56:23

1and1.com server down again

Well, the server is down again. I've given up on 1and1.com as a web hosting provider. I'm slowly moving the websites and domain registrations over to another provider. It's ridiculous that 1and1.com's policy is that you have to prove to them it's their fault that the server is crashing before they'll replace it. The fact that it keeps crashing would be a clue to anyone with at least half a brain.

Once again before reboot the serial console showed only:

RAID1 conf printout:
--- wd:2 rd:2
disk 0, wo:0, o:1, dev:sda7
disk 1, wo:0, o:1, dev:sdb7

Monday, March 9, 2009

Server at 1and1.com down again

I just had to reboot the unreliable server that I rent from 1and1.com. It's crashed again and again since I rented it. I tried to get it replaced through 1and1's tech support but they insist that they won't replace it because there's no proof it's their problem. They provided the server and loaded the operating system but claim they're not responsible if it doesn't work right. Reputable hosting companies repair or replace servers that crash. After 1and's tech support refused I emailed their complaints address (management), sales, billing, tech support, and even their press contact. No one was willing to do a thing about it crashing.

The serial console was locked up but showed this before the reboot:

RAID1 conf printout:
--- wd:2 rd:2
disk 0, wo:0, o:1, dev:sda7
disk 1, wo:0, o:1, dev:sdb7

Thursday, March 5, 2009

Unreliable 1and1.com server crashes again

The software I'm using to monitor the defective server 1and1.com provides just notified me that the server has crashed again. By 1and1 hosting's standards this server is great, it stayed up for a whole week before it crashed this time. Once again, the logs and serial console show no reason for the crash. I rebooted it again

It's hard to imagine how 1and1.com stays in business with their normal server being this unreliable. Their management insists that they're not responsible if the server they provide crashes all the time. Nor will they repair or replace it. I get the impression that they don't have anyone on staff who knows enough about webservers and the linux operating system to troubleshoot problems like this.