Results 1 to 2 of 2

Thread: Bizzare Issue After Upgrade (3.0.1->4.0.3) - Debian

  1. #1
    Join Date
    Oct 2006
    Posts
    1
    Rep Power
    9

    Default Bizzare Issue After Upgrade (3.0.1->4.0.3) - Debian

    Hello all...

    I recently upgraded from 3.0.1 to 4.0.3 on Debian Sarge. I encountered a few password sync and file permission issues...but all-in-all it wen't rather smoothly (so it seemed). Zimbra is running great without any issues...until services are manually stopped or restarted!!

    When Zimbra services are stopped...they will not startup again...Error message states "Cannot determine services - exiting".

    The only thing I can find in my zimbra logs follow...
    -----
    Oct 30 16:21:33 alpha postfix-policyd: FATAL: you did not upgrade correctly or have broken something. Please read the Changelog.txt. You're missing the CONN_ACL setting
    Oct 30 16:21:37 alpha zimbramon[2712]: 2712:info: Starting services
    Oct 30 16:22:02 alpha zimbramon[2844]: 2844:info: 2006-10-30 16:22:01, STATUS: : Cannot: determine
    Oct 30 16:24:02 alpha zimbramon[2875]: 2875:info: 2006-10-30 16:24:01, STATUS: : Cannot: determine
    -----

    To get things working again I perform a "dummy" upgrade install using the same version (4.0.3). Then things work again...

    A "dpkg -l | grep zimbra" shows the zimbra packages are in fact installed. And there are no issues while the services are running.

    Any thoughts would greatly be appreciated!
    Last edited by jasonsz; 10-30-2006 at 08:14 PM.

  2. #2
    Join Date
    Nov 2005
    Posts
    36
    Rep Power
    10

    Default

    I had similar problems:

    - Upgrading worked fine...well, it seems to be fine
    - After a reboot of the machine, we also had permission problems
    - Mails were deferred and the slapd could not resolve correctly, lmtp was on the wrong IP-adress...

    Weird things happened...searching the forum, i came to the conclusion, that there is a Debian KERNEL bug, which changes the permissions in some 'zimbra' owned folders, if you make a '/etc/init.d/zimbra stop' as root.



    Check:
    ========
    - redo.log
    - and look in /opt/zimbra/index/
    => if all permissions are: 'zimbra:zimbra'

    If NOT:
    - stop zimbra
    - and make: /opt/zimbra/libexec/zmfixperms as root !

    Check also /opt/zimbra/log/zimbra.log, if there are any exceptions !

    Actually i upgraded Debian Sarge to Kernel 2.6.17-2-686 (from backports), because i had to enable HIGHMEM support (but this was a personal problem). I recognized, that with a newer kernel Zimbra performs much better.

    The bug should be
    "fixed in debian's linux-source-2.6.17-8~bpo.1"
    Read:
    =====
    http://www.zimbra.com/forums/showthread.php?t=3418
    http://www.zimbra.com/forums/showthread.php?t=5012

    Maybe this was a little help ;-)

    /harry

Similar Threads

  1. Debian - Upgrade Error
    By xiller in forum Installation
    Replies: 4
    Last Post: 02-06-2007, 03:00 PM
  2. Skin issue after upgrade
    By Maja in forum Installation
    Replies: 3
    Last Post: 10-24-2006, 03:40 PM
  3. 3.1.2 debian upgrade error
    By MarcTwain in forum Installation
    Replies: 1
    Last Post: 06-01-2006, 03:25 PM
  4. Replies: 2
    Last Post: 04-15-2006, 08:34 AM
  5. 3.0.1 GA upgrade problem
    By kollross in forum Administrators
    Replies: 5
    Last Post: 04-04-2006, 11:42 AM

Posting Permissions

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