MySQL down at f2s ...

Junior WebHelper Joined: 10 Oct 2002 Posts: 49

I have paid hosting with f2s and note that yesterday and today I am unable to connect to MySQL. I hope the problem with MySQL isn't too serious. Fortunately, this doesn't affect most of my site, but it's still a vexsome issue. I hope f2s is working on resolving this matter. I'm very grateful that 4webhelp provides the f2s email contact list (far better than what is listed at f2s), so I was able to easily send email to the appropriate person there. Anyone know how f2s's business is doing these days?

4WebHelp Addict Joined: 07 Jan 2002 Posts: 1060

Hi,

Yep, there is a current outage on DB Servers 47 & 2 respectively, Server0005.freedom2surf.net is responding correctley at the present time.

Unfortunatley, the cause of the problem is from what we gather over at Freedom2Support, a routing problem, which is resulting in the server not being avaliable at the present time.

Quote:

Tracing route to server0047.freedom2surf.net [194.106.33.59]
over a maximum of 30 hops:

1 170 ms 160 ms 179 ms 192.168.250.61
2 183 ms 184 ms 178 ms 192.168.251.61
3 189 ms 159 ms 198 ms 172.16.93.29
4 175 ms 189 ms 159 ms 213.120.62.201
5 188 ms 172 ms 189 ms core1-pos12-3.bletchley.ukcore.bt.net [194.72.31
.41]
6 195 ms 199 ms 157 ms core1-pos13-0.ealing.ukcore.bt.net [62.6.196.245
]
7 153 ms 165 ms 179 ms core1-pos7-0.telehouse.ukcore.bt.net [194.74.65.
113]
8 175 ms 159 ms 199 ms freedom2surf-2.linx.net [195.66.225.41]
9 186 ms 209 ms 189 ms i-194-106-32-20.freedom2surf.net [194.106.32.20]

10 i-194-106-32-20.freedom2surf.net [194.106.32.20] reports: Destination host
unreachable.

Junior WebHelper Joined: 10 Oct 2002 Posts: 49

Justin,

Thanks for finding out what's going on with those two database servers at f2s. Hope they can resolve things soon. I checked this a.m. and I still couldn't connect to f2s.

On a related note, I am curious as to how to do that route trace. How did you do it? Is there a special utility that I need to download?

4WebHelp Addict Joined: 07 Jan 2002 Posts: 1060

hmmmm, from what they are saying, the database servers are not 47 and 02, but are 05 and 19 now, which would probbably explain the problems, just as an intrest, it says :

Ping request could not find host db.preservestaffnow.org. Please check the name
and try again.

I guess that is your site? it sounds like they may have deleted your database Sad

Posted: Mon Jun 17, 2002 11:07 pm (21 years, 10 months ago)

So they still havent got their act together?

I used to like them too Laughing

Junior WebHelper Joined: 10 Oct 2002 Posts: 49

Well, I just checked and apparently there is still a problem with database server 2 at f2s.
This is the error message I rec'd:

Error
MySQL said:

Can't connect to MySQL server on 'server0002.freedom2surf.net' (113)

Now, this has been going on since Saturday. And, I also emailed f2s and my correspondence went unacknowledged.

If my database had been deleted would't I have rec'd a different kind of error message?

Junior WebHelper Joined: 19 Jun 2002 Posts: 1

Yep, it's definitely a problem with Server0002 since I have 2 databases on 0002 and 1 on 0005 and the one on 0005 is working no problem. I get the same response on 0002 with a ping ("Destination host unreachable") and going through the F2S account management side ("Can't connect to MySQL server on 'server0002.freedom2surf.net' (113)").

And, as seems to be the norm these days, I've received no acknowledgement by email from the support staff at F2S after a couple of emails.

Has anyone heard of an expected up time on 0002? For me, I need it PDQ since it holds a small pricing system for one of my sites and after 3 days it's getting a bit hairy!!

Off topic: feels a bit weird not having a World Cup game today... no excuses now not to do a full days work!! Confused

Mart

4WebHelp Addict Joined: 07 Jan 2002 Posts: 1060

Okay, Give them a call and ask them what is going on :

01727 811 530

Junior WebHelper Joined: 10 Oct 2002 Posts: 49

MartinH, thanks for sharing. Sorry we're in the same boat but somehow it feels better knowing that I'm not alone in experiencing that malfunctioning database server 0002 at f2s.
Justin, thanks for the phone number. Unfortunately, I'm another unemployed US techie, so I am unable to make that long distance call overseas. MartinH, if you're able to give f2s a call, would you please share whatever you manage to find out.

One of the reasons I joined f2s was to have a site where I could hone my skills and have s.thing to show a perspective employer since most of the dot-coms I worked for are no longer. I sure hope that f2s is able to resolve this issue speedily as I truly need my site to function as it should.

Junior WebHelper Joined: 10 Oct 2002 Posts: 49

I asked a question in a recent posting above as to how to trace a route and will now answer my own question. So, for all those who like myself may be less knowledgeable with respect to system administration, here's some info you may find useful if you find that you cannot connect to MySQL whether it be at f2s or elsewhere.

To help detect why you may be having a problem connecting to MySQL, it may be helpful to use Trace Route, an Internet utility that traces how data travels from a computer to a server.

If you use Windows, just exit to a dos prompt and type:

tracert [url]

and if you use UNIX/Linux:

traceroute [url]

Note: url being the url of the database server. And I use [] just to indicate the parameter -- you don't actually type the brackets.

If you wish to get a more meaningful report you can use a free, public utility provided by
http://www.visualroute.com

Also, if you want more info on anything I've written here, check out this url:
http://www.its.umd.umich.edu/documentation_and_faq/TraceRoute_Instructions.html

4WebHelp Addict Joined: 07 Jan 2002 Posts: 1060

Quote:

10 i-194-106-32-20.freedom2surf.net [194.106.32.20] reports: Destination host
unreachable.

Found out something weird, it says that 194.106.32.20 is not reachable, but all the other DB Servers go through exactly the same server fine, you do a tracert to server0005.freedom2surf.net, and the last but one hop is 194.106.32.20 and it gets through it without any problems, but if you do a tracert to 02 & 47, it gives Destination host unreachable, but not on all servers, which is extremely weird.....

Team Member Joined: 06 Jan 2002 Posts: 2564

I think the way a lot of companies, including F2S, deal with these kind of issues is to fix the problem instead of spending time replying to emails asking about the problems...

4WebHelp Addict Joined: 07 Jan 2002 Posts: 1060

Quote:

Microsoft(R) Windows.NET DOS
(C)Copyright Microsoft Corp 1990-2002

E:\WinNet\admin\> ping server0002.freedom2surf.net

Pinging server0002.freedom2surf.net [194.106.33.37] with 32 bytes of data:

Reply from 194.106.32.20: Destination host unreachable.
Reply from 194.106.32.20: Destination host unreachable.
Reply from 194.106.32.20: Destination host unreachable.
Reply from 194.106.32.20: Destination host unreachable.

Ping statistics for 194.106.33.37:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

ping server0047.freedom2surf.net

Pinging server0047.freedom2surf.net [194.106.33.59] with 32 bytes of data:

Reply from 194.106.32.20: Destination host unreachable.
Reply from 194.106.32.20: Destination host unreachable.
Reply from 194.106.32.20: Destination host unreachable.
Reply from 194.106.32.20: Destination host unreachable.

Ping statistics for 194.106.33.59:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Both Still down for me Sad

I think F2S Are still relatively a small company, and don't really have the staff to reply to every email they are sent, and I think they just basically don't have time to reply, but they do seem to take action on things if you email INDUVIDUALS rather than the support people......

Junior WebHelper Joined: 10 Oct 2002 Posts: 49

Daniel:

While your perception may be correct about why f2s and other tech companies don't answer email when problems occur, their lack of communication is not good in terms of customer service. They really should have someone send out s.thing, such as:

"We are aware that you may be experiencing a lack of availability in database service. We apologize for any inconvenience that this may cause you temporarily while we are working to speedily resolve the problem. Thank you for your understanding and patience."

And, so with one click this short notification could be mass emailed. Or, if resources are really scarce, there could be a status page at a company's site with the above message. I don't think that should require a whole lot of web development effort.

# # #

Daniel and Justin:

I am glad that you make available the listing of the individuals at f2s with their emails. I just now sent off an email to each named individual at f2s with the same query as to what's going on with the database server 02. You may want to confirm if "Peter" is still there b/c I just got my email to him kicked back as undeliverable and the message said something about Peter being an unknown user.

4WebHelp Addict Joined: 07 Jan 2002 Posts: 1060

Traceroute from Server in States :

Quote:

Tracing route to server0002.freedom2surf.net
1 192.168.213.200 (192.168.213.200) 1.499 ms 1.163 ms 1.159 ms
2 adsl-65-69-3-254.dsl.hstntx.swbell.net (65.69.3.254) 67.963 ms 16.420 ms 15.640 ms
3 dist1-vlan50.hstntx.swbell.net (151.164.11.126) 26.460 ms 17.113 ms 15.949 ms
4 bb1-g8-0.hstntx.swbell.net (151.164.11.246) 28.529 ms 16.260 ms 18.783 ms
5 bb1-p12-0.dllstx.sbcglobal.net (151.164.240.213) 24.130 ms 22.419 ms 23.362 ms
6 151.164.240.46 (151.164.240.46) 24.086 ms 22.743 ms 29.345 ms
7 bb2-p12-0.rcsntx.sbcglobal.net (151.164.240.237) 34.315 ms 22.157 ms 21.295 ms
8 bb1-p15-0.rcsntx.sbcglobal.net (151.164.243.9) 34.267 ms 22.233 ms 23.802 ms
9 sl-gw39-fw-8-0.sprintlink.net (144.228.130.185) 35.188 ms 38.600 ms 27.186 ms
10 144.232.11.62 (144.232.11.62) 34.512 ms 24.002 ms 23.419 ms
11 144.232.11.89 (144.232.11.89) 34.866 ms 24.011 ms 26.056 ms
12 sl-bb23-atl-10-0.sprintlink.net (144.232.20.60) 53.000 ms 53.522 ms 40.960 ms
13 sl-bb21-atl-8-0.sprintlink.net (144.232.12.25) 49.995 ms 41.299 ms 39.403 ms
14 sl-bb22-rly-15-1.sprintlink.net (144.232.8.125) 64.658 ms 55.103 ms 55.852 ms
15 sl-bb21-msq-1-0.sprintlink.net (144.232.19.97) 70.595 ms 57.634 ms 58.425 ms
16 sl-bb20-msq-15-0.sprintlink.net (144.232.9.109) 71.108 ms 61.081 ms 58.801 ms
17 sl-bb21-lon-14-0.sprintlink.net (144.232.19.70) 201.190 ms 263.395 ms 132.328 ms
18 sl-gw10-lon-15-0.sprintlink.net (213.206.128.46) 139.504 ms 129.110 ms 129.635 ms
19 213.232.65.181 (213.232.65.181) 140.216 ms 128.455 ms 130.506 ms
20 i-194-106-32-20.freedom2surf.net (194.106.32.20) 140.093 ms 130.527 ms 129.733 ms
21 i-194-106-32-20.freedom2surf.net (194.106.32.20) 3136.242 ms !H 3121.425 ms !H 3130.277 ms !H

look at the last hop - Ouch!