MySQL error 1030: Got error 134 from storage engine

[cbvillegas]

Hello

Tonight I tried to login in my administrative user and I recived this error

Query Failed:SELECT tracker.* from tracker WHERE user_id='max_id' ORDER BY id DESC LIMIT 0,10::MySQL error 1030: Got error 134 from storage engine


I have looked over in internet and I can not find an answer that explains what to do.

Can any one help !!! I am really desperate, I have being trying to convince my people to use de system and now that they are happy with it I have this error. Sorry to sound so tragic but I have an audit next week and all the information is on sugar and I do not know what to do.

Clara

Tecnical data

» Operating system type and version Linux 10.1
» Sugar Suite version 4.??? before the upgrade 4.5 o 4.3)
» Webserver type and version Apache
» PHP version phpMyAdmin - 2.8.1
» MySQL server version MySQL - 4.1.13

[cbvillegas]

It looks like I have repared the problem. I use the repair option in phpmyadmin in tracker database.

In any case, i would like to know what happend so the error will not happend again.

clara

[cbvillegas]

The sugar is working with other undesirable consequences:
- every time some users login the system asks for the date and time

Query Failed:INSERT into user_preferences set id='595a870e-4772-01db-0fb4-46c85d71585f', category='global', deleted='0', date_entered='2007-08-19 15:09:06', date_modified='2007-08-19 15:09:06', assigned_user_id='max_id', contents='YToyOntzOjg6InRpbWV6b25lIjtzOjE0OiJBbWVy aWNhL0JvZ290YSI7czoyOiJ1dCI7aToxO30='::MySQL error 1016: Can't open file: 'user_preferences.MYI' (errno: 145)

- I can not modify the dashlets


Fatal error: main() [function.require]: Failed opening required '' (include_path='./:/srv/www/vhosts/prueba.enlaceconsultores.com.co/sugarcrm/include/utils') in /srv/www/vhosts/www.enlaceconsultores.com.co/sugarcrm/modules/Home/DisplayDashlet.php on line 30

Can any one help?

Clara

[cbvillegas]

A new report.

In this link

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

I found how to check and fix databases. I run the command an repair more databases. All the error stoped.

Clara

[SteeLx]

It looks like I have repared the problem. I use the repair option in phpmyadmin in tracker database.

In any case, i would like to know what happend so the error will not happend again.

clara

yes, the REPAIR option in phpMyadmin helped me too today.

I too got same error & it worked.


can any1 tell me why this erorr accrued.