About a week ago, I changed the password to my site (via cPanel). I dutifully changed my settings.php file and everything was fine.
The next day, the site was gone, with this message: Access denied for user 'username'@'localhost' (using password: YES).
I went back and double-checked settings.php, and it had everything correct. And the site came back up. I played around with my sandbox, adding modules, uploading pictures.
Then the next day, it was gone again!
This repeated a few times. At one point, I discovered I was still using an older version of settings.php, so I replaced that, editing in the relevant info.
And it went down again!
I've got a ticket in to my hosting provider, just in case my MySQL database is horked. But I wanted to put this out to the Drupal community, because I searched and searched, and never found anybody having quite the same problem.
What have I done? What can I do?
Thanks in advance for any suggestions.
Comments
> I changed the password to
> I changed the password to my site (via cPanel). I dutifully changed my settings.php file
Do you mean that you went to cpanel -> my sql databases -> delete user -> create new user with different password
That is the only reason why you would need to change the password in settings.php.
Any *other* password that you changed in cPanel has nothing to do with the one in settings.php.
> I discovered I was still using an older version of settings.php
There are never any old or new 'versions' of settings.php; it is never changed after installation.
However, it will have had 555 chmod. If you tried to edit it without chmodding the 'sites/default' directory and the settings.php file to 755, then any edits you made would have *failed*. It depends on which software you used to do the editing as to whether you would get an error message about this. This would give the appearance of having an 'old version' when you went back to check the edits you (unsuccessfully) made, because the file would not have changed in the first place.
> Then the next day, it was gone again!
Gone as in 'white screen of death'?
http://drupal.org/node/158043
My guess is that you have added too many modules for your php memory allocation. Especially likely if you are on a shared hosting account. This is causing a fatal error *sometimes*, depending on how busy the server is. Shared hosting shares resources with 100 other people, with no protection or minimum resource allocation. You may need to upgrade to a VPS account, or uninstall some modules.
If you have drupal error reporting disabled, I would enable it again whilst you're troubleshooting, so you get errors printed to screen.
Any *other* password that you
Not with my host. cPanel password is the password for the user of my database. Like I said, I've done this before, and never had a problem.
Uh, no. I hadn't replaced settings.php when I upgraded, so there were, indeed, different versions. And the edits to the password in the file took just fine. That's not the problem.
No, as in "Site off-line" page, with this message: Access denied for user 'username'@'localhost' (using password: YES).
Thanks, but no. I've dealt with php memory issues before, and this is nothing like that. It's something between Drupal & MySQL -- fail-yure to commun'cate!
Thanks, though.
Sorry I didn't have any ideas
Sorry I didn't have any ideas that helped.
If you're on shared hosting, because the problem is intermittent, I do still think it is a resource problem of some sort.
Is it the first-lutheran site? I checked how many sites are on the same shared ip - there are about 320.
That's 100 more websites than I've ever had on a shared host, perhaps suggesting that they've over-sold.
So it's possible they've lowered/restricted the total number of connections to SQL in order to stop it crashing.
I'm not sure of the error you'd see if this was the case, but the 'access denied' error makes logical sense.
Hope you get it solved.
Sure did get it solved!
Turns out my host changed the way they do MySQL usernames: They do _. Guess my old one worked just fine until I changed the password, then all hell broke loose.
As to resources, this is such a tiny, low-traffic site, it doesn't present a problem. I get more traffic from Russian hackers than parishioners!
Thanks for your help, though.
> Guess my old one worked
> Guess my old one worked just fine until I changed the password
Weird. You'd think that it would just not connect at all, rather than intermittently throw an error.
> I get more traffic from Russian hackers than parishioners!
Well, I'm atheist and anti-theist, so I kind of hope it stays that way! :)