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.

Restore + MySQL + Horde = Fail :(

Discussion in 'General Discussion' started by Silent Ninja, Oct 2, 2008.

  1. Silent Ninja

    Silent Ninja Well-Known Member

    Joined:
    Apr 18, 2006
    Messages:
    198
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Buenos Aires, Argentina
    Here's the deal. I previously had a Centos 5 server with cpanel, but the rpm database corrupted so I had to do a full restore. Everything went well, but I restored MySQL folder (/var/lib/mysql) and after that realized that the server had MySQL5 and the files where MySQL4.1 based, so I've done a mysqlup force, and it went well.. 500 error, easyapache, and that also went well.

    Everything works.. but the InnoDB tables for horde.
    Horde started failing.
    I've tried to do a fullhordereset and this was the error that showed up:
    Code:
    root@osiris [/sysbk/backup/dirs/dirs]# /scripts/fullhordereset 
    New horde password: [...]
    
    Updating Horde 3.1.7p7
    tar -x -p -z --no-same-owner -f /usr/local/cpanel/src/3rdparty/gpl/horde-3.1.7p7.cpanel.tar.gz -C /usr/local/cpanel/base
    Archiving current Horde data to /var/cpanel/horde/horde.backup.sql.1222964216
    [B]Failed to backup existing Horde DB. DB likely did not exist.[/B]
    Cleaning old Horde data archives
    Skipping /var/cpanel/horde/horde.backup.sql.1222961560 (archived)
    Skipping /var/cpanel/horde/horde.backup.sql.1222757713 (archived)
    Skipping /var/cpanel/horde/horde.backup.sql.1222755841 (archived)
    Skipping /var/cpanel/horde/horde.backup.sql.1222755582 (archived)
    Skipping /var/cpanel/horde/horde.backup.sql.1216579825 (archived)
    Skipping /var/cpanel/horde/horde.backup.sql.1216483366 (archived)
    Creating Horde database
    [B]ERROR 1005 (HY000) at line 166: Can't create table './horde/horde_sessionhandler.frm' (errno: 121)[/B]
    Updating Pear modules ...Done
    Horde updated to 3.1.7p7
    Restoring previous Horde data
    Resyncing Horde database items
    
    Your horde password is above.  Horde has been reset
    At this point Horde still doesn't work properly. I've tried to manually remove horde dB and recreate it. When you drop the database mysql seems to do offline, this is the error:
    Code:
    [B]mysql> drop database horde;[/B]
    ERROR 2013 (HY000): Lost connection to MySQL server during query
    [B]mysql> drop database horde;[/B]
    ERROR 2006 (HY000): MySQL server has gone away
    No connection. Trying to reconnect...
    Connection id:    1
    Current database: *** NONE ***
    
    ERROR 1008 (HY000): Can't drop database 'horde'; database doesn't exist
    The mysqld log doesn't show anything about it.
    I've read that the innodb files could be corrupted or maybe the "mysql" mysql database could be corrupted.

    Do you think about a way to repair this files without doing a rollback on the hole mysql files of my clients ?
    I still have the .gz backup for the mysql that I've started from the monday (it's a bit outdated though).

    This are the final lines from the mysql log:
    Code:
    root@osiris [/sysbk/backup/dirs/dirs]# tail -n 60 /var/log/mysqld.log 
    It is possible that mysqld could use up to 
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2177068 K
    bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.
    
    thd=0x14893300
    Attempting backtrace. You can use the following information to find out
    where mysqld died. If you see no messages after this, something went
    terribly wrong...
    Cannot determine thread, fp=0x438680f0, backtrace may not be correct.
    Stack range sanity check OK, backtrace follows:
    (nil)
    New value of fp=0x14893300 failed sanity check, terminating stack trace!
    Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
    stack trace is much more helpful in diagnosing the problem, so please do 
    resolve it
    Trying to get some variables.
    [B]Some pointers may be invalid and cause the dump to abort...
    thd->query at 0x1485c660 = DROP DATABASE horde
    thd->thread_id=59[/B]
    The manual page at http://www.mysql.com/doc/en/Crashing.html contains
    information that should help you find out what is causing the crash.
    
    Number of processes running now: 0
    081002 12:55:53  mysqld restarted
    081002 12:55:53  InnoDB: Database was not shut down normally!
    [B]InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    081002 12:55:53  InnoDB: Starting log scan based on checkpoint at
    InnoDB: log sequence number 0 43371565.
    InnoDB: Doing recovery: scanned up to log sequence number 0 43371565[/B]
    081002 12:55:53  InnoDB: Flushing modified pages from the buffer pool...
    081002 12:55:53  InnoDB: Started; log sequence number 0 43371565
    081002 12:55:53 [Warning] Found invalid password for user: 'estudiop@localhost'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'jsplasti@localhost'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'hogarcpe@localhost'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'puerto48_joom1@192.168.1.%'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'redpata@localhost'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'shitto@localhost'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'puerto48@localhost'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'puerto48@192.168.1.%'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'puerto48_joom1@localhost'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'puerto48_mamb1@192.168.1.%'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'puerto48_mamb1@localhost'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'puerto48_ssm1@192.168.1.%'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'puerto48_ssm1@localhost'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'puerto48_ostt1@192.168.1.%'; Ignoring user
    081002 12:55:53 [Warning] Found invalid password for user: 'puerto48_ostt1@localhost'; Ignoring user
    /usr/sbin/mysqld: ready for connections.
    Version: '4.1.22-standard'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
    081002 12:57:11 [Note] /usr/sbin/mysqld: Normal shutdown
    
    081002 12:57:11  InnoDB: Starting shutdown...
    081002 12:57:14  InnoDB: Shutdown completed; log sequence number 0 43371575
    081002 12:57:14 [Note] /usr/sbin/mysqld: Shutdown complete
    
    081002 12:57:14  mysqld ended
     
    #1 Silent Ninja, Oct 2, 2008
    Last edited: Oct 2, 2008
  2. Silent Ninja

    Silent Ninja Well-Known Member

    Joined:
    Apr 18, 2006
    Messages:
    198
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Buenos Aires, Argentina
    I haven't got complaints about other innodb databases on the server besides the one from Horde... I guess nobody uses them, or nobody realized about it..

    Do you have any idea about how to fix this?
    I kinda need the Horde running, and I really don't get much about InnoDB
     
  3. s.a.

    s.a. Active Member
    PartnerNOC

    Joined:
    Aug 16, 2007
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Toronto, Canada
    All innodb tables are stored in one file - /var/lib/mysql/ibdata1, unless you have 'innodb_file_per_table' in my.cnf.
     
  4. Silent Ninja

    Silent Ninja Well-Known Member

    Joined:
    Apr 18, 2006
    Messages:
    198
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Buenos Aires, Argentina
    NOBODY ??

    Come on, I need to fix this, at least somebody tell me where the InnoDB fles are stored so I can do a full cleanup.

    EDIT: Sorry s.a. I haven't seen your post. I'll check on that.
     
    #4 Silent Ninja, Oct 3, 2008
    Last edited: Oct 3, 2008
  5. Silent Ninja

    Silent Ninja Well-Known Member

    Joined:
    Apr 18, 2006
    Messages:
    198
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Buenos Aires, Argentina
    Yahoo ! Fixed thanks to s.a. :D

    I've done...
    - 1st a backup for the ibdata1 file (as bkp-ibdata1)
    - replaced it with the one on my backup (from almost 5 days ago)
    - restarted mysql
    - deleted, re-created, re-deleted the horde database
    - ran the fullhordereset script

    And this time it did work out well :D
    You're the man !
     
Loading...

Share This Page