| Re: Multi-Server Error When Provisioning First Backend [message #124523 is a reply to message #124519] |
Mon, 28 September 2015 14:55   |
markus.k1985
Messages: 11
Registered: September 2015
|
|
|
|
Hello,
some additional details from /var/log/syslog during manual startup:
Sep 28 12:23:10 shs-mail-be-01 mysqld: 150928 12:23:10 [Warning] WSREP: last inactive check more than PT1.5S ago (PT3.50166S), skipping check
Sep 28 12:23:35 shs-mail-be-01 /etc/init.d/mysql[53372]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Sep 28 12:23:35 shs-mail-be-01 /etc/init.d/mysql[53372]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Sep 28 12:23:35 shs-mail-be-01 /etc/init.d/mysql[53372]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111 "Connection refused")'
Sep 28 12:23:35 shs-mail-be-01 /etc/init.d/mysql[53372]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Sep 28 12:23:35 shs-mail-be-01 /etc/init.d/mysql[53372]:
Sep 28 12:23:39 shs-mail-be-01 mysqld: 150928 12:23:39 [Note] WSREP: view((empty))
Sep 28 12:23:39 shs-mail-be-01 mysqld: 150928 12:23:39 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out)
Sep 28 12:23:39 shs-mail-be-01 mysqld: #011 at gcomm/src/pc.cpp:connect():161
Sep 28 12:23:39 shs-mail-be-01 mysqld: 150928 12:23:39 [ERROR] WSREP: gcs/src/gcs_core.cpp:long int gcs_core_open(gcs_core_t*, const char*, const char*, bool)():206: Failed to open backend connection: -110 (Connection timed out)
Sep 28 12:23:39 shs-mail-be-01 mysqld: 150928 12:23:39 [ERROR] WSREP: gcs/src/gcs.cpp:long int gcs_open(gcs_conn_t*, const char*, const char*, bool)():1379: Failed to open channel 'my_wsrep_cluster' at 'gcomm://172.18.3.66,172.18.3.68': -110 (Connection timed out)
Sep 28 12:23:39 shs-mail-be-01 mysqld: 150928 12:23:39 [ERROR] WSREP: gcs connect failed: Connection timed out
Sep 28 12:23:39 shs-mail-be-01 mysqld: 150928 12:23:39 [ERROR] WSREP: wsrep::connect() failed: 7
Sep 28 12:23:39 shs-mail-be-01 mysqld: 150928 12:23:39 [ERROR] Aborting
Sep 28 12:23:39 shs-mail-be-01 mysqld:
Sep 28 12:23:39 shs-mail-be-01 mysqld: 150928 12:23:39 [Note] WSREP: Service disconnected.
Sep 28 12:23:40 shs-mail-be-01 mysqld: 150928 12:23:40 [Note] WSREP: Some threads may fail to exit.
Sep 28 12:23:40 shs-mail-be-01 mysqld: 150928 12:23:40 [Note] /usr/sbin/mysqld: Shutdown complete
Sep 28 12:23:40 shs-mail-be-01 mysqld:
Sep 28 12:23:40 shs-mail-be-01 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
|
|
|
|
| Re: Multi-Server Error When Provisioning First Backend [message #124530 is a reply to message #124523] |
Mon, 28 September 2015 17:40 |
nate.keegan
Messages: 46
Registered: June 2015
|
|
|
|
I would say that your MySQL/Galera setup is off.
I would try removing the VM, removing the DHCP lease that the VM was using, and running 'puppet cert clean <fqhn of system being removed>' on the Puppet role and then re-run the VM initialization.
There is a command I have seen come up on a downstream (from the Puppet system's perspective' when the Puppet setup isn't completed that can be run on the downstream system but I can't remember what it is off the top of my head. Something like 'puppet agent something or other' that would kick off the Puppet config again on this host and that should fill in the blanks so to speak for what might be missing.
|
|
|
|
|
|
Members
Search
Help
Register
Login
Home
