Multi-Server Error When Provisioning First Backend [message #121971] |
Thu, 11 June 2015 20:05  |
nate.keegan
Messages: 46 Registered: June 2015
|
|
|
|
I'm testing a deployment of Kerio Connect Multi-Server 8.5.0 and everything was going pretty well until I went to provision our first Backend Server.
Everything looks like it goes well until this point:
notice: /Stage[main]/Galera/Package[rsync]/ensure: ensure changed 'purged' to 'present'
err: /Stage[main]/Mysql::Server::Install/Package[mysql-server]/en sure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install mariadb-galera-server' returned 100: Reading package lists...
Things look fine and then this:
dpkg: error processing mariadb-galera-server-10.0 (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mariadb-galera-server:
mariadb-galera-server depends on mariadb-galera-server-10.0 (= 10.0.19+maria-1~wheezy); however:
Package mariadb-galera-server-10.0 is not configured yet.
dpkg: error processing mariadb-galera-server (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mariadb-galera-server-10.0
mariadb-galera-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
After this point the provisioning process blows up as it cannot connect to MySQL.
Full log is attached and I have opened a ticket with tech support on this issue.
I deleted this VM, removed the DHCP lease (to keep the same IP and identity), and removed the Puppet Master SSL cert for this VM and I get the same thing on a fresh VM/vmdk.
|
|
|
|
Re: Multi-Server Error When Provisioning First Backend [message #122025 is a reply to message #121971] |
Tue, 16 June 2015 00:33   |
 |
Pavel Stepanek (Kerio)
Messages: 17 Registered: January 2005 Location: Kerio Technologies
|
|
|
|
Dear Nate,
It seems some dependent script in Puppet has failed. Despite there are dependencies within puppet scripts, in fact some of these parts can run in random order based on processing time, compilation order and other aspects. We may possibly inspect the issue further more, but to confirm this was just puppet script processing issue, run following command few times please:
puppet agent -t
It means to run the puppet agent and download latest configuration files and to process all the scripts again. This is in fact run automatically each hour. So running it more offten is not against common setup.
If the puppet agent -t pass finally with all notice green, it was just a timing issue of the script. If you will have repetitive error message, it is final error and the puppet scripts can not recover from it. If you see any other error, send it to us please so we can inspect it.
Thank you for the report,
|
|
|
|
|
|
|
|
|
|
Re: Multi-Server Error When Provisioning First Backend [message #122439 is a reply to message #121971] |
Mon, 29 June 2015 19:00   |
nate.keegan
Messages: 46 Registered: June 2015
|
|
|
|
I just ran an install/provision of the IM role in our test environment after all of the other roles have been installed.
The installation went off without issue so I suspect that it was either VM memory (seems to do some weird stuff if a VM is tamped down too much on memory during a provision) or something that I will try to create in our test environment the next time we build it.
|
|
|
Re: Multi-Server Error When Provisioning First Backend [message #124489 is a reply to message #121971] |
Fri, 25 September 2015 15:33   |
markus.k1985
Messages: 11 Registered: September 2015
|
|
|
|
Hello,
I tried today a deployment of version 8.5.2
It looks like a similar issue on first BackEnd Node:
notice: /Stage[main]/Kerio_cloud/Notify[system-role]/message: defined 'message' as 'System role is: 'backend/172.18.3.68' repository address is:172.18.3.66'
err: /Stage[main]/Galera::Repo/Apt::Source[galera_mariadb_repo]/A pt::Key[Add key: CBCB082A1BB943DB from Apt::Source galera_mariadb_repo]/Apt_key[Add key: CBCB082A1BB943DB from Apt::Source galera_mariadb_repo]/ensure: change from absent to present failed: Execution of '/usr/bin/apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 1BB943DB' returned 2: Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.aVIST5V0hK --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-jessie-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-jessie-security-autom atic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-jessie-stable.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg --keyserver keyserver.ubuntu.com --recv-keys 1BB943DB
gpg: requesting key 1BB943DB from hkp server keyserver.ubuntu.com
gpg: keyserver timed out
gpg: keyserver receive failed: keyserver error
Any solution for that?
|
|
|
|
|
Re: Multi-Server Error When Provisioning First Backend [message #124519 is a reply to message #124496] |
Mon, 28 September 2015 14:11   |
markus.k1985
Messages: 11 Registered: September 2015
|
|
|
|
OK, Port 11371 was necessary for the connection.
but now mysql startup fails:
err: /Stage[main]/Mysql::Server::Service/Service[mysqld]/ensure: change from stopped to running failed: Could not start Service[mysqld]: Execution of '/etc/init.d/mysql start' returned 1: at /etc/puppet/modules/mysql/manifests/server/service.pp:23
err: Could not prefetch mysql_user provider 'mysql': Execution of '/usr/bin/mysql --defaults-extra-file=/root/.my.cnf -NBe SELECT CONCAT(User, '<_at_>',Host) AS User FROM mysql.user' returned 1: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111 "Connection refused")
|
|
|