Ad Widget

Collapse

Не стартует zabbix

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Gererro
    Junior Member
    • Jul 2019
    • 4
    #1

    Не стартует zabbix

    Не стартует zabbix, точнее скорее не сам zabbix, а mysql. Проблема с сокетом MySql. Точнее с его отсутствием.
    Лог /var/log/mysql/error.log:

    [Warning] Changed limits: max_open_files: 1024 (requested 5000)
    [Warning] Changed limits: table_open_cache: 431 (requested 2000)
    [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
    [Note] /usr/sbin/mysqld (mysqld 5.7.26-0ubuntu0.16.04.1) starting as process 13483 ...
    [Note] InnoDB: PUNCH HOLE support available
    [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    [Note] InnoDB: Uses event mutexes
    [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    [Note] InnoDB: Compressed tables use zlib 1.2.8
    [Note] InnoDB: Using Linux native AIO
    [Note] InnoDB: Number of pools: 1
    [Note] InnoDB: Using CPU crc32 instructions
    [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
    [Note] InnoDB: Completed initialization of buffer pool
    [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
    [Note] InnoDB: Highest supported file format is Barracuda.
    [Note] InnoDB: Log scan progressed past the checkpoint lsn 907574947701
    [Note] InnoDB: Doing recovery: scanned up to log sequence number 907580190208
    [Note] InnoDB: Doing recovery: scanned up to log sequence number 907583922933
    [Note] InnoDB: Database was not shutdown normally!
    [Note] InnoDB: Starting crash recovery.
    [Note] InnoDB: Starting an apply batch of log records to the database...

    Сам лог zabbix_server.log
    874:20190716:091620.372 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    874:20190716:091620.372 database is down: reconnecting in 10 seconds
    874:20190716:091630.373 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    874:20190716:091630.373 database is down: reconnecting in 10 seconds
    Прошу хелпа, чего mysql хватает?!
    Tags: None
    • DSV12
      Senior Member
      Zabbix Certified Specialist
      • Nov 2018
      • 156
      #2
      Originally posted by Gererro
      Не стартует zabbix, точнее скорее не сам zabbix, а mysql. Проблема с сокетом MySql. Точнее с его отсутствием.
      Лог /var/log/mysql/error.log:
      ...
      [Note] InnoDB: Database was not shutdown normally!
      [Note] InnoDB: Starting crash recovery.
      [Note] InnoDB: Starting an apply batch of log records to the database...
      У вас база битая. Вы её инициализировали при установке? Или это сломалось уже в работающей системе? Если да, то нужно базу ремонтировать, может придётся через dump/restore делать...

      Сам лог zabbix_server.log
      874:20190716:091620.372 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
      874:20190716:091620.372 database is down: reconnecting in 10 seconds
      874:20190716:091630.373 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
      874:20190716:091630.373 database is down: reconnecting in 10 seconds
      Это уже следствие не работающей mysql

      Прошу хелпа, чего mysql хватает?!
      Ремонтируйте базу. Подобная проблема здесь уже озвучивалась: https://www.zabbix.com/forum/in-russ...0%D0%B5-zabbix

        Comment

        • Gererro
          Junior Member
          • Jul 2019
          • 4
          #3
          Она работала больше года, после отключения света свалилась.

            Comment

            • Catalysto
              Junior Member
              • Jul 2015
              • 11
              #4
              запускаешь базу с опцией innodb_force_recovery = 1
              далее делай бэкап mysqldump'ом или xtrabackup
              удаляешь базу (если делал бэкап mysqldump'ом) или все базы данных (в случае xtrabackup)
              и заливай базу mysqldump'ом или xtrabackup

              Originally posted by Gererro
              Она работала больше года, после отключения света свалилась.
              она могла и 5 лет проработать, бэкапы делай на будущее

                Comment

                • Gererro
                  Junior Member
                  • Jul 2019
                  • 4
                  #5
                  Помогло только "innodb_force_recovery = 6", 1-5 не стартовал.
                  В момент бэкапа mysqldump'ом валится ошибка:
                  root@zabbix:/home/appliance# mysqldump zabbix | gzip > database.sql.gz
                  mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `history` at row: 787502

                    Comment

                    • Gererro
                      Junior Member
                      • Jul 2019
                      • 4
                      #6
                      Покурив инет дописал в my.cnf
                      [mysqld]
                      innodb_force_recovery = 6
                      innodb_buffer_pool_size=2048M
                      max_allowed_packet=2048M
                      net_read_timeout=3600
                      net_write_timeout=3600
                      secure-file-priv = ""
                      !includedir /etc/mysql/conf.d/
                      !includedir /etc/mysql/mysql.conf.d/
                      Результат тот же
                      Last edited by Gererro; 18-07-2019, 03:31.

                        Comment

                        Previous template Next
                        Working...