Hallo @MyKey0815,
das Thema wird derzeit noch untersucht.
Hi @MyKey0815,
to finally resolve this i have uploaded a new app version for 4.1 and 4.2 to the appcenter. this is currently available from the test appcenter (see https://wiki.univention.de/index.php/Testing how to enable the test appcenter and disable it afterwards). Can you give this a spin to see if it resolves your issue as well?
In addition to installing the latest app the repositories must also be manually disabled. I have added some extra explanation to https://wiki.z-hub.io/display/K4U/Updating+Kopano+packages+directly+from+the+Kopano+download+server#UpdatingKopanopackagesdirectlyfromtheKopanodownloadserver-UpgradingfromUCS4.1to4.2withrepositories.
1 Like
Please be advised that using the test app center should only be done on test machines, not in production. Apps in the test app center are not ready for production usage, they may contain bugs. Univention is generally not able to support this scenario
The Update was now possible. But only the Kopano is not working anymore.
1.) The installed WebApp is older than 3.4 from the external repos - i have activate the external repos again, but they dont updatet.
2.) Kopano core is not running anymore. Here the logfile:
Wed Jan 3 19:06:08 2018: [ notice] Starting kopano-server version 8.4.5.0 (pid 2559)
Wed Jan 3 19:06:09 2018: [warning] Config warning: Option 'sync_log_all_changes' is not used anymore.
Wed Jan 3 19:06:09 2018: [warning] Config warning: Option 'plugin_path' is not used anymore.
Wed Jan 3 19:06:09 2018: [warning] Config warning: Option 'thread_stacksize' is not used anymore.
Wed Jan 3 19:06:09 2018: [warning] Config warning: Option 'client_update_enabled' is not used anymore.
Wed Jan 3 19:06:09 2018: [warning] Config warning: Option 'client_update_path' is not used anymore.
Wed Jan 3 19:06:09 2018: [warning] Config warning: Option 'client_update_log_level' is not used anymore.
Wed Jan 3 19:06:09 2018: [warning] Config warning: Option 'client_update_log_path' is not used anymore.
Wed Jan 3 19:06:11 2018: [error ] Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0.
Wed Jan 3 19:06:11 2018: [error ] KDatabase::Connect(): database access error Unknown error code (0x80000007), mysql error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' $
Wed Jan 3 19:06:11 2018: [crit ] Unable to connect to database: MYSQL not initialized
Wed Jan 3 19:06:12 2018: [ notice] Server shutdown complete.
3.) No mail delivery from fetchmail to postfix/kopano
Jan 3 22:08:43 ucs002090 fetchmail[3160]: Nachricht xxxxxx@t-online.de@sfwdallmx.t-online.de:1 von 5 wird gelesen (18727 Bytes) (Log-Meldung unvollstÀndig)
Jan 3 22:08:43 ucs002090 fetchmail[3160]: SMTP-Fehler: 451 4.3.0 <michael.kolowicz@xxxxxx.lan>: Temporary lookup failure
Jan 3 22:08:43 ucs002090 fetchmail[3160]: Nachricht xxxxxx@t-online.de@sfwdallmx.t-online.de:2 von 5 wird gelesen (177592 Bytes) (Log-Meldung unvollstÀndig)
Jan 3 22:08:43 ucs002090 fetchmail[3160]: SMTP-Fehler: 451 4.3.0 <michael.kolowicz@xxxxxx.lan>: Temporary lookup failure
Jan 3 22:08:43 ucs002090 fetchmail[3160]: Nachricht xxxxxx@t-online.de@sfwdallmx.t-online.de:3 von 5 wird gelesen (3274 Bytes) (Log-Meldung unvollstÀndig)
Jan 3 22:08:43 ucs002090 fetchmail[3160]: SMTP-Fehler: 451 4.3.0 <michael.kolowicz@xxxxxx.lan>: Temporary lookup failure
Jan 3 22:08:43 ucs002090 fetchmail[3160]: Nachricht xxxxxx@t-online.de@sfwdallmx.t-online.de:4 von 5 wird gelesen (56940 Bytes) (Log-Meldung unvollstÀndig)
Jan 3 22:08:43 ucs002090 fetchmail[3160]: SMTP-Fehler: 451 4.3.0 <michael.kolowicz@xxxxxx.lan>: Temporary lookup failure
Jan 3 22:08:43 ucs002090 fetchmail[3160]: Nachricht xxxxxx@t-online.de@sfwdallmx.t-online.de:5 von 5 wird gelesen (20487 Bytes) (Log-Meldung unvollstÀndig)
Jan 3 22:08:43 ucs002090 fetchmail[3160]: SMTP-Fehler: 451 4.3.0 <michael.kolowicz@xxxxxx.lan>: Temporary lookup failure
Jan 3 22:09:04 ucs002090 postfix/cleanup[1431]: error: open /etc/postfix/ldap.external_aliases: No such file or directory
Jan 3 22:09:04 ucs002090 postfix/cleanup[1431]: error: open /etc/postfix/ldap.sharedfolderlocal_aliases: No such file or directory
Jan 3 22:09:30 ucs002090 postfix/cleanup[1446]: error: open /etc/postfix/ldap.external_aliases: No such file or directory
Jan 3 22:09:30 ucs002090 postfix/cleanup[1446]: error: open /etc/postfix/ldap.sharedfolderlocal_aliases: No such file or directory
Jan 3 22:11:58 ucs002090 postfix/cleanup[1790]: error: open /etc/postfix/ldap.external_aliases: No such file or directory
Jan 3 22:11:58 ucs002090 postfix/cleanup[1790]: error: open /etc/postfix/ldap.sharedfolderlocal_aliases: No such file or directory
Jan 3 22:12:26 ucs002090 postfix/cleanup[1974]: error: open /etc/postfix/ldap.external_aliases: No such file or directory
Jan 3 22:12:26 ucs002090 postfix/cleanup[1974]: error: open /etc/postfix/ldap.sharedfolderlocal_aliases: No such file or directory
Jan 3 22:12:27 ucs002090 postfix/cleanup[1976]: error: open /etc/postfix/ldap.external_aliases: No such file or directory
Jan 3 22:12:27 ucs002090 postfix/cleanup[1976]: error: open /etc/postfix/ldap.sharedfolderlocal_aliases: No such file or directory
-
are you referring to the version shown in the appcenter or the actual version of the webapp? webapp is not touched by the update and it being automatically downgraded is quite unlikely
-
did you reboot after the upgrade? is mysql running?
-
I would not expect that the mta is able to deliver mails as long as kopano-server is not running. In any case the app upgrade only updates Kopano and the integration package and does not touch postfix. for the âNo such file or directoryâ I would just regenerate them from their templates, e.g.
ucr commit /etc/postfix/ldap.external_aliasesÂŽ
-
By starting the WebApp it shows 3.4 - in the appcenter it shown 3.3
-
When I reboot the server then kopano-server (and kopano-serch) can not start. If i log in via ssh an type âkopano-server startâ than it works. I think mysql is starting to late for kopano
-
My configuration is a sender dependent relayhost. Every user in my kopano has have a different external mail by t-online, gmail or gmx. I have manualy create a /etc/postfix/sasl_password, /etc/postfix/sender_dependent and /etc/postfix/sender_canonical. Also I have create a /etc/univention/templates/files/etc/postfix/main.cf.d/31_sender_dependent_relayhostmaps
#Absenderabhaengige Zuweisung von SMTP Servern
#d.h. jeder Zarafa Benutzer kann seinen eigenen SMTP haben
#sender_dependent_relayhost_maps = yes
smtp_sender_dependent_authentication = yes
smtp_sasl_auth_enable = yes
# noplaintext weglassen, wenn Passwoerter Klartext uebertragen werden muessen,
# d.h. wenn in der sasl_password die Passwoerter im Klattext verwaltet:
# (nicht empfohlen, nur wenn's anders nicht funktioniert)
smtp_sasl_security_options = noanonymous
smtp_connection_cache_on_demand = no
smtp_sasl_password_maps = hash:/etc/postfix/sasl_password
sender_dependent_relayhost_maps = hash:/etc/postfix/sender_dependent
sender_canonical_maps = hash:/etc/postfix/sender_canonical
What is the right way to do it in 4.2?
BTW:
After setting following variables is it possible to send out mails - but no mails come in
univention-config-registry set mail/relayauth = 'false'
univention-config-registry set mail/postfix/virtual/enabled = 'false'
This is my actual kopano/server.log:
Thu Jan 4 08:02:38 2018: [ notice] Starting kopano-server version 8.4.5.0 (pid 4507)
Thu Jan 4 08:02:38 2018: [warning] Config warning: Option 'sync_log_all_changes' is not used anymore.
Thu Jan 4 08:02:38 2018: [warning] Config warning: Option 'plugin_path' is not used anymore.
Thu Jan 4 08:02:38 2018: [warning] Config warning: Option 'thread_stacksize' is not used anymore.
Thu Jan 4 08:02:38 2018: [warning] Config warning: Option 'client_update_enabled' is not used anymore.
Thu Jan 4 08:02:38 2018: [warning] Config warning: Option 'client_update_path' is not used anymore.
Thu Jan 4 08:02:38 2018: [warning] Config warning: Option 'client_update_log_level' is not used anymore.
Thu Jan 4 08:02:38 2018: [warning] Config warning: Option 'client_update_log_path' is not used anymore.
Thu Jan 4 08:02:39 2018: [error ] Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0.
Thu Jan 4 08:03:42 2018: [error ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Thu Jan 4 08:14:27 2018: [error ] Previous message logged 71 times
Thu Jan 4 08:14:27 2018: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Thu Jan 4 08:14:28 2018: [error ] Previous message logged 3 times
Thu Jan 4 08:14:28 2018: [error ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Thu Jan 4 08:22:20 2018: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Thu Jan 4 08:22:29 2018: [error ] Previous message logged 2 times
Thu Jan 4 08:22:29 2018: [error ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Thu Jan 4 08:22:31 2018: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Thu Jan 4 08:22:31 2018: [error ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Thu Jan 4 08:30:03 2018: [error ] Previous message logged 57 times
Thu Jan 4 08:30:03 2018: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Here I add a the log. What is the reason, that no mails will be delivered to kopano?
Jan 4 09:23:27 ucs002090 fetchmail[11821]: Nachricht mkolowicz@t-online.de@sfwdallmx.t-online.de:1 von 1 wird gelesen (20461 Bytes) gelöscht
Jan 4 09:23:27 ucs002090 postfix/smtp[12303]: warning: database /etc/postfix/tls_policy.db is older than source file /etc/postfix/tls_policy
Jan 4 09:23:27 ucs002090 postfix/smtpd[12300]: disconnect from localhost[127.0.0.1]
Jan 4 09:23:27 ucs002090 postfix/smtpd[12306]: connect from localhost[127.0.0.1]
Jan 4 09:23:27 ucs002090 postfix/smtpd[12306]: E24124B0025C: client=localhost[127.0.0.1], orig_queue_id=F17C54B00104, orig_client=localhost[127.0.0.1]
Jan 4 09:23:27 ucs002090 postfix/cleanup[12302]: E24124B0025C: message-id=<003201d38535$a07b4370$e171ca50$@gmx.de>
Jan 4 09:23:27 ucs002090 postfix/qmgr[3409]: E24124B0025C: from=<michael.kolowicz@gmx.de>, size=21606, nrcpt=1 (queue active)
Jan 4 09:23:27 ucs002090 postfix/smtpd[12306]: disconnect from localhost[127.0.0.1]
Jan 4 09:23:28 ucs002090 amavis[10400]: (10400-02) Passed CLEAN {RelayedInternal}, LOCAL [127.0.0.1]:53186 [134.3.22.6] <michael.kolowicz@gmx.de> -> <michael.kolowicz@xxxxxxx.lan>, Queue-ID: F17C54B00104, Message-ID: <003201d38535$a07b4370$e171ca50$@gmx.de>, mail_id: dWMXyTKrUrwp, Hits: 1.275, size: 20821, queued_as: E24124B0025C, 855 ms
Jan 4 09:23:28 ucs002090 postfix/smtp[12295]: E24124B0025C: to=<michael.kolowicz@xxxxxxx.lan>, relay=none, delay=0.08, delays=0.07/0/0.01/0, dsn=5.4.6, status=bounced (mail for xxxxxxx.lan loops back to myself)
Jan 4 09:23:28 ucs002090 postfix/cleanup[12302]: 11D2D4B00350: message-id=<20180104082328.11D2D4B00350@ucs002090.xxxxxxx.lan>
Jan 4 09:23:28 ucs002090 postfix/bounce[12307]: E24124B0025C: sender non-delivery notification: 11D2D4B00350
Jan 4 09:23:28 ucs002090 postfix/qmgr[3409]: 11D2D4B00350: from=<>, size=23646, nrcpt=1 (queue active)
Jan 4 09:23:28 ucs002090 postfix/qmgr[3409]: E24124B0025C: removed
Jan 4 09:23:28 ucs002090 postfix/smtp[12303]: F17C54B00104: to=<michael.kolowicz@xxxxxxx.lan>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.2, delays=0.15/0.03/0/1, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as E24124B0025C)
Jan 4 09:23:28 ucs002090 postfix/qmgr[3409]: F17C54B00104: removed
-
yes, this is how the appcenter works, it shows the version of the app and not the version of the installed app. can safely be ignored. new packages are not installed, since you were already running the latest version.
-
that sounds like Fehler nach Upgrade 4.2: Kopano startet nicht mehr
-
cannot say anything about postfix setup in Univention 4.2. maybe it would be worth opening an extra topic for this?
Hello,
the issue has been resolved and a new Kopano Core App is available for UCS 4.1. Once Version 8.4.5.0 is installed, it is possible to upgrade UCS to Version 4.2. The update is still blocked if an incompatible App is installed and a note is displayed to upgrade the App version.
Hi there,
is deinstallation of the kopano apps still the actually way to update (on 4.3)? On my testserver Iâve got this message:
ERROR: An external repository for the Kopano Apps is currently configured.
There are known issues when updating to UCS 4.3 and using software
from the Kopano software repository.
The update is blocked while Kopano and Univention are working
on a solution.
Error: Update aborted by pre-update script of release 4.3-0
sv002:~# univention-app info
UCS: 4.2-4 errata418
App Center compatibility: 4
Installed: dhcp-server=11.0.0 kopano-core=8.4.5.0 kopano-webapp=3.3.0.610 nagios=3.5 pkgdb=10 samba4=4.6 squid=3.4 z-push-kopano=2.3.7
Upgradable:
Thanks
Ulf
Hi @ulf.kosack,
no need to remove the current package, the repo configuration page in the kopano4ucs wiki lists instructions that have been confirmed to work for a clean upgrade. Unfortunately the wiki is down at the moment (will probably be back up monday morning) else i would directly link to it.
Any Idea when an aupdate with php switch will be availabe ?
Thanks
Rainer
hopefully soon, but I cannot give an eta at the moment the app is currently expected for the beginning of next week.
Currently we use Kopano core 8.6.2. According to this link Link there is still a risk of a faulty upgrade.
There are no more offical updates available for 4.2 so I would like to upgrade asap.
Any idea when a suitable core will be available ?
Thanks
Rainer
We are in preparations of pushing a new release to our repositories
8.6.4 for is now available, see https://forum.kopano.io/topic/1596/kopano-groupware-core-8-6-4-available for more details.
Have not tested though, if the workaround now works any better than before (from the filenames it should).
Hello,
has anyone successfully tried the upgrade workaround from the Kopano Wiki with the 8.6.4+ core?
BR,
TP
Yes I have done it yesterday.
You will find some additional help here: UCS 4.3-0: Nach Upgrade PHP mapi extension not found
and the comments below.
1 Like
Hello,
thank you all for testing this and reporting here! This made the task a lot easier for me.
After performing the steps mentioned HERE the upgrade went through smoothly, besides 20-minute wait and fear without output in the updater.log because of this BUG, which is still not resolved.
Still, the App Center offers upgrades for âKopano WebAppâ to version 3.4.19.1649 and âZ-Push for Kopanoâ to version 2.4.2 because the actual version numbers are not transferred for the Kopano Repo installed products.
Is there something I should/could do about this?
BR,
TP
I would rather recommend to follow the steps layed out in the official documentation. This also states that you should install the available updates from the appcenter, this is required since integration updates are only provided through the appcenter.
Hello @fbartels,
- install any available app updates
I have in fact tried to install these updates from App Center for both WebApp and Z-Push prior to reactivating the Kopano-Repo again, but ended up with errors in GUI on both.
I didnât analyze it further because I thought it had been caused by the newer versions already installed in UCS 4.2 and couldnât install any older versions from the App Center anyway.
Should I uninstall both Kopano-Repo updated packages and try to install the App Center delivered ones again prior to reactive Kopano-Repo?
BR,
TP