SitePoint Sponsor

User Tag List

Results 1 to 3 of 3
  1. #1
    SitePoint Addict
    Join Date
    Mar 2008
    Location
    Sterling, CO
    Posts
    275
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Database was not shut down normally!

    I give up. I've looked everywhere.

    How come I get this


    121204 22:05:38 [Note] Plugin 'FEDERATED' is disabled.
    121204 22:05:38 InnoDB: The InnoDB memory heap is disabled
    121204 22:05:38 InnoDB: Mutexes and rw_locks use Windows interlocked functions
    121204 22:05:38 InnoDB: Compressed tables use zlib 1.2.3
    121204 22:05:38 InnoDB: Initializing buffer pool, size = 128.0M
    121204 22:05:38 InnoDB: Completed initialization of buffer pool
    121204 22:05:38 InnoDB: highest supported file format is Barracuda.
    InnoDB: The log sequence number in ibdata files does not match
    InnoDB: the log sequence number in the ib_logfiles!
    121204 22:05:38 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.

    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    121204 22:05:39 InnoDB: Waiting for the background threads to start
    121204 22:05:40 InnoDB: 1.1.8 started; log sequence number 17035621
    121204 22:05:40 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
    121204 22:05:40 [Note] - '0.0.0.0' resolves to '0.0.0.0';
    121204 22:05:40 [Note] Server socket created on IP: '0.0.0.0'.
    121204 22:05:40 [Note] Event Scheduler: Loaded 0 events
    121204 22:05:40 [Note] mysql\bin\mysqld: ready for connections.
    Version: '5.5.28' socket: '' port: 3306 MySQL Community Server (GPL)



    Everytime I restart. The database seems to be doing fine but if looks like it's unstable. How can I fix it?

  2. #2
    Always A Novice bronze trophy
    K. Wolfe's Avatar
    Join Date
    Nov 2003
    Location
    Columbus, OH
    Posts
    2,079
    Mentioned
    53 Post(s)
    Tagged
    0 Thread(s)
    By restart, you mean restart your physical machine? Try forcing a shutdown on mysqld before continuing with a system restart and see what happens.
    Code:
    mysqladmin shutdown

  3. #3
    SitePoint Addict
    Join Date
    Mar 2008
    Location
    Sterling, CO
    Posts
    275
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I'm sorry I didn't know someone replied here. No email.

    This worries the dog poop out of me because today I think it crashed. Lucky for me I have back-ups all over my computer, but all the back ups have the same error.

    What I mean is if I do a restart I get this error. I have done everything I now to fix it. My site seems to be working fine right now but I'm gun shy after today!

    I can't find any information on the web except something about delete the InnoDB and some files and restarting it. But they never said how to delete the InnoDB.

    Any advice is welcome.


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •