Ad Widget

Collapse

ERROR: Error connecting to database [Connection refused]

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ingvar
    Junior Member
    • Apr 2012
    • 1

    #1

    ERROR: Error connecting to database [Connection refused]

    Сегодня Zabbix перестал коннектиться к базе.
    При проверке:
    zabbix:~ # /etc/init.d/mysql status
    Checking for service MySQL: unused


    При запуске:
    zabbix:~ # /etc/init.d/mysql start
    Starting service MySQL warning: /var/run/mysql/mysql.sock didn't appear within 30 seconds
    chmod: cannot access `/var/run/mysql/mysqld.pid': No such file or directory
    failed


    В лог пишет следующее:

    120426 10:27:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    120426 10:27:28 InnoDB: Initializing buffer pool, size = 8.0M
    120426 10:27:28 InnoDB: Completed initialization of buffer pool
    InnoDB: Error: tried to read 65536 bytes at offset 0 245248.
    InnoDB: Was only able to read 512.
    InnoDB: Fatal error: cannot read from file. OS error number 17.
    120426 10:27:42 InnoDB: Assertion failure in thread 3074063152 in file ../../../storage/innobase/os/os0file.c line 2299
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    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: http://dev.mysql.com/doc/refman/5.1/...-recovery.html
    InnoDB: about forcing recovery.
    120426 10:27:42 - mysqld got signal 6 ;
    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=16777216
    read_buffer_size=262144
    max_used_connections=0
    max_threads=151
    threads_connected=0
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133320 K
    bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    Thread pointer: 0x0
    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...
    stack_bottom = (nil) thread_stack 0x30000
    /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x84e1789]
    /usr/sbin/mysqld(handle_segfault+0x514) [0x82061b4]
    [0xffffe400]
    [0xffffe430]
    /lib/libc.so.6(gsignal+0x4f) [0xb73d38df]
    /lib/libc.so.6(abort+0x180) [0xb73d5220]
    /usr/sbin/mysqld() [0x840f088]
    /usr/sbin/mysqld(os_aio+0x26f) [0x841020f]
    /usr/sbin/mysqld(fil_io+0x211) [0x83da431]
    /usr/sbin/mysqld(log_group_read_log_seg+0xe4) [0x8400694]
    /usr/sbin/mysqld() [0x840579c]
    /usr/sbin/mysqld(recv_recovery_from_checkpoint_start+0x4c3) [0x8405ce3]
    /usr/sbin/mysqld(innobase_start_or_create_for_mysql+0x12fb) [0x84473bb]
    /usr/sbin/mysqld() [0x839a512]
    /usr/sbin/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x 3e) [0x82f48ce]
    /usr/sbin/mysqld() [0x8380ff0]
    /usr/sbin/mysqld(plugin_init(int*, char**, int)+0x5f6) [0x8383be6]
    /usr/sbin/mysqld() [0x8206b50]
    /usr/sbin/mysqld(main+0x204) [0x8209f14]
    /lib/libc.so.6(__libc_start_main+0xfe) [0xb73bec2e]
    /usr/sbin/mysqld() [0x813e2f1]
    The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
    information that should help you find out what is causing the crash.
    120426 10:27:42 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended


    Кто сталкивался?
  • dima_dm
    Senior Member
    • Dec 2009
    • 2697

    #2
    Похоже, что у вас файлы INNODB повреждены, надеюсь вы делали резервные копии MySQL базы?

    Comment

    • dotneft
      Senior Member
      • Nov 2008
      • 699

      #3
      When I upgraded my ubuntu server to a more recent mysql version, the mysql server didn't come up anymore.The error.log said:InnoDB: Log scan progressed past the checkpoint lsn 0 726937418110103 23:55:57 InnoDB: Database was not shut down normally!...


      Должно помочь, надеюсь

      Comment

      Working...