mariadb cluster suddenly failed/stopped

Follow

pinoekio

• March 31, 2022 09:57

hi, my mariadb cluster suddenly failed/stopped

in node 1

members(3):
        0: 53cb1cf0-b0bf-11ec-98bf-7e15398291fc, 10.1.84.156
        1: 67a57949-b0cc-11ec-a751-cbb8878b491e, 10.1.84.155
        2: a968c074-b0ba-11ec-bf3f-7f63fa40ee6a, 10.1.84.157
=================================================
2022-03-31 16:29:01 2 [Note] WSREP: Non-primary view
2022-03-31 16:29:01 2 [Note] WSREP: Server status change disconnected -> connected
2022-03-31 16:29:01 2 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2022-03-31 16:29:01 2 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2022-03-31 16:29:04 0 [Note] WSREP: (67a57949-a751, 'ssl://0.0.0.0:4567') turning message relay requesting off

in node 2 & 3

[Warning] WSREP: Send action {0x7f0b5401e120, 158, STATE_REQUEST} returned -107 (Transport endpoint is not connected)

please give me pointer sir

Thank You

0

• 

  Duncan Kabue Mwangi

  • March 31, 2022 10:21

  Hi,

  I think the best action here is to create a support request at the following link: https://severalnines.zendesk.com/hc/en-us/requests/new? So we can follow this issue there.

  Kindly also generate an error report from the ClusterControl UI. You can do this by choosing the cluster > Logs > Error Reports > Create Error Report. Attach the tarball generated to the ticket.

  Thank you.

  Regards,

  Duncan

  0

  Comment actions Permalink
• 

  pinoekio

  • March 31, 2022 11:35

  ok, on it sir, thank you

  0

  Comment actions Permalink

Please sign in to leave a comment.