Results 1 to 7 of 7

Thread: Zarafa crashes Apache after logrotation on Ubuntu 14.04 LTS

  1. #1
    Junior Member
    Join Date
    Jul 2011
    Posts
    9

    Question Zarafa crashes Apache after logrotation on Ubuntu 14.04 LTS

    Hi All,

    I recently installed Zarafa from zcp-7.1.11-46050-ubuntu-14.04-x86_64-free.tar.gz on a Ubuntu 14.04 LTS server.
    Everything seemed to be running fine until the logrotate daemon was trying to rotate Apache logfiles this morning.
    Last sign of life was found in Apache's error.log:
    I googled around for some time and found a thread that was giving some hints to analyze the issue:


    It also gave a way how to reproduce the behaviour:
    Apache immediately went down with the same error AH00060.

    Doing what was recommended in this blog, I tried to load the php modules one by one - finally it turned out that it was the zarafa.ini that was responsible for the crash.
    Since it is "only" loading mapi.so, this is the main suspect.

    I searched for mapi.so in my usr dir:
    This turns out to be the version delivered by the Zarafa installer:
    Some details about my system configuration:
    Searching for mapi.so I found a very old thread here, but there was no real solution provided:


    I'd pretty much like to avoid my Apache crashing again with the next logrotation, so has anyone encountered the same problem in recent time?

    Any help appreciated,
    fladenbrot

  2. #2
    Junior Member
    Join Date
    Nov 2012
    Posts
    10
    Eventhough that is a while older, I faced the same issue with now Zarafa 7.1.12, basically directly after updating from 7.1.11 to .12 on Debian 7.8 with all latest updates.

    The way of reproducing is exactly the same. The only thing that makes we wonder is, why mapi.so should now have an issue.

    Not knowing if the libical is related to mapi or not,the only thing that I could see is that when I installed the updated zarafa-debs, with each repo update, debian will upgrade the zarafa shipped "libical0 0.44-6" with "libical0_0.48-2_amd64.deb", which then causes the shipped "libical-dev_0.44-6_amd64.deb" to break, as that depends on the non-dev libical which is upgraded, but there is no upgrade for "libical-dev_0.44-6_amd64.deb" in the debian repo.

    Now looking with ldd into mapi.so, I could see the following:
    ldd /usr/lib/php5/20100525/mapi.so
    linux-vdso.so.1 => (0x00007ffc02729000)
    libmapi.so.0 => /usr/lib/libmapi.so.0 (0x00007f040c3e9000)
    libinetmapi.so.1 => /usr/lib/libinetmapi.so.1 (0x00007f040c149000)
    libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f040bf43000)
    libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f040bd2c000)
    libicui18n.so.48 => /usr/lib/x86_64-linux-gnu/libicui18n.so.48 (0x00007f040b961000)
    libicuuc.so.48 => /usr/lib/x86_64-linux-gnu/libicuuc.so.48 (0x00007f040b5f1000)
    libicudata.so.48 => /usr/lib/x86_64-linux-gnu/libicudata.so.48 (0x00007f040a281000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f040a07d000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0409e60000)
    libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f0409b59000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f04098d7000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f040954b000)
    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f0409335000)
    libboost_filesystem.so.1.49.0 => /usr/lib/libboost_filesystem.so.1.49.0 (0x00007f0409314000)
    libboost_system.so.1.49.0 => /usr/lib/libboost_system.so.1.49.0 (0x00007f040930f000)
    libicalmapi.so.1 => /usr/lib/libicalmapi.so.1 (0x00007f04090c9000)
    libvmime.so.0 => /usr/lib/libvmime.so.0 (0x00007f0408c98000)
    libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x00007f0408937000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f040c925000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f040872f000)
    libical.so.0 => /usr/lib/libical.so.0 (0x00007f04084cb000)
    libicalss.so.0 => /usr/lib/libicalss.so.0 (0x00007f04082b2000)
    liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f040808f000)

    seeing libical.so appearing there, I checked the libical from above, to see what it contains:
    dpkg --contents libical0_0.44-6_amd64.deb
    drwxr-xr-x root/root 0 2014-10-28 12:13 ./
    drwxr-xr-x root/root 0 2014-10-28 12:13 ./usr/
    drwxr-xr-x root/root 0 2014-10-28 12:13 ./usr/share/
    drwxr-xr-x root/root 0 2014-10-28 12:13 ./usr/share/doc/
    drwxr-xr-x root/root 0 2014-10-28 12:13 ./usr/share/doc/libical0/
    -rw-r--r-- root/root 14489 2009-09-27 04:38 ./usr/share/doc/libical0/changelog.gz
    -rw-r--r-- root/root 1459 2009-09-27 04:38 ./usr/share/doc/libical0/copyright
    -rw-r--r-- root/root 625 2014-10-28 12:13 ./usr/share/doc/libical0/changelog.Debian.gz
    drwxr-xr-x root/root 0 2014-10-28 12:13 ./usr/lib/
    -rw-r--r-- root/root 386872 2014-10-28 12:13 ./usr/lib/libical.so.0.44.0
    -rw-r--r-- root/root 90152 2014-10-28 12:13 ./usr/lib/libicalss.so.0.44.0
    -rw-r--r-- root/root 84288 2014-10-28 12:13 ./usr/lib/libicalvcal.so.0.44.0
    lrwxrwxrwx root/root 0 2014-10-28 12:13 ./usr/lib/libicalss.so.0 -> libicalss.so.0.44.0
    lrwxrwxrwx root/root 0 2014-10-28 12:13 ./usr/lib/libical.so.0 -> libical.so.0.44.0
    lrwxrwxrwx root/root 0 2014-10-28 12:13 ./usr/lib/libicalvcal.so.0 -> libicalvcal.so.0.44.0

    In my interpretation, the mapi.so references to ical shared objects shipping with libical 0.44, which might then break, when the debian update comes, as the symlinks are changed to point to "libical.so.0.48.0" instead of "libical.so.0.44.0".

    So I rolled backed to the zarafa shipped version, and put that package on hold to see if things get better.

    Any ideas, why it breaks with the debian shipped version?

  3. #3
    Zarafa

    Join Date
    Jan 2009
    Location
    Hanover, Germany
    Posts
    1,891
    Hello Piotr,

    at least for 7.1.12 this is already known and fixed for the next release. 7.1.12 introduced a new configuration file (php-mapi.cfg) and the absence of this configuration file currentlly leads to the segfault on reload of apache.

    As a workaround you can simply copy the default configuration from /usr/share/doc/zarafa/example-config/(php-mapi.cfg) to /etc/zarafa.

    The internal ticket number is (not public due to core dump of customer).
    Regards Felix

    How to get Kopano

    Zarafa ALPHA/BETA/RC feedback in BETA forum please.
    Zarafa IRC chat: irc.freenode.com > #zarafa
    Zarafa documentation: http://documentation.zarafa.com/

    No support via PM! Please contact our sales team for an offer if you want my full attention.

  4. #4
    Junior Member
    Join Date
    Sep 2014
    Posts
    2
    Updating to 7.1.12-49411 didn't fix the problem. Though, manually fixing it like you described did.

  5. #5
    Junior Member
    Join Date
    Nov 2012
    Posts
    10
    Hi fbartels,

    thanks for the response, ah ok that's why I missed it when looking for some open case

    Adding the file manually seems to have solved it, thanks.

  6. #6
    Member
    Join Date
    Dec 2010
    Location
    Wr. Neustadt, Austria
    Posts
    51
    Hi,

    same issue with Debian 7, fortunately coping php-mapi.cfg fixes this issue.
    Regards

    Walter

  7. #7
    Member IDECable's Avatar
    Join Date
    Jul 2010
    Location
    Ottawa Canada
    Posts
    52
    I had same issue. Fixed! Thx!

Similar Threads

  1. Zarafa Community on Ubuntu 12.04 LTS php5_mapi crashes apache2
    By bruderjakob in forum Installation, Configuration and Maintenance
    Replies: 0
    Last Post: 11-06-2013, 12:23 PM
  2. Zarafa Server 6.40.5 on Ubuntu 8.04 crashes with SIGSEGV(6)
    By blackjack97 in forum Installation and Configuration Archives
    Replies: 3
    Last Post: 03-03-2011, 08:17 AM
  3. [SOLVED] Error upgrade zarafa/ubuntu 804 to ubuntu 10.04
    By pieter96 in forum Installation and Configuration Archives
    Replies: 2
    Last Post: 27-10-2010, 08:18 PM
  4. Zarafa/Apache/PHP Problem
    By christof in forum Installation and Configuration Archives
    Replies: 4
    Last Post: 21-10-2009, 11:00 AM
  5. mapi.so error: apache crashes after reload
    By dominic in forum Installation and Configuration Archives
    Replies: 2
    Last Post: 30-12-2008, 08:48 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •