![]() |
![]() |
![]() |
||||
Welcome to the GoFuckYourself.com - Adult Webmaster Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact us. |
|
New Webmasters ask "How-To" questions here. This is where other fucking Webmasters help. |
|
Thread Tools |
![]() |
#1 |
Confirmed User
Industry Role:
Join Date: Feb 2003
Location: Down Under
Posts: 188
|
![]() An Error Has Occurred
Could not connect to MySQL database The site administrator has been notified of this issue and will look into it as soon as possible Could not append data to the error log! Any Ideas ? Thanks. |
![]() |
![]() ![]() ![]() ![]() |
![]() |
#2 |
♥♥♥ Likes Hugs ♥♥♥
Industry Role:
Join Date: Nov 2001
Location: /home
Posts: 15,841
|
Your mysql login information is probably incorrect or mysql isn't running.
Then the script was unable to add debug information to the error log because either the path or permissions were incorrect. |
![]() |
![]() ![]() ![]() ![]() |
![]() |
#3 |
Confirmed User
Industry Role:
Join Date: Feb 2003
Location: Down Under
Posts: 188
|
The strange thing is the script throws back at you the databse name,login and username.
I considered a typo causing it,so I deleted the existing db,user and password and made another with 100% match to what the script error said. Still cannot connect. The server has multiple wordpress blogs running on it with no db connection issues. Probably right on the path being incorrect for the error reporting as I've found JMB's scripts are not so good at auto detecting paths depending on the sever setup. Hmm I'll keep looking for an answer. Thanks, |
![]() |
![]() ![]() ![]() ![]() |
![]() |
#4 |
♥♥♥ Likes Hugs ♥♥♥
Industry Role:
Join Date: Nov 2001
Location: /home
Posts: 15,841
|
That's a pretty dumb error message. Wow. Going to have to test that one out and see if it happens to me. I can't imagine why it would echo the login information.
|
![]() |
![]() ![]() ![]() ![]() |
![]() |
#5 |
Registered User
Industry Role:
Join Date: Oct 2011
Posts: 5
|
First thing that comes to mind on the topic of the error message output to screen is your php.ini settings.
Look for "display_errors" in your php.ini Make sure it's set to "Off" PHP Code:
As for why it's not talking to the DB in the first place, check the log files to see what the true error message is. |
![]() |
![]() ![]() ![]() ![]() |
![]() |
#6 |
Confirmed User
Industry Role:
Join Date: Oct 2011
Location: Dreamland
Posts: 52
|
I think it could be incorrect SQL information.. Never really faced such problem !
|
![]() |
![]() ![]() ![]() ![]() |
![]() |
#7 |
Confirmed User
Industry Role:
Join Date: Aug 2002
Location: cali
Posts: 3,135
|
never seen it that weird
|
![]() |
![]() ![]() ![]() ![]() |