Public bug reported:
Issue in autopkgtest on migration of recent kopanocore:
=>
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/k/kopanocore/20171121_085527_b723d@/log.gz
TL;DR - issue when installing:
Setting up kopano-server (8.3.4-4ubuntu3) ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dbconfig-common: writing config to /etc/dbconfig-common/kopano-server.conf
Creating config file /etc/dbconfig-common/kopano-server.conf with new
version
Creating config file /etc/kopano/debian-db.cfg with new version
checking privileges on database kopanoserver for kopano-server@localhost: user
creation needed.
granting access to database kopanoserver for kopano-server@localhost: success.
verifying access for kopano-server@localhost: success.
creating database kopanoserver: success.
verifying database kopanoserver exists: success.
dbconfig-common: flushing administrative password
Processing triggers for libc-bin (2.26-0ubuntu2) ...
Processing triggers for systemd (235-2ubuntu3) ...
done.
Check that we have a running server and can create users...
Unable to open Admin session: network error (0x80040115)
The server is not running, or not accessible through "default:".
Using the -v option (possibly multiple times) may give more hints.
I can reproduce the same in autopkgtest via:
$ autopkgtest --apt-upgrade --shell-fail --apt-upgrade --apt-pocket=proposed
--no-built-binaries kopanocore_8.3.4-4ubuntu3.dsc -- qemu
~/work/autopkgtest-bionic-amd64.img
Affects i386 AND amd64 when ran in my autopkgtest
In a container the following should be the same:
# enable proposed
cat <<EOF | debconf-set-selections
kopano kopano-server/mysql/method select unix socket
kopano kopano-server/missing-db-package-error select abort
kopano kopano-server/internal/reconfiguring boolean true
kopano kopano-server/internal/skip-preseed boolean false
kopano kopano-server/dbconfig-upgrade boolean true
kopano kopano-server/dbconfig-install boolean true
kopano kopano-server/dbconfig-reinstall boolean true
kopano kopano-server/db/app-user string kopano-server
kopano kopano-server/mysql/admin-user string root
kopano kopano-server/database-type select mysql
kopano kopano-server/db/dbname string kopanoserver
EOF
DEBIAN_FRONTEND=noninteractive apt -y install mariadb-server
/etc/init.d/mysql start
DEBIAN_FRONTEND=noninteractive apt -y install kopano-server kopano-utils
$ kopano-admin -l | grep -qs "SYSTEM.*Kopano"
=> Reproduced in the container
I ran this three ways now:
1. from bionic
2. from bionic-proposed
3. from bionic, but interactive instead of debconf-set-selections
=> Only the one in proposed is failing.
Upgrading the working #3 (with manual config) makes it break as well.
Note there is a new mariadb in proposed which could cause this.
The server / service is actually failed in those environments.
root@bionic-i386-proposed:~# systemctl restart kopano-server
root@bionic-i386-proposed:~# systemctl status kopano-server
● kopano-server.service - Kopano Server
Loaded: loaded (/lib/systemd/system/kopano-server.service; disabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 2017-11-21 13:09:03 UTC; 18s ago
Docs: man:kopano-server(8)
Process: 4319 ExecStart=/usr/sbin/kopano-server -F -c /etc/kopano/server.cfg
(code=exited, status=127)
Process: 4318 ExecStartPre=/bin/chown kopano /var/lib/kopano (code=exited,
status=0/SUCCESS)
Process: 4317 ExecStartPre=/bin/chown kopano /var/run/kopano (code=exited,
status=0/SUCCESS)
Process: 4316 ExecStartPre=/bin/mkdir -p /var/run/kopano (code=exited,
status=0/SUCCESS)
Main PID: 4319 (code=exited, status=127)
Nov 21 13:09:03 bionic-i386-proposed systemd[1]: Starting Kopano Server...
Nov 21 13:09:03 bionic-i386-proposed systemd[1]: Started Kopano Server.
Nov 21 13:09:03 bionic-i386-proposed systemd[1]: kopano-server.service: Main
process exited, code=exited, status=127/n/a
Nov 21 13:09:03 bionic-i386-proposed systemd[1]: kopano-server.service: Failed
with result 'exit-code'.
Sometimes in the log there is a message more and I see it when running the
server manually:
root@bionic-i386-proposed:~# /usr/sbin/kopano-server -F -c
/etc/kopano/server.cfg
/usr/sbin/kopano-server: error while loading shared libraries: cannot apply
additional memory protection after relocation: Permission denied
I remember seeing something like that in the past.
It was apparmor then and I see now such messages as well:
[2338345.982219] audit: type=1400 audit(1511269881.445:2191):
apparmor="DENIED" operation="file_mprotect" namespace="root//lxd-
bionic-i386-proposed_<var-lib-lxd>" profile="/usr/sbin/kopano-server"
name="/usr/sbin/kopano-server" pid=23050 comm="kopano-server"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
The new version might need that an extension.
** Affects: kopanocore (Ubuntu)
Importance: Undecided
Status: Confirmed
** Changed in: kopanocore (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733591
Title:
new kopanocore fails in autopkgtest in i386 (fails to start at all
actually)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kopanocore/+bug/1733591/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
