kopano-spooler upgrade problem K-1733
-
About the files, i have
python2-mapi_8.6.80.760-0+89.1_amd64.deb
python3-mapi_8.6.80.760-0+89.1_amd64.debYou are showing
python-mapi_8.6.80.760-0+90.1_amd64.debso yes, a change in the deb names, and an error in the Debian Control file.
@fbartels
the control in the file stats:
Replaces: libkcpyconv0, libkcpydirector0, python-mapiwhich is incorrect, it replaces python2-mapi.
@rothirschtech so
yes, use your versionNo, try to get the 0.89+1 version.
That one is ok. -
I also notice the complete lib and it content is missing here.
the .89+1 also contains in the deb /usr/lib/ a few files and python2.7/files and /usr/share/doc…
the .90+1 only contrains /usr/share/doc. -
Ok thanks for the fast response.
I’ll try the next version on my testing environment and will report here if the problem has been resolved.
Have a great day
-
I had the same issue today and a revert to the previous version fixed it for me for emails sent after the revert. Still, all mails supposed to be sent, while the broken version was live, are still in the Outboxes of the users. How can I tell Kopano to send those?
Thanks.
-
Same issue here.
kopano-spooler should normally resend them every couple seconds.As I had installed the version 8.6.80.760-0+90.1 I got Sent successfully popup-messages on kopano-webapp after sending an e-mail.
So it seems that some process recognized them as sent but webapp left them in the outbox. -
Hi everyone,
we discussed this internally this morning and are going to remove the additional python3 dependencies from these packages for the moment. Follow https://jira.kopano.io/browse/KC-1149 for more updates.
-
Thanks for the support
-
Update: we have just kicked off our nightly release pipeline again, so new packages (which will resolve this issue) will be available shortly (if all automated tests succeed).
edit: for everyone not wanting to wait till then, there is obviously the possibility to disable the python plugin framework in spooler/dagent by setting
plugin_enabled = no
. -
Hai,
I saw this old bug report, i’ve seen this also in version : 8.7.81.151.4eaf3e0cf-0+249.1
-
@thctlo reply to myself.
This is happening due to the wrong rights after kopano-server (re)start
/var/run/kopano/*.sock shows root:root, not kopano:kopano -
@thctlo said in kopano-spooler upgrade problem K-1733:
This is happening due to the wrong rights after kopano-server (re)start
This issue is already being discussed in https://forum.kopano.io/topic/2512/socket-permissions-issues-with-kopano-server-build-8-7-81-162.
Since the original issue has been resolved I am going to close this topic.