1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Weird things with MySQL

Discussion in 'Plesk for Linux - 8.x and Older' started by PedstersPlanet, Jan 10, 2006.

  1. PedstersPlanet

    PedstersPlanet Guest

    O/S: Linux 2.4.20-021stab028.18.777-enterprise - Fedora
    CPU: GenuineIntel, Intel(R) Xeon(TM) CPU 2.80GHz
    MySQL: MySQL 3.23.58

    I doubt it's anything to do with Plesk, but I'm pulling my hair out here..... I hope I can find a solution to this..... I have one on these VPS with Plesk 7.5.4 from a hosting company. I have this serious problem concerning MySQL.... It keeps crashing, or just gives up.

    This is a bit of the log:

    Ok, I added:

    to my.cnf, ok, great......... However, it still crashes (without the innodb advice), and the error log doesnt give me a reason as to why it crashed/stopped:

    ..... It crashed 3 times in a space of 24 hours today........ This problem has just appeared (from early December 05), and my hosting support isnt giving me any useful advice, and this problem is affecting my web site(s)......

    Anyone have any ideas?

    Okay. I have a table of 128meg..but that shouldnt make a difference... MySQL is capable of huge tables, no?.. and seeing the log doesn't give me a reason to the crash, let alone which database, how am I supposed to identify the problem? The blind leading the blind here.....

    Totally stupid......

    UPDATE: It looks like its a problem with huge tables/databases, as when I REPAIR TABLE tbl_name EXTENDED, mysql crashed.... am trying it in shell now..REPAIR TABLE tbl_name EXTENDED.... <whistle.. whistle.. whistle..>..... <8 minutes later>.. Table OK.. CHECK TABLE tbl_name.....<1 second later>....Table OK.....

    Ok, lets try a search in my search engine (beta) for games:
    Fast, but a bit too slow? However, a week ago it was 12.xxx seconds lol.... Not good at all.. So I'm wondering if my problem is with HUGE tables? If so, I can kiss my search engine bye! :( and its only indexed 25,312 pages :(.....
    Search Engine Database stats: total number of records in its database is 26,100 - with a total size of 94.4mb (decreased in REPAIR)...

    If this is the case, then my Directory will suffer too, as the site count is only 31,687 (but a lot pending) - and total number of records in its database is 124,550 - with a total size of 12.4mb... Its ok for now, but in the future?

    So, is my theory with the big databases valid or flawed?
  2. PedstersPlanet

    PedstersPlanet Guest

    It crashed again:

    It doesnt even say why it ends.. also, why does MySQL restart, or is this normal?

    Looks like my research isnt the cause, as 1. from october to the end of november, it was running smoothly; and 2. I have not added any scripts from then.

    So, there must be something wrong with the InnoDB - which is very odd as my databases are all MyISAM's, so, what gives? Does Plsk use InnoDB's?
  3. Cron0

    Cron0 Guest

    I have the same EXACT problem here with my server.

    Any clues?

  4. gonzalo

    gonzalo Guest

    Please i have the same problem. How do you solved it?

    Thanks in advance
  5. Fury

    Fury Guest

    I am having the same problems, ever since I upgraded the Virtuozzo kernel of the hostmachine from 2.4.20-021stab028.24.777-enterprise to 2.6.8-022stab078.9-enterprise.

    Under the 2.4 kernel this VPS has been stable for more than half a year.

    I just tried giving the VPS more memory, let's hope that solves the problem. (Otherwise I am going back to 2.4)