Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-9300

If --wsrep-new-cluster is specified and max_allowed_packet is not valid, cluster won't start

    XMLWordPrintable

Details

    Description

      This command failed:

      mysqld_safe --wsrep-new-cluster &

      From the errlog:

      151217 12:58:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
      2015-12-17 12:58:46 140061782251456 [Warning] option 'max_allowed_packet': unsigned value 2147483648 adjusted to 1073741824
      2015-12-17 12:58:46 140061782251456 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --log_slow_queries is not set
      2015-12-17 12:58:46 140061782251456 [Note] /usr/sbin/mysqld (mysqld 10.1.9-MariaDB-1~trusty-log) starting as process 4042 ...
      2015-12-17 12:58:46 140061782251456 [Note] Using unique option prefix 'myisam_recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
      2015-12-17 12:58:46 140061782251456 [Note] Using unique option prefix 'myisam_recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
      2015-12-17 12:58:46 7f62acc717c0 InnoDB: Warning: Using innodb_locks_unsafe_for_binlog is DEPRECATED. This option may be removed in future releases. Please use READ COMMITTED transaction isolation level instead, see http://dev.mysql.com/doc/refman/5.6/en/set-transaction.html.
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: The InnoDB memory heap is disabled
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: Memory barrier is not used
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: Compressed tables use zlib 1.2.8
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: Using Linux native AIO
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: Using CPU crc32 instructions
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: Initializing buffer pool, size = 3.0G
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: Completed initialization of buffer pool
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: Highest supported file format is Barracuda.
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: 128 rollback segment(s) are active.
      2015-12-17 12:58:46 140061782251456 [Note] InnoDB: Waiting for purge to start
      2015-12-17 12:58:47 140061782251456 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1641782
      2015-12-17 12:58:47 140057453233920 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2015-12-17 12:58:47 140061782251456 [Note] Plugin 'FEEDBACK' is disabled.
      2015-12-17 12:58:47 140061782251456 [Note] Server socket created on IP: '0.0.0.0'.
      2015-12-17 12:58:47 140061782251456 [Note] Reading of all Master_info entries succeded
      2015-12-17 12:58:47 140061782251456 [Note] Added new Master_info '' to hash table
      2015-12-17 12:58:47 140061782251456 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.1.9-MariaDB-1~trusty-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution

      What changed between the 2 restarts? I fixed this line in the config file:

      max_allowed_packet = 2147483648

      Attachments

        Activity

          People

            Unassigned Unassigned
            f_razzoli Federico Razzoli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.