Updating grommunio 2022.12.1 to 2023.11.1

nettania

Hi,
today I tried to perform an update of the 2022.12.1 appliance to 2023.11.1 using zypper dup. After updating I had a problem with MariaDB, the timeout was too short to update the databases to the current version, but after changing timeout it worked.
However there exists no ews.cfg file in /etc/gromox/- What can be the reason fot this?
This are the currently installed grommunio packages:

grommunio-admin-api-1.14.0.7c32a58-lp154.85.1.noarch grommunio-admin-common-19.fca083c-lp154.15.1.noarch grommunio-admin-web-2.8.0.18.a39ffbd-lp154.67.1.noarch grommunio-antispam-3.7.3-lp154.6.1.x86_64 grommunio-archive-1.3.13.g137.d1b0df1b-lp154.5.9.x86_64 grommunio-common-21.8eb9e0e-lp154.34.1.x86_64 grommunio-cui-1.0.255.e6a3c53-lp154.56.1.noarch grommunio-dav-1.3.16.17b01b4-lp154.1.1.noarch grommunio-dbconf-1.1.1.da20a46-lp154.4.6.x86_64 grommunio-error-pages-1.0.10.bb2df37-lp154.10.1.noarch grommunio-files-25.0.12-lp154.4.1.noarch grommunio-imapsync-2.264-lp154.1.1.noarch grommunio-index-0.1.37.74e396b-lp154.40.2.x86_64 grommunio-release-2022.12.1-lp154.7.1.x86_64 grommunio-setup-1.0.103.7786fbd-lp154.41.1.noarch grommunio-sync-2.0.38.12b2e4f-lp154.139.1.noarch grommunio-web-3.6.0.d28e88b9-lp154.4.2.noarch gromox-2.17.88.da6bc72-lp154.28.1.x86_64 gromox-debuginfo-2.17.88.da6bc72-lp154.28.1.x86_64 gromox-debugsource-2.17.88.da6bc72-lp154.28.1.x86_64 grub2-theme-grommunio-1-lp154.15.1.noarch patterns-grommunio-1-lp154.9.1.x86_64 plymouth-theme-grommunio-1-lp154.15.1.noarch systemd-coredump-grommunio-1-lp154.3.1.noarch systemd-presets-branding-grommunio-2023.11-lp154.1.1.noarch system-user-grommunio-3-lp154.10.3.noarch

Thanks, Florian

WalterH

nettania However there exists no ews.cfg file in /etc/gromox/- What can be the reason fot this?

You need to create this file with only one line: ews_beta=1
like:
echo "ews_beta=1" > /etc/gromox/ews.cfg

nettania

Thank you for the information. I just wanted to get sure, that not something went wrong during update.

Florian

nettania

EWS works, great work, thank you!
Unfortunately, since the update the webmail has some severe problems, if I check the web console of the browser a lot of 504 error are returned, loading an e-mail, or switching into a folder, is nearly impossible, because it takes a long time, oder I get the information that the connection is lost. But there are no errors in the logs and I already reinstalled grommunio-web.
Has someone a suggestion where I should look?

Florian

mwilliams

nettania

You might want to try a normal zypper ref; zypper up followed by grommunio-update for full distro upgrade.

Andy

mwilliams try a normal zypper ref; zypper up followed by grommunio-update for

It means, I use that commands in succession it means first

zypper ref; zypper up

and after is done I use

grommunio-update

right?

nettania

mwilliams

Hi,
thank you for the information, tried zypper ref; zypper up and than grommunio-update check, grommunio-update update and grommunio-update upgrade, result of the last call:

`
This system : grommunio
Uptime : 14:15
Load : Last Minute: 2,65, Last 5 Minutes: 1,67, Last 15 Minutes: 0,77
IP Address : 10.20.1.2
Executed : /usr/sbin/grommunio-update upgrade
Start : Mi 2023-11-22 10:12:14 CET
Operation : Upgrade

Starting Upgrade (zypper ref && zypper dup -y)
Repository 'base' ist aktuell.
Repository 'debug' ist aktuell.
Repository 'debug-update' ist aktuell.
Repository 'grommunio' ist aktuell.
Repository 'repo-backports-update' ist aktuell.
Repository 'repo-sle-update' ist aktuell.
Repository 'update' ist aktuell.
Alle Repositorys wurden aktualisiert.
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
Warnung: Sie sind im Begriff, eine Distributionsaktualisierung mit allen aktivierten Repositorys durchzuführen. Vergewissern Sie sich, dass diese Repositorys kompatibel sind, bevor Sie fortfahren. Weitere Informationen zu diesem Kommando finden Sie unter 'man zypper'.
Distributions-Aktualisierungen werden verarbeitet...
Keine auszuführenden Aktionen.

Upgrade completed successfully.
Updating postfix configuration with new maps if exist
Running post-update/upgrade checksdbop: Current database schema: gx-131

Checking for pending service restart or reboot

End Upgrade : Mi 2023-11-22 10:12:21 CET
`

Unfortunately I still get many 503 and 504 errors. and when I reboot the appliance still shows me 2022.12.1 as version. It's confusing because, sending and receiving E-Mails works fine, only the frontend has currently problems (and is extremely slow), even top does not show any system load.

Florian

Andy

Is there a documentation or syntax about grommunio-update?

nettania

Andy
If you enter grommunio-update a list with options are displayed. There are not a lot, mainly, the three mentioned by me in the last thread.

Florian

Florian1903

Hallo at all,
this is my first post here! Our server has been running with Grommunio since August, changed from Exchange.
I have the same thing with the ews.cfg
But I have many other problems, which I will discuss in a separate thread

Best, Florian

nettania

Current situation after latest update (16:00):

Outlook on windows is working without issues!
Webmail is unfortunately currently nearly not useable, still 503 and 504 error and a lot of messages about lossing connection to the server, loading of an E-Mail takes a long time.
Outlook for Mac: E-Mails arriving and sending is possible, but serveral sync conflicts, when loading E-Mail with external sources. Calendar entries are shown and can be edited. Contacts are displayed but only as empty entry.
MacOS: Contacts are shown also as empty.
iOS: Fortunately I have no issues.

How should we update the appliance?

With grommunio-update (which seams that the command simple call some zypper commands), or using zypper? This is confusing.

I hope this helps and/or someone can give me a hint to my webmail problem, which is currently the most severe one, for me.

Florian

crpb

nettania With grommunio-update (which seams that the command simple call some zypper commands), or using zypper? This is confusing.

from what i understand it is basically just a wrapper to help people doing updates and it is also the script which gets called via the web-admin which can be used by clicking on the gear on the top-right as shown here

Vogi

nettania Current situation after latest update (16:00):

Outlook on windows is working without issues!
Webmail is unfortunately currently nearly not useable, still 503 and 504 error and a lot of messages about lossing connection to the server, loading of an E-Mail takes a long time.
Outlook for Mac: E-Mails arriving and sending is possible, but serveral sync conflicts, when loading E-Mail with external sources. Calendar entries are shown and can be edited. Contacts are displayed but only as empty entry.
MacOS: Contacts are shown also as empty.
iOS: Fortunately I have no issues.

For me the situation after update is much worse:

Outlook working, but very slow sync
iPhone: Working but even slower. Often stops syncing with "account error". From time to time the password must be re-entered
Webmail: First login shows the web-UI. But as soon as i select an item, it hangs and responds with a 504 error

My system is a VM on a Synology 920+ It worked without any issues until the update.
No error entries can be seen in the logs, only timeouts in the sync.log.

I know that this is not a good error report - but I have no idea what to do to locate the problem
Went back to a snapshot before this update and everything is good again.

WalterH

crpb from what i understand it is basically just a wrapper to help people doing updates

grommunio-update launches zypper ref; zypper up or dup to upgrade the system and repairs some other issues like postfix maps.

crpb

WalterH

Thx for the info about postfix, i missed that it calls /usr/sbin/grommunio-postfix. So basically your Article about extending it to the latest state to make use of all changes?
That was still on my list for a couple hosts 🙈.
I will probably try my first upgrade this weekend. Was only testing the OVA till yet and already have a few tickets open 😊

WalterH

crpb So basically your Article about extending it to the latest state to make use of all changes?

The script works similar.

Andy

I currently have two VM installations on a Synology DS1621xs+ for testing with the new appliance Build11.2 with the ISO. In parallel I performed with my productive installation v2022.12.1 “Update” via the admin GUI.

The installation was completely changed from v2022.12.1 with lp154 to v2023.11.1 with lp155 and run without problems. Maybe you can describe how did you carry out the update?

nettania

Today, I tried a second approach to migrate a 2022.12.1 to 2023.11.1, performing the following steps:

Changed the timeout for starting mariadb to infinity
Login on CUI and select "Aktualisiere das System"
Executing the update process without any issues.
Restarting the appliance
Executing update using the GUI.

The result ist, that the update works, but the webmail is still not useable, endless loading, and permanent 503 and 504 errors in the browser console. Several synchronization conflicts with Microsoft Outlook for windows. Deleting the browser cache did not help.

I had to rollback the update loading the old snapshot.

I also created a virtual machine with the current ova and there everything worked. But I do not hope that I have to migrate the productive instance by exporting all accounts and importing it to the new appliance.

Florian

Vogi

nettania The result ist, that the update works, but the webmail is still not useable, endless loading, and permanent 503 and 504 errors in the browser console. Several synchronization conflicts with Microsoft Outlook for windows. Deleting the browser cache did not help.

This describes exactly ma problems.

@Andy: I don't think, that this is an "installation issue". I tried to update several times (via zypper, WebUI and combinbations) but the result was always the same. The system became unusable with the latest versions but without any helpful log entries... returning to the last working snapshot was the only way for me to make it work again...

WalterH

nettania Changed the timeout for starting mariadb to infinity
Login on CUI and select "Aktualisiere das System"

Why you change the timeout? The database is small, the update needs only seconds.
Try the update on command line with zypper ref -f; zypper up; grommunio-update update --noreboot

Andy

Doe you try the above showed "UPGRADE" button for this? Which browser you are using and doe you try to use different browsers? How many postboxes you have? Maybe is possible, to use Outlook to transfer and test one postbox.