Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect Multi-Server » Puppet Upgrade 9.0 to 9.0.1
  •  
nate.keegan is currently offline nate.keegan

Messages: 46
IP: 63.229.103.88
Karma: 0
I followed the update procedure but I goofed up and did the initial cd /var/packages/pool/non-free && update-archive for the 9.0.1 deb file without having the site.pp file configured for auto-updates on the Pupper server.

In my logs on the downstream server (backend for example) I'm seeing the attached which I'm not 100 percent certain how to address or whether this is due to my screwing up the sequence on the Puppet server or not.

In a nutshell this is what I'm seeing in the logs:

Jan 7 16:48:11 kerio-backend1 puppet-agent[5605]: (/Stage[main]/Kerio_cloud::Backend/Debconf_package[kerio-con nect]/Package[kerio-connect]/ensure) change from 9.0.0.291-1 to 9.0.1.394-1 failed:

Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install kerio-connect' returned 100: Reading package lists...
#012Building dependency tree...
#012Reading state information...
#012The following packages will be upgraded:
#012 kerio-connect#0121 upgraded, 0 newly installed, 0 to remove and 28 not upgraded.
#012Need to get 312 MB of archives.
#012After this operation, 105 kB of additional disk space will be used.
#012WARNING: The following packages cannot be authenticated!
#012 kerio-connect
#012E: There are problems and -y was used without --force-yes
#012 at /etc/puppet/modules/debconf_package/manifests/init.pp:64

For some reason my logs are in UTC time rather than local time but that isn't a big deal.

My question then is whether this is caused by my sequencing mistake (and if so how to fix it) or something else related to a Puppet config or the .deb file itself.

This is in our lab environment so is not impacting anything for production although I want to start our migration process from Exchange to Kerio using 9.0.1

  •  
nate.keegan is currently offline nate.keegan

Messages: 46
IP: 63.229.103.88
Karma: 0
The other variable potentially here is that the procedure I am following for KMS is listed for 8.5 and the process is different somehow for KMS 9.x
  •  
nate.keegan is currently offline nate.keegan

Messages: 46
IP: 63.229.103.88
Karma: 0
For example, http://forums.kerio.com/t/30489/ would indicate that maybe the update should be run through the admin interface rather than the Puppet method?
  •  
Sam Cizkovsky (Kerio) is currently offline Sam Cizkovsky (Kerio)

Messages: 27
IP: 195.113.184.10
Karma: 0
Hello Nate,

Quote:

...without having the site.pp file configured.

Do you mean you didn't change site.pp at all?
Did running update-archive end with any error?
Please try to run following commands on any backend:
apt-get update
apt-get install kerio-connect


Quote:
...is this the preferred way to perform updates under 9.x?

If you mean Multi-Server you can use it but you just have to do it on every single backend.
Hope it helps.

Regards,

Samuel Čížkovský
QA Engineer | Kerio
Stay Connected Anytime, Anywhere. Discover Kerio Cloud!
  •  
Sam Cizkovsky (Kerio) is currently offline Sam Cizkovsky (Kerio)

Messages: 27
IP: 195.113.184.10
Karma: 0
nate.keegan wrote on Thu, 14 January 2016 23:21
Running update-archive on the Puppet system did not return any errors.

Running apt-get update and apt-get install kerio-connect works on each back-end.

On my back-end I have kerio-connect version 9.0.1.394-1 and kerio-connect-cloud 9.0.0.291-1 (9.0).

I guess the question then is if this method is the actual way this should be done. The documentation suggests that this should automatically happen provided the Puppet setup is done.

Is this issue due to running update-archive without having the site.pp updates in place or is the process correct as far as site.pp update, update-archive on the Puppet system, and then apt-get update && apt-get install kerio-whatever on the various KMS servers?

If I had to choose I would say that the manual process is actually better/more sure versus waiting for something to happen/not happen within a 30 minute type of a deal.





Samuel Čížkovský
QA Engineer | Kerio
Stay Connected Anytime, Anywhere. Discover Kerio Cloud!
  •  
Sam Cizkovsky (Kerio) is currently offline Sam Cizkovsky (Kerio)

Messages: 27
IP: 195.113.184.10
Karma: 0
Hello Nate,

nate.keegan
On my back-end I have kerio-connect version 9.0.1.394-1 and kerio-connect-cloud 9.0.0.291-1 (9.0).


Is it correct that all your backend are updated to Kerio Connect 9.0.1 and it finally worked fine?

nate.keegan
Is this issue due to running update-archive without having the site.pp updates in place or is the process correct as far as site.pp update, update-archive on the Puppet system, and then apt-get update && apt-get install kerio-whatever on the various KMS servers?


This issue isn't due having site.pp updates in place. We don't know what exactly messed up, it seems deb package was somehow damaged or partially downloaded when you were running update-archive first.
Anyway, your steps were correct if you:
- had DEB x64 package on puppet master in /var/packages/pool/non-free/
- ran update-archive on puppet master
- ran "apt-get update" and "apt-get install kerio-connect" on each backend

Samuel Čížkovský
QA Engineer | Kerio
Stay Connected Anytime, Anywhere. Discover Kerio Cloud!
  •  
nate.keegan is currently offline nate.keegan

Messages: 46
IP: 63.229.103.88
Karma: 0
All back-end updated following the procedure listed:

- Deb x86 package on Puppet in /var/packages/pool/non-free
- Edited site.pp on Puppet to allow auto-update
- Ran update-archive on Puppet, no issues
- Ran apt-get update and apt-get install kerio-connect on each back-end

I will update our internal documentation set on the procedure.

I appreciate the help on this as this type of a scenario is very useful since one doesn't typically have to upgrade a mail system with a high rate of frequency.

Compared to say an Exchange cumulative update procedure this is a breeze so no complaints on my end of things.
  •  
Sam Cizkovsky (Kerio) is currently offline Sam Cizkovsky (Kerio)

Messages: 27
IP: 195.113.184.10
Karma: 0
nate.keegan wrote on Fri, 15 January 2016 15:13

Deb x86 package on Puppet...

I believe you meant x64 Smile

nate.keegan wrote on Fri, 15 January 2016 15:13

Edited site.pp on Puppet...

There's no need to edit site.pp for this steps.

Also, I found out we have inaccurate documentation (but we're working on it) about automatic updates at the moment for Multi-Servers 9.0.0 and 9.0.1, currently, the puppet looks after automatic updates every 30 minutes defaultly - no matters to site.pp editation described. Since now default is automatic update, the documentation would contain the way how to turn it off.
Best regards,

Samuel Čížkovský
QA Engineer | Kerio
Stay Connected Anytime, Anywhere. Discover Kerio Cloud!
  •  
nate.keegan is currently offline nate.keegan

Messages: 46
IP: 63.229.103.88
Karma: 0
Right you are on the x64, Surprised

Looking forward to the documentation update.
  •  
Sam Cizkovsky (Kerio) is currently offline Sam Cizkovsky (Kerio)

Messages: 27
IP: 195.113.184.10
Karma: 0
Hello Nate,
recently, the knowledge base article has been updated - sorry for time it took.
You can see information about disabling auto-upgrade on following URL: http://kb.kerio.com/product/kerio-connect/kerio-connect-mult i-server/upgrading-and-downgrading-kerio-connect-multi-serve r-1779.html

Hope it helps!
Best regards,

Samuel Čížkovský
QA Engineer | Kerio
Stay Connected Anytime, Anywhere. Discover Kerio Cloud!
  •  
nate.keegan is currently offline nate.keegan

Messages: 46
IP: 63.229.103.88
Karma: 0
Not a problem at all and I appreciate the update on this.
Previous Topic: Setting up webmail on port 80 while running IIS on Port 80
Next Topic: Public & Shared Folders
Goto Forum:
  

 ] [ PDF ]

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: Sun Dec 17 18:26:36 CET 2017

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