The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

innodb has alot of problem

Discussion in 'Database Discussions' started by josh123456, Sep 25, 2012.

  1. josh123456

    josh123456 Member

    Joined:
    Jun 19, 2010
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    hello
    i have 8 cpanel server and i upgraded mysql from MySQL Upgrade in whm in my all server at tonight
    after upgrade i can not give any backup on my cpanel servers and i get bellow error and backups going fail :
    please help me for solve this dangerous event

    for example :
    Code:
    /scripts/pkgacct hdhopir
    
    warn [pkgacct] hdshopir_allgraphicd: mysqldump failed -- database may be corrupt
    (57795 bytes) warn [pkgacct] Failed to dump database hdshopir_allgraphicd
    horde.turba_objectswarn [pkgacct] horde.turba_objects: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    horde.turba_objects
    note     : The storage engine for the table doesn't support repair
    warn [pkgacct] horde.turba_objects: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    warn [pkgacct] horde: mysqldump failed -- database may be corrupt
    (1163 bytes) warn [pkgacct] Failed to dump database horde
    horde.horde_prefswarn [pkgacct] horde.horde_prefs: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    horde.horde_prefs
    note     : The storage engine for the table doesn't support repair
    warn [pkgacct] horde.horde_prefs: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    warn [pkgacct] horde: mysqldump failed -- database may be corrupt
    (1155 bytes) warn [pkgacct] Failed to dump database horde
    horde.kronolith_shareswarn [pkgacct] horde.kronolith_shares: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    horde.kronolith_shares
    note     : The storage engine for the table doesn't support repair
    warn [pkgacct] horde.kronolith_shares: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    warn [pkgacct] horde: mysqldump failed -- database may be corrupt
    (1181 bytes) warn [pkgacct] Failed to dump database horde
    horde.kronolith_storagewarn [pkgacct] horde.kronolith_storage: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    horde.kronolith_storage
    note     : The storage engine for the table doesn't support repair
    warn [pkgacct] horde.kronolith_storage: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    warn [pkgacct] horde: mysqldump failed -- database may be corrupt
    (1181 bytes) warn [pkgacct] Failed to dump database horde
    horde.mnemo_memoswarn [pkgacct] horde.mnemo_memos: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    horde.mnemo_memos
    note     : The storage engine for the table doesn't support repair
    warn [pkgacct] horde.mnemo_memos: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    warn [pkgacct] horde: mysqldump failed -- database may be corrupt
    (1159 bytes) warn [pkgacct] Failed to dump database horde
    horde.nag_taskswarn [pkgacct] horde.nag_tasks: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    horde.nag_tasks
    note     : The storage engine for the table doesn't support repair
    warn [pkgacct] horde.nag_tasks: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'horde'': Cannot load from mysql.proc. The table is probably corrupted (1548)
    
    warn [pkgacct] horde: mysqldump failed -- database may be corrupt
    (1151 bytes) warn [pkgacct] Failed to dump database horde
    
    ERROR: Failed to dump one or more databases
    ...Done
     
  2. josh123456

    josh123456 Member

    Joined:
    Jun 19, 2010
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    i skipped hord in
    skiphorde=1 in /var/cpanel/cpanel.config (WHM > Tweak Settings file)

    but pkgacct still try to give backup from horde
     
    #2 josh123456, Sep 25, 2012
    Last edited: Sep 25, 2012
  3. acenetgeorge

    acenetgeorge Well-Known Member
    PartnerNOC

    Joined:
    Mar 6, 2008
    Messages:
    64
    Likes Received:
    2
    Trophy Points:
    8
    Location:
    Southfield, MI
    cPanel Access Level:
    DataCenter Provider
    Try running this command:

    /scripts/fullhordereset

    That will drop the existing horde database, and rebuild it. Then see if you can manually package that account. I think that should resolve it.

    Horde is still installed, even if it is disabled.
     
  4. josh123456

    josh123456 Member

    Joined:
    Jun 19, 2010
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    thanks for your reply
    i runned bellow commands
    /scripts/fullhordereset
    /usr/local/cpanel/bin/update-horde –-force

    horde database successfuly droped and inserted again without any problem
    but The problem is not solved

    also mysql is not stable
    when i start mysql it work for For a short time and then going down
    this is last error log :

    Code:
    120925 11:51:53 mysqld_safe mysqld from pid file /var/lib/mysql/server24.mylittledatacenter.com.pid ended
    120925 11:51:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    120925 11:51:54 [Note] Plugin 'FEDERATED' is disabled.
    120925 11:51:54 InnoDB: The InnoDB memory heap is disabled
    120925 11:51:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    120925 11:51:54 InnoDB: Compressed tables use zlib 1.2.3
    120925 11:51:54 InnoDB: Using Linux native AIO
    120925 11:51:54 InnoDB: Initializing buffer pool, size = 128.0M
    120925 11:51:54 InnoDB: Completed initialization of buffer pool
    120925 11:51:54 InnoDB: highest supported file format is Barracuda.
    120925 11:51:54  InnoDB: Waiting for the background threads to start
    120925 11:51:55 InnoDB: 1.1.8 started; log sequence number 1784839288
    120925 11:51:55 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
    120925 11:51:55 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
    120925 11:51:55 [Note] Server socket created on IP: '0.0.0.0'.
    120925 11:51:55 [Note] Event Scheduler: Loaded 0 events
    120925 11:51:55 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.25-cll'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
    120925 11:59:38 [ERROR] Incorrect definition of table mysql.proc: expected column 'comment' at position 15 to have type text, found type char(64).
    120925 12:03:17 [ERROR] /usr/sbin/mysqld: Can't open file: './namakpas_wordp/wp_term_taxonomy.frm' (errno: 24)
    120925 12:03:17 [ERROR] /usr/sbin/mysqld: Sort aborted: Out of resources when opening file './bardiyab_bux/xeon_forum_topics.MYD' (Errcode: 24)
    120925 12:03:17 [ERROR] /usr/sbin/mysqld: Can't open file: './behroozd_YAS/wp_statistics_date.frm' (errno: 24)
    120925 12:03:17 [ERROR] /usr/sbin/mysqld: Sort aborted: Out of resources when opening file './baranpic_nuke/nuke_bbtopics.MYD' (Errcode: 24)
    (errno: 24)
    120925 12:04:28 [ERROR] /usr/sbin/mysqld: Can't open file: './baranpic_nuke
    120925 12:05:50 [ERROR] /usr/sbin/mysqld: Can't open file: './asangame_asangame/wps8Bh6IQrHS_options.frm' (errno: 24)
    120925 12:09:29 [ERROR] /usr/sbin/mysqld: Can't open file: './eximstats/sends.frm' (errno: 24)
    120925 12:09:35 [Note] /usr/sbin/mysqld: Normal shutdown
    
    120925 12:09:35 [Note] Event Scheduler: Purging the queue. 0 events
    120925 12:09:37  InnoDB: Starting shutdown...
    120925 12:09:39  InnoDB: Shutdown completed; log sequence number 1785293560
    120925 12:09:39 [Note] /usr/sbin/mysqld: Shutdown complete
    
    ended
    120925 17:51:16 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    120925 17:51:16 [Note] Plugin 'FEDERATED' is disabled.
    120925 17:51:16 InnoDB: The InnoDB memory heap is disabled
    120925 17:51:16 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    120925 17:51:16 InnoDB: Compressed tables use zlib 1.2.3
    120925 17:51:16 InnoDB: Using Linux native AIO
    120925 17:51:16 InnoDB: Initializing buffer pool, size = 128.0M
    120925 17:51:16 InnoDB: Completed initialization of buffer pool
    120925 17:51:16 InnoDB: highest supported file format is Barracuda.
    120925 17:51:16  InnoDB: Waiting for the background threads to start
    120925 17:51:17 InnoDB: 1.1.8 started; log sequence number 1822574935
    120925 17:51:17 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
    120925 17:51:17 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
    120925 17:51:17 [Note] Server socket created on IP: '0.0.0.0'.
    120925 17:51:17 [Note] Event Scheduler: Loaded 0 events
    120925 17:51:17 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.25-cll'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
    120925 17:53:39 [ERROR] Incorrect definition of table mysql.proc: expected column 'comment' at position 15 to have type text, found type char(64).
     
    #4 josh123456, Sep 25, 2012
    Last edited: Sep 25, 2012
  5. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    14,451
    Likes Received:
    195
    Trophy Points:
    63
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
  6. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    If you search for that error online, you'll find the following discussion:

    MySQL :: Incorrect definition of table mysql.proc:

    Most of that thread discusses using mysql_upgrade to correct the issue:

    Code:
    mysql_upgrade
    If that doesn't work, try using the --force flag with it:

    Code:
    mysql_upgrade --force
    If that also doesn't work, then yes, please submit a ticket and post the ticket number here. Of note, this is not a bug if you are having an upgrade error. Horde itself backing up when skipped is already an internal case (58112), and the mysql.proc error is a different issue entirely.
     
Loading...

Share This Page