Results 1 to 2 of 2

Thread: ZCP 7.2.2 beta 2 feedback

  1. #1
    Senior Member
    Join Date
    Jan 2008
    Posts
    400

    ZCP 7.2.2 beta 2 feedback

    Hi,

    Im as we speak in progress of an update of 7.2.1 to 7.2.2. beta 2.

    I use a local repo for my packages so upgrading of the packages was smooth.
    I went over te config files and must say, this was one of the easiest updates.
    i diffed the configs, backuped old, keept the new one, and change the new to my settings.

    did a chown zarafa:zarafa on /var/lib/zarafa
    and started up the zarafa services

    I have only 1 thing to comment.

    for the search.log
    2016-03-16 16:20:07,185 - search - WARNING - index_attachment_parser: config option ignored
    2016-03-16 16:20:07,185 - search - WARNING - index_attachment_parser_max_memory: config option ignored
    2016-03-16 16:20:07,185 - search - WARNING - index_attachment_parser_max_cputime: config option ignored
    2016-03-16 16:20:07,185 - search - WARNING - index_attachment_mime_filter: config option ignored
    2016-03-16 16:20:07,185 - search - WARNING - index_attachment_extension_filter: config option ignored
    2016-03-16 16:20:08,203 - search - WARNING - could not connect to server at 'file:///var/run/zarafad/server.sock', retrying in 5 sec

    Did i miss something?

    beside these warning, i can only say GOOD JOB ! this i like.


    Ok, now the one "Bad" thing i saw.

    symlinking zarafa-webaccess.conf in /etc/apache2/sited-enabled messup my config again.

    The zarafa-webaccess.conf should really only be in /etc/zarafa/conf-available and not in /etc/zarafa/sites-available .
    Use a2enconf for that to place the config in the "general" config dir. /etc/apache2/conf-enabled
    dpkg-reconfigure -plow zarafa-webaccess does not give the option to choose if you want zarafa-webaccess by default enabled.
    ( which i dont want. )

    But in general, and again only tested the install/upgrade, a good beta.

    Keep it going guys.
    I like where its going.
    Last edited by thctlo; 16-03-2016 at 05:00 PM.

  2. #2
    Senior Member
    Join Date
    Jan 2008
    Posts
    400
    After update-ing from init.d scripts to systemd . I noticed zarafa wasnt started after server reboot.
    So please enable it to start by default.
    After that change, i got multiple errors are in the logs, due to incorrect boot oder in systemd.

    for example :
    zarafa-licensed :
    Mon Mar 21 10:10:34 2016: [ notice] Base serial [email protected]@Pj3SK1Ik3n, valid for 10 users
    Mon Mar 21 10:10:34 2016: [ notice] Starting zarafa-licensed version 7,2,2,481 (481), pid 871
    Mon Mar 21 10:10:39 2016: [fatal ] CreateProfileTemp(): ConfigureMsgService failed 80040115: network error
    Mon Mar 21 10:10:39 2016: [warning] CreateProfileTemp(SSL) failed: 80040115: network error
    Mon Mar 21 10:10:39 2016: [error ] Unable to connect to zarafa server on 'file:///var/run/zarafad/prio.sock': 0x80040115

    zarafa-spooler
    Mon Mar 21 10:54:14 2016: [ notice] [ 861] Starting zarafa-spooler version 7,2,2,481 (481), pid 861
    Mon Mar 21 10:54:14 2016: [fatal ] [ 861] CreateProfileTemp(): ConfigureMsgService failed 80040115: network error
    Mon Mar 21 10:54:14 2016: [warning] [ 861] CreateProfileTemp(SSL) failed: 80040115: network error
    Mon Mar 21 10:54:14 2016: [error ] [ 861] Unable to open admin session. Error 0x80040115
    Mon Mar 21 10:54:14 2016: [warning] [ 861] Server connection lost. Reconnecting in 3 seconds...

    EDIT : ^^^^^^ due to my error, old certifcates with in correct names. ^^^^^^^

    And these messaged are not needed, a simple change in systemd files.
    What i did for now, i copied, the following

    /lib/systemd/system/zarafa-* to /etc/systemd/system
    Here i did edit the zarafa-*.service files.

    in all files, add in the [Unit] section ( exept the zarafa-server that one is correct )
    After=zarafa-server.service

    and this one for the zarafa-spooler
    After=zarafa-server.service zarafa-gateway.service zarafa-dagent.service

    and systemctl daemon-reload

    i cleaned up my logs again, rebooted, after these changes, i have a nice error free log at startup.

    Greetz,

    ---------- Post added ----------

    when rebooting the server, the zarafa-search gives :


    Mar 21 11:34:33 mail1 zarafa-search[1260]: Exception SystemExit: SystemExit('Terminating on signal 15',) in <bound method IMAPISession.<lambda> of <MAPICore.IMAPISession; proxy of <Swig Object of type 'IMAPISession *' at 0x7fe1870cd870> >> ignored
    6Mar 21 11:34:33 mail1 zarafa-search[1260]: Exception SystemExit: SystemExit('Terminating on signal 15',) in <bound method IMAPISession.<lambda> of <MAPICore.IMAPISession; proxy of <Swig Object of type 'IMAPISession *' at 0x7fe1870cd870> >> ignored
    Mar 21 11:34:33 mail1 zarafa-search[1260]: Exception SystemExit: SystemExit('Terminating on signal 15',) in <bound method IMAPISession.<lambda> of <MAPICore.IMAPISession; proxy of <Swig Object of type 'IMAPISession *' at 0x7fe1870cd870> >> ignored
    Mar 21 11:34:33 mail1 zarafa-search[1260]: Exception SystemExit: SystemExit('Terminating on signal 15',) in <bound method IMAPISession.<lambda> of <MAPICore.IMAPISession; proxy of <Swig Object of type 'IMAPISession *' at 0x7fe1870cd870> >> ignored
    Mar 21 11:34:33 mail1 zarafa-search[1260]: Exception SystemExit: SystemExit('Terminating on signal 15',) in <bound method IMAPISession.<lambda> of <MAPICore.IMAPISession; proxy of <Swig Object of type 'IMAPISession *' at 0x7fe1870cd870> >> ignored
    Mar 21 11:34:33 mail1 zarafa-search[1260]: Exception SystemExit: SystemExit('Terminating on signal 15',) in <bound method IMAPISession.<lambda> of <MAPICore.IMAPISession; proxy of <Swig Object of type 'IMAPISession *' at 0x7fe1870cd870> >> ignored
    Mar 21 11:34:33 mail1 zarafa-search[1260]: Exception SystemExit: SystemExit('Terminating on signal 15',) in <bound method IMAPISession.<lambda> of <MAPICore.IMAPISession; proxy of <Swig Object of type 'IMAPISession *' at 0x7fe1870cd870> >> ignored
    Mar 21 11:34:33 mail1 zarafa-search[1260]: Exception SystemExit: SystemExit('Terminating on signal 15',) in <bound method IMAPISession.<lambda> of <MAPICore.IMAPISession; proxy of <Swig Object of type 'IMAPISession *' at 0x7fe1870cd870> >> ignored


    If you need more info in this, please contact me.
    Last edited by thctlo; 21-03-2016 at 03:03 PM.

Similar Threads

  1. Z-Push 2.2.4 Beta Feedback
    By 1of16 in forum Z-Push when using Kopano/Zarafa
    Replies: 17
    Last Post: 21-10-2015, 11:17 PM
  2. Z-Push 2.2.3 Beta Feedback
    By 1of16 in forum Z-Push when using Kopano/Zarafa
    Replies: 3
    Last Post: 03-09-2015, 07:11 AM
  3. Feedback WebApp 2.0 beta 2
    By Martyn in forum Beta Feedback
    Replies: 2
    Last Post: 09-12-2014, 02:17 PM
  4. ZCP 7.0.0-beta-1 feedback request
    By Remon in forum Beta Feedback Archives
    Replies: 7
    Last Post: 17-01-2011, 03:04 PM
  5. 6.03 Beta 2 Feedback
    By luis in forum Beta Feedback Archives
    Replies: 3
    Last Post: 10-07-2008, 07:38 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
  •