Results 1 to 4 of 4

Thread: zarafa update from 7.2.1-51838 to 7.2.5.109

  1. #1

    zarafa update from 7.2.1-51838 to 7.2.5.109

    Hi there folks.

    I am in a bit of dilemma.
    Up to this morning I was successfully running 7.2.1-51838
    It thought I shoudl upgrade to the latest version... downloaded the packages... and installed via dpkg -i

    now the new version does not run any more..

    errors like this are coming up:
    Sun Feb 26 09:34:49 2017: [crit ] Unable to bind to socket /var/run/zarafa-prio (Address already in use). This is usually caused by another process (most likely another zarafa-server) already using this port. This program will terminate now.


    When checking via lsof I cannot see any programm using this port.


    Can anyone help me here, please !?
    Thanks
    M

  2. #2
    Zarafa

    Join Date
    Jan 2009
    Location
    Hanover, Germany
    Posts
    1,891
    Inbetween the default location for sockets and pids and the run_user has changed. The error you posted can theoretically also be thrown, when the socket cannot be created in the first place (since a normal user cannot write to /var/run).

    More info:

    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.

  3. #3
    I also was thinking of a permission problem. and changed in the
    server.cfg
    from: #run_as_user = zarafa
    to : run_as_user = root

    and it is running again.
    I also see that it is still running with the zarafa user I originally created.

    # ps -ef | grep zarafa
    zarafa 722 1 0 10:34 ? 00:00:00 /usr/sbin/zarafa-dagent -d -c /etc/zarafa/dagent.cfg
    zarafa 724 722 0 10:34 ? 00:00:00 /usr/sbin/zarafa-dagent -d -c /etc/zarafa/dagent.cfg
    zarafa 772 1 0 10:34 ? 00:00:00 /usr/sbin/zarafa-ical -c /etc/zarafa/ical.cfg
    zarafa 774 772 0 10:34 ? 00:00:00 /usr/sbin/zarafa-ical -c /etc/zarafa/ical.cfg
    zarafa 798 1 0 10:34 ? 00:00:00 /usr/sbin/zarafa-licensed -c /etc/zarafa/licensed.cfg
    zarafa 823 1 0 10:34 ? 00:00:00 /usr/sbin/zarafa-monitor -c /etc/zarafa/monitor.cfg
    zarafa 849 1 0 10:34 ? 00:00:00 /usr/bin/python /usr/sbin/zarafa-presence
    zarafa 934 1 0 10:34 ? 00:00:00 /usr/sbin/zarafa-spooler -c /etc/zarafa/spooler.cfg
    zarafa 936 934 0 10:34 ? 00:00:00 /usr/sbin/zarafa-spooler -c /etc/zarafa/spooler.cfg
    root 1204 1 0 10:35 ? 00:00:00 /usr/sbin/zarafa-server -c /etc/zarafa/server.cfg

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

    ... and thanks for the quick answer and help on this matter!!

  4. #4
    Member
    Join Date
    Dec 2010
    Location
    Wr. Neustadt, Austria
    Posts
    51
    The zarafa server process did not stop completely. I have seen this issue many times.
    try a "ps -ax | grep zarafa-server" and kill the running zarafa-server process.
    Regards

    Walter

Similar Threads

  1. problem with new installation 7.2.1-51838-rhel-6-x86_64
    By zilkanir in forum Installation, Configuration and Maintenance
    Replies: 2
    Last Post: 17-08-2016, 10:35 AM
  2. Zarafa 7.2.0.48204 to 7.2.1.51838 failed with many dependencies ...
    By [email protected] in forum Installation, Configuration and Maintenance
    Replies: 2
    Last Post: 26-01-2016, 03:06 PM
  3. Replies: 2
    Last Post: 06-01-2016, 12:51 PM
  4. Replies: 3
    Last Post: 21-07-2015, 10:00 AM
  5. Zarafa 6.40.2 Update to 6.40.3
    By ruecki016 in forum Installation and Configuration Archives
    Replies: 1
    Last Post: 01-11-2010, 07:11 AM

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
  •