flyingcheesehead
Taxi to Parking
Went down at 9:32 CDT tonight, still down at 9:37, back up at 9:41.
It happened again at 0906pm MDT.
Right about the same time for me with the computer clock showing 10:31 EDT. I just gave up and went off to take out my frustration by abusing some packing boxes.Went down at 9:32 CDT tonight, still down at 9:37, back up at 9:41.
It's time to address this or move.
Going dedicated, aside from the cost concerns, brings others. I am NOT a linux expert, and we would need to recruit one whom we could trust absolutely to "hold the keys" and make sure we were doing everything right. I've already made a bit of a mess of the current one... but it limps along for now.
Regarding 1 person with all the keys, I actually agree. Adam Z is, as time allows, working on establishing PoA as a non-profit (non tax exempt) entity.There are several people on this forum with the Linux skills to take care of this problem. I don't think moving to a dedicated server and having it properly maintained would be an issue at all.
All of us have jobs. All of us have lifes. That said this performance problem does not take much time to resolve at all. The community just needs the ability to solve the problem.
I do not think that just one individual should hold the keys. There are plenty of ways to set things up to where this wouldn't be the case. Personally I think a "technical board" per say should be setup where some trusted long term members can respond to these problems. Things will be properly maintained and not one person can pack up and run.
Yep, it just happen to me. And, I'm on a slow air card in the car. It took over five minutes for me to get a return on new posts yet it managed to post my new thread twice.Problem has been coming and going for the last two hours. The double posts and double threads right now are the result.
That remotely sounds like a campaign promise.FYI:
I'm looking in to setting up a test run on another host. Its in the beginning stages right now, but I just wanted you all to know that we're not ignoring this.
Chuck
A what???
Mmm not a r-tard!Hmmm artard, perhaps?
Me thinks there is about 4 Courics of bovine material in the above statement
Please elaborate!Right now I'm experimenting with different ways we could move to a test run on a new server.
The way I prefer - a clean code install and a data migration - will be a very slow process - but might be worth it. However, it would mean that some of the conveniences we're used to here would go away, for a while.
I will when its not so late.
Tho right now I think perhaps the *first* test should be with the code exactly as it is now, and then we can either prove that its something on our end, or it isn't...
I had timeouts from 1100 to 1107 EDT.called godaddy during this last freeze - they didn't see anything.
What I could see was that all 4 proc's were tied up with > 90% iowait reports. :/
to follow up on this I posted my experience on AOPA and evidently this is a common occurance over there also http://forums.aopa.org/showthread.php?t=35258Just another clue, but I see the same thing over at AOPA.
Might be something VB does periodically to the DB like an index optimize or garbage collection.
Joe