11
dplittle
Re: Broken log in for 2.0.14 Site
  • 2009/11/19 20:31

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Quote:

wcrwcr wrote:
Did you try a complete DB repair?
The typo you are talking aboiut is almost due to a db corruption (eg. XOOPS users)


Is this something I can do outside the XOOPS interface? I can't log into XOOPS at all so it would have to be an external executable script/etc.

12
wcrwcr
Re: Broken log in for 2.0.14 Site
  • 2009/11/19 20:53

  • wcrwcr

  • Home away from home

  • Posts: 1114

  • Since: 2003/12/12


Sorry, Yep

Go to your host´s control panel and look for Databases > phpMyAdmin (or any other app that controls you DB).

Click on it and once in the app look for your XOOPS db. Click on it, scroll down and look for a checkbox named "check all", clickon it look at your right and you´ll find a drop down menu with some functions. Find the ones labled "repair tables" and "otmize table".

I hope it helps

BTW . if you´re still usaing XOOPS 2014 look for a nice and old module "DBtools" It´s pretty handy once you logged.

13
dplittle
Re: Broken log in for 2.0.14 Site
  • 2009/11/19 22:15

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


So here's a little more info ... I went out to phpMyAdmin to disable the modules and see several tables listed as "in use".

xoops_online
xoops_priv_msgs
xoops_session
xoops_xoopsheadline

If I try and get info on these the error message given is

#1016 - Can't open file: 'xoops_online.MYI'. (errno: 130)

I found this file ...

http://dev.mysql.com/doc/refman/5.0/en/myisam-repair.html

and am going to run through the steps there but could this be the problem?

14
dplittle
Re: Broken log in for 2.0.14 Site
  • 2009/11/19 22:42

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Eureka! I was at least able to log back in after I dropped the session table and recreated it!

Does anyone know what these other tables are for?

online
priv_msgs
xoopsheadline

I can guess and I'm thinking I'll just lose saved private messages but I'm a little worried about the xoopsheadline table since I do use that module.

Since it looks like the tables were corrupt I'm guessing I''m not getting data from them now anyway. Think I can just go ahead and recreate the others and see what happens? Any other suggestions?

15
dplittle
Re: Broken log in for 2.0.14 Site
  • 2009/11/19 22:57

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


I am completely back!

I recreated the tables that were having problems and restored data from older backups. The only thing I lost was stored private messages and we don't use thee much anyway!!

Thanks for all the help. Now I can move on to upgrading.

David

Login

Who's Online

189 user(s) are online (134 user(s) are browsing Support Forums)


Members: 0


Guests: 189


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits