[Kolab-devel] server 2.2.0b2 horde, ppc and upgrading from 2.1

Bernhard Reiter bernhard at intevation.de
Wed Oct 24 12:43:30 CEST 2007


Still on the train I did some experiments trying to 
upgrade from server 2.1 on a Debian Sarge ppc to 2.2.0b2.
Right now I do not have the time to further examin and open
good issues. On the other hand I do not want to let my experience rot
in my head. 

So there is the dump-it-all version,
it is worth or a couple of issues. 

I also discovered issue2128 that you neew online access as well.

Doing stuff from CD I cd /kolab and used
 bash /cdrom/sources/install-kolab.sh -H -F -i /cdrom/sources/ | tee 
kolab-install-20071022-1.log
                warning: unknown option -kK

	 bash -x shows that "-kK" is an argument to /kolab/bin/openpkg build -kK
        so the old version of openpkg has this problem.

It stopped with
             FATAL: errors occured while building:
                kolabd-2.1.99-20071018: kolabd has conflicting requirement

        Not very helpful.

        Trying the command manually to save the output and see what is wrong.
        /kolab/bin/openpkg build -kK -r /cdrom/sources -p ppc-debian3.1-kolab 
-D
 openldap::with_pth=no -D sasl::with_ldap -D sasl::with_login -D 
postfix::with_s
asl -D postfix::with_ssl -D postfix::with_ldap -D kolabd::with_horde 
-Dkolabd::k
olab_version=2.2-beta2 -Dkolab-webadmin::kolab_version=2.2-beta2 openpkg-tools 
o
penldappostfix kolabd kolab-filter kolab-freebusy kolab-webadmin 
kolab-horde-fra
meworkhorde-kolab-client fbview-kronolith >x

        This did not help as executing the commands in "x" seems to work.
        Thus adding an '| tee y ' before the '| sh' in the install-kolab.sh.

        I believe I can see the problem in there with:
        # apache-2.2.6-20070910 has conflicting requirement with_mod_ldap = 
no !
= yes
        # kolabd has conflicting requirement

        Thus trying:
                /kolab/bin/openpkg rpm -e --nodeps apache
        and again install-kolab.sh, now I get a lot more problem.
        php-5.2.4-20071012 has conflicting requirement with_mm = no != yes
                /kolab/bin/openpkg rpm -e --nodeps apache
        # imapd-2.3.9-20071015 has conflicting requirement with_kolab = no != 
yes
                /kolab/bin/openpkg rpm -e --nodeps imapd
        -> now stuff starts!!!
        Debugging is a problem, though, maybe better with a newer openpkg?


        Stops with
                :::: /cdrom/sources/mhash-0.9.9-20070807.src.rpm ::::
                error: cannot write to %sourcedir /kolab/RPM/SRC/mhash
                error: /cdrom/sources/mhash-0.9.9-20070807.src.rpm cannot be 
installed

        rm -r /kolab/RPM/SRC/mhash/
        rm -r /kolab/RPM/TMP/mhash-0.9.9/ /kolab/RPM/TMP/rpm-tmp.12841

        Stopped while building php5.2.4:
                checking for PCRE support... yes
                configure: error: The PCRE extension requires PCRE library 
version >= 6.6
                error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.64616 
(%build
                /kolab/bin/openpkg rpm -e --nodeps pcre
        restarting
        stopping with
                 kolabd >= 2.1.99-20070607 is needed by 
kolab-horde-framework-2.1.99-20070607
       Restarting it continues with apache, this is at least strange,
       a simple restart should not just make it better.

        Stopped again.
        :::: /cdrom/sources/kolab-horde-framework-2.1.99-20070607.src.rpm ::::
        error: Failed dependencies:
                kolabd >= 2.1.99-20070607 is needed by 
kolab-horde-framework-2.1.99-20070607

        Restarting again.
        Now ends at:
        :::: /cdrom/sources/kolabd-2.1.99-20071018.src.rpm ::::
        error: cannot write to %sourcedir /kolab/RPM/SRC/kolabd
        error: /cdrom/sources/kolabd-2.1.99-20071018.src.rpm cannot 
        eione:/kolab# rm -r /kolab/RPM/SRC/kolabd/
        eione:/kolab# rm -r /kolab/RPM/TMP/pear/

        Restarting again, maybe deleting the "pear" was not good:
                Error: Unknown channel "pear.horde.org"
	-> issue2182 
	
	For next progress had to
                /kolab/bin/openpkg rpm -e --nodeps kolab-resource-handlers
			 /kolab/bin/openpkg rpm -e --nodeps kolab-horde-fbview

	Restarted
     Now done without further notice.        How can I check if all is good?        
The directory has 1.1 GByte size now (this includes the old user data)  

             Trying         /kolab/bin/openpkg rc openldap start         
/kolab/sbin/kolabconf        Failed, kolab.conf is not correct.        
Yesterday one process saved the old one in kolab.conf.rpmsave.        
cd /kolab/etc/kolab/                mv kolab.conf.rpmsave kolab.conf        
in addition I have tried to check:        /kolab/sbin/kolabcheckperm    

this gave strange results need to be examined is      kolabcheckperm
up to date?

		got a couple of .rpmsaves to be resolved after kolabconf and
	     later starting things.
                  /kolab/sbin/kolabconf
        /kolab/sbin/kolabconf -h
Use of uninitialized value in print at /kolab/sbin/kolabconf line 51.
kolabconf - Version 2.2.beta2Usage: kolabconf [-d] [-n] [-h]

    Option d (debug) to print out the current config.
    Option n (noreload) to skip reloading services after changing 
configuration.
    Option h (help) to get this text.

        Would it be wise to print the usage information when an unknown
        option was given?

        kolabconf does not output the version number anymore,
        what is the reason for the change? If it is run on a shell
        interactively I believe it should still output what it does
        in the normal case.

        master.cf: Is this line correct?
        +kolabfilter     unix  -       n       n       -       -       pipe 
user=kolab-n null_sender= argv=/kolab/bin/php

       Apache is slow trying to optimise a bit.
        http.conf.template
        Changed to
                <IfModule mpm_prefork_module>
                PidFile              /kolab/var/apache/run/apache.pid
                StartServers         2
                MinSpareServers      2
                MaxSpareServers      4
        used kolabconf, but it did not say that it restarted apache,
        but it probably did.
       

        Hmmmm "HostnameLookups On" is strange, should this really be done?
        I disabled it, but it.

	This all was not the problem. It seem that old version of Konqueror
	from KDE 3.3.2 coming with Debin Sarge cannot deal with how the new 
     apache serves the pages, it will hang the 15 seconds on the keep-a-live
     connection. :/ We should find a configuration option for this as this
     will make people stumble if they use old browsers.

        The php test from the 1st.README failed, so I had to do:
        eione:/cdrom/sources#         ln -s /dev/null /kolab/lib/libdb3.so.3

	I deleted /kolab/var/kolab/www/freebusy/cache/pfbcache.db
	without further migration.

	Horde seems to issue the wrong triggers for Kalenderfolders
     especialy when they are nested. Also Horde had problems to
     create an appointment in the default calender folder and to display
     the folder Kalender/privat correctly.
                   

Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20071024/5416bc74/attachment.sig>


More information about the devel mailing list