Kopano Core Update 8.6.9 to 8.7.0 at UCS 4.2-5 w/ Kopano repo: missing/old integration package

kopano

#1

Hi forum,

an update today pulled Kopano Core 8.7.0 from Kopano repo but
the stated newer integration package 8.6.8 seems not be available for UCS 4.2-5, the integration package is still stuck at version 8.4.5.0-1 and so there ist no needed upgrade script at
/usr/share/kopano4ucs/kopano4ucs-update-settings870.sh as mentioned at:

Any hints?

TIA Robert


#2

Hi @pro4567,

if you cannot (yet) upgrade to 4.3, then you can also manually execute the steps from the integration package on your system. The related code is at:

https://stash.z-hub.io/projects/K4U/repos/kopano4ucs/browse/scripts/kopano4ucs-update-settings870.sh
https://stash.z-hub.io/projects/K4U/repos/kopano4ucs/browse/debian/kopano4ucs.postinst#71-188

Since usage of 4.2 is declining no effort was made backporting all integration changes into a state that is compatible with 4.2. Hence also the

  • To benefit from further improvements to the integration packages it is recommended to Upgrade to UCS 4.3

in the last app update.


#3

Hi @fbartels,

THX a lot, this was helping but

additionaly I had to chown kopano:kopano -R /etc/kopano/ssl/

because I got

Tue Feb  5 13:50:01 2019: [crit   ] K-2170: Unable to setup SSL context: soap_ssl_server_context: Can't find or read certificate in private key PEM file: SSL_ERROR_SYSCALL

at ~log/kopano/server.log after manually executing the steps from the integration package.

I’m just wondering why this 8.7 update is also released for UCS 4.2 if it breaks the app integration like this and causes a service failure.
I had included the direct Kopano repos as recommended at https://wiki.z-hub.io/display/K4U/Updating+Kopano+packages+directly+from+the+Kopano+download+server, so will many other UCS 4.2 users probably have the same? And 4.2 is still fully supported and 4.3 hasn’t been released that long.

After that there was no warning before the update, I triggered it with
univention-upgrade --ignoressh --ignoreterm --enable-app-updates

Anyway, thanks for your quick help here,

regards,
Robert


#4

UCS 4.2 is still a fully supported platform for the packages, its just that the magic performed by the integration packages has not been updated for this release. In retrospect it may have been an idea to disable the repo settings for 4.2 in the integration package.

4.2 is already in the “extended maintenance” if you look at https://errata.software-univention.de/ucs/4.2/. imho the focus is at the moment on 4.3 (and the upcoming 4.4). But someone involved in the support side of Univention may be a better judge of that.


#5

Yes, we are usually more on the conservative, cautious side when it comes to updates and only update customer systems when the last stable release is already a bit “suspended”. The update to Kopano V8.7 happened earlier than planned because it is installed as a “normal” package update with UCS updates during the Kopano Repo integration. Maybe there will be a better way to integrate current Kopano versions or the original repo in the future. In a few months at the latest we will update everything to UCS 4.3.

Thanks again for your quick reaction, which has fixed the situation well :wink:

Most of the time we are really happy with Kopano & UCS!

Regards Robert


#6

Addendum: Yesterday’s periodic change of /etc/machine.secret unfortunately caused us another failure (with mail loss, because postfix/lmtp is bouncing and NDN / backscatter is not allowed, even the sender is not informed about non-delivery), because the corresponding integration script for the secret change was missing here as well. :frowning_face:

Solution: Kopano ldap problem

This should (actually) not happen with supported systems/versions.

How can one actually achieve that with such errors/failures of the delivery agent (here Kopano) mails are lost by bounce & NDN / backscatter prohibition? So either Postfix does not accept anything from external in such cases anymore or there would be a backup(queue). Should Postfix not bounce with “hard” 500 errors and discard them with such errors within the internal mail cascade?

Mail-Log:

Feb 11 08:38:38 metis kopano-dagent[17436]: Failed to resolve recipient buchhaltung@xxxxxxxxxx.at (0)
Feb 11 08:38:38 metis kopano-dagent[17436]: Requested e-mail address "buchhaltung@xxxxxxxxxx.at" does not resolve to a user.
Feb 11 08:38:38 metis postfix/lmtp[17435]: F149F5F98B: to=<buchhaltung@xxxxxxxxxx.at>, relay=127.0.0.1[127.0.0.1]:2003, delay=0.18, delays=0.06/0.01/0.07/0.05, dsn=5.1.1, status=bounced (host 127.0.0.1[127.0.0.1] said: 503 5.1.1 User does not exist (in reply to RCPT TO command))
Feb 11 08:38:38 metis postfix/cleanup[17427]: 2614E5F999: message-id=<20190211073838.2614E5F999@metis.xxxxxxxxxx.local>
Feb 11 08:38:38 metis postfix/bounce[17440]: F149F5F98B: sender non-delivery notification: 2614E5F999
Feb 11 08:38:38 metis postfix/qmgr[20304]: 2614E5F999: from=<>, size=3844, nrcpt=1 (queue active)
Feb 11 08:38:38 metis postfix/qmgr[20304]: F149F5F98B: removed
Feb 11 08:38:38 metis postfix/smtp[17441]: 2614E5F999: to=<prvs=938f25d5b=Pk@yyyyyyyyy.at>, relay=bsmtp.a1.net[213.33.87.54]:587, delay=0.2, delays=0/0.01/0.17/0.02, dsn=5.7.1, status=bounced (host bsmtp.a1.net[213.33.87.54] said: 550 5.7.1 <unknown[80.120.219.226]:18
974>: Client host rejected: sending backscatter not permitted (in reply to RCPT TO command))
Feb 11 08:38:38 metis postfix/qmgr[20304]: 2614E5F999: removed

TIA Robert


#7

Like i’ve written in the other thread I do not see the relation to the upgrade (but I also agree that the file should of course stay). On all my test systems (also the ones that were upgraded to 8.7) this file exists.


#8

Hello Felix,

I don’t mean to blame Kopano in particular. The Kopano update was installed together with a UCS update from 4.2-5 erratum584 to 4.2-5 erratum588, maybe there were unfavorable interactions. But I just checked the previous day’s backups and there the file /usr/lib/univention-server/server_password_change.d/70kopano was definitely still there, but after the updates it disappeared.


#9

In that case I’d recommend to check if the kopano4ucs packages are still installed.


#10

Yes, the package was actually removed during the upgrade, probably because of that:

root@XXXXXX / # apt-get install kopano4ucs
Paketlisten werden gelesen... Fertig
AbhÀngigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Package kopano4ucs is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'kopano4ucs' has no installation candidate


#11

can you run the following command to get some insights why it was removed?

apt-get -s -o Debug::pkgProblemResolver=yes install kopano4ucs

(and then further down for whatever package he marks there as missing)


#12

That usually indicates that the app repository is not registered anymore. It has to be registered before @fbartels’s note about debugging the installation issue should be done. Register the latest kopano-core app repository with: univention-app register kopano-core --do-it


#13

You probably mean univention-app register kopano-core --do-it right?

1 root@XXXXX ~ # univention-app register kopano-core --do-it                                                                                                                                                                                                                :(
Registering component for kopano-core
Module: kopano-cfg

File: /etc/apt/sources.list.d/20_ucs-online-component.list

File: /etc/apt/mirror.list

File: /etc/apt/sources.list.d/15_ucs-online-version.list

Creating data directories for kopano-core...
Registering UCR for kopano-core
Marking kopano-core=8.4.5.0-1 as installed
Module: kopano-cfg
File: /etc/univention/service.info/services/univention-appcenter.cfg
Multifile: /etc/postgresql/9.1/main/pg_hba.conf
File: /usr/share/univention-portal/apps.json
Multifile: /etc/apache2/sites-available/000-default.conf
Multifile: /etc/apache2/sites-available/default-ssl.conf
Module: kopano-cfg
Adding localhost to LDAP object
Module: kopano-cfg
univention-app register kopano-core --do-it  13,40s user 1,49s system 27% cpu 53,397 total

The (integration) app was apparently unconsciously removed, I am not aware of any guilt at the first glance.

Ah, now we can see more dependency issues:

100 root@XXXXX ~ # apt-get -s -o Debug::pkgProblemResolver=yes install kopano4ucs                                                                                                                                                                                           :(
Paketlisten werden gelesen... Fertig
AbhÀngigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) kopano4ucs [ amd64 ] < none -> 1.3.10 > ( univention )
Broken kopano4ucs:amd64 HĂ€ngt ab von on kopano-server-packages [ amd64 ] < none -> 8.4.5.0-0+33.2 > ( mail )
  Considering kopano-server-packages:amd64 1 as a solution to kopano4ucs:amd64 9999
    Reinst Failed early because of kopano-backup:amd64
Done
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

Die folgenden Pakete haben unerfĂŒllte AbhĂ€ngigkeiten:
 kopano4ucs : HĂ€ngt ab von: kopano-server-packages soll aber nicht installiert werden
E: Probleme können nicht korrigiert werden, Sie haben zurĂŒckgehaltene defekte Pakete.

dpkg --audit shows nothing which means package status at generell seems to be good.

TIA Robert


#14

Correct, thanks, i fixed it in my previous post.

That issue looked complicated so i took a closer look. The updated Kopano packages introduced a dependency that could not be resolved, so the app repo was just updated with the python-bsddb3 package. When the app is registered, it should now be possible to install the package - univention-install kopano4ucs


#15
....
Paketlisten werden gelesen...
AbhÀngigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

Die folgenden Pakete haben unerfĂŒllte AbhĂ€ngigkeiten:
 kopano4ucs : HĂ€ngt ab von: kopano-server-packages soll aber nicht installiert werden
E: Probleme können nicht korrigiert werden, Sie haben zurĂŒckgehaltene defekte Pakete.
univention-install kopano4ucs  5,54s user 0,98s system 44% cpu 14,638 total

didn’t work 
 should I maybe clear the package cache first or something?

TIA Robert


#16

Sorry for the inconvenience, i reproduced your initial error, and after the package was added i could successfully install kopano4ucs.

The python package i mentioned should be install-able right now, correct? A repository URL should be shown when executing apt-cache policy python-bsddb3.

The package cache should not cause a problem here. Instead, please follow the package dependency chain by added the mentioned package to the univention-install ... line, in your case try univention-install kopano4ucs kopano-server-packages next. Keep adding packages until the error message changes to something like ‘package not available’.


#17

Yes, this should be install-able:

100 root@XXXXXX ~ # apt-cache policy python-bsddb3                                                                                                                                                                                                                           :(
python-bsddb3:
  Installiert:           (keine)
  Installationskandidat: 6.1.0-1
  Versionstabelle:
     6.1.0-1 0
        500 https://updates.software-univention.de/4.2/unmaintained/ 4.2-0/amd64/ Packages
        500 https://appcenter.software-univention.de/univention-repository/4.2/maintained/component/ kopano-core_20181010132900/amd64/ Packages
     5.2.0-1.4.201403121652 0
        500 https://updates.software-univention.de/4.0/unmaintained/ 4.0-0/amd64/ Packages

but output of univention-install kopano4ucs kopano-server-packages means to me that the dependency of the package kopano-server-packages on the old Kopano version 8.4.5 is the problem here, when Kopano 8.7 is already installed?

...
Paketlisten werden gelesen...
AbhÀngigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

Die folgenden Pakete haben unerfĂŒllte AbhĂ€ngigkeiten:
 kopano-server-packages : HĂ€ngt ab von: kopano-backup (= 8.4.5.0-0+33.2) aber 8.7.0.0-0+1.1 soll installiert werden
                          HĂ€ngt ab von: kopano-dagent (= 8.4.5.0-0+33.2) aber 8.7.0.0-0+1.1 soll installiert werden
                          HĂ€ngt ab von: kopano-gateway (= 8.4.5.0-0+33.2) aber 8.7.0.0-0+1.1 soll installiert werden
                          HĂ€ngt ab von: kopano-ical (= 8.4.5.0-0+33.2) aber 8.7.0.0-0+1.1 soll installiert werden
                          HĂ€ngt ab von: kopano-monitor (= 8.4.5.0-0+33.2) aber 8.7.0.0-0+1.1 soll installiert werden
                          HĂ€ngt ab von: kopano-presence (= 8.4.5.0-0+33.2) aber 8.7.0.0-0+1.1 soll installiert werden
                          HĂ€ngt ab von: kopano-search (= 8.4.5.0-0+33.2) aber 8.6.9.0-0+24.1 soll installiert werden
                          HĂ€ngt ab von: kopano-server (= 8.4.5.0-0+33.2) aber 8.7.0.0-0+1.1 soll installiert werden
                          HĂ€ngt ab von: kopano-spooler (= 8.4.5.0-0+33.2) aber 8.7.0.0-0+1.1 soll installiert werden
                          HĂ€ngt ab von: kopano-utils (= 8.4.5.0-0+33.2) aber 8.7.0.0-0+1.1 soll installiert werden
E: Probleme können nicht korrigiert werden, Sie haben zurĂŒckgehaltene defekte Pakete.
univention-install kopano4ucs kopano-server-packages  5,59s user 0,89s system 43% cpu 14,769 total