Different error than usual though: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator, bugs-admin(a)winehq.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p> <p>More information about this error may be available in the server error log.</p> </body></html> Is there anything we can do to prevent it from going down so much? -- -Austin
mysqld didn't crash at least. This seems to be a temporary issue that cleared up when the server load came back down. I don't think the server has been down hardly at all? Where are you getting your "down so much" from? -Newman Austin English wrote:
Different error than usual though:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator, bugs-admin(a)winehq.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p> <p>More information about this error may be available in the server error log.</p> </body></html>
Is there anything we can do to prevent it from going down so much?
On Wed, Nov 26, 2008 at 4:12 PM, Jeremy Newman <jnewman(a)codeweavers.com> wrote:
mysqld didn't crash at least. This seems to be a temporary issue that cleared up when the server load came back down.
I don't think the server has been down hardly at all? Where are you getting your "down so much" from?
-Newman
Austin English wrote:
Different error than usual though:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator, bugs-admin(a)winehq.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p> <p>More information about this error may be available in the server error log.</p> </body></html>
Is there anything we can do to prevent it from going down so much?
Sorry if that came off as rash. It's been much better in the past few months. But I was referring to the semi-frequent mysql crashes. I'm on bugzilla a lot, so even if it's only down for a few minutes, I usually catch it. -- -Austin
On Wed, Nov 26, 2008 at 2:15 PM, Austin English <austinenglish(a)gmail.com> wrote:
On Wed, Nov 26, 2008 at 4:12 PM, Jeremy Newman <jnewman(a)codeweavers.com> wrote:
mysqld didn't crash at least. This seems to be a temporary issue that cleared up when the server load came back down.
I don't think the server has been down hardly at all? Where are you getting your "down so much" from?
-Newman
Austin English wrote:
Different error than usual though:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator, bugs-admin(a)winehq.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p> <p>More information about this error may be available in the server error log.</p> </body></html>
Is there anything we can do to prevent it from going down so much?
Sorry if that came off as rash. It's been much better in the past few months. But I was referring to the semi-frequent mysql crashes. I'm on bugzilla a lot, so even if it's only down for a few minutes, I usually catch it.
-- -Austin
I notice it from time to time as well. 95% of the time it works fine, but every so often, for about 30 minutes or so, I get an error 500 or a mysql error.
participants (3)
-
Austin English -
Jeremy Newman -
Lei Zhang