Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: No HTTP and HTTPs Access

  1. #11
    Join Date
    Oct 2009
    Posts
    147
    Rep Power
    6

    Default

    nothing to mailbox.log
    when mysql.server start is ran it just reports done
    I tried to see if a pid file was created at /opt/zimbra/db/mysql.pid but nothing was created indicating nothing started up.

  2. #12
    Join Date
    Jan 2008
    Posts
    658
    Rep Power
    8

    Default

    How about in mysql_error.log?

  3. #13
    Join Date
    Oct 2009
    Posts
    147
    Rep Power
    6

    Default

    Looks like we are zeroing into something. Here's the relevant portion of the log. How do we proceed now ? thanks in advance

    100913 11:34:51 mysqld started
    InnoDB: The log sequence number in ibdata files does not match
    InnoDB: the log sequence number in the ib_logfiles!
    100913 11:34:51 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...
    InnoDB: Error: trying to access page number 4294966131 in space 0,
    InnoDB: space name ./ibdata1,
    InnoDB: which is outside the tablespace bounds.
    InnoDB: Byte offset 0, len 16384, i/o type 10.
    InnoDB: If you get this error at mysqld startup, please check that
    InnoDB: your my.cnf matches the ibdata files that you have in the
    InnoDB: MySQL server.
    100913 11:34:52InnoDB: Assertion failure in thread 3074336432 in file fil0fil.c line 3959
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to MySQL Bugs.
    InnoDB: If you get repeated assertion failures or crashes, even
    InnoDB: immediately after the mysqld startup, there may be
    InnoDB: corruption in the InnoDB tablespace. Please refer to
    InnoDB: MySQL :: MySQL 5.0 Reference Manual :: 13.2.6.2 Forcing InnoDB Recovery
    InnoDB: about forcing recovery.
    100913 11:34:52 - mysqld got signal 11 ;
    This could be because you hit a bug. It is also possible that this binary
    or one of the libraries it was linked against is corrupt, improperly built,
    or misconfigured. This error can also be caused by malfunctioning hardware.
    We will try our best to scrape up some info that will hopefully help diagnose
    the problem, but since we have already crashed, something is definitely wrong
    and this may fail.

    key_buffer_size=0
    read_buffer_size=1048576
    max_used_connections=0
    max_connections=110
    threads_connected=0
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225280K bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    thd=(nil)
    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=0xbff39208, backtrace may not be correct.
    Stack range sanity check OK, backtrace follows:
    0x81a6088
    0x83c57da
    0x83a195b
    0x83a1fcf
    0x8395c61
    0x838f08c
    0x838325b
    0x83834c7
    0x83851d5
    0x83013b5
    0x828a14c
    0x827e662
    0x81a54c8
    0x81aa667
    0xb7402450
    0x8101e61
    New value of fp=(nil) failed sanity check, terminating stack trace!
    Please read MySQL :: MySQL 5.1 Reference Manual :: 22.5.1.5 Using a Stack Trace 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
    The manual page at MySQL :: MySQL 5.1 Reference Manual :: B.5.4.2 What to Do If MySQL Keeps Crashing contains
    information that should help you find out what is causing the crash.
    100913 11:34:52 mysqld ended

  4. #14
    Join Date
    Jan 2008
    Posts
    658
    Rep Power
    8

    Default

    I'd start with forcing innodb recovery. Here's the Zimbra wiki article on recovering MySQL: Mysql Crash Recovery - Zimbra :: Wiki

  5. #15
    Join Date
    Oct 2009
    Posts
    147
    Rep Power
    6

    Default

    Adding the innodb_force_recovery value and attempting to restart mysql didn't work. Basically, mysql just won't start.

    So, even though we have some stuff to try, we can't get mysql to even start. I suppose now the focus is on why or what prevents mysql from starting ?

    Humm.....
    TIA

Similar Threads

  1. Clicking on link opens HTTP instead of HTTPS
    By mlanner in forum Administrators
    Replies: 4
    Last Post: 06-17-2009, 09:49 AM
  2. [SOLVED] Access web mail using https protocol
    By dewaltjdy in forum Administrators
    Replies: 2
    Last Post: 07-22-2008, 01:25 AM
  3. Replies: 2
    Last Post: 01-18-2007, 03:05 PM
  4. Changing browser access from HTTPS to Both HTTPS and HTTP
    By kelley.ch in forum Administrators
    Replies: 5
    Last Post: 09-19-2006, 12:50 AM
  5. HTTPS Is Working, HTTP Not Working
    By uh-nu-bu in forum Installation
    Replies: 12
    Last Post: 11-09-2005, 06:58 AM

Posting Permissions

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