Unable to export mail

jasgggit

Thank you for your replies, all of them, question :

How can I get the 8.7 ??? its not available on the APP store …

Regards.
JG

fbartels

As explained in https://kopano.com/blog/staying-up-to-date-with-kopano-releases-on-ucs we cannot upload all our releases to the ucs appcenter, since an app uploaded to the appcenter is always available to all ucs users.

If you have a subscription, then you can enable our “final” repository from the appcenter settings (this is also explained in the above log). at this point in time our 8.7 release is not in the final repo, but in a dedicated subdir. To add this repo you can execute the following command on your ucs system:

echo "deb https://$(ucr get kopano/repo/username):$(ucr get kopano/repo/password)@download.kopano.io/supported/core:/8.7/Univention_4.3/ /" >> /etc/apt/sources.list

jasgggit

@fbartels said in Unable to export mail:

Univention_4.3/

Thank you @fbartels

It’s for 4.3 and I’m on 4.4 … any issues with that ???

Regards.
JG

fbartels

@jasgggit both ucs 4.3 and 4.4 share the same Debian base. I have discussed this already a few times and even got confirmation from the Univention developers that its safe to use the same packages for both releases.

PS: why the surplus of question marks?

jasgggit

@fbartels Thanks for your quick reply.

Tried and failed …

Err:257 https://download.kopano.io/supported/core:/8.7/Univention_4.3  Release
  401  Unauthorized
Err:278 https://download.kopano.io/supported/core:/8.7/Univention_4.4  Release
  401  Unauthorized
A ler as listas de pacotes... Pronto
E: The repository 'https://download.kopano.io/supported/core:/8.7/Univention_4.3  Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'https://download.kopano.io/supported/core:/8.7/Univention_4.4  Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

PSS - Surplus of question marks? This ‘???’ ? – Nothing in special, I’m not an English speaking person, and sometimes we tend to use some of ‘native’ language ‘marks’. If that was wrong please apologise.

Regards.
JG

fbartels

@jasgggit said in Unable to export mail:

https://download.kopano.io/supported/core:/8.7/Univention_4.4

This is wrong, there is no such folder (Univention_4.4) on the server.

@jasgggit said in Unable to export mail:

401 Unauthorized

Maybe your trial has expired?

jasgggit

@fbartels said in Unable to export mail:

@jasgggit said in Unable to export mail:

https://download.kopano.io/supported/core:/8.7/Univention_4.4

This is wrong, there is no such folder (Univention_4.4) on the server.

I will remove that, it was a test.

@jasgggit said in Unable to export mail:

401 Unauthorized

Maybe your trial has expired?

HI, and again thank you for your quick reply.
I’ve requested the trial key on 18/4 , but I used a different email address from the one I’ve installed the UCS system, although on same domain. Could it be that ?

Regards.
JG

fbartels

@jasgggit said in Unable to export mail:

I’ve requested the trial key on 18/4 , but I used a different email address from the one I’ve installed the UCS system, although on same domain. Could it be that ?

No, the email address should be irrelevant here. I’d suggest to send a short mail to our sales team to check your trial license. You should have received some follow up mails to which you can just reply, ir you could send it to info at kopano dot com.

jasgggit

@fbartels Thank you, I 'll reply to one of those emails.

Thank you for all the support and the quick replies.

Best regards.
JG

jasgggit

@fbartels , I managed to contact Kopano support and them sorted out the issue with the trial key.

So, I upgraded the Kopano-core to 8.7 version, and now … well for now the kopano-gateway is not working …

BTW, I upgraded it using the ‘univention-upgrade’ command.

it says:

root@k4ucs:~# systemctl status kopano-gateway.service 
● kopano-gateway.service - Kopano Groupware Core IMAP/POP3 Gateway
   Loaded: loaded (/lib/systemd/system/kopano-gateway.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2019-04-26 14:04:32 WEST; 4s ago
     Docs: man:kopano-gateway(8)
           man:kopano-gateway.cfg(5)
  Process: 15795 ExecStart=/usr/sbin/kopano-gateway -F (code=exited, status=1/FAILURE)
 Main PID: 15795 (code=exited, status=1/FAILURE)
      CPU: 23ms

abr 26 14:04:32 k4ucs systemd[1]: Started Kopano Groupware Core IMAP/POP3 Gateway.
abr 26 14:04:32 k4ucs kopano-gateway[15795]: [crit   ] Config error: Unknown option "pop3s_enable" found!
abr 26 14:04:32 k4ucs kopano-gateway[15795]: [crit   ] Config error: Unknown option "imaps_enable" found!
abr 26 14:04:32 k4ucs kopano-gateway[15795]: /usr/sbin/kopano-gateway: Startup failed: call failed (80004005). Please check the logfile () for details.
abr 26 14:04:32 k4ucs systemd[1]: kopano-gateway.service: Main process exited, code=exited, status=1/FAILURE
abr 26 14:04:32 k4ucs systemd[1]: kopano-gateway.service: Unit entered failed state.
abr 26 14:04:32 k4ucs systemd[1]: kopano-gateway.service: Failed with result 'exit-code'.

Any ideas?

Regards.
Jorge Gomes

fbartels

@jasgggit the answer to this can be found in the update readme (file that is displayed when updating the app on univention)

the integration has been updated to support the upcoming Kopano Groupware Core 8.7 release

IMPORTANT: After updating to 8.7.x through the Kopano apt repository you will find that ´kopano-gateway´ and ´kopano-ical´ will refuse to start because of an incompatible configuration. Please execute the script `/usr/share/kopano4ucs/kopano4ucs-update-settings870.sh´ to update your configuration files. This will be done later on automatically when the Kopano Core app natively provides this release.

jasgggit

@fbartels , Hi

I tried to comment out those two options on the /etc/kopano/gateway.cfg file but didn’t solve my problem :

root@k4ucs:~# systemctl status kopano-gateway.service 
● kopano-gateway.service - Kopano Groupware Core IMAP/POP3 Gateway
   Loaded: loaded (/lib/systemd/system/kopano-gateway.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2019-04-26 14:26:23 WEST; 13min ago
     Docs: man:kopano-gateway(8)
           man:kopano-gateway.cfg(5)
 Main PID: 549 (kopano-gateway)
    Tasks: 1 (limit: 9830)
   Memory: 7.4M
      CPU: 67ms
   CGroup: /system.slice/kopano-gateway.service
           └─549 /usr/sbin/kopano-gateway -F

abr 26 14:26:23 k4ucs systemd[1]: Started Kopano Groupware Core IMAP/POP3 Gateway.
abr 26 14:26:32 k4ucs kopano-gateway[549]: Starting kopano-gateway version 8.7.0 (pid 549 uid 0)
abr 26 14:26:32 k4ucs kopano-gateway[549]: Starting kopano-gateway version 8.7.0 (pid 549 uid 998)

I can’t see anything on the log (syslog) regarding why is stuck.

Hope you can shine some light.

Regards.
JG

jasgggit

@fbartels said in Unable to export mail:

/usr/share/kopano4ucs/kopano4ucs-update-settings870.sh

@fbartels its seems not working.

root@k4ucs:/etc/kopano# /usr/share/kopano4ucs/kopano4ucs-update-settings870.sh  
Installation with Kopano Groupware Core 8.7 detected
configuring kopano-gateway
Not updating kopano/cfg/gateway/pop3s_listen
Not updating kopano/cfg/gateway/imaps_listen
Not updating kopano/cfg/gateway/ssl_private_key_file
Not updating kopano/cfg/gateway/ssl_certificate_file
removing obsolete options from kopano-gateway configuration
W: The config registry variable 'kopano/cfg/gateway/imap_enable' does not exist
W: The config registry variable 'kopano/cfg/gateway/imap_generate_utf8' does not exist
W: The config registry variable 'kopano/cfg/gateway/imap_port' does not exist
W: The config registry variable 'kopano/cfg/gateway/imap_store_rfc822' does not exist
W: The config registry variable 'kopano/cfg/gateway/imaps_port' does not exist
W: The config registry variable 'kopano/cfg/gateway/pop3_enable' does not exist
W: The config registry variable 'kopano/cfg/gateway/pop3_port' does not exist
W: The config registry variable 'kopano/cfg/gateway/pop3s_port' does not exist
configuring kopano-ical
Not updating kopano/cfg/ical/icals_listen
Not updating kopano/cfg/ical/server_timezone
Not updating kopano/cfg/ical/ssl_private_key_file
Not updating kopano/cfg/ical/ssl_certificate_file
removing obsolete options from kopano-ical configuration
W: The config registry variable 'kopano/cfg/ical/icals_enable' does not exist
W: The config registry variable 'kopano/cfg/ical/ical_enable' does not exist
W: The config registry variable 'kopano/cfg/ical/ical_port' does not exist
W: The config registry variable 'kopano/cfg/ical/icals_port' does not exist

Before doing this I reverted to the saved config file prior my manual changes.

Regards.
JG

fbartels

@jasgggit why do you think its stuck? according to your systemctl output the service is running.

I would really recommend to run the existing script. while these two options prevent the service from starting, there are some other things that need to be updated as well.

Alternatively have a look at the release announcement for other changed configuration options: https://forum.kopano.io/topic/2110/kopano-groupware-core-8-7-final-available

jasgggit

@fbartels ,

It seems NOT to work, from my post above and prior to your last one, but as I said, after reading the one that mentioned the scrip, that BTW was upgraded using CLI, and no message displayed, but thank you for your input regarding the script, I have reverted the config file to the state when it was upgraded.

I run the script, but gave me the above messages, regarding not finding the variables needed, but, a check using the GUI tels me that they are there.

root@k4ucs:/etc/kopano# ucr search kopano/cfg/gateway/*                                                                                                                             
kopano/cfg/gateway/imaps_enable: yes
kopano/cfg/gateway/imaps_listen: *:993
kopano/cfg/gateway/pop3s_enable: no
kopano/cfg/gateway/pop3s_listen: *:995
kopano/cfg/gateway/ssl_certificate_file: /etc/univention/letsencrypt/signed_chain.crt
kopano/cfg/gateway/ssl_private_key_file: /etc/univention/letsencrypt/domain.key

Regards.
JG

fbartels

@jasgggit yes, the script is a bit chatty, but if you check your output you will see it complained about other values missing.

The important question is: does gateway work now?

jasgggit

@fbartels

It does not.

Step 1: Reverting to config file after the upgrade process and started the service, fails

root@k4ucs:/etc/kopano# systemctl status kopano-gateway.service                                                                                                                     
● kopano-gateway.service - Kopano Groupware Core IMAP/POP3 Gateway
   Loaded: loaded (/lib/systemd/system/kopano-gateway.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2019-04-26 15:54:32 WEST; 3s ago
     Docs: man:kopano-gateway(8)
           man:kopano-gateway.cfg(5)
  Process: 20184 ExecStart=/usr/sbin/kopano-gateway -F (code=exited, status=1/FAILURE)
 Main PID: 20184 (code=exited, status=1/FAILURE)
      CPU: 23ms

abr 26 15:54:32 k4ucs systemd[1]: Started Kopano Groupware Core IMAP/POP3 Gateway.
abr 26 15:54:32 k4ucs kopano-gateway[20184]: [crit   ] Config error: Unknown option "pop3s_enable" found!
abr 26 15:54:32 k4ucs kopano-gateway[20184]: [crit   ] Config error: Unknown option "imaps_enable" found!
abr 26 15:54:32 k4ucs kopano-gateway[20184]: /usr/sbin/kopano-gateway: Startup failed: call failed (80004005). Please check the logfile () for details.
abr 26 15:54:32 k4ucs systemd[1]: kopano-gateway.service: Main process exited, code=exited, status=1/FAILURE
abr 26 15:54:32 k4ucs systemd[1]: kopano-gateway.service: Unit entered failed state.
abr 26 15:54:32 k4ucs systemd[1]: kopano-gateway.service: Failed with result 'exit-code'.

Step2: Running the script and started the service, failed too

root@k4ucs:/etc/kopano# systemctl status kopano-gateway.service                 
● kopano-gateway.service - Kopano Groupware Core IMAP/POP3 Gateway
   Loaded: loaded (/lib/systemd/system/kopano-gateway.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2019-04-26 15:56:58 WEST; 2s ago
     Docs: man:kopano-gateway(8)
           man:kopano-gateway.cfg(5)
  Process: 20242 ExecStart=/usr/sbin/kopano-gateway -F (code=exited, status=1/FAILURE)
 Main PID: 20242 (code=exited, status=1/FAILURE)
      CPU: 23ms

abr 26 15:56:58 k4ucs systemd[1]: Started Kopano Groupware Core IMAP/POP3 Gateway.
abr 26 15:56:58 k4ucs kopano-gateway[20242]: [crit   ] Config error: Unknown option "pop3s_enable" found!
abr 26 15:56:58 k4ucs kopano-gateway[20242]: [crit   ] Config error: Unknown option "imaps_enable" found!
abr 26 15:56:58 k4ucs kopano-gateway[20242]: /usr/sbin/kopano-gateway: Startup failed: call failed (80004005). Please check the logfile () for details.
abr 26 15:56:58 k4ucs systemd[1]: kopano-gateway.service: Main process exited, code=exited, status=1/FAILURE
abr 26 15:56:58 k4ucs systemd[1]: kopano-gateway.service: Unit entered failed state.
abr 26 15:56:58 k4ucs systemd[1]: kopano-gateway.service: Failed with result 'exit-code'.

Rebboting the server, as been done before but going to do it again …

jasgggit

@fbartels , ok nothing seems to work, so I’m reverting the VM to a previous restore point, and going to do it all over …

jasgggit

@fbartels ,

Just a very quick update !!!

It seems that everything I try fails.

I’ve reverted the VM to a previous state, on 8.6.x, all working.

I’ve run the ‘kopano-dbadm k-1216’ , previously and after the upgrade, got some issues with Kopano-Server, and run ‘kopano-dbadm usmp’ , and the kopano-server started, but kopano-gateway it won’t, even after running the script.

If you have some ‘steps’ that I should run to give you more info about this upgrade, please let me know.

I’ll continue this on Monday, please have a nice weekend.

Regards.
JG

fbartels

Hi @jasgggit ,

as you’ve already been in contact with our support please sort this out with them. It’s not entirely clear to me which steps you are taking.