XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Modules Support forums / 
  3. Module usage questions 
  4.  / Got error 134 from storage engine
Register
1
Northern
Got error 134 from storage engine

  • 2007/4/18 6:14

  • Northern

  • Just can't stay away

  • Posts: 420

  • Since: 2004/12/26


Heres the down low.

when any member goes to post a reply or make a new topic, they cant, all they get is a white page.
but the rest of the CBB works.

In admin, if you refresh the CBB, you get this
( Got error 134 from storage engine )
in a red banner before anything else


I had the server updated to
PHP 5 and SQL 5
Xoops version 2.0.16
CBB version 3.07

any ideas?

Thanks,
Marc
2
Northern
Re: Got error 134 from storage engine

  • 2007/4/18 17:55

  • Northern

  • Just can't stay away

  • Posts: 420

  • Since: 2004/12/26


Bump!
3
wizanda
Re: Got error 134 from storage engine

  • 2007/4/18 18:00

  • wizanda

  • Home away from home

  • Posts: 1585

  • Since: 2004/3/21


Try switching off Censor words, if you have a long list and see if that helps, as i just found is a cause of this.
MySql has a 30 second standard process limit, the censor words alone switched off, fixed it.
4
Northern
Re: Got error 134 from storage engine

  • 2007/4/21 18:42

  • Northern

  • Just can't stay away

  • Posts: 420

  • Since: 2004/12/26


nope, didnt work. any other suggestions?
5
vaughan
Re: Got error 134 from storage engine

  • 2007/4/21 18:47

  • vaughan

  • Friend of XOOPS

  • Posts: 680

  • Since: 2005/11/26


this message can appear if MySQL can't write to the tmp folder (defined in the MySQL config files on the server).

also tho i'm not sure, have you checked the DB using phpmyadmin and if possible run a repair query on the CBB tables.
6
Northern
Re: Got error 134 from storage engine

  • 2007/4/21 19:09

  • Northern

  • Just can't stay away

  • Posts: 420

  • Since: 2004/12/26


The check db give me this.

Problems with indexes of table `xoops_bb_posts`
More than one INDEX key was created for column `forum_id`
More than one INDEX key was created for column `topic_id`

Problems with indexes of table `xoops_bb_topics`
PRIMARY and INDEX keys should not both be set for column `topic_id`

and the repair sats, every thing is OK

now the CBB db works purfictly in a 4 on 4 server.
but onece on a 5 on 5 server, it acts up.

but I have another site that has the same version of XOOPS and same version of cbb, but tailing bhind in posts and topics, it was moved to the 5 on 5 server, and its not having any problem.
7
vaughan
Re: Got error 134 from storage engine

  • 2007/4/21 19:20

  • vaughan

  • Friend of XOOPS

  • Posts: 680

  • Since: 2005/11/26


ok looks like you have a primary key thats identical to an index key, which is pointless.

remove the index key for topic_id in table xoops_bb_topics

and then in bb_posts set only 1 index key for topic_id and only 1 key for forum_id

(maybe set topic_id as primary key & forum_id as index)

i'm no expert tho
8
Northern
Re: Got error 134 from storage engine

  • 2007/4/21 19:37

  • Northern

  • Just can't stay away

  • Posts: 420

  • Since: 2004/12/26


I know very little on SQL
just enuff to know how to make a db and to import files.
well mabe a tad bit more, but mot much.

as for what you said..

?
9
xgarb
Re: Got error 134 from storage engine

  • 2007/7/21 13:28

  • xgarb

  • Not too shy to talk

  • Posts: 154

  • Since: 2003/3/30


I don't really get this either.

CBB installer has

KEY `uid` (`uid`),
  KEY `pid` (`pid`),
  KEY `forum_id` (`forum_id`),
  KEY `topic_id` (`topic_id`),
  KEY `subject` (`subject`(40)),
  KEY `forumid_uid` (`forum_id`,`uid`),
  KEY `topicid_uid` (`topic_id`,`uid`),
  KEY `post_time` (`post_time`),
  KEY `topicid_postid_pid` (`topic_id`,`post_id`,`pid`),


for bb_posts table.

But phpMyadmin/mysql complains about..

More than one INDEX key was created for column `forum_id`
More than one INDEX key was created for column `topic_id`

I found this article that explains indexeshttp://www.databasejournal.com/features/mysql/article.php/1382791 (basically an index is literally that.. it speeds up queries) but which index is best to delete in the bb_posts table?
10
xgarb
Re: Got error 134 from storage engine

  • 2007/7/21 13:34

  • xgarb

  • Not too shy to talk

  • Posts: 154

  • Since: 2003/3/30


ok, found some more info Quote:
Consider column cardinality. The cardinality of a column is the number of distinct values that it contains. For example, a column that contains the values 1, 3, 7, 4, 7, and 3 has a cardinality of four. Indexes work best for columns that have a high cardinality relative to the number of rows in the table (that is, columns that have many unique values and few duplicates). If a column contains many different age values, an index will differentiate rows readily. An index will not help for a column that is used to record sex and contains only the two values 'M' and 'F'. If the values occur about equally, you'll get about half of the rows whichever value you search for.
from..http://www.informit.com/articles/article.asp?p=377652&rl=1

so basically look for the keys with the lowest cardinality value and remove those.
(1) 2 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

179 user(s) are online (121 user(s) are browsing Support Forums)

Members: 0

Guests: 179

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