Buy Percona ServicesBuy Now!

cluster fail

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • cluster fail

    Hello


    After clustering, I started again on two servers I had. But I get an error when starting server 1 as below.
    There is no data on it right now. What is the cause of the problem?

    srv1:
    Os: Ubuntu 16.04

    srv2:
    Os: Ubuntu 16.04

    # /etc/init.d/mysql bootstrap-pxc

    # tail -f /var/log/mysqld.log

    017-12-09T19:21:40.933510Z mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
    2017-12-09T19:21:45.927701Z mysqld_safe Logging to '/var/log/mysqld.log'.
    2017-12-09T19:21:45.945611Z mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    2017-12-09T19:21:45.955051Z mysqld_safe Skipping wsrep-recover for dd3abd12-dd0c-11e7-aae3-b234582bcef8:6 pair
    2017-12-09T19:21:45.956276Z mysqld_safe Assigning dd3abd12-dd0c-11e7-aae3-b234582bcef8:6 to wsrep_start_position
    2017-12-09T19:21:46.142191Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
    2017-12-09T19:21:46.143773Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.19-17-57-log) starting as process 11235 ...
    2017-12-09T19:21:46.145970Z 0 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=uninginx0-bin' to avoid this problem.
    2017-12-09T19:21:46.146376Z 0 [Note] WSREP: Setting wsrep_ready to false
    2017-12-09T19:21:46.146407Z 0 [Note] WSREP: No pre-stored wsrep-start position found. Skipping position initialization.
    2017-12-09T19:21:46.146429Z 0 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib/libgalera_smm.so'
    2017-12-09T19:21:46.149608Z 0 [Note] WSREP: wsrep_load(): Galera 3.22(r8678538) by Codership Oy <info@codership.com> loaded successfully.
    2017-12-09T19:21:46.149686Z 0 [Note] WSREP: CRC-32C: using hardware acceleration.
    2017-12-09T19:21:46.150076Z 0 [Note] WSREP: Found saved state: dd3abd12-dd0c-11e7-aae3-b234582bcef8:6, safe_to_bootsrap: 0
    2017-12-09T19:21:46.155178Z 0 [Note] WSREP: Passing config to GCS: base_dir = /var/lib/mysql/; base_host = 94.130.226.187; base_port = 4567; cert.log_conflicts = no; debug = no; evs.auto_evict = 0; evs.delay_margin = PT1S; evs.delayed_keep_period = PT30S; evs.inactive_check_period = PT0.5S; evs.inactive_timeout = PT15S; evs.join_retrans_period = PT1S; evs.max_install_timeouts = 3; evs.send_window = 10; evs.stats_report_period = PT1M; evs.suspect_timeout = PT5S; evs.user_send_window = 4; evs.view_forget_timeout = PT24H; gcache.dir = /var/lib/mysql/; gcache.keep_pages_count = 0; gcache.keep_pages_size = 0; gcache.mem_size = 0; gcache.name = /var/lib/mysql//galera.cache; gcache.page_size = 128M; gcache.recover = no; gcache.size = 128M; gcomm.thread_prio = ; gcs.fc_debug = 0; gcs.fc_factor = 1; gcs.fc_limit = 100; gcs.fc_master_slave = no; gcs.max_packet_size = 64500; gcs.max_throttle = 0.25; gcs.recv_q_hard_limit = 9223372036854775807; gcs.recv_q_soft_limit = 0.25; gcs.sync_donor = no; gmcast.segment = 0; gmcast.version = 0; pc.announce_timeout = PT3S; pc.checksum = false; pc.ignore_quorum = false; pc.ignore_sb = false; pc.npvo = false; pc.recovery = 1; pc.version = 0; pc.wait_prim = true; pc.wait_prim_timeout = PT30S; pc.weight = 1; protonet.backend = asio; protonet.version = 0; repl.causal_read_timeout = PT30S; repl.commit_order = 3; repl.key_format = FLAT8; repl.max_ws_size = 2147483647; repl.proto_max = 7; socket.checksum = 2; socket.recv_buf_size = 212992;
    2017-12-09T19:21:46.169496Z 0 [Note] WSREP: GCache history reset: dd3abd12-dd0c-11e7-aae3-b234582bcef8:0 -> dd3abd12-dd0c-11e7-aae3-b234582bcef8:6
    2017-12-09T19:21:46.174327Z 0 [Note] WSREP: Assign initial position for certification: 6, protocol version: -1
    2017-12-09T19:21:46.174384Z 0 [Note] WSREP: Preparing to initiate SST/IST
    2017-12-09T19:21:46.174397Z 0 [Note] WSREP: Starting replication
    2017-12-09T19:21:46.174435Z 0 [Note] WSREP: Setting initial position to dd3abd12-dd0c-11e7-aae3-b234582bcef8:6
    2017-12-09T19:21:46.174675Z 0 [Note] WSREP: Using CRC-32C for message checksums.
    2017-12-09T19:21:46.174817Z 0 [Note] WSREP: gcomm thread scheduling priority set to other:0
    2017-12-09T19:21:46.174979Z 0 [Warning] WSREP: Fail to access the file (/var/lib/mysql//gvwstate.dat) error (No such file or directory). It is possible if node is booting for first time or re-booting after a graceful shutdown
    2017-12-09T19:21:46.175002Z 0 [Note] WSREP: Restoring primary-component from disk failed. Either node is booting for first time or re-booting after a graceful shutdown
    2017-12-09T19:21:46.175234Z 0 [Note] WSREP: GMCast version 0
    2017-12-09T19:21:46.175471Z 0 [Note] WSREP: (32583645, 'tcp://0.0.0.0:4567') listening at tcp://0.0.0.0:4567
    2017-12-09T19:21:46.175498Z 0 [Note] WSREP: (32583645, 'tcp://0.0.0.0:4567') multicast: , ttl: 1
    2017-12-09T19:21:46.176031Z 0 [Note] WSREP: EVS version 0
    2017-12-09T19:21:46.176175Z 0 [Note] WSREP: gcomm: connecting to group 'uni_cluster', peer '94.x.x.x.x:,94.x.x.x.x:'
    2017-12-09T19:21:46.177243Z 0 [Note] WSREP: (32583645, 'tcp://0.0.0.0:4567') connection established to 32583645 tcp://94.x.x.x.x:4567
    2017-12-09T19:21:46.177279Z 0 [Warning] WSREP: (32583645, 'tcp://0.0.0.0:4567') address 'tcp://94.x.x.x.x:4567' points to own listening address, blacklisting
    2017-12-09T19:21:49.177657Z 0 [Note] WSREP: (32583645, 'tcp://0.0.0.0:4567') connection to peer 32583645 with addr tcp://94.x.x.x.x:4567 timed out, no messages seen in PT3S
    2017-12-09T19:21:49.178712Z 0 [Warning] WSREP: no nodes coming from prim view, prim not possible
    2017-12-09T19:21:49.178764Z 0 [Note] WSREP: Current view of cluster as seen by this node
    view (view_id(NON_PRIM,32583645,1)
    memb {
    32583645,0
    }
    joined {
    }
    left {
    }
    partitioned {
    }
    )
    2017-12-09T19:21:49.678945Z 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT3.50294S), skipping check

  • #2
    There are only NOTE & WARNINGS no ERRORS. Can you please provide complete error log and my.cnf settings from both nodes.

    Comment


    • #3
      It looks as if this node is not able to communicate with the other node. Maybe the cluster names are different?

      Comment

      Working...
      X