Feedback We've moved to a new server. Hows it going?

Amin

Hall of Famer
We've moved to a new server, which should have more resources. One good thing about the new host is that future upgrades should be seamless.

How does performance seem so far? Better? Worse?

The Gallery uploads were broken, and I fixed that. Attachment thumbnails aren't appearing, and I'm working on that.

Any other glitches?
 
I know that was an issue at times on the other server as well. Are you getting the popup notification on the site, the email notification, or neither?
 
Have seen your message on another thread, many thanks Amin, glad to be able to get back here. Something funny must have happen because I was on the new site earlier in the day when it locked up on me. After that I was only able to access the old site. About an hour ago I tried a google search, it found the new site and I found I was immediately logged in, 2012 is starting off as a bit confusing. :confused:, now I'm reluctant to log out :), but I'll have to sooner or later.

Hope the New Year goes well for you and yours.

Barrie
 
I keep getting these flashing on my pages (and it keeps saying I posted already, then it's stacking pages, literally, one on top of another):

Warning: require() [function.require]: Unable to allocate memory for pool. in /home/asabet/public_html/seriouscompacts.com/vbseo.php on line 1392

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/search.php on line 89

Warning: require() [function.require]: Unable to allocate memory for pool. in [path]/vb/vb.php on line 222

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbdbsearch/core.php on line 22

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbdbsearch/indexer.php on line 26

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbdbsearch/core.php on line 23

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbdbsearch/coresearchcontroller.php on line 13

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbdbsearch/core.php on line 24

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbdbsearch/postindexcontroller.php on line 15

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbforum/search/indexcontroller/post.php on line 18

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbforum/search/indexcontroller/post.php on line 19

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/vb/legacy/post.php on line 24

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/vb/legacy/thread.php on line 24

Warning: require() [function.require]: Unable to allocate memory for pool. in [path]/vb/vb.php on line 222

Warning: require() [function.require]: Unable to allocate memory for pool. in [path]/vb/vb.php on line 222

Warning: require() [function.require]: Unable to allocate memory for pool. in [path]/vb/vb.php on line 222

Warning: require() [function.require]: Unable to allocate memory for pool. in [path]/vb/vb.php on line 222

Warning: require() [function.require]: Unable to allocate memory for pool. in [path]/vb/vb.php on line 222

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbforum/search/type/thread.php on line 24

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbforum/search/result/thread.php on line 23

Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in [path]/packages/vbforum/search/result/thread.php on line 100
 
Okaaaaay, so I completely broke all the forums and got in over my head trying to make them faster. I think I've undone that problem but that still leaves the performance not exactly where I want it on the new servers.

I'm still working on things but hopefully won't mess up as big as I did today. A big SORRY to everyone who encountered all the craziness today.
 
Yay! Looks OK right at the minute... but seriously... if you are going to do major stuff, you need to use the built in maintenance script. That way nobody is trying to acces, post, etc when you are working on stuff. If you keep making major changes behind the scenes, there are bound to be more errors. That said, keeping my fingers crossed for you.
 
Back
Top