AjaxNinjaHello everyone!
I know that IIS w/ PHP and MySQL isn't the recommended platform for WordPress It works great, but a few times a day I'll get an ugly "unable to establish connection with mysql01.discountasp.net"
Here's the message exchange that proceeded between me and tech support:
Hello DiscountASP.NET Support!
I'm using WordPress 2.2 blogging software (PHP/MySQL) on your service and I keep running into random timeout errors, which are annoying because I have to clear my authenticated user session in order to see the site properly until the error occurs again. The most recent error was at 6:45 CST today; I can provide you with a screen shot if you'd like. I see the wordpress error on average of 4-5 times a day and it will not go away unless I clear my authenticated session data on firefox. Do you have any ideas what the problem might be, and would you like to see the screenshot? The screenshot doesn't provide any error messages other than "unable to connect to database."
The first reply
Tech Support said...
Dear Customer,If the screen shot is just displaying a generic error message, as you said, it probably won't be of much assistance. Is this a problem that you can replicate by any chance by taking a certain series of steps in WordPress?
Thank you,
Joe
My next reply
AjaxNinja said...
Hey Joe,
>
> Yeah I figured the error message wouldn't be of much help to you. The
> problem is that there's no sequence of steps I have to take to produce
> the error; it seems to come and go at random intervals. The vast
> majority of the errors occur on my site's root document, index.php, but
> that's to be expected given that that's the only page that serves
> content to people logging onto my site. Sometimes I get errors when
> index.php is trying to serve up it's default content (last 10 posts),
> sometimes it's when I'm trying to view a specific article, and sometimes
> the error even occurs when I try to access wordpress' administrative
> panel /wp-admin/index.php.
>
> However, once the error is raised, a simple refresh of the page that
> raised it won't get rid of it. I have to manually clear my authenticated
> session first, and this strikes me as interesting. Originally I thought
> my browser might be caching the error message but I went ahead and
> modified the error message content to include a meta no-cache header,
> and I thought I'd see the next time if that error came up if a simple
> refresh would do the trick. Finally when an error message as a result of
> an inability to establish a connection to the mysql server (meaning that
> WordPress couldn't connect to the server's address at all), I used
> Firefox's "Clear Private Data" to clear ONLY the authenticated user
> sessions; all cookies, history, cache files, and saved form data was
> preserved. Once I cleared the authenticated session data I could reload
> the page that triggered the error message and it would refresh without
> any hint of an error.
>
> This makes me wonder if the IIS sessions may have something to do with
> it. I don't have a web.config in the root directory of the site so I
> don't know what options have been specified for running a session. I
> assume that by default sessions are run in process with cookies, right?
> Do you have any ideas as to what might be causing these seemingly random
> moments where WordPress can't connect to the MySQL server?
And the final reply from tech support
Tech Support said...
Hi Aaron,I've checked the MySQL server and everything does seem to be normal and unfortunately, WordPress isn't an application that I can provide direct support for and I do apologize. I've spoken with the Unix administrator who has much more background knowledge of MySQL and here's some of the factors that might be causing the problem:
1. All available database connections used.
2. Long queries.
3. Trying to index or search through a large database.I also do recommend posting the problem in the DiscountASP.NET Community Forum <http://community.discountasp.net/> for peer support as well. The staff members here are encouraged by the management team to post resolutions to problems on the forum.
Again, I do apologize that I am unable to further assist you but I've gathered some information up for you that you can start looking into.
Thank you,
Joe
Anyone know what might be causing this? Does anyone know why the error message won't go away unless I clear the authenticated session? Thanks!
