Error installing / upgrading Zarafa -> Kopano
-
While upgrading from Zarafa to Kopano I encountered some errors that I don’t seem to be able to fix.
I’m now in the process to install the server-package / core.System: Ubuntu 16.04
Version: core-8.5.81.224_0%2B30-Ubuntu_16.04-amd64.tar.gzI followed the (manual) upgrade guide and tried to solve the errors using this topic: https://forum.kopano.io/topic/343/install-kopano-core-on-ubuntu-16-04-error/15
However, I keep getting this error:
Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 11 Starting 2 pkgProblemResolver with broken count: 11 Investigating (0) kopano-server-packages [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-server-packages:amd64 Depends on kopano-server [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (= 8.5.81.224-0+29.1) Considering kopano-server:amd64 0 as a solution to kopano-server-packages:amd64 9999 Reinst Failed early because of libgsoap-kopano-2.8.60:amd64 Investigating (0) libmapi1 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken libmapi1:amd64 Depends on kopano-client [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (>= 8.5.81.224-0+29.1) Considering kopano-client:amd64 0 as a solution to libmapi1:amd64 30 Holding Back libmapi1:amd64 rather than change kopano-client:amd64 Investigating (0) libkcicalmapi0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken libkcicalmapi0:amd64 Depends on libmapi1 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libmapi1:amd64 30 as a solution to libkcicalmapi0:amd64 9 Holding Back libkcicalmapi0:amd64 rather than change libmapi1:amd64 Investigating (0) libkcfreebusy0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken libkcfreebusy0:amd64 Depends on libmapi1 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libmapi1:amd64 30 as a solution to libkcfreebusy0:amd64 8 Holding Back libkcfreebusy0:amd64 rather than change libmapi1:amd64 Investigating (0) libkcinetmapi0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken libkcinetmapi0:amd64 Depends on libkcicalmapi0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libkcicalmapi0:amd64 9 as a solution to libkcinetmapi0:amd64 6 Holding Back libkcinetmapi0:amd64 rather than change libkcicalmapi0:amd64 Investigating (0) libkcarchiver0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken libkcarchiver0:amd64 Depends on libmapi1 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libmapi1:amd64 30 as a solution to libkcarchiver0:amd64 4 Holding Back libkcarchiver0:amd64 rather than change libmapi1:amd64 Investigating (0) python-mapi [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( python ) Broken python-mapi:amd64 Depends on libkcfreebusy0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libkcfreebusy0:amd64 8 as a solution to python-mapi:amd64 3 Holding Back python-mapi:amd64 rather than change libkcfreebusy0:amd64 Investigating (0) libkcsync0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken libkcsync0:amd64 Depends on libmapi1 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libmapi1:amd64 30 as a solution to libkcsync0:amd64 2 Holding Back libkcsync0:amd64 rather than change libmapi1:amd64 Investigating (0) libkcarchivercore0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken libkcarchivercore0:amd64 Depends on libkcarchiver0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libkcarchiver0:amd64 4 as a solution to libkcarchivercore0:amd64 1 Holding Back libkcarchivercore0:amd64 rather than change libkcarchiver0:amd64 Investigating (0) python-kopano [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( python ) Broken python-kopano:amd64 Depends on python-mapi [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( python ) Considering python-mapi:amd64 3 as a solution to python-kopano:amd64 1 Holding Back python-kopano:amd64 rather than change python-mapi:amd64 Investigating (0) kopano-search [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-search:amd64 Depends on python-kopano [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( python ) Considering python-kopano:amd64 1 as a solution to kopano-search:amd64 0 Holding Back kopano-search:amd64 rather than change python-kopano:amd64 Investigating (0) kopano-contacts [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-contacts:amd64 Depends on libmapi1 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libmapi1:amd64 30 as a solution to kopano-contacts:amd64 0 Holding Back kopano-contacts:amd64 rather than change libmapi1:amd64 Investigating (0) kopano-gateway [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-gateway:amd64 Depends on libkcinetmapi0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libkcinetmapi0:amd64 6 as a solution to kopano-gateway:amd64 0 Holding Back kopano-gateway:amd64 rather than change libkcinetmapi0:amd64 Investigating (0) kopano-backup [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-backup:amd64 Depends on python-kopano [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( python ) Considering python-kopano:amd64 1 as a solution to kopano-backup:amd64 0 Holding Back kopano-backup:amd64 rather than change python-kopano:amd64 Investigating (0) kopano-utils [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-utils:amd64 Depends on libkcarchiver0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libkcarchiver0:amd64 4 as a solution to kopano-utils:amd64 0 Holding Back kopano-utils:amd64 rather than change libkcarchiver0:amd64 Investigating (0) kopano-spooler [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-spooler:amd64 Depends on libkcarchiver0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libkcarchiver0:amd64 4 as a solution to kopano-spooler:amd64 0 Holding Back kopano-spooler:amd64 rather than change libkcarchiver0:amd64 Investigating (0) kopano-ical [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-ical:amd64 Depends on libkcfreebusy0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libkcfreebusy0:amd64 8 as a solution to kopano-ical:amd64 0 Holding Back kopano-ical:amd64 rather than change libkcfreebusy0:amd64 Investigating (0) php7-mapi [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( php ) Broken php7-mapi:amd64 Depends on libkcfreebusy0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libkcfreebusy0:amd64 8 as a solution to php7-mapi:amd64 0 Holding Back php7-mapi:amd64 rather than change libkcfreebusy0:amd64 Investigating (0) kopano-dagent [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-dagent:amd64 Depends on libkcarchiver0 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libkcarchiver0:amd64 4 as a solution to kopano-dagent:amd64 0 Holding Back kopano-dagent:amd64 rather than change libkcarchiver0:amd64 Investigating (0) kopano-monitor [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-monitor:amd64 Depends on libmapi1 [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Considering libmapi1:amd64 30 as a solution to kopano-monitor:amd64 0 Holding Back kopano-monitor:amd64 rather than change libmapi1:amd64 Investigating (1) kopano-server-packages [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) Broken kopano-server-packages:amd64 Depends on kopano-backup [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (= 8.5.81.224-0+29.1) Considering kopano-backup:amd64 0 as a solution to kopano-server-packages:amd64 9999 Reinst Failed early because of libgsoap-kopano-2.8.60:amd64 Reinst Failed because of kopano-client:amd64 Reinst Failed because of libmapi1:amd64 Reinst Failed because of libkcfreebusy0:amd64 Reinst Failed because of python-mapi:amd64 Reinst Failed because of python-kopano:amd64 Broken kopano-server-packages:amd64 Depends on kopano-dagent [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (= 8.5.81.224-0+29.1) Considering kopano-dagent:amd64 0 as a solution to kopano-server-packages:amd64 9999 Reinst Failed because of libmapi1:amd64 Reinst Failed because of libkcarchiver0:amd64 Broken kopano-server-packages:amd64 Depends on kopano-gateway [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (= 8.5.81.224-0+29.1) Considering kopano-gateway:amd64 0 as a solution to kopano-server-packages:amd64 9999 Reinst Failed because of libkcfreebusy0:amd64 Reinst Failed because of libkcicalmapi0:amd64 Reinst Failed because of libkcinetmapi0:amd64 Broken kopano-server-packages:amd64 Depends on kopano-ical [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (= 8.5.81.224-0+29.1) Considering kopano-ical:amd64 0 as a solution to kopano-server-packages:amd64 9999 Reinst Failed because of libkcfreebusy0:amd64 Broken kopano-server-packages:amd64 Depends on kopano-monitor [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (= 8.5.81.224-0+29.1) Considering kopano-monitor:amd64 0 as a solution to kopano-server-packages:amd64 9999 Reinst Failed because of libmapi1:amd64 Broken kopano-server-packages:amd64 Depends on kopano-search [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (= 8.5.81.224-0+29.1) Considering kopano-search:amd64 0 as a solution to kopano-server-packages:amd64 9999 Reinst Failed because of python-kopano:amd64 Broken kopano-server-packages:amd64 Depends on kopano-server [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (= 8.5.81.224-0+29.1) Considering kopano-server:amd64 0 as a solution to kopano-server-packages:amd64 9999 Broken kopano-server-packages:amd64 Depends on kopano-spooler [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (= 8.5.81.224-0+29.1) Considering kopano-spooler:amd64 0 as a solution to kopano-server-packages:amd64 9999 Reinst Failed because of libkcarchiver0:amd64 Broken kopano-server-packages:amd64 Depends on kopano-utils [ amd64 ] < none -> 8.5.81.224-0+29.1 > ( mail ) (= 8.5.81.224-0+29.1) Considering kopano-utils:amd64 0 as a solution to kopano-server-packages:amd64 9999 Reinst Failed because of libkcarchiver0:amd64 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: kopano-server-packages : Depends: kopano-backup (= 8.5.81.224-0+29.1) but it is not going to be installed Depends: kopano-dagent (= 8.5.81.224-0+29.1) but it is not going to be installed Depends: kopano-gateway (= 8.5.81.224-0+29.1) but it is not going to be installed Depends: kopano-ical (= 8.5.81.224-0+29.1) but it is not going to be installed Depends: kopano-monitor (= 8.5.81.224-0+29.1) but it is not going to be installed Depends: kopano-search (= 8.5.81.224-0+29.1) but it is not going to be installed Depends: kopano-server (= 8.5.81.224-0+29.1) but it is not going to be installed Depends: kopano-spooler (= 8.5.81.224-0+29.1) but it is not going to be installed Depends: kopano-utils (= 8.5.81.224-0+29.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages.The only strange thing I notice is that the package / tar contains libgsoap-kopano-2.8.61 while it keeps failing on libgsoap-kopano-2.8.60 (which I can’t find or download).
I also tried to install Kopano on a clean installation, resulting in the same error.
Anybody knows how to fix this?
-
Hi @rbdw ,
can you retry with a new download from the server. it should work now.
-
Yes, the new build fixed it. Thank you!
-
Unfortunately the kopano-server service fails to start (using the default configuration, only changed the database settings). The only thing I can find in the log is:
“Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0. See kopano-coredump(5) for details.”However, I have an OpenVZ VPS and therefore I can’t change this setting. Is there any way around it?
-
That one is a non fatal error and the server should start nonetheless.
But I would really advice against using Kopano on openvz, there have been weird effects at customers in the past because of it. (There should be a bit about that in the manual)
Rather use lxc.
-
Hmm, not sure if I just didn’t look good or it magically fixed itself, but the server is running.
I’ll keep the advice in mind about OpenVZ. Thanks!
