webapp-3.4.11.1346 login problem

Hi it wants to update the following packages:

Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.dataone.nl
 * epel: mirror.kinamo.be
 * extras: mirror.amsiohosting.net
 * updates: mirror.netrouting.net
Resolving Dependencies
--> Running transaction check
---> Package kopano-backup.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-backup.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-bash-completion.noarch 0:8.6.80.45-84.1 will be updated
---> Package kopano-bash-completion.noarch 0:8.6.80.397-42.1 will be an update
---> Package kopano-client.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-client.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-common.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-common.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-compat.x86_64 0:8.6.80.45-84.1 will be obsoleted
---> Package kopano-contacts.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-contacts.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-dagent.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-dagent.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-debuginfo.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-debuginfo.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-devel.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-devel.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-gateway.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-gateway.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-ical.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-ical.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-lang.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-lang.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-migration-imap.noarch 0:8.6.80.45-84.1 will be updated
---> Package kopano-migration-imap.noarch 0:8.6.80.397-42.1 will be an update
---> Package kopano-migration-pst.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-migration-pst.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-monitor.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-monitor.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-presence.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-presence.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-search.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-search.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-server.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-server.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-server-packages.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-server-packages.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-spamd.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-spamd.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-spooler.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-spooler.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-utils.x86_64 0:8.6.80.45-84.1 will be updated
---> Package kopano-utils.x86_64 0:8.6.80.397-42.1 will be an update
---> Package kopano-webapp-plugin-filesbackend-owncloud.noarch 0:2.1.1.72-48.1 will be updated
---> Package kopano-webapp-plugin-filesbackend-owncloud.noarch 0:2.1.1.74-50.1 will be an update
---> Package kopano-webapp-plugin-intranet.noarch 0:0.1-30.3 will be updated
---> Package kopano-webapp-plugin-intranet.noarch 0:0.1-31.1 will be an update
---> Package kopano-webapp-plugin-mattermost.noarch 0:0.1-12.2 will be updated
---> Package kopano-webapp-plugin-mattermost.noarch 0:0.1-13.1 will be an update
---> Package libkcarchiver0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcarchiver0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libkcarchivercore0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcarchivercore0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libkcfreebusy0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcfreebusy0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libkcicalmapi0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcicalmapi0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libkcinetmapi0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcinetmapi0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libkcmapi0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcmapi0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libkcserver0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcserver0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libkcsoap0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcsoap0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libkcssl0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcssl0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libkcsync0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcsync0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libkcutil0.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libkcutil0.x86_64 0:8.6.80.397-42.1 will be an update
---> Package libmapi1.x86_64 0:8.6.80.45-84.1 will be updated
---> Package libmapi1.x86_64 0:8.6.80.397-42.1 will be an update
---> Package php-mapi.x86_64 0:8.6.80.45-84.1 will be updated
---> Package php-mapi.x86_64 0:8.6.80.397-42.1 will be an update
---> Package python-kopano.x86_64 0:8.6.80.45-84.1 will be obsoleted
---> Package python-mapi.x86_64 0:8.6.80.45-84.1 will be obsoleted
---> Package python2-kopano.x86_64 0:8.6.80.397-42.1 will be obsoleting
---> Package python2-mapi.x86_64 0:8.6.80.397-42.1 will be obsoleting
---> Package python2-zarafa.x86_64 0:8.6.80.397-42.1 will be obsoleting
---> Package whatsapp4deskapp.noarch 0:0.1-4.7 will be updated
---> Package whatsapp4deskapp.noarch 0:0.1-4.8 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package                               Arch   Version         Repository   Size
================================================================================
Installing:
 python2-kopano                        x86_64 8.6.80.397-42.1 Kopano-core 228 k
     replacing  python-kopano.x86_64 8.6.80.45-84.1
 python2-mapi                          x86_64 8.6.80.397-42.1 Kopano-core 380 k
     replacing  python-mapi.x86_64 8.6.80.45-84.1
 python2-zarafa                        x86_64 8.6.80.397-42.1 Kopano-core  10 k
     replacing  kopano-compat.x86_64 8.6.80.45-84.1
Updating:
 kopano-backup                         x86_64 8.6.80.397-42.1 Kopano-core  40 k
 kopano-bash-completion                noarch 8.6.80.397-42.1 Kopano-core  11 k
 kopano-client                         x86_64 8.6.80.397-42.1 Kopano-core 397 k
 kopano-common                         x86_64 8.6.80.397-42.1 Kopano-core  29 k
 kopano-contacts                       x86_64 8.6.80.397-42.1 Kopano-core  44 k
 kopano-dagent                         x86_64 8.6.80.397-42.1 Kopano-core 157 k
 kopano-debuginfo                      x86_64 8.6.80.397-42.1 Kopano-core  23 M
 kopano-devel                          x86_64 8.6.80.397-42.1 Kopano-core 166 k
 kopano-gateway                        x86_64 8.6.80.397-42.1 Kopano-core 141 k
 kopano-ical                           x86_64 8.6.80.397-42.1 Kopano-core 137 k
 kopano-lang                           x86_64 8.6.80.397-42.1 Kopano-core  66 k
 kopano-migration-imap                 noarch 8.6.80.397-42.1 Kopano-core  76 k
 kopano-migration-pst                  x86_64 8.6.80.397-42.1 Kopano-core  79 k
 kopano-monitor                        x86_64 8.6.80.397-42.1 Kopano-core  61 k
 kopano-presence                       x86_64 8.6.80.397-42.1 Kopano-core  22 k
 kopano-search                         x86_64 8.6.80.397-42.1 Kopano-core  50 k
 kopano-server                         x86_64 8.6.80.397-42.1 Kopano-core 296 k
 kopano-server-packages                x86_64 8.6.80.397-42.1 Kopano-core 9.4 k
 kopano-spamd                          x86_64 8.6.80.397-42.1 Kopano-core  20 k
 kopano-spooler                        x86_64 8.6.80.397-42.1 Kopano-core  99 k
 kopano-utils                          x86_64 8.6.80.397-42.1 Kopano-core 252 k
 kopano-webapp-plugin-filesbackend-owncloud
                                       noarch 2.1.1.74-50.1   Kopano-core 181 k
 kopano-webapp-plugin-intranet         noarch 0.1-31.1        Kopano-core  16 k
 kopano-webapp-plugin-mattermost       noarch 0.1-13.1        Kopano-core  19 k
 libkcarchiver0                        x86_64 8.6.80.397-42.1 Kopano-core 106 k
 libkcarchivercore0                    x86_64 8.6.80.397-42.1 Kopano-core 105 k
 libkcfreebusy0                        x86_64 8.6.80.397-42.1 Kopano-core  56 k
 libkcicalmapi0                        x86_64 8.6.80.397-42.1 Kopano-core 118 k
 libkcinetmapi0                        x86_64 8.6.80.397-42.1 Kopano-core 211 k
 libkcmapi0                            x86_64 8.6.80.397-42.1 Kopano-core 116 k
 libkcserver0                          x86_64 8.6.80.397-42.1 Kopano-core 678 k
 libkcsoap0                            x86_64 8.6.80.397-42.1 Kopano-core 258 k
 libkcssl0                             x86_64 8.6.80.397-42.1 Kopano-core  42 k
 libkcsync0                            x86_64 8.6.80.397-42.1 Kopano-core  46 k
 libkcutil0                            x86_64 8.6.80.397-42.1 Kopano-core 133 k
 libmapi1                              x86_64 8.6.80.397-42.1 Kopano-core 200 k
 php-mapi                              x86_64 8.6.80.397-42.1 Kopano-core 201 k
 whatsapp4deskapp                      noarch 0.1-4.8         Kopano-core  16 k

Transaction Summary
================================================================================
Install   3 Packages
Upgrade  38 Packages

Total download size: 28 M

Coffee_is_life

hi @ckruijntjens,

like i said:

—> Package libkcarchiver0.x86_64 0:8.6.80.45-84.1 will be updated
—> Package libkcarchiver0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package libkcarchivercore0.x86_64 0:8.6.80.45-84.1 will be updated
—> Package libkcarchivercore0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package libkcfreebusy0.x86_64 0:8.6.80.45-84.1 will be updated
—> Package libkcfreebusy0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package libkcicalmapi0.x86_64 0:8.6.80.45-84.1 will be updated
—> Package libkcicalmapi0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package libkcinetmapi0.x86_64 0:8.6.80.45-84.1 will be updated
—> Package libkcinetmapi0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package **libkcmapi0.x86_64** 0:8.6.80.45-84.1 will be updated
—> Package libkcmapi0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package **libkcserver0.x86_64** 0:8.6.80.45-84.1 will be updated
—> Package libkcserver0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package **libkcsoap0.x86_64** 0:8.6.80.45-84.1 will be updated
—> Package libkcsoap0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package libkcssl0.x86_64 0:8.6.80.45-84.1 will be updated
—> Package libkcssl0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package libkcsync0.x86_64 0:8.6.80.45-84.1 will be updated
—> Package libkcsync0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package **libkcutil0.x86_64** 0:8.6.80.45-84.1 will be updated
—> Package libkcutil0.x86_64 0:8.6.80.397-42.1 will be an update
—> Package **libmapi1.x86_64** 0:8.6.80.45-84.1 will be updated
—> Package libmapi1.x86_64 0:8.6.80.397-42.1 will be an update
—> Package php-mapi.x86_64 0:8.6.80.45-84.1 will be updated
—> Package php-mapi.x86_64 0:8.6.80.397-42.1 will be an update

these packages wont install (if i remember correctly) if you use “yum update kopano*”
the packages in “**” are the ones that throws the errors in your system

try it on your testsystem and report back

coffee_is_life

fbartels

@ckruijntjens for readability could you use code tags when posting console output? https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#code

@coffee_is_life

Should I update with yum update kopano* then?

Why is a yum update not ok?

@Coffee_is_life

if i do yum update kopano*

No errors when installing but after package installations kopano-spooler is not running anymore

Coffee_is_life

with yum update kopano* you will only update packages with name kopano.
The dependencies are broken, so yum doesnt know that libkc should be installed too.

in the past i observed this issue in previous releases.

my advise is to use “yum update” and update everything from this server or if there are packages which you dont want to upgrade at this moment use

yum update kopano* -y
yum update libkc* -y
yum update libmapi* -y

coffee_is_life

@coffee_is_life

hi i did the above however i cant start the spooler service, can we do something with this error?

*** Error in `/usr/sbin/kopano-spooler’: free(): invalid pointer: 0x00007f61ca708080 ***

@coffee_is_life

yum update libkc* -y “is not available”?

not if i update and not if i want to install the package?

Can dis be the problem?

Coffee_is_life

what does

rpm -qva | grep libkc

say?

and another question, is the Repository “Kopano-Core” enabled by default in your /etc/yum.repos.d/<something>.repo

coffee_is_life

@coffee_is_life

Hi i just restored all to an earlyer version.

rpm -qva | grep libkc output is now:

libkcmapi0-8.6.80.45-84.1.x86_64
libkcsync0-8.6.80.45-84.1.x86_64
libkcicalmapi0-8.6.80.45-84.1.x86_64
libkcutil0-8.6.80.45-84.1.x86_64
libkcfreebusy0-8.6.80.45-84.1.x86_64
libkcinetmapi0-8.6.80.45-84.1.x86_64
libkcarchivercore0-8.6.80.45-84.1.x86_64
libkcserver0-8.6.80.45-84.1.x86_64
libkcssl0-8.6.80.45-84.1.x86_64
libkcsoap0-8.6.80.45-84.1.x86_64
libkcarchiver0-8.6.80.45-84.1.x86_64

If i upgrade to a newer version it stops working on my centos 7 machine.

"

@coffee_is_life
i believe this is the problem. How can i resolve this.

0_1522874581758_487091f7-7310-491d-b89c-82c02fe071ca-image.png

Coffee_is_life

Hello @ckruijntjens,

something like this will do it:

yum reinstall $(repoquery --requires --recursive --resolve <pkg>)

replacing <pkg> wiht the packagename which you want to check (in your case “gperftools-devel”)

coffee_is_life

@coffee_is_life

Hi. What is the problem is the depensie broken?

If I install all packages with rpm -Uvh and the last run with my OWN created repo like above the the spooler wont start anymore.

How can skip the above problems if I create my OWN repo?

Coffee_is_life

since i dont know how you update your own repo its more guessing than straight to the solution…

you could check the state of your own repo, is it up to date?
whats with kopano repo? - does your yum access kopano directly or your cloned one? - is this up to date

after veryfied that you can try to clean everything yum knows:

(before installation)
rpm -qva | grep "kopano\|libkc\|mapi"
(copy the output and save it in some txt file)

yum clean all
yum update kopano* libkc* libmapi*

(after installation)
rpm -qva | grep "kopano\|libkc\|mapi"
(now you can compare the outputs)

additionally your missing files are shipped with gperftools itself (maybe reinstall?)

yum whatprovides */libprofiler.so
gperftools-devel-2.4-8.el7.i686 : Development libraries and headers for gperftools
Quelle      : base
Übereinstimmung von:
Dateiname     : /usr/lib/libprofiler.so

or did your “yum check” solved this particiluar issue?

coffee_is_life

@coffee_is_life

Hi I downloaded the packages From Community download site and created my OWN repo. I dont have a serial so I Can not use a direct repo for kopano.

Coffee_is_life

i just checked the rpm and the cpio file in there, libprofiler.so is inserted so its should be installed properly.
maybe its a corrupt package… - can someone from Kopano-team check that?

does gperftools update within the update process or does it skip this?

coffee_is_life

@coffee_is_life

It slips the package. It inkt installs When —No-deps is used.

Coffee_is_life

and your centos testmachine is a fresh installed kopano with this version? - if yes, the package should not be updated but fresh installed… i think its corrupt and/or not compatible with php56 or something like that…

cant do that much in this case, stay on your version for a little while longer till someone from kopano-team replys here and checked the package…
sorry

coffee_is_life

@coffee_is_life

now it does not skip the package. I think some package is broken,

Apr 05 11:51:43 kopano kopano-spooler[2371]: Thu Apr 5 11:51:43 2018: [crit ] [ 2371] #11. /lib64/libmapi.so.1(+0x36d28) [0x7f433418cd28]
Apr 05 11:51:43 kopano kopano-spooler[2371]: Thu Apr 5 11:51:43 2018: [crit ] [ 2371] #12. /lib64/libmapi.so.1(ZN2KC15HrOpenECSessionEPP12IMAPISessionPKcS4_PKwS6_S4_jS4_S4_S4+0…7f433418d256]
Apr 05 11:51:43 kopano kopano-spooler[2371]: Thu Apr 5 11:51:43 2018: [crit ] [ 2371] #13. /lib64/libmapi.so.1(ZN2KC20HrOpenECAdminSessionEPP12IMAPISessionPKcS4_S4_jS4_S4+0x20)…7f433418d450]
Apr 05 11:51:43 kopano kopano-spooler[2371]: Thu Apr 5 11:51:43 2018: [crit ] [ 2371] #14. /usr/sbin/kopano-spooler() [0x409e4f]
Apr 05 11:51:43 kopano kopano-spooler[2371]: Thu Apr 5 11:51:43 2018: [crit ] [ 2371] #15. /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f432f1d3c05]
Apr 05 11:51:43 kopano kopano-spooler[2371]: Thu Apr 5 11:51:43 2018: [crit ] [ 2371] #16. /usr/sbin/kopano-spooler() [0x40b0ff]
Apr 05 11:51:43 kopano kopano-spooler[2371]: Thu Apr 5 11:51:43 2018: [crit ] [ 2371] Signal errno: Success, signal code: -6
Apr 05 11:51:43 kopano kopano-spooler[2371]: Thu Apr 5 11:51:43 2018: [crit ] [ 2371] Sender pid: 2371, sender uid: 997, si_status: 0
Apr 05 11:51:43 kopano kopano-spooler[2371]: Thu Apr 5 11:51:43 2018: [crit ] [ 2371] Signal value: 0, faulting address: 0x3e500000943
Apr 05 11:51:43 kopano kopano-spooler[2371]: Thu Apr 5 11:51:43 2018: [crit ] [ 2371] When reporting this traceback, please include Linux distribution name (and version), system …pano version.

However libmapi.so.1 is installed!

libmapi1-8.6.80.493-50.1.x86_64 : Kopano’s implementation of the Messaging API
Repo : Kopano
Matched from:
Filename : /usr/lib64/libmapi.so.1

fbartels

i’d guess this is related to https://forum.kopano.io/topic/1254/segmentation-fault/. We already did some investigation in that matter and found https://bugzilla.redhat.com/show_bug.cgi?id=1519073 as the potential issue.

No Jira ticket on our side yet, though.

Edit: still no Jira ticket, but a proposed fix is in pr #1864