Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#907396: kopano-server: Tools all fail with: MAPI error 80040111 (MAPI_E_LOGON_FAILED)

43 views
Skip to first unread message

Teun Kloosterman

unread,
Aug 27, 2018, 10:50:03 AM8/27/18
to
Package: kopano-server
Version: 8.6.5-1
Severity: important

Dear Maintainer,

Trying to get Kopano to run, but all tools fail with:
root$ kopano-cli --create-store
[error ] virtual HRESULT M4LMAPISession::OpenMsgStore(ULONG_PTR, ULONG, const ENTRYID*, LPCIID, ULONG, IMsgStore**): msp>Logon failed: logon failed (80040111)MAPI error 80040111 (MAPI_E_LOGON_FAILED)

On the forum they state that: [SOLVED] in kopanocore-8.6.80.1420-1.x86_64 built from sources
https://forum.kopano.io/topic/1522/solved-db-backend-kopano-cli-mapi-error-80040111-mapi_e_logon_failed/9

-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kopano-server depends on:
ii dbconfig-common 2.0.9
ii debconf [debconf-2.0] 1.5.69
ii kopano-common 8.6.5-1
ii kopano-libs 8.6.5-1
ii libc6 2.27-5
ii libcom-err2 1.44.3-1
ii libgcc1 1:8.2.0-4
ii libgsoap-2.8.60 2.8.60-2
ii libgssapi-krb5-2 1.16-2
ii libicu60 60.2-6
ii libk5crypto3 1.16-2
ii libkrb5-3 1.16-2
ii libldap-2.4-2 2.4.46+dfsg-5
ii libmariadbclient18 1:10.1.35-1
ii libpam0g 1.1.8-3.8
ii libssl1.1 1.1.0h-4
ii libstdc++6 8.2.0-4
ii libuuid1 2.32.1-0.1
ii lsb-base 9.20170808
ii mariadb-client 1:10.1.35-1
ii mariadb-client-10.1 [virtual-mysql-client] 1:10.1.35-1
ii zlib1g 1:1.2.11.dfsg-1

Versions of packages kopano-server recommends:
ii mariadb-server 1:10.1.35-1

kopano-server suggests no packages.

-- debconf information:
kopano-server/mysql/admin-pass: (password omitted)
kopano-server/password-confirm: (password omitted)
kopano-server/mysql/app-pass: (password omitted)
kopano-server/app-password-confirm: (password omitted)
kopano-server/remote/host: localhost
* kopano-server/mysql/admin-user: root
* kopano-server/dbconfig-install: true
* kopano-server/install-error: ignore
* kopano-server/db/dbname: kopanoserver
kopano-server/internal/skip-preseed: false
kopano-server/database-type: mysql
kopano-server/remote/port:
kopano-server/internal/reconfiguring: false
* kopano-server/passwords-do-not-match:
kopano-server/remote/newhost:
kopano-server/dbconfig-upgrade: true
kopano-server/upgrade-backup: true
kopano-server/purge: false
* kopano-server/dbconfig-reinstall: true
* kopano-server/mysql/method: Unix socket
* kopano-server/db/app-user: kopano-server@localhost
kopano-server/missing-db-package-error: abort
kopano-server/dbconfig-remove: true
kopano-server/upgrade-error: abort
kopano-server/remove-error: abort

Carsten Schoenert

unread,
Sep 1, 2018, 6:40:03 AM9/1/18
to
severity -1 serious
affects -1 icu

Hello Teun,

On Mon, Aug 27, 2018 at 04:42:31PM +0200, Teun Kloosterman wrote:
> Trying to get Kopano to run, but all tools fail with:
> root$ kopano-cli --create-store
> [error ] virtual HRESULT M4LMAPISession::OpenMsgStore(ULONG_PTR, ULONG, const ENTRYID*, LPCIID, ULONG, IMsgStore**): msp>Logon failed: logon failed (80040111)MAPI error 80040111 (MAPI_E_LOGON_FAILED)
>
> On the forum they state that: [SOLVED] in kopanocore-8.6.80.1420-1.x86_64 built from sources
> https://forum.kopano.io/topic/1522/solved-db-backend-kopano-cli-mapi-error-80040111-mapi_e_logon_failed/9

unfortunately I can confirm the behaviour you see.
Understanding the link you providing correctly we would need libicu61
which kopano needs to be linked against. Debian currently is only
providing version 60.2 in unstable and testing. I opened up a whishlist
bug for packaging a recent version into Debian [1].

OTOH also the configure script in 8.6.5 and .7 isn't detecting this
requirement, this is an upstream issue which should be added to the
autotools setup for kopano-core.

@Jan
What's your opinion on this? Anything we can do here in Debian to work
around? ICU will probably not be available in the required version in
the near future based on the experience of updating ICU in the past.

[1] https://bugs.debian.org/907748

Regards
Carsten

Jan Engelhardt

unread,
Sep 1, 2018, 7:20:03 AM9/1/18
to

On Saturday 2018-09-01 12:32, Carsten Schoenert wrote:

>severity -1 serious
>affects -1 icu
>
>Hello Teun,
>
>On Mon, Aug 27, 2018 at 04:42:31PM +0200, Teun Kloosterman wrote:
>> Trying to get Kopano to run, but all tools fail with:
>> root$ kopano-cli --create-store
>> [error ] virtual HRESULT M4LMAPISession::OpenMsgStore(ULONG_PTR, ULONG, const ENTRYID*, LPCIID, ULONG, IMsgStore**): msp>Logon failed: logon failed (80040111)MAPI error 80040111 (MAPI_E_LOGON_FAILED)
>>
>> On the forum they state that: [SOLVED] in kopanocore-8.6.80.1420-1.x86_64 built from sources
>> https://forum.kopano.io/topic/1522/solved-db-backend-kopano-cli-mapi-error-80040111-mapi_e_logon_failed/9
>
>unfortunately I can confirm the behaviour you see.

But what ARE you doing? The report is just way too fucking confusing,
making jumps between LFS and then Fedora and then back... damn.

>Understanding the link you providing correctly we would need libicu61
>which kopano needs to be linked against. Debian currently is only
>providing version 60.2 in unstable and testing. I opened up a whishlist
>bug for packaging a recent version into Debian [1].
>OTOH also the configure script in 8.6.5 and .7 isn't detecting this
>requirement, this is an upstream issue which should be added to the
>autotools setup for kopano-core.

There is no requirement on a particular ICU version!
It is even buildable with the very old ICU 4.2 from RHEL6.

Carsten Schoenert

unread,
Sep 1, 2018, 7:40:03 AM9/1/18
to
On Sat, Sep 01, 2018 at 01:00:12PM +0200, Jan Engelhardt wrote:
> >> On the forum they state that: [SOLVED] in kopanocore-8.6.80.1420-1.x86_64 built from sources
> >> https://forum.kopano.io/topic/1522/solved-db-backend-kopano-cli-mapi-error-80040111-mapi_e_logon_failed/9
> >
> >unfortunately I can confirm the behaviour you see.
>
> But what ARE you doing? The report is just way too fucking confusing,
> making jumps between LFS and then Fedora and then back... damn.

Well, I try to understand what the problem is. Of course it's confusing
to jump between various distributions, I'm completely agree.
I'm not able currently to follow the upstream development of kopano-core
in all details, that's why I tried to ask you.

As long as we don't know what this behavior is provoking we can't fix
this in the debain builds.

The autopkgtest [1] for src:kopanocore is failing for long time (all
after 8.5.4), so far I was able to track this down this isn't related to
AppArmor. Until 8.6.2 I was able with some manual setup to get
kopano-core running and keep it usable with kopano-webapp.
Since 8.6.5 this isn't working also, so something must have been
changed.

We haven't done a groupware meeting this year due time constrains and so
we didn't have found enough time until now to figure out what's currently
needed to get kopano correctly working (again). I have some hope to get
all this solved if we could attend this year again at some Kopano
Conference.

> >Understanding the link you providing correctly we would need libicu61
> >which kopano needs to be linked against. Debian currently is only
> >providing version 60.2 in unstable and testing. I opened up a whishlist
> >bug for packaging a recent version into Debian [1].
> >OTOH also the configure script in 8.6.5 and .7 isn't detecting this
> >requirement, this is an upstream issue which should be added to the
> >autotools setup for kopano-core.
>
> There is no requirement on a particular ICU version!
> It is even buildable with the very old ICU 4.2 from RHEL6.

Fine, than we can exlude a hard version requirement on ICU. I will
remove the affecting of kopanocore on the wishlist

[1] https://ci.debian.net/packages/k/kopanocore/unstable/amd64/

Regards
Carsten

L.P.H. van Belle

unread,
Sep 14, 2018, 5:00:03 AM9/14/18
to
Hai,
 
I did have a look at this and this report is missing a lot what we need to determin the problem.
 
The installed packages does not show mariadb-server installed.
Is this kopano setup connecting to a remote store when you tested?
 
from the server.cfg
# drop privileges and run the process as this user
run_as_user = kopano
 
# drop privileges and run the process as this group
run_as_group = kopano
These are the default and is not needed to enable it.
 
 
After removing kopano there are some left overs, after upgrading from 8.5 to 8.6 a simular problem. ( with the kopano community packages ).
https://jira.kopano.io/browse/KC-1138   shows fixed in 8.6.2 and 8.7.0
 
If it was an upgrade, remove and purge kopano, check for left overs, remove them and install again.
 
My test showed.
dpkg: warning: while removing python-kopano, directory '/usr/lib/python2.7/dist-packages/kopano' not empty so not removed
 
ls -al /usr/lib/python2.7/dist-packages/kopano
total 60
drwxr-xr-x 2 root root 4096 Sep 14 09:48 .
drwxr-xr-x 5 root root 4096 Sep 14 09:48 ..
-rw-r--r-- 1 root root 6422 Sep 14 09:45 compat.pyc
-rw-r--r-- 1 root root 7498 Sep 14 09:45 config.pyc
-rw-r--r-- 1 root root 1757 Sep 14 09:45 errors.pyc
-rw-r--r-- 1 root root 5537 Sep 14 09:45 __init__.pyc
-rw-r--r-- 1 root root 5958 Sep 14 09:45 lru_cache.pyc
-rw-r--r-- 1 root root 8407 Sep 14 09:45 utils.pyc
-rw-r--r-- 1 root root  169 Sep 14 09:45 version.pyc
dpkg: warning: while removing python-mapi, directory '/usr/lib/python2.7/dist-packages/MAPI' not empty so not removed
 
ls -al /usr/lib/python2.7/dist-packages/MAPI
total 12
drwxr-xr-x 2 root root 4096 Sep 14 09:48 .
drwxr-xr-x 5 root root 4096 Sep 14 09:48 ..
-rw-r--r-- 1 root root  361 Sep 14 09:45 __init__.pyc

I have a deeper look into this and try to help finding the problem.
Kopano in debian is what i wanted for a long time so i'll help out what i can.
im not a coder, but im working with kopano (zarafa) since 4.x.
 
 
Greetz,
 
Louis
 

 
 

Mark Dufour

unread,
Dec 2, 2018, 6:00:03 AM12/2/18
to
Hi David,

> any update on this? kopano-core and its deps are scheduled for removal in
> testing in a couple of days, and the package has not been updated ever since
> 8.6.5. has kopano been abandoned for debian buster?

There has actually been quite some effort going into preparing new 8.7 packages, and we are hoping to upload new packages very soon.. This bug was fixed somewhere in 8.6, so should also be fixed with the new packages.


Cheers,
Mark.
0 new messages