that was a proof of concept :) hehe...
weird stuff id that I cant
login to mysql anymore..., ask me for pass but nojoy
got this:
7-12-11 23:01:07 139777269786880 [Note] WSREP: gcomm: connecting to
group 'pfcluster', peer
'10.252.2.142:,10.252.2.141:,10.252.2.140:'
2017-12-11 23:01:07
139777269786880 [Note] WSREP: (2bc68a44, 'tcp://0.0.0.0:4567')
connection established to 2bc68a44 tcp://10.252.2.140:4567
2017-12-11
23:01:07 139777269786880 [Warning] WSREP: (2bc68a44,
'tcp://0.0.0.0:4567') address 'tcp://10.252.2.140:4567' points to own
listening address, blacklisting
2017-12-11 23:01:10 139777269786880
[Note] WSREP: (2bc68a44, 'tcp://0.0.0.0:4567') connection to peer
2bc68a44 with addr tcp://10.252.2.140:4567 timed out, no messages seen
in PT3S
2017-12-11 23:01:10 139777269786880 [Warning] WSREP: no nodes
coming from prim view, prim not possible
2017-12-11 23:01:10
139777269786880 [Note] WSREP: view(view_id(NON_PRIM,2bc68a44,1) memb {
2bc68a44,0
} joined {
} left {
} partitioned {
})
2017-12-11 23:01:10
139777269786880 [Warning] WSREP: last inactive check more than PT1.5S
ago (PT3.50485S), skipping check
2017-12-11 23:01:40 139777269786880
[Note] WSREP: view((empty))
2017-12-11 23:01:40 139777269786880 [ERROR]
WSREP: failed to open gcomm backend connection: 110: failed to reach
primary view: 110 (Connection timed out)
at
gcomm/src/pc.cpp:connect():158
2017-12-11 23:01:40 139777269786880
[ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():208: Failed to open
backend connection: -110 (Connection timed out)
2017-12-11 23:01:40
139777269786880 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1380: Failed
to open channel 'pfcluster' at
'gcomm://10.252.2.142,10.252.2.141,10.252.2.140': -110 (Connection
t
imed out)
2017-12-11 23:01:40 139777269786880 [ERROR] WSREP: gcs
connect failed: Connection timed out
2017-12-11 23:01:40 139777269786880
[ERROR] WSREP:
wsrep::connect(gcomm://10.252.2.142,10.252.2.141,10.252.2.140) failed:
7
2017-12-11 23:01:40 139777269786880 [ERROR] Aborting
171211 23:01:41
mysqld_safe mysqld from pid file /var/lib/mysql/pf01.pid ended
171211
23:01:41 mysqld_safe Starting mysqld daemon with databases from
/var/lib/mysql
171211 23:01:41 mysqld_safe WSREP: Running position
recovery with --log_error
Em 2017-12-11 22:45, Sallee, Jake via
PacketFence-users escreveu:
> Rebooting all nodes at once is ... less
than desirable : )
>
> What is the error you are getting in your
maraidb logs?
>
> Also, look here:
>
>
http://galeracluster.com/documentation-webpages/monitoringthecluster.html
[1]
>
> and here
>
>
http://galeracluster.com/documentation-webpages/troubleshooting.html
[2]
>
> Both places have some excellent info that will probably help
you get back up and running again.
>
> My gut says your first stop
should be the mariadb log, that will point you in the correct
direction.
>
> If you find more specific info and get stuck post back
to this list and if I see it I'll try to assist as I can.
>
> Jake
Sallee
> Godfather of Bandwidth
> System Engineer
> University of Mary
Hardin-Baylor
> WWW.UMHB.EDU
>
> 900 College St.
> Belton, Texas
>
76513
>
> Fone: 254-295-4658
> Phax: 254-295-4221
>
________________________________
> From: Luís Torres via
PacketFence-users <[email protected]>
> Sent:
Monday, December 11, 2017 3:34 PM
> To:
[email protected]
> Cc: Luís Torres
> Subject:
[PacketFence-users] Clustering-nodes rebooted
>
> Hello mates,
>
> I
rebooted all 3 nodes at same time and now it keeps me sending me this
error:
>
> pf::db::db_connect)
> Dec 11 21:33:02 pf01 packetfence:
FATAL -e(626): unable to connect to database: Can't connect to local
MySQL server through socket '/var/lib/mysql/mysql.sock' (111 "Connection
refused") at -e line 1.
> (pf::db::db_connect)
> Dec 11 21:33:03 pf01
packetfence: INFO pf-mariadb(1278): There is an alive quorum but no db
available on any server (main::startup_clean_shutdown)
> Dec 11 21:33:03
pf01 packetfence: INFO pf-mariadb(1278): This node is not safe to
bootstrap from. Starting in normal mode to connect to a bootstrapped
peer. (main::startup_clean_shutdown)
> Dec 11 21:33:03 pf01 packetfence:
FATAL -e(626): unable to connect to database: Can't connect to local
MySQL server through socket '/var/lib/mysql/mysql.sock' (111 "Connection
refused") at -e line 1.
> (pf::db::db_connect)
>
> I cannot start now
the cluster :(
>
> any ideas?
>
> Regards to all
>
> LT
>
>
------------------------------------------------------------------------------
>
Check out the vibrant tech community on one of the world's most
>
engaging tech sites, Slashdot.org! http://sdm.link/slashdot [3]
>
_______________________________________________
> PacketFence-users
mailing list
> [email protected]
>
https://lists.sourceforge.net/lists/listinfo/packetfence-users [4]
Links:
------
[1]
http://galeracluster.com/documentation-webpages/monitoringthecluster.html
[2]
http://galeracluster.com/documentation-webpages/troubleshooting.html
[3]
http://sdm.link/slashdot
[4]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
