Re: [Kolab-devel] Upgrade report 3.1 to 3.2 on Debian Wheezy

A short report from my viewpoint. I just did a 3.1 to 3.2 upgrade on a 
debian based system (clone from my live system).

1) After apt-get dist-upgrade I was greeted from a nice wallace 
traceback

Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/wallace/__init__.py", line 235, 
in do_wallace
     pair = s.accept()
   File "/usr/lib/python2.7/socket.py", line 202, in accept

I've the feeling that there was a conflict between the old maybe running 
or dying wallace process and the new one. wallace wasn't running anymore 
but `service wallace restart` did the job. No error and wallace was 
running (Even it's not configured and used in my setup)

The other thing I want to mentioned that you shouldn't replace any of 
the configuration files debhelper is asking you for. If you really press 
yes, you've to rollback the *.dpkgold files, because it doesn't contain 
any of your settings or credentials.


2) First check: Roundcube login works, but no contacts are displayed

cd /usr/share/roundcubemail/
plugins/libkolab/bin/modcache.sh clear -a
Still no luck. Even iRony has nothing to show via CardDAV. Everything 
empty. (Solution below)


3) A php error found in the error log.

PHP message: PHP Warning:  Missing argument 3 for 
kolab_storage_cache::save(), called in 
/usr/share/roundcubemail/plugins/libkolab/lib/kolab_storage_cache.php on 
line 305 and defined in 
/usr/share/roundcubemail/plugins/libkolab/lib/kolab_storage_cache.php on 
line 321

that's an easy one. Bugfix reported and patch attached
https://issues.kolab.org/show_bug.cgi?id=2863


4) Database layout changed, but not updated during upgrade

One commit a week ago made me wonder if my database was up2date
https://git.kolab.org/roundcubemail-plugins-kolab/commit/?id=af6d366a1f8c7761aaabd53c6ab80f4b6a75face

In fact no, the debian packages haven't updated the database layout. I 
looked at the OBS Scripts ant indeed. the RPM .spec files contains a 
section where database patches get applied during installation, the 
debian postinst script is missing this one.

Package merged, update and submitted
https://obs01.kolabsys.com/package/rdiff?linkrev=base&package=roundcubemail-plugins-kolab&project=home%3Adhoffend%3Abranches%3AKolab%3ADevelopment&rev=2

I've tested the package above and it upgrades my database layout nicely 
from 3.1 to 3.2. I haven't tested it on clean 3.2 installation but since 
it's was already getting executed during a RPM installation, I see now 
issues why it should't work either. I'm not sure if that's the 
debian-way-of db-upgrades but it will work.


5) Kolab Server not starting after reboot


Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/kolabd/__init__.py", line 183, 
in run
     self.do_sync()
   File "/usr/lib/python2.7/dist-packages/kolabd/__init__.py", line 250, 
in do_sync
     for primary_domain in list(set(domains.values())));
TypeError: unhashable type: 'list'

Hint: This problem exists already in Kolab 3.1 but hasn't been target 
yet.

So kolabd/kolab-server isn't running after reboot which can cause 
problems cause people are wondering why mailboxes aren't getting created 
etc. A friendly `service kolab-server restart` solves the issue, but 
this can't be the solution.

I've the feeling that kolabd comes up at a point where the ldap 
directory hasn't fully loaded yet. During the connection attempt it 
crashes leaving you with no servíce.

--

Regarding the ptloader issue Tobias mentioned:
not sure if you're using a single-domain setup or a multi-domain setup. 
But when you're planning to run a multidomain setup you've to disable 
ptloader anyway (just remove it from imapd.conf) like mentioned in the 
http://docs.kolab.org/howtos/multi-domain.html#cyrus-imap-changes 
documentation.

--

I hope the 2 fixes mentioned above will make it into the 3.2:Updates 
section soon.

--
Regards
Daniel Hoffend




------ Originalnachricht ------
Von: "Tobias Brunner" <[email protected]>
An: [email protected]
Gesendet: 18.02.2014 17:02:13
Betreff: Re: [Kolab-devel] Upgrade report 3.1 to 3.2 on Debian Wheezy

>Hi,
>
>I could resolve some of the Cyrus errors:
>
>>Feb 15 19:04:30 james lmtpunix[8795]: ptload(): can't connect to
>>ptloader server: Connection refused
>>[...]
>>Feb 15 19:15:01 james imaps[8790]: ptload failed: but canonified
>>cyrus-admin -> cyrus-admin
>
>Can be resolved by adding the following lines to the config files:
>
>/etc/cyrus.conf:
>
>SERVICES {
>[...]
>   ptloader cmd="ptloader" listen="/var/lib/imap/socket/ptsock" 
>prefork=1
>[...]
>}
>
>/etc/imapd.conf:
>ptloader_sock: /var/lib/imap/socket/ptsock
>
>That resolvs the above errors, but produces other ones:
>
>Feb 18 09:39:09 james lmtpunix[26346]: ptload(): bad response from 
>ptloader server: identifier not found
>Feb 18 09:39:09 james lmtpunix[26346]: ptload failed for 
>mailto:tobias%[email protected]
>
>>Feb 15 19:04:30 james lmtpunix[8795]: IDLE: error sending message
>>NOTIFY to idled for mailbox tobrunet.ch!user.tobias^brunner:
>>Connection refused.
>>[...]
>>Feb 15 19:05:35 james imap[8789]: IDLE: error sending message INIT to
>>idled for mailbox tobrunet.ch!user.tobias^brunner: Connection refused.
>>Falling back to polling every 60 seconds.
>
>Can be resolved by adding the following line to the config file:
>
>/etc/cyrus.conf:
>
>START {
>[...]
>   # this is only necessary if using idled for IMAP IDLE
>   idled cmd="idled"
>[...]
>}
>
>Cheers,
>Tobias
>
>_______________________________________________
>devel mailing list
>[email protected]
>https://lists.kolab.org/mailman/listinfo/devel

_______________________________________________
devel mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/devel