Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
"Database Unavailable" in only one subdomain?
I use multiple subdomains to test multiple client sites before they get copied out to their own domains. I just noticed that I have a “Database Unavailable” error permanently on one of the subdomains of my site. I do not know if this just happened or has been around for a week.
Yes, I’ve read the FAQ on this, but since another subdomain works just fine I do not think it can be anything like server load. phpMyAdmin shows the contents just fine. I have not changed the settings or config.php. I tried temporarily disabling the .htaccess but nothing changed.
In order to avoid conflicts, one of the databases uses a prefix and the other does not.
Any other clues?
robin
Offline
#2 2008-01-29 22:24:02
- els
- Moderator
- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: "Database Unavailable" in only one subdomain?
Are you sure the user name, db name and password in config.php are correct for the database in question? You might have copied a config.php from one install to another and forgotten just one tiny modification? (it’s something that could happen to me…)
Offline
Re: "Database Unavailable" in only one subdomain?
That is like something I would do. But it is the new subdomain that works perfectly, and the one I copied it from that does not. Bizarre!
robin
Offline
#4 2008-01-30 20:28:25
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: "Database Unavailable" in only one subdomain?
Hmm. Does your username have proper privileges for the database?
Last edited by Mary (2008-01-30 20:29:40)
Offline
Re: "Database Unavailable" in only one subdomain?
That’s it!
When I went through the setup procedure for the second install of textpattern I created an admin database user with the same name as before but a different password. I thought that was kosher since I was on a different database. But apparently my understanding was incorrect.
Establishing this user must have merely replaced the previous one with a new password, with no warning to me that this was happening. So to fix the problem I needed only to change the password in the original site’s config.php.
I am not sure how I ever figured this out, but thanks to you guys for helping!
robin
Offline