[FQuest Alert] Community Forum Instability

[Terra]

There was a MySQL database outage on the NEO server, which drives our Community Support Forums...

This is twice now that MySQL 4.0.12 has let us down... I have already downgraded it back to 3.23.56 which has proven to be stable...

I was hoping that MySQL 4.0.12 was (as they said) production ready, but now I have serious doubts... We will give it another shot in a few months to see if they improve stability...

--
Terra
--it was supposed to be a surprise--
FutureQuest

[dank]

I was curious what caused that... I don't know if it means I've got a nose for spotting trouble or if I spend too much time here, but I happened to check in during both of the outages. :)

Dan

[TVB]

Probably too much time Dan :P But you are in good company (that is if I can call myself good company--many would likely disagree)

Betsy

PS...admitting to a bit of panic when I saw the FQ forums down and then seeing ours up and functioning was grateful for figuring out how to do a much needed upgrade

[Stephen]

is it possible there is some wobbliness in mysql02?

for the last couple of days i have been trying to understand why one of my programs hangs (i have been killing them off). i have not yet been able to figure out what exactly is happening. i have seen it disappear into DBI internal methods and never return (i've seen this doing a DBI->trace), but with different input parameters it hangs elsewhere, so i'm still scratching my head.

right now i'm not ruling out something else in my program being the cause of this, but given that i had been questioning the server before i saw this thread it seems reasonable to enquire about this.

[Deb]

MySQL02 is not likely to be the cause of the problem. The aota forums operate on a separate MySQL server from the Community Accounts. Only our forums/accounts went through a MySQL change that was not 'put to the test' with client's production servers ;) It most likely is something within the script itself...

Deb
- He's only allowed to play in one corner of the sandbox

[Stephen]

you were right. it was my programming at fault. i was not adequately monitoring my MySQL connections and after WRITE LOCKing tables on one database handle i tried to READ on another and caused a blocking condition. the one good thing to come of it was that i was forced to try DBI->trace() and set some DBI internal error flagging that until now i'd managed without.

just sign me dazed and (a little less) confused %)

[Deb]

Thanks for the follow-up. It always helps, when someone has posted a concern, to have the follow-up to bring it to a close for the voyeurs out there. Additionally, it is what keeps the forums useful as an educational tool ;)

Happy to hear it's fixed, and that you dived into new territory!

Deb
- Storybook endings are always nice