Server move complete, please post problems here

FWIW In the 15 min since my last post things haven't gotten any better, I just had the BFC "Server Busy" message for a short time as well...
 
Just tried to do a search in Service and Support, with the key words being back door, and this is the message I got.

Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 35 bytes) in /srv/www/html/forums/search.php on line 1151
 
If that's the case then it wasn't bad at all. If a Ganza is only going to shut down the forum for five to ten minutes, that's quite manageable.

It used to be 20 to 30 minutes before the switch, I am happy, not a hog, but happy that the servers seemed to take the refresh that EVERYONE does during a ganza.
Jim
 
Just tried to do a search in Service and Support, with the key words being back door, and this is the message I got.

Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 35 bytes) in /srv/www/html/forums/search.php on line 1151

Just tried same search with same parameters and found 24 posts. although it took 57 seconds to load.
Jim
 
I have had ZERO Problems since the server move. Thanks for doing that.

Is there any chance at all that we could get certain terms made allowed or allow "two character" searches? I ask because when searching for stuff like "D2" or "H1" or "A2" it will not allow me to because it's too short.

Thanks. :)
add an asterisk - D2*, H1*, A2*.
 
If that's the case then it wasn't bad at all. If a Ganza is only going to shut down the forum for five to ten minutes, that's quite manageable.

Unfortunately, this went on for about 30 min...

Same here. Terrible lags for the last 10min. or so.

I've gotten this a couple of times also...

and then

FWIW In the 15 min since my last post things haven't gotten any better, I just had the BFC "Server Busy" message for a short time as well...
 
Issue is being worked on. Hopefully will be fixed this weekend around 2-5 am on sunday
 
Hi Spark, I just glanced through and didn't see it mentioned, but it looks like the site's clock is about 8 minutes fast. Keeps throwing me for a loop, looking at post times that are later than the current time, when I know I haven't been sitting here for almost a full day:D yet :o:foot:;)
 
Perhaps I'm doing something improper ? I can't turn off text messaging when trying to write in bold, Italic, underline or color. Can someone help me with this please ?

Thanks,
 
Interesting situation just happened... But it didn't repeat itself. The new normal time beween searches= 5 seconds. (BTW, thank you for cutting down the time between!!) Here's a screengrab image:

Screengrab_BFcom.jpg


...And it DID make me wait til all 471 of those seconds (7.85 minutes) ran out. :eek: lolz ...Kinda funny, but figured I should mention it.
 
Ok, that might be related to the server time being off. EDIT: The database server had it's time off. It is now set to check its' own time against atomic clocks once per hour, this shouldn't happen again.
 
Two updates:

The server switchover was done. The tech in charge of this project is saying that we're seeing high server load status when there are a lot of processes backed up waiting for CPU access, but the processors themselves aren't even seeing 10% of their capability used... this means there's a bottleneck somewhere either in the kernel or it's wrapper and we're attempting to figure out what.

The second update is that at times we're pushing over 40gigabits per second in traffic. That's frigging unreal.
 
Third update: vB has a server load limit setting that prevents the forums from allowing the server to go down because of runaway processes. Previously our load limit was set to 10, which when hit would cause those "Server too busy" errors to be automatically generated by vB. Our techs have had us disable the load limits to allow us to further test the new setup. If there is a slowdown, our virtualization setup should instantly migrate us to a more powerful server... ideally. We'll see what happens in reality. The way it was explained to me is that there are clients on these setups that have thousands more transactions per second compared to us, so we should be good to go.
 
I have some vague input:

Since the upgrade I've noticed that lots of times when I post a PM to someone, click on the "new posts" button next to a thread, or click a forum name from the index, my browser status bar says "waiting for bladeforums.com" and seems to hang there. If I reload the request (esc/re-click or f5) it'll do the same, but on some subsequent reload it will work instantaneously. This is new behavior since the upgrade.

PS - I was just editing this post and clicking "save changes" does the same thing. Wait, wait, wait....
 
Back
Top