Site downtime as I change hosting package (1 Viewer)

[cheekybuddha]

Clearing all access-programmers.co.uk cookies and logging back in seems to have cured that - just posting in case that helps anyone else.

I may have spoken too soon.

Site is still glitchy

 

[Minty]

First time I've managed to get in 09.30 GMT

 

[GaP42]

Just wish I had some hair to go grey!

me too! Still finding that the site is up and down.

 

[Jon]

Propagation can take 24 to 48 hours to be completed. If you want to check the propagation status, go to:

DNS Propagation Checker - Global DNS Checker Tool

Instant DNS Propagation Check. Global DNS Propagation Checker - Check DNS records around the world.

www.whatsmydns.net

67.222.28.252 is the new ip address.

 

[Jon]

My host struggled to transfer the forum due to the size. Part of that is because of the thousands of file uploads that have been added over the years.

Then, there was a problem with elasticsearch, which is used for search. I have some troubleshooting to do, and I am not even sure if my email is working right now. Lots of testing required.

 

[Jon]

Curious if anyone notices any difference in speed, i.e. slower or faster, or pretty much the same?

 

[AccessBlaster]

Curious if anyone notices any difference in speed, i.e. slower or faster, or pretty much the same?

For me, I'm getting logged on and off continuously, so it's hard to tell.

 

[Jon]

I think the propagation kind of flip flops for a while. It will resolve to a steady state eventually.

 

[Gasman]

I just got as below on a simple search.
A server error occurred. Please try again later.

Still some way to go.

 

[Jason Lee Hayes]

It is me or does it seem faster! Maybe due to migration process but definitely feels faster... We will see once settled...

 

[Minty]

My impression was that it seemed a bit quicker.
Maybe it's rebuilt the indexes

 

[tvanstiphout]

It feels a bit faster to me. Not that speed has ever been an issue.

 

[Jon]

It has been a nightmare fixing things behind the scenes. They had put in some wrong IP addresses in one of the nameservers, so that might have been part of the problem with slow propagation. I went in there and fixed it myself. I've spent all day on this and still at it. The hosts support didn't acknowledge their error when I said I had to change IP addresses. Probably company policy to avoid any blame or liability.

Regarding the site speed, the hosting costs just over 1/3rd of the previous costs, but I was on an older server. I removed litespeed, which was supposed to be fast, but fast software running on a knackered old server leads to hardware bottlenecks. The new hosting has a faster processor and hard drives.

 

[Gasman]

I think, only time will tell?
Fingers crossed.

 

[Edgar_]

I've been making these moves for a while now, a bunch of my servers were using old tech and the new tech allows API access and improved file size. But I know the pain of making things work again and waiting for each IP to fully propagate. It can take more than 2 days from the day you change where the domain is pointing to, Europe and USA are usually the first places where propagation occurs, but it's indeed a nightmare.

According to dnschecker, your domain points to 158.106.133.182 in their Germany server.

Anyway, what's the size of the uploads so far?

 

[Isaac]

I'm so glad I stumbled across this thread. And that the site is back up! Thank you Jon.

The other day when I came to the site and it said something like sorry we're not available right now, I feared the absolute worst and my mind was full of all kinds of desperate ideas for what might be happening, having never seen this post beforehand. I thought to myself surely not utter access and now awf!

 

[The_Doc_Man]

I thought to myself surely not utter access and now awf!

Yep, losing this site would be awf-ul.

 

[Jon]

I have found the issue with elastic search. Fixed that using terminal commands (thanks Opus 4.7!). Now running a rebuild of the search index, which will take a while due to the sheer volume of posts.

 

[Jon]

Tried to rebuild caches, but failed. Browser timed out, so tried terminal. That also failed. Back to the drawing board...

 

[Jason Lee Hayes]

Tried to rebuild caches, but failed. Browser timed out, so tried terminal. That also failed. Back to the drawing board...

What are you seeing in the logs Jon - i can help..
Remeber - XenForo allows batch size tuning!