Community Forum

Resolved
0 votes
Hi,

I want to install the EWS funtion on my ClearOS7.3 server with Zarafa, but there is only a version 7.2.4 available from Zarafa portal and we are still at version 7.2.1
Is there a version 7.2.1 somewhere available ?
I see in the roadmap there will be a upgrade to 7.2.4 (7.4), but does anybody know when this can be expected ? https://tracker.clearos.com/view.php?id=10471
Friday, February 03 2017, 02:06 PM
Share this post:

Accepted Answer

Saturday, February 11 2017, 05:00 PM - #Permalink
Resolved
0 votes
Ben Chambers wrote:


Yup...your old instance of Zarafa ran with root permissions. Let's not stray from that for now.

Edit /etc/zarafa/server.cfg

and set:

run_as_user = root

# drop privileges and run the process as this group
run_as_group = root




Ben,

this did the trick !!!!!

Thank you very much (again)
The reply is currently minimized Show
Responses (16)
  • Accepted Answer

    Friday, September 15 2017, 07:46 AM - #Permalink
    Resolved
    0 votes
    Hi Ben,

    The mail server is running again.
    I've removed Zarafa completely and re-installed Zarafa 7.2.0..
    The Zarafa-server doesn't start, due to a database version conflict (7.2.6 vs 7.2.0)

    After searching the web, i've found a solution. (LINK
    zarafa-server --ignore-database-version-conflict


    The only thing is that i need to start Zarafa-server manually.
    Is the database conflict solvable ?? or is the upgrade to 7.2.6 possible
    The reply is currently minimized Show
  • Accepted Answer

    Monday, September 11 2017, 02:44 PM - #Permalink
    Resolved
    0 votes
    Ben Chambers wrote:

    Hi Patrick,

    app-core-community


    This must be a typo...I don't think there is an RPM with this name.

    Can you post all of your shell output where you're getting stumped...I'll see if I can spot something.

    B

    Hi Ben,

    correct... typo ;-)

    It is package "app-zarafa-community-core" which caused the problem. Installing this app is taking a very long time, but the system resource don't show any activity.

    The system is not down, because the mail server doesn't work.
    Zarafa-dagent won't start any more and therefor zarafa-server.
    I'll check the log files and come back shortly.

    How can i drop the zarafa database ?
    I've tried setup a testserver, but i looks that the database isn't correct after import and installing 7.2.6 (after the stop command at app-zarafa-core)
    The reply is currently minimized Show
  • Accepted Answer

    Monday, September 11 2017, 01:54 PM - #Permalink
    Resolved
    0 votes
    Hi Patrick,

    app-core-community


    This must be a typo...I don't think there is an RPM with this name.

    Can you post all of your shell output where you're getting stumped...I'll see if I can spot something.

    B
    The reply is currently minimized Show
  • Accepted Answer

    Monday, September 11 2017, 06:58 AM - #Permalink
    Resolved
    0 votes
    Hi Ben,

    I've done the update on another server with Zarafa 7.2.0.
    The update in repo is now Zarafa 7.2.6, but it fails to install app-core-community. After more than a hours, i stopped the process.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 11 2017, 05:01 PM - #Permalink
    Resolved
    0 votes
    Ben Chambers wrote:

    You should pull or edit some of those config files you posted...they contain some passwords you probably don't want out in public.

    B


    Done !!
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 11 2017, 04:54 PM - #Permalink
    Resolved
    0 votes
    You should pull or edit some of those config files you posted...they contain some passwords you probably don't want out in public.

    B
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 11 2017, 04:53 PM - #Permalink
    Resolved
    0 votes
    I hope this helps.


    Yup...your old instance of Zarafa ran with root permissions. Let's not stray from that for now.

    Edit /etc/zarafa/server.cfg

    and set:

    run_as_user = root

    # drop privileges and run the process as this group
    run_as_group = root



    And restart zarafa-server.

    If you want i can give you access to the server. Makes it much easier for you to help


    Sure...I'm OK with that. Use this link

    B
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 11 2017, 04:25 PM - #Permalink
    Resolved
    0 votes
    Ben,

    ls -l /var/lib/zarafa/attachments
    total 40
    drwxr-xr-x 22 root root 4096 May 7 2016 0
    drwxr-xr-x 22 root root 4096 May 7 2016 1
    drwxr-xr-x 22 root root 4096 May 7 2016 2
    drwxr-xr-x 22 root root 4096 May 7 2016 3
    drwxr-xr-x 22 root root 4096 May 7 2016 4
    drwxr-xr-x 22 root root 4096 May 7 2016 5
    drwxr-xr-x 22 root root 4096 May 7 2016 6
    drwxr-xr-x 22 root root 4096 May 7 2016 7
    drwxr-xr-x 22 root root 4096 May 7 2016 8
    drwxr-xr-x 22 root root 4096 May 7 2016 9


    server.cfg
    at Feb 11 16:55:45 2017: [error  ] Error while connecting to search on "file:///var/run/zarafad/search.sock"
    Sat Feb 11 16:56:17 2017: [error ] Previous message logged 35 times
    Sat Feb 11 16:56:17 2017: [error ] Unable to open attachment "/var/lib/zarafa/attachments/6/11/22516" for writing: Permission denied
    Sat Feb 11 16:58:00 2017: [error ] Not all objects in relation found for object "patrick"
    Sat Feb 11 16:58:31 2017: [error ] Unable to open attachment "/var/lib/zarafa/attachments/7/11/22517" for writing: Permission denied
    Sat Feb 11 17:00:04 2017: [error ] ECFileAttachment::Commit() error during commit
    Sat Feb 11 17:00:04 2017: [error ] Error while removing softdelete message objects, error code: 0x80000007.
    Sat Feb 11 17:01:03 2017: [error ] Unable to open attachment "/var/lib/zarafa/attachments/8/11/22518" for writing: Permission denied
    Sat Feb 11 17:06:19 2017: [error ] Error while connecting to search on "file:///var/run/zarafad/search.sock"
    Sat Feb 11 17:13:00 2017: [error ] Previous message logged 27 times
    Sat Feb 11 17:13:00 2017: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
    Sat Feb 11 17:22:03 2017: [error ] Unable to gzopen attachment "/var/lib/zarafa/attachments/9/11/22519.gz" for writing: Permission denied
    Sat Feb 11 17:23:14 2017: [error ] Unable to gzopen attachment "/var/lib/zarafa/attachments/0/12/22520.gz" for writing: Permission denied
    Sat Feb 11 17:28:00 2017: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
    Sat Feb 11 17:31:37 2017: [error ] Error while connecting to search on "file:///var/run/zarafad/search.sock"


    the logfiles:
    server.cfg
    server.cfg.rpmsave
    search.cfg
    search.cfg.rpmsave
    mail.cfg
    messages.cfg

    I hope this helps.
    If you want i can give you access to the server. Makes it much easier for you to help
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 11 2017, 04:17 PM - #Permalink
    Resolved
    0 votes
    For Zarafa search, did you make the changes to /etc/zarafa/search.cfg?

    That wouldn't be stopping mail from flowing though...

    For the permissions error, can you post your /etc/zarafa/server.cfg file.

    Do you have /etc/zarafa/server.cfg and /etc/zarafa/server.cfg.rpmnew ? Wonder if Zarafa moved the locations between versions. What is the permissions on your zarafa attachments folder?

    ls -l /var/lib/zarafa/attachments


    The more info you can add to your posts, the less 'back-and-forth' and quicker a resolution can be found.

    B
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 11 2017, 03:54 PM - #Permalink
    Resolved
    0 votes
    Ben,

    I'm not able to receive or send any mail.
    Please your help with this.

    messages.log
    Feb 11 16:50:41 pdebrabander systemd: Cannot add dependency job for unit microcode.service, ignoring: Unit is not loaded properly: Invalid argument.
    Feb 11 16:50:41 pdebrabander zarafa-search: 2017-02-11 16:50:41,577 - search - INFO - stopping search
    Feb 11 16:50:41 pdebrabander zarafa-search: Terminating on signal 15
    Feb 11 16:50:41 pdebrabander zarafa-search: Exception SystemExit: 0 in <bound method IMAPISession.<lambda> of <MAPICore.IMAPISession; proxy of <Swig Object of type 'IMAPISession *' at 0x1a19d20> >> ignored
    Feb 11 16:50:41 pdebrabander systemd: zarafa-search.service: main process exited, code=exited, status=1/FAILURE
    Feb 11 16:50:41 pdebrabander systemd: Unit zarafa-search.service entered failed state.
    Feb 11 16:50:41 pdebrabander systemd: zarafa-search.service failed.
    Feb 11 16:50:41 pdebrabander zarafa-search: 2017-02-11 16:50:41,780 - search - INFO - starting search
    Feb 11 16:50:41 pdebrabander zarafa-search: 2017-02-11 16:50:41,827 - search - INFO - found previous server sync state: 01000000A86E0100
    Feb 11 16:50:41 pdebrabander zarafa-search: 2017-02-11 16:50:41,830 - search - INFO - starting incremental sync
    Feb 11 16:50:41 pdebrabander zarafa-search: 2017-02-11 16:50:41,853 - query - INFO - listening on socket file:///var/run/zarafad/search.sock
    Feb 11 16:50:46 pdebrabander systemd: Cannot add dependency job for unit microcode.service, ignoring: Unit is not loaded properly: Invalid argument.
    Feb 11 16:50:47 pdebrabander zarafa-search: Sat Feb 11 16:50:47 2017: [error ] M4LMsgServiceAdmin::ConfigureMsgService() MSGServiceEntry failed 80040115: network error
    Feb 11 16:50:47 pdebrabander zarafa-search: 2017-02-11 16:50:47,876 - search - WARNING - could not connect to server at 'default:', retrying in 5 sec


    /var/log/zarafa/server.log
    Sat Feb 11 16:55:45 2017: [error  ] Error while connecting to search on "file:///var/run/zarafad/search.sock"
    Sat Feb 11 16:56:17 2017: [error ] Previous message logged 35 times
    Sat Feb 11 16:56:17 2017: [error ] Unable to open attachment "/var/lib/zarafa/attachments/6/11/22516" for writing: Permission denied
    Sat Feb 11 16:58:00 2017: [error ] Not all objects in relation found for object "patrick"
    Sat Feb 11 16:58:31 2017: [error ] Unable to open attachment "/var/lib/zarafa/attachments/7/11/22517" for writing: Permission denied
    Sat Feb 11 17:00:04 2017: [error ] ECFileAttachment::Commit() error during commit
    Sat Feb 11 17:00:04 2017: [error ] Error while removing softdelete message objects, error code: 0x80000007.
    Sat Feb 11 17:01:03 2017: [error ] Unable to open attachment "/var/lib/zarafa/attachments/8/11/22518" for writing: Permission denied
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 11 2017, 02:45 PM - #Permalink
    Resolved
    0 votes
    Patrick,

    This:

    [code]
    * private-clearcenter-zarafa-community: download2.clearsdn.com:80
    * private-clearcenter-zarafa-community-testing: download4.clearsdn.com:80
    [/code[

    Suggests to me that you don't have a Zarafa small business license, but instead, Zarafa community license.

    So, in your case, substitute app-zarafa-small-business with app-zarafa-community

    B.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 11 2017, 02:05 PM - #Permalink
    Resolved
    0 votes
    **************** UPDATE ****************

    Hi Ben,

    It looks that over the past time due severall updates and testing packages the system was "contaminated" and is yum not able to remove some packages.
    I did a rough removal of all the zarafa packages with the help of this website http://serverfault.com/questions/613256/yum-error-in-preun-scriptlet-when-removing-packages

    After removing using "yum --setopt=tsflags=noscripts remove zarafa* " i could install Zarafa again.

    the only error is still : No package app-zarafa-small-business available.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 11 2017, 12:21 PM - #Permalink
    Resolved
    0 votes
    Hi Ben,

    I'm trying the update, but see the following errors:

    ENABLE_BETA=True yum --disablerepo=clearos-epel upgrade app-zarafa-small-business zarafa-server
    Loaded plugins: clearcenter-marketplace, fastestmirror
    ClearCenter Marketplace: fetching repositories...
    Loading mirror speeds from cached hostfile
    * clearos: mirror1-frankfurt.clearos.com
    * clearos-centos-verified: mirror1-frankfurt.clearos.com
    * clearos-centos-verified-testing: mirror1-frankfurt.clearos.com
    * clearos-contribs: mirror1-frankfurt.clearos.com
    * clearos-epel-verified: mirror1-frankfurt.clearos.com
    * clearos-epel-verified-testing: mirror1-frankfurt.clearos.com
    * clearos-fast-updates: download2.clearsdn.com
    * clearos-infra: mirror1-frankfurt.clearos.com
    * clearos-qa: mirror2.egloo.ca
    * clearos-verified: mirror1-frankfurt.clearos.com
    * private-clearcenter-antimalware: download2.clearsdn.com:80
    * private-clearcenter-antispam: download4.clearsdn.com:80
    * private-clearcenter-content-filter: download2.clearsdn.com:80
    * private-clearcenter-dyndns: download2.clearsdn.com:80
    * private-clearcenter-home: download2.clearsdn.com:80
    * private-clearcenter-ids: download2.clearsdn.com:80
    * private-clearcenter-owncloud: download4.clearsdn.com:80
    * private-clearcenter-rbs: download2.clearsdn.com:80
    * private-clearcenter-remote-backup-testing: download2.clearsdn.com:80
    * private-clearcenter-verified-updates: download4.clearsdn.com:80
    * private-clearcenter-zarafa-community: download2.clearsdn.com:80
    * private-clearcenter-zarafa-community-testing: download4.clearsdn.com:80
    No Match for argument: app-zarafa-small-business
    No package app-zarafa-small-business available.


    Running transaction
    Erasing : 1:app-zarafa-community-2.1.17-1.v7.noarch 1/20
    Erasing : 1:app-zarafa-2.1.20-1.v7.noarch 2/20
    Erasing : 1:app-zarafa-community-core-2.1.17-1.v7.noarch 3/20
    Erasing : 1:app-zarafa-core-2.1.20-1.v7.noarch 4/20
    Erasing : zarafa-server-packages-7.2.0.48204-211.1.x86_64 5/20
    /var/tmp/rpm-tmp.fqsR8L: line 1: fg: no job control
    error: %preun(zarafa-search-plus-7.2.0.48204-211.1.x86_64) scriptlet failed, exit status 1
    Error in PREUN scriptlet in rpm package zarafa-search-plus-7.2.0.48204-211.1.x86_64
    Erasing : zarafa-webaccess-7.2.0.48204-211.1.x86_64 6/20
    error: zarafa-search-plus-7.2.0.48204-211.1.x86_64: erase failed
    warning: /etc/zarafa/webaccess-ajax/config.php saved as /etc/zarafa/webaccess-ajax/config.php.rpmsave
    warning: /etc/httpd/conf.d/zarafa-webaccess.conf saved as /etc/httpd/conf.d/zarafa-webaccess.conf.rpmsave
    /var/tmp/rpm-tmp.dDfN7I: line 1: fg: no job control
    error: %preun(zarafa-presence-7.2.0.48204-211.1.x86_64) scriptlet failed, exit status 1
    Error in PREUN scriptlet in rpm package zarafa-presence-7.2.0.48204-211.1.x86_64
    Erasing : python-zarafa-7.2.0.48204-211.1.x86_64 7/20
    error: zarafa-presence-7.2.0.48204-211.1.x86_64: erase failed
    Erasing : zarafa-webapp-plugins-delayeddelivery-1.0.22-70.1.noarch 8/20
    Erasing : zarafa-webapp-2.2.1.43-199.1.noarch 9/20
    warning: /usr/share/zarafa-webapp/.htaccess saved as /usr/share/zarafa-webapp/.htaccess.rpmsave
    warning: /etc/httpd/conf.d/zarafa-webapp.conf saved as /etc/httpd/conf.d/zarafa-webapp.conf.rpmsave
    Erasing : zarafa-webapp-compat_zcp-2.2.0-0.noarch 10/20
    Erasing : php-mapi-7.2.0.48204-211.1.x86_64 11/20
    Erasing : zarafa-contacts-7.2.0.48204-211.1.x86_64 12/20
    Erasing : python-mapi-7.2.0.48204-211.1.x86_64 13/20
    /var/tmp/rpm-tmp.Bh7bgH: line 1: fg: no job control
    error: %preun(zarafa-dagent-7.2.0.48204-211.1.x86_64) scriptlet failed, exit status 1
    Error in PREUN scriptlet in rpm package zarafa-dagent-7.2.0.48204-211.1.x86_64
    error: zarafa-dagent-7.2.0.48204-211.1.x86_64: erase failed
    /var/tmp/rpm-tmp.ihNNsF: line 1: fg: no job control
    error: %preun(zarafa-spooler-7.2.0.48204-211.1.x86_64) scriptlet failed, exit status 1
    Error in PREUN scriptlet in rpm package zarafa-spooler-7.2.0.48204-211.1.x86_64
    Erasing : zarafa-utils-7.2.0.48204-211.1.x86_64 14/20
    error: zarafa-spooler-7.2.0.48204-211.1.x86_64: erase failed
    Erasing : zarafa-libarchiver-7.2.0.48204-211.1.x86_64 15/20
    Erasing : zarafa-client-7.2.0.48204-211.1.x86_64 16/20
    Verifying : zarafa-webapp-plugins-delayeddelivery-1.0.22-70.1.noarch 1/20
    Verifying : zarafa-client-7.2.0.48204-211.1.x86_64 2/20
    Verifying : 1:app-zarafa-community-core-2.1.17-1.v7.noarch 3/20
    Verifying : 1:app-zarafa-2.1.20-1.v7.noarch 4/20
    Verifying : zarafa-utils-7.2.0.48204-211.1.x86_64 5/20
    Verifying : zarafa-webapp-2.2.1.43-199.1.noarch 6/20
    Verifying : python-zarafa-7.2.0.48204-211.1.x86_64 7/20
    Verifying : zarafa-presence-7.2.0.48204-211.1.x86_64 8/20
    Verifying : zarafa-libarchiver-7.2.0.48204-211.1.x86_64 9/20
    Verifying : php-mapi-7.2.0.48204-211.1.x86_64 10/20
    Verifying : 1:app-zarafa-community-2.1.17-1.v7.noarch 11/20
    Verifying : zarafa-dagent-7.2.0.48204-211.1.x86_64 12/20
    Verifying : zarafa-webapp-compat_zcp-2.2.0-0.noarch 13/20
    Verifying : zarafa-contacts-7.2.0.48204-211.1.x86_64 14/20
    Verifying : zarafa-webaccess-7.2.0.48204-211.1.x86_64 15/20
    Verifying : zarafa-spooler-7.2.0.48204-211.1.x86_64 16/20
    Verifying : zarafa-search-plus-7.2.0.48204-211.1.x86_64 17/20
    Verifying : zarafa-server-packages-7.2.0.48204-211.1.x86_64 18/20
    Verifying : python-mapi-7.2.0.48204-211.1.x86_64 19/20
    Verifying : 1:app-zarafa-core-2.1.20-1.v7.noarch 20/20

    Removed:
    zarafa-client.x86_64 0:7.2.0.48204-211.1 zarafa-webaccess.x86_64 0:7.2.0.48204-211.1

    Dependency Removed:
    app-zarafa.noarch 1:2.1.20-1.v7 app-zarafa-community.noarch 1:2.1.17-1.v7
    app-zarafa-community-core.noarch 1:2.1.17-1.v7 app-zarafa-core.noarch 1:2.1.20-1.v7
    php-mapi.x86_64 0:7.2.0.48204-211.1 python-mapi.x86_64 0:7.2.0.48204-211.1
    python-zarafa.x86_64 0:7.2.0.48204-211.1 zarafa-contacts.x86_64 0:7.2.0.48204-211.1
    zarafa-libarchiver.x86_64 0:7.2.0.48204-211.1 zarafa-server-packages.x86_64 0:7.2.0.48204-211.1
    zarafa-utils.x86_64 0:7.2.0.48204-211.1 zarafa-webapp.noarch 0:2.2.1.43-199.1
    zarafa-webapp-compat_zcp.noarch 0:2.2.0-0 zarafa-webapp-plugins-delayeddelivery.noarch 0:1.0.22-70.1

    Failed:
    zarafa-dagent.x86_64 0:7.2.0.48204-211.1 zarafa-presence.x86_64 0:7.2.0.48204-211.1 zarafa-search-plus.x86_64 0:7.2.0.48204-211.1
    zarafa-spooler.x86_64 0:7.2.0.48204-211.1




    ** Found 6 pre-existing rpmdb problem(s), 'yum check' output follows:
    zarafa-dagent-7.2.0.48204-211.1.x86_64 has missing requires of libarchiver-core.so.0()(64bit)
    zarafa-dagent-7.2.0.48204-211.1.x86_64 has missing requires of libarchiver.so.0()(64bit)
    zarafa-presence-7.2.0.48204-211.1.x86_64 has missing requires of python-zarafa
    zarafa-search-plus-7.2.0.48204-211.1.x86_64 has missing requires of python-zarafa
    zarafa-spooler-7.2.0.48204-211.1.x86_64 has missing requires of libarchiver-core.so.0()(64bit)
    zarafa-spooler-7.2.0.48204-211.1.x86_64 has missing requires of libarchiver.so.0()(64bit)


    I've remove manually the failed packages :
    zarafa-dagent.x86_64 0:7.2.0.48204-211.1
    zarafa-presence.x86_64 0:7.2.0.48204-211.1
    zarafa-search-plus.x86_64 0:7.2.0.48204-211.1
    zarafa-spooler.x86_64 0:7.2.0.48204-211.1

    i'm running Clearos 7.3 and using the Home essential edition with Zarafa Home edition.
    I see now that the upgrade is for app-zarafa-small-business. Is this correct
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, February 05 2017, 03:06 AM - #Permalink
    Resolved
    0 votes
    Hi Ben,

    Thanks for the quick reply.
    I'm currently travelling abroad (Korea), so I will no be able to test it now.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 04 2017, 07:56 PM - #Permalink
    Resolved
    0 votes
    Hi Patrick,

    I had a chance to sanity check the procedure above. Worked great except for one thing...at the end, edit /etc/zarafa/search.cfg

    and look for:


    #run_as_user = zarafa
    #run_as_user = zarafa


    to


    run_as_user = root
    run_as_user = root


    Note...don't forget/miss the fact that you have to remove the preceding hash (#).

    Then restart zarafa-search
    service zarafa-search restart


    Here's the versions I ended up with:


    # rpm -qv zarafa-server
    zarafa-server-7.2.4.29-99.1.x86_64
    # rpm -qv zarafa-webapp
    zarafa-webapp-2.2.1.43-199.1.noarch


    Does that help?

    B.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, February 03 2017, 08:28 PM - #Permalink
    Resolved
    0 votes
    Patrick,

    We have made 7.2.4 available in the test repositories.

    If you are running 7.2.1 with Zarafa, the instructions to upgrade are:


    yum remove zarafa-webaccess zarafa-client
    ENABLE_BETA=True yum --disablerepo=clearos-epel upgrade app-zarafa-small-business zarafa-server
    ENABLE_BETA=True yum --disablerepo=clearos-epel install app-zarafa-small-business app-zarafa
    /usr/clearos/apps/zarafa/deploy/zarafa-7.2.0.48204-cleanup
    /usr/clearos/apps/zarafa/deploy/upgrade
    service httpd restart


    Your data/mail on the upgrade from 7.2.x to 7.2.4 will remain, of course.

    Our apologies for the unusually 'crude' upgrade practice...it is through no fault of our own, but an issue with Zarafa's packaging of RPM's.

    I know that the migration from 7.2.1 to 7.2.4 is OK...I've done it twice. However, I do recall that I had some difficulties with my own notes and ran into some dependency issues and I may not have updated my notes above. I'll try and get a VM up and run it though over the weekend to see if I can fill in any gaps I may have forgotten. The migration to ClearOS 7.3 (CentOS 7.3) and the state of our repos may complicate thing further...dunno.

    B.
    The reply is currently minimized Show
Your Reply