I'm going to try a new EEVblog web server with sitecloud.com
Could take a few days to process and do a trial transfer, but if you see any hiccups in the next few days, that's likely what's happening. The plan is to change everything over intact, so you won't notice the difference., but we'll see what happens.
Twitter will be where I post updates if/when the shit hits the fan!
Dave.
man! i just transferring and never been able to restore my previous site yet! now just due to this 1TBytes/month issue, you are transferring too! well, way to go, if you think its good to go
but in case you dont manage, and its like we will not be seeing each other again... i'm sorry for any faults that i've made to you or your blog or to your friends or your pets, and i thank you for anything that you have given us! ahakssss!
wish u luck and success!
The old server won't be going down, so it it all goes tits-up I can point the DNS back to Hostmonster and it's business as usual!
SiteCloud claim to handle the web site migration for you, so lets see what they can do.
The worst that will happen is a few blog comments and forum posts are lost in the few hours it takes to transfer. Although I should really disable the forum and comments until the change is done.
Dave.
Migration is now in progress!
Ok, the deed is done.
However there is one quirk I'm interested in if anyone has the technical knowledge to answer it.
Using
www.network-tools.comIf I do a trace on eevblog.com I get plenty of timeouts and it eventually can't finish the trace. This is to my new Sitecloud server.
However, if I try the same trace on my old server (hostmonster) using boondaburra.com, there are no timeouts, and completes the trace in 9 hops every time.
Pings to either site are fine and very fast, but it's the trace thing that has me concerned.
Anyone know exactly what this means and what impact (if any) it might have one using this new server to host EEVbog?
i.e. would it impact my search engine ranking or anything else?
Thanks
Dave.
It's nothing to worry about - Amazon are blocking the traceroute packets within their network, or their routers are using private address space. If you have shell access to the server it's running on, you could try the trace from that end to see if it's being blocked at the border router or on those machines.
I just tried doing a ping with the record route option set and got:
gi1-0-0.bdr1.iad1.internode.on.net (206.223.115.197)
72.21.197.35
72.21.222.144
216.182.224.54
216.182.224.18
216.182.232.66
Compare this with the traceroute:
8 equinix01-iad2.amazon.com (206.223.115.68) 264.754 ms 265.372 ms 266.058 ms
9 72.21.197.40 (72.21.197.40) 264.802 ms 264.833 ms 265.145 ms
10 72.21.222.149 (72.21.222.149) 265.643 ms * 265.188 ms
11 * * *
12 * * *
13 * * *
14 s1.cloudwelcome.com (184.73.164.210) 265.145 ms 265.384 ms 265.209 ms
So it's the 216.182.x.x routers aren't responding to traceroute.
Yep, its completely normal. The response is blocked so it is more difficult to map out the inside of of various providers networks. All you are getting when you get IPs are the public facing edges.
I would suggest to let this day pass ... with out benchmarks.
There is an serious issue today with the main Internet connections , between US and Europe.
I have serious issues all day , but when I connect on the current server , my navigation are truly fast ..
When I tried to use the
www.network-tools.com , because the service are located in US ,
I got one report indicating problems .. and time outs .
So, lets forget the benchmarks today ...
I'm not having any problems and I'm in the UK see looks like this Europe things is load of rubbish after all
I've gotten a few "Your attempt to post timed out" or something similar. Just kept clicking
on the "Post" button until this message went away. Otherwise things seem to be
acting normally for me.
Scott
"Failed requests" generally means any request that had a 400 or 500 error code. You'd probably have to look at the logs to see when and why this happened, if it's working at the moment.
I've encountered a couple of 503 error's but a refresh fixed them.
- Patrick
So when using the forum looking for unread posts, I've now gotten the
following error a couple times over the past week:
502 Bad Gateway
The server returned an invalid or incomplete response.
Refreshing seems to bring things right back, but it's kinda weird.
Scott
So when using the forum looking for unread posts, I've now gotten the
following error a couple times over the past week:
502 Bad Gateway
The server returned an invalid or incomplete response.
Refreshing seems to bring things right back, but it's kinda weird.
Scott
I've seen this once or twice myself. No idea why, but at least the forum and site don't go down for hours on end for me like it used to before the switch.
Dave.
So I hate to say this, but for at least an hour this morning (California time),
I was getting something like:
Service Unavailable
I'm currently seeing some kind of problem with unread messages. If I click
on "Show unread posts since last visit", I get nothing, but if I just go to
the front page of the forum, some of the forum sections are showing new
posts (i.e. the icon is *not* grayed out). And the forum stats show a posting
within the last hour. Kinda puzzled over this split personality.
Scott
Well, I tried logging out and back in again, but that hasn't cured the new messages problem.
Even weirder, I had to click on logout 3 times, because the first 2 times I got this message:
Session verification failed. Please try logging out and back in again, and then try again.
[now getting this session verification message on first try to post this message]
Think I'll just go to bed and hope things are healed overnight :-)
Scott
Got the same error myself yesterday : 503
I think it has something to do with the load on the server. Can you measure it, Dave, and maybe tell us the results ?
At least what does /proc/loadavg says. SHould be something like this :
[root@private02 ~]# cat /proc/loadavg
0.36 0.45 0.49 2/214 30494
I had these problems too on a high-traffic server but mine were mostly because of a flood
LE : i keep getting session expired error. I think it has to do with some php.ini modifications you might have made recently.
Any php upgrade or something like this ? Check where your session files are stored (should be in /tmp folder or something else with write access for the owner of the php process). Also try to check if there is enough space on the server (sounds like check if it is plugged in but believe me, i have been in a situation like this; paranoid is not enough)
I am now on cloud based server (sitecloud.com) specifically to prevent any server load problems!
I have contacted them about this and lets see what happens, because I can't figure it out.
There is now way I can monitor my "compute cycle" usage, they don't have that facility working yet.
Sitecloud.com is looking suckier every day. I should have stuck with Hostmonster.com
Dave.