1
rabideau
CBB 3.08 Timeout problem &Got error 134 from table handler
  • 2007/3/5 19:39

  • rabideau

  • Home away from home

  • Posts: 1042

  • Since: 2003/4/25


I am unable to get a CBB 3.08 operating correctly my site is running using:

XOOPS 2.0.16
php 4
MySQL 4.1.10

Debug does not seem to yield any useful information. What we get is random timeout errors when someone attempts to post. I have cleared cache; removed all time limits from cbb; reinstalled Frameworks, Class and the module three times.

Any ideas out there???
Pax vobiscum,
...mark

may the road rise to meet your feet!

http://treemagic.org

2
wizanda
Re: CBB 3.08 Timeout problem &Got error 134 from table handler
  • 2007/3/5 21:53

  • wizanda

  • Home away from home

  • Posts: 1585

  • Since: 2004/3/21


Yes its the MySql indexing of it, i have rebuilt ours very much.....there are many index's not need and some that are extra.

3
rabideau
Re: CBB 3.08 Timeout problem &Got error 134 from table handler
  • 2007/3/5 22:22

  • rabideau

  • Home away from home

  • Posts: 1042

  • Since: 2003/4/25


So what do I do then Wizanda???
Pax vobiscum,
...mark

may the road rise to meet your feet!

http://treemagic.org

4
wizanda
Re: CBB 3.08 Timeout problem &Got error 134 from table handler
  • 2007/3/5 22:50

  • wizanda

  • Home away from home

  • Posts: 1585

  • Since: 2004/3/21


Question is what do we do , overall XOOPS its self, needs many fixes in MySQL indexing, these can vastly improve XOOPS speed overall......
An index in any MySql entry can be replaced and added to when live, it's what i have been doing allot lately checking and changing Mysql, to find what it needs to run XOOPS faster........
Now just need to know how to share this information, for feed back......there is a bit in dev forum on here...

5
wuddel
Re: CBB 3.08 Timeout problem &Got error 134 from table handler
  • 2007/3/6 5:42

  • wuddel

  • Just popping in

  • Posts: 71

  • Since: 2005/9/13


Look here and here

Quote:

By: phppp ( D. J. )
ReplyRE: CBB 3.08 and Frameworks 1.10 error on upg [ Reply ]
2007-01-11 10:52
"Got error 134 from storage engine"
-- you can ignore the error. It usually means that the script is trying to remove a non-existing record from database, which makes no harm if the removal is not executed; or it could indicate crash of your database, which obvious not your case.
cu wuddel

[size=x-small]sorry about my sh** english [/size]

6
Anonymous
Re: CBB 3.08 Timeout problem &Got error 134 from table handler
  • 2007/4/29 17:36

  • Anonymous

  • Posts: 0

  • Since:


Any solution for this problem ?

Login

Who's Online

239 user(s) are online (138 user(s) are browsing Support Forums)


Members: 0


Guests: 239


more...

Donat-O-Meter

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

Latest GitHub Commits