Question about upgrading cyrus-imapd in Kolab 3.3 Updates

[Cornelius Hald]

I can't really find anything in the logs that explains why cyrus does
not start anymore. All I have is a bunch of those lines:

Jan 25 15:53:03 mail cyr_info[22385]: Option 'flushseenstate' is
deprecated in version 2.5.0.
Jan 25 15:53:03 mail cyr_info[22385]: Option 'tls_ca_file' is deprecated
in favor of 'tls_client_ca_file' since version 2.5.0.
Jan 25 15:53:03 mail cyr_info[22385]: Option 'tls_cert_file' is
deprecated in favor of 'tls_server_cert' since version 2.5.0.
Jan 25 15:53:03 mail cyr_info[22385]: Option 'tls_key_file' is
deprecated in favor of 'tls_server_key' since version 2.5.0.

But they don't look fatal to me.


On Sun, 2015-01-25 at 16:10 +0100, Cornelius Hald wrote:
> Hi,
> 
> so it looks like the repo is published now. Thanks a lot!
> 
> Unfortunately the update doesn't really work for me on CentOS 7. I'll
> have to investigate further, but my first findings are here.
> 
> yum update
> 
> -------------
> Total download size: 1.4 M
> Is this ok [y/d/N]: y
> Downloading packages:
> Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
> cyrus-imapd-2.5-106.el7.kolab_3.4.x86_64.rpm
> | 1.4 MB  00:00:00     
> Running transaction check
> Running transaction test
> Transaction test succeeded
> Running transaction Updating :cyrus-imapd-2.5-106.el7.kolab_3.4.x86_64
> 1/2 
> warning: /etc/cyrus.conf created as /etc/cyrus.conf.rpmnew
> warning: %post(cyrus-imapd-2.5-106.el7.kolab_3.4.x86_64) scriptlet
> failed, exit status 1
> Non-fatal POSTIN scriptlet failure in rpm package
> cyrus-imapd-2.5-106.el7.kolab_3.4.x86_64
> /var/tmp/rpm-tmp.4ySWBm: line 1: fg: no job control
> error: %preun(cyrus-imapd-2.5-48.5.el7.kolab_3.3.x86_64) scriptlet
> failed, exit status 1
> Error in PREUN scriptlet in rpm package
> cyrus-imapd-2.5-48.5.el7.kolab_3.3.x86_64
> Verifying  : cyrus-imapd-2.5-106.el7.kolab_3.4.x86_64 1/2 
> Verifying  : cyrus-imapd-2.5-48.5.el7.kolab_3.3.x86_64 2/2 
> 
> Updated:
>   cyrus-imapd.x86_64 0:2.5-106.el7.kolab_3.4
> 
> Failed:
>   cyrus-imapd.x86_64 0:2.5-48.5.el7.kolab_3.3
> -------------
> 
> After that I cannot start cyrus-imapd anymore (don't know why yet). Also
> it looks like both versions of imapd are installed in parallel.
> 
> 
> If anyone has similar issues or knows something about it, please let me
> know.
> 
> Thanks!
> Conny
> 
> 
> 
> On Fri, 2015-01-23 at 21:21 +0100, gregory.bahde at laposte.net wrote:
> > Hello,
> > 
> > Well I could publish it if the OBS didn't end up with an error 500
> > when I'm trying to connect :/
> > 
> > 
> > 
> >    any clue?
> > 
> > 
> > 
> > regards
> > 
> > 
> > 
> > 
> > 
> > Greg B
> > 
> > 
> > ______________________________________________________________________
> > De: "Cornelius Hald" <hald at icandy.de>
> > À: "Timotheus Pokorra" <timotheus at kolab.org>
> > Cc: users at lists.kolab.org, "gregory bahde" <gregory.bahde at laposte.net>
> > Envoyé: Vendredi 23 Janvier 2015 15:03:57
> > Objet: Re: Question about upgrading cyrus-imapd in Kolab 3.3 Updates
> > 
> > 
> > Hi and thanks to all involved!
> > 
> > 
> > I can give it a try once the package is published. Is there any chance
> > it also fixes this SEGV?
> > 
> > 
> > https://issues.kolab.org/show_bug.cgi?id=3962
> > 
> > 
> > Thanks!
> > Conny
> > 
> > 
> > On Fri, 2015-01-23 at 14:47 +0100, Timotheus Pokorra wrote:
> > > Hello,
> > > 
> > > this email is directed to all users of the Kolab 3.3 community
> > packages.
> > > 
> > > We have a segfault bug in Cyrus Imap which is delivered with Kolab
> > 3.3.
> > > 
> > > It has been discussed on this mailinglist:
> > >
> > http://lists.kolab.org/pipermail/users/2015-January/thread.html#18583
> > >
> > http://lists.kolab.org/pipermail/users/2015-January/thread.html#18663
> > > 
> > > There is also this bug for it:
> > > https://issues.kolab.org/show_bug.cgi?id=3963
> > > 
> > > Thanks to Gregory, we have a pull request for Kolab 3.3 Updates:
> > > https://obs.kolabsys.com/request/show/782
> > > 
> > > Since there is no other quality assurance for the community edition
> > of 
> > > Kolab other than us the community, I want to ask if some people can
> > test 
> > > this for a couple of days, before I merge the request into Kolab
> > 3.3 
> > > Updates.
> > > 
> > > I am not using Kolab in production yet myself, so I don't feel in a 
> > > position to make such a decision on my own.
> > > 
> > > To test the package suggested by Gregory, please add his repository:
> > > 
> > > wget 
> > >
> > http://obs.kolabsys.com/repositories/home:/goonieb:/branches:/Kolab:/Development/CentOS_6/home:goonieb:branches:Kolab:Development.repo 
> > > -O kolab-3-test-new_cyrus.repo
> > > yum update
> > > 
> > > Hmm, this does not work yet, because the package is not published
> > yet.
> > > 
> > > @Gregory: can you please publish the packages for testing? go to
> > >
> > https://obs.kolabsys.com/package/repositories/home:goonieb:branches:Kolab:Development/cyrus-imapd
> > > and in section "Publish Flag" make sure that All/All has a green
> > mark, 
> > > with right click you get a popup menu to select that.
> > > 
> > > When enough people say this works for them, I will be happy to
> > merge 
> > > this pull request into Kolab 3.3 Updates, and everyone will be
> > using 
> > > it...
> > > 
> > > Thanks,
> > >    Timotheus
> > > _______________________________________________
> > > users mailing list
> > > users at lists.kolab.org
> > > https://lists.kolab.org/mailman/listinfo/users
> > 
> > 
> > 
> > 
> 
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users