31
tedsmith
Re: Admin login problem
  • 2004/9/30 8:12

  • tedsmith

  • Home away from home

  • Posts: 1151

  • Since: 2004/6/2 1


Checked permissions (again). No joy.

I just noticed this thread too. How many people are that have this problem?

I posted here http://www.iis-resources.com/modules/newbb/viewtopic.php?forum=20&post_id=10286&topic_id=2121 and they said that this is a known bug? Any fixes created yet?

I've also just found this thread

https://xoops.org/modules/newbb/viewtopic.php?topic_id=24864&forum=7 where its happended to others. They refer to clearing the sql database tables somehow but don't give instruction on how. I cannot get phpMyAdmin to function (I had the XOOPS module but cannot access that now) for some reason - it never worked for me even though the XOOPS module did. I just kept getting the 'No Input File Specified' error.

How can I do these MySQL flushes using command lines?

Thanks

Ted

32
wolvy
Re: Admin login problem
  • 2004/9/30 8:46

  • wolvy

  • Just popping in

  • Posts: 11

  • Since: 2004/9/23


Ted,

i'm no MySQL expert but if you just want to empty a whole table then the command would be : delete from table-name; (in your case fill in the right table-name whatever the table name is in your case)


that is when you can connect locally to the mysql.
careful the table is then totally empty so make sure you don't need any info in it.

33
tedsmith
Re: Admin login problem
  • 2004/9/30 8:51

  • tedsmith

  • Home away from home

  • Posts: 1151

  • Since: 2004/6/2 1


Thanks Wolvy.

I will try that if I need to, but I have got the latest version of phpMyAdmin to work!! Hooray.

Anyway, I have looked at the xoops_session table and it says 'in use' and you can't do anything with it. If you click on it, it says 'Error 1016 - cannot open file 'xoops_session.myi' (Error 145). Does that mean anything to anyone? Using phpMyAdmin how can I flush this table, or create a new version of it?

34
tedsmith
Re: Admin login problem
  • 2004/9/30 9:26

  • tedsmith

  • Home away from home

  • Posts: 1151

  • Since: 2004/6/2 1


Ok, i fixed it. If you are reading this then there's a possiblity its because you are having the same problem. To FIX IT DO THE FOLLOWING:

If you have phpMyAdmin working, select your database from the list, and scroll down the list of tables that you get. Tick the 'xoops_session' table, which, if it is the cause (which it is likley to be IF YOU HAVE TRIED ALL THE OTHER TIPS ABOVE WITHOUT SUCCESS) will say 'in use' in the status. Once its ticked, scroll down to the bottom and there's a little drop down menu. Click it, and select 'Empty' and click OK\Submit. It will check that you are sure that you want to empty the table. Say yes and it will clear it for you.

Then go back and try to logon. With me, its worked. So in my case it was not to do with cookies, permissions, firewalls, php or IIS, but a MySQL table. Thanks to everyone who has taken the time to help me with this - I really appreciate the time of all of you.

Perhaps this 'tip' or 'fix' could be made official so that it is well know. I have found a dozen or more people who have encountered this problem. For some, the earlier issues fixed it. Perhaps they should all be compiled together as a troubleshooting guide.

Bye the way - the creators of phpMyAdmin are gods!

Thanks again.

Ted

35
Dave_L
Re: Admin login problem
  • 2004/9/30 9:29

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


Error 145 is usually resolved by repairing the table. You can do the query "REPAIR TABLE xoops_session", or use phpMyAdmin's menu function for repairing the table.

Are you still getting those test failures from Browser Check, with Browser Check installed under your XOOPS directory? The Referrer-HSQ failure might not matter as long as the other two referrer checks pass, since that may be adequate for Xoops. I don't think XOOPS handles cookies with Javascript, so that test probably doesn't matter either. But the HTTP cookie test failure is likely to be a problem.

36
tedsmith
Re: Admin login problem
  • 2004/9/30 9:55

  • tedsmith

  • Home away from home

  • Posts: 1151

  • Since: 2004/6/2 1


Yes, still get the 3 errors. It isn't stopping us using the site though? Is that a little odd? Any tips for correcting this would be appreciated (except for the Enable Cookies one which I have done).

37
winnesoup
Re: Admin login problem // xoops_session table "in use"
  • 2004/11/7 13:20

  • winnesoup

  • Just popping in

  • Posts: 29

  • Since: 2004/10/15


tedsmith was right. I had the same problem at my site. PHPmyadmin showed that the xoops_session table was "in use". Repairing it solved my problem!!

Hail Tedsmith

38
tedsmith
Re: Admin login problem // xoops_session table "in use"
  • 2004/11/7 21:33

  • tedsmith

  • Home away from home

  • Posts: 1151

  • Since: 2004/6/2 1


No need to hail me - I just documented what others perhaps did not have the time to do, but being a regular user of these forums for answers, I thought it best to ensure others will have the answer. Its not fair to take without giving back.

I'd love to know what causes this because I am inheritantly nosey and love to know why things are the way they are as opposed to just accepting them. Does anyone know - one of you MySQL gurus perhaps why this particular table gets in a state? Its clearly a common problem.

39
Dave_L
Re: Admin login problem // xoops_session table "in use"
  • 2004/11/7 22:21

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


I don't have the answer, but I'm curious about it too. I don't think it's Xoops-specific. I've seen the same problem occur with a different web application, in which a very frequently updated MySQL table gets "broken" often, and has to be emptied or repaired.

One brute force solution could be to add some code that periodically checks the problem tables, and automatically repairs them if needed.

40
winnesoup
Re: Admin login problem // xoops_session table "in use"
  • 2004/11/8 21:20

  • winnesoup

  • Just popping in

  • Posts: 29

  • Since: 2004/10/15


ok Ted, no hailing then. I stick to thanx, ok ?

Maybe the following helps.

Phpmyadmin showed that the number of entries was corrected from 8 to 5 when repairing the xoops_session table. My guess is that it is something to do with MySQL and then probably in a ISP hosted environment. Offered MySQL functionalities often reside at servers that do not have, as you may call it, a well balanced load.
Having 8 entries corrected back to 5 and a myi file "in use" gives me ideas of "not completed" write actions etc.

But I also think we should jump out of this thread in case we might discuss this thing out.

Again thnx. I got my site up and running.

Login

Who's Online

329 user(s) are online (118 user(s) are browsing Support Forums)


Members: 0


Guests: 329


more...

Donat-O-Meter

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

Latest GitHub Commits