Hey all,
This seems like a vague question, but I tried upgrading (the process seems so simple!) and now my browser errors out and I cannot connect to my DB to run the upgrade script. Suxor, I think i am going insane. I have gone over the username, password, etc, about a thousand and one times and there are no mistakes for sure. It's the same file! I also tried modifying the new default settings.php and arrived in the same place. When I switch back to 4.6 it's all good. What in the world could be causing this problem?
I am just about to contact the administrator of the server (I do not have root here) and ask about which versions of php and sql we are running, but I thought that there was not a huge difference in system requirements between 4.6 & 4.7 . I am basing this on other people's posts with the same problem.
Can anyone help me figure out the steps to troubleshoot this? I really have tried very hard.
Thx
mos
Comments
Did you run the update script?
Each drupal version has an update script. In the old (pre-4.7) days, you had to log in as user #1, and then run "update.php" in the browser. Today, Drupal does this in a more automated way. You go to the administer/modules section, and click the "update" link (at the top), and then follow the on-screen instructions.
You want to do this once each time you update drupal itself, and then add your modules back in and turn them on and do update again, this time NOT updating drupal core, but updating each module Drupal says you need to update. The on-screen instructions should explain it as you go.
When you do the update if there are any problems you should see error messages, and then you'll know that it is a DB issue. If there are no error messages then you should be good to go.
The behavior can be very bizzare if you try to use Drupal without running the update script. The update script is basically re-configuring your SQL tables so they "look right" for the current version of Drupal.
SV
Can't get in to run it!
Hey Steve, thanks so much for your reply....
Here is what I did:
1. I logged in as user1 and disabled all contrib modules and custom themes till I was back to just core.
2. In the shell I renamed the new drupal 4.7 folder to replace the old one, which is now called drupal_backup , so the entire file system was replaced with the new 4.7 one.
3. I moved over the settings.php file. (Also tried recreating it based on 4.7's default)
4. I moved over the files and themes dirs (we run a multi-site install).
5. I tried going to update.php, and was told I wan't able to connect to the DB.
6. I checked, rechecked and rerererechecked the settings.php and am positive all is well.
I also watched the video on upgrading about ten times and did not miss a step, up until I actually get to run update.php, that is!
I switched back to 4.6.5 and do not see a link on the administer > modules page to update stuff, however I do have access to the update.php page. Do you think I could try to run update.php? I am not sure that it would do anything, since everything is already up to date for 4.6.5. I am expecting a few of the contrib ones to break once I make it to 4.7 , and at the moment anything that was not included in core is still disabled.
So I guess the whole problem is, I can't get to the update script until I can connect to the database! I am boggled, and am waiting for my sys-admin to get back to me with what versions of Apache, PHP and SQL we run, maybe that info will help. Do you think that might be the problem?
Take good care, thanks so much
mos
Somehow
Somehow, you need to get 4.7's update.php script to work. I'm not sure why you can't connect to the DB. I'm afraid I'm not very knowledgeable about SQL. Mine so far has "just worked", so perhaps I have been lucky.
I do think you need to backup your site and then delete everything in the main directory where Drupal is installed. If you have proprietary folders (not part of the drupal distribution), say, a "myfiles" directory, those can stay. But otherwise, all the main Drupal folders and all the files in the root of your durpal drectory need to be deleted completely, and then 4.7.0 uploaded. Tons of people have reported trouble just trying to "over-write" 4.6.x with 4.7 -- it doesn't generally work.
Once you have a totally clean, new install (with the old SQL sitting there), and settings.php is configured right, you should be OK to run the update script from the admin/modules page.
If you still can't get to the DB, double-check the SQL line in the settings.php file. It needs to have the right database name, address, and password in there. If it doesn't drupal will not be able to read your SQL files. If that is right and you have an otherwise clean in stall then... I am stumped.
Not sure if this helps... but I'm about at the limit of what I know here.
No cigar!
Hey Steven
Thanks again. Yes, I have done all of the above numerous times since May 1st. I am pretty stumped too, it really makes no sense, especially since the settings.php file remains the same, and works with my old Drupal install perfectly.
If anyone else has any suggestions, I could really really really use some help. I need 4.7 in order to get the site working in such a way that I can have a summer student add content. She starts in a week and I still haven't been able to get in there and see which modules are broken.
Has this happened to anyone else and not had something to do with a bad password/username, etc?
Could it be a compatibility problem on my service provider's end?
Thanks again!
*sticking to Drupal despite weeks of near tears*
mosa
Troubleshooting.
I switched back to the old version again and intentionally broke the settings.php file by screwing up the password/user/dbname (troubleshooting), and the error is different -- it is a one liner:
Access denied for user '****'@'localhost' (using password: YES), the usual errors.
The error I get after trying to upgrade is complete with the drupal logo and a lot more text, and specifically says I cannot connect to the database.
Is there soemthing additional to do for multi-site drupals?
Okay, that's about every avenue I can think of. The server's software is totally compatible. What else?
mmmosa
crazy upgrade magik
i'm a friend of mosa's. mosa gave me the login creds and i went in to take a look. crazy mad shit is happening there. i tried everything i could think of and ended up with the same results.
i saw the site working with the 4.6 code. i backed up the 4.6 codebase, downloaded a new 4.7 tarball, and unpacked it. i used the 4.6 settings file and got the same erorr. can't connect to database. drupal can obviously see the settings file because it displays the username and db name on the error page.
the *only* longshot i could think of is that 4.7 handles passwords differently than 4.6. the password has a "+" in it.
good luck mosa. i hope the drupal community can pull together to help you with this one.
Going to try the password suggestion
Ah, thnx elraun.
At least now i know i have not been GOING TOTALLY NUTS these last few weeks. I emailed the sys-admin to change my db password to something sans-special-characters, we'll see, i'll post the solution if there ever is one, other than to wait till version four point seven point one. thank you soooooo much for looking at it, i really couldn't make any sense of this problem.
I hope this bad com-pu-tor magik doesn't mean i am cursed by Drupal forever.
If this password change does not work, we have exhausted every possible avenue of repair on our end. What I am hoping is that there is someone out there who may see some sort of link to some server setting i can ask my sys-admin to change. It seems like this problem must be a server problem, we really have been very thorough with this upgrade.
xos mos
FInally
Hey all,
I just wanted to post the follow up to this, in case anyone else has the same thing happen. I had my sys-admin change my SQL password, which originally contained the '+' symbol. I was able to connect to the database after this special character was removed.
I can't explain why, I don't know enough, just that it allowed me to connect!! :-)
It's all working password-wise, but there are so many interesting failed upgrades.... wish me luck.
Good luck and thanks to anyone who mulled this over for awhile.
drupalcore.
mos
Server Specs
We are running:
PHP Version 4.3.9
Apache 2.0
MySQL 4.1.12
and I am trying to upgrade from 4.6.5 to 4.7....
plspls if there's a gosh i need to figure this out!
mos
My password is normal but still same problem
I am having the exact same problems and my db password does not have any special characters. Any more ideas on what to try?