By Sunshiney on
My computer crashed -- BSOD/kernel error. Anyway, got that taken care of and when I returned to my locally hosted dev site, I can no longer log-in as user1. I tested an additional user I had created; can't log-in either. It's been working fine for five months; never had this happen. I don't know what to do.
My set-up:
-
Drupal 6x with clean urls enabled
Using theme I created for site; using Garland for admin theme
pathauto, cck, views, datefield, aggregator installed
What happens:
1. I type username/pwd into log-in supplied in content area when I browser to http://domain/user
2. After submitting, the username becomes red and the box after username has a red outline Nothing more happens
Also, the log-in is on my custom theme.
Sooo, now what? Anybody know what to do next, how to solve?
Comments
Additional info: I added
Additional info: I added this line: $conf['theme_default'] = 'garland'; to my settings.php file to override the custom theme. Garland has been my admin theme, as I said in my prior post. So, now when I log-in as admin, I get the message: Sorry, unrecognized username or password. Have you forgotten your password?
I haven't changed my admin login name or password. And, I've stored it in two places so I know it's accurate.
Before the computer crashed, I had no log-in problems.
I can open phpmyadmin but need someone to tell me what to look for in the database. noob.
Running apache2triad on WinXP.
POSTSCRIPT:
I'd like to try to change the password for userid1 by using UPDATE `users` SET pass = MD5('newpwd') WHERE uid=1;
But where do I enter that code in PHPMYADMIN?
You are lucky. Go to your
You are lucky. Go to your drupal db via PMA.
1. Scroll to the end, find check all. From the dropdown menu, Check tables. See what crashed. If all is fine, refresh browser. Try login.
2. If fails, go back, some tables are probably crashed, recheck the tables, now select Repair tables. Try log in. If fails again, I'll have to hear from you first before:)
3. No, j/k, go on. Only if above fails. Open table "users". You see uid: 0, 1. So 0 is anonymous, 1 is admin. Click the pencil (edit button). Change the "pass" row to your password, and pick MD5 under Function.
Update too: paste the code you gave under SQL tabs, there will be a form: Run SQL query/queries on database
Only do the last if the others fail.
love, light n laughter
Ok... I'm doing this now....
Ok... I'm doing this now.... and will report back. Curious though....why not do the password change on user1? I am skipping that step now..based on your advice.
Thanks so much for the
Thanks so much for the hand-holding. I need your hand in mine!! :-))
OK. This is cool. Didn't know I could do what you are teaching me to do.
I did #1. I got:
1. In the table/message text area: I got
water.users check warning Found row where the auto_increment column has the value 0
2. And below the table/message text area, it says the following:
Problems with indexes of table `blocks`
Warning UNIQUE and INDEX keys should not both be set for column `theme`
Problems with indexes of table `filters`
Warning UNIQUE and INDEX keys should not both be set for column `format`
Problems with indexes of table `menu_links`
Warning More than one INDEX key was created for column `menu_name`
Problems with indexes of table `search_index`
Warning UNIQUE and INDEX keys should not both be set for column `word`
Problems with indexes of table `system`
Warning More than one INDEX key was created for column `type`
Problems with indexes of table `term_data`
Warning More than one INDEX key was created for column `vid`
(wierd.... how did this happen, I'm wondering.)
*** So next, I selected repair tables. The result was that every entry said " repair ..... status.... OK"
BUT, after getting excited about that result, I decided to go "back" to the database and do the "Check Tables" once again. I thought everything would be cleared up, but nope, it gives me the identical warnings and water.users message that I wrote about before I did the repair.
????
Now what?
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!
From the last repair, have
From the last repair, have you been able to login? If not, perhaps you should try the last resort and see.
love, light n laughter
6:30 am here...and rushed to
6:30 am here...and rushed to computer to see if I could log in. Used firefox last night and no go. So tried IE, thinking cache. Durn. No, it won't long in.
So, I'll try the last resort. But, first, some questions:
1. What about those warnings? Do I do something with them?
2. Optimize and analyze menu items -- what are they? Should I try 'em?
3. Should i do anything about the row where auto increment is 0? it's in users.
4. "Open table "users". You see uid: 0, 1. So 0 is anonymous, 1 is admin. " ?? Should it actually "say" anonymous? it does say "admin" and I did add one user and it added fine (but no email on local so no pwd).
Back shortly..
YAHOOOOOOOOOOOOOOOOOOOOO!
YAHOOOOOOOOOOOOOOOOOOOOO! Jumping up and down. It worked. It worked! yahhhh.
I did your password change instructions and that did it. :-))
***So, those errors that were under the table.... are they perhaps a result of using garland as admin theme and having a custom theme, too? Should I go ahead and try to fix them?
You made my day.
***But what happen? Why did the pwd get mussed up in the crash?
that's why you are lucky, you
that's why you are lucky, you have PMA to fix things:) I went to terminal with a book on my hand, back then:)
No idea about those warnings, perhaps you can google around. At least no crash or horrible error messages up there. I'm no SQL guy.
Try clearing all cache tables (via drupal is better, use admin_menu.module or devel.module), and then run update.php to let drupal see the left errors as well. Who knows there are some important errors that may trouble your installation. If all is well after update, you are good to go. One of those warnings happened in my installation as well.
love, light n laughter
Ah, now I understand the
Ah, now I understand the "lucky" thing. I thought you might have known intuitively how lucky I really am --- went into casino two days ago and put 20 bucks into machine... pushed once...won 400 dollars..and left. Now that's lucky!
I'm glad, too, for PMA. Just learning how to use it, though...one more thing. I'll do what you've suggested. If there's anything I can do to return the favor (beta testing or marketing advice) don't hesitate to ask.. I owe ya...
No worries. Glad you made it.
No worries. Glad you made it. Helping each other will always make a better community.
love, light n laughter
same problem on drupal 6.13
I had the same problem yesterday. tearing my hair out. i am running a brand new 6.13 install as localhost. I followed the procedure to use PMA to check tables, and found the table drupal_users had the warning about the autoincrement not set correctly. so I repaired it, and after that i could login fine with my admin acocunt drupaluser. fortunately i had no other errors in the check of the tables.
I have a conjecture on where this came from. On the install I set up the drupaluser account using PMA in advance, right after i created the database drupal. then i modified the file to assign the database and user to my drupaluser account, and proceeded to run the install.
the install worked, and the first login worked. but thereafter it did not. this happened before, so I was on my second rebuild of the configuration. Perhaps I should have let the install script create the db and user. i have not looked at the code.
hope this helps someone else. try the PMA repair approach!!!