Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect Multi-Server » Multi-Server Error When Provisioning First Backend
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
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.

  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
Bueller? Bue-ller? Bue-ller?
  •  
Pavel Stepanek (Kerio)

Messages: 29
Karma: 0
Send a private message to this user
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,

  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
I'm getting the same error repeatedly after running 'puppet agent -t' several times on the Back-End Server.

Attached is the full puppet log and a snippet showing the error in isolation after running 'puppet agent -t'.

  •  
Stepan Potys (Kerio)

Messages: 86
Karma: 2
Send a private message to this user
Halle Nate,

the problem is that the galera package configuration fails because it has changed couple of days ago (a new package was released). We're working on a bug fix and will release it with next minor build of Kerio Connect.

Thank you for reporting the issue and for your patience.
I'm very sorry for the inconvenience.

Stepan Potys
Connect Core team leader
Kerio Technologies
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
These things happen and I appreciate the response.
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
My Kerio sales engineer advised me to try 8.5.1 pre-release and this has fixed the issue I was having as outlined here
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
8.5.1 pre-release looks good up to IM role when I get the attached which is very similar to Back-End in 8.5.0.

I tried waiting a bit and running 'puppet agent -t' and I get the same error message.

  • Attachment: puppet-im.txt
    (Size: 12.21KB, Downloaded 274 times)
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
I confirmed that Front-End role does not have the same issue.
  •  
Jakub Schwarzmeier, Kerio

Messages: 67
Karma: 1
Send a private message to this user
Can you take a look into these files (if present) after the backend or IM deployment finishes?

/var/log/apt/history.log
/var/log/dpkg.log
/var/log/syslog
/var/log/mysql/error.log

Can you try to double RAM size for the VM before you deploy the backend node?

We cannot reproduce this issue here.
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
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.
  •  
markus.k1985

Messages: 11
Karma: 0
Send a private message to this user
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?
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
Allowing firewall access for the Multi-Server host(s) to keyserver.ubuntu.com for HTTP/HTTPS and FTP should fix the issue.
  •  
nate.keegan

Messages: 46
Karma: 0
Send a private message to this user
I would expand that to include FTP, HTTP, HTTPS access to ftp.debian.org and security.debian.org as well.
markus.k1985

Messages: 11
Karma: 0
Send a private message to this user
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")


Previous Topic: Repository Error When installing Puppet Master
Next Topic: Clarification of connectivity
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Tue Feb 21 21:58:34 CET 2017

Total time taken to generate the page: 0.04777 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.