tf91 to cleanup / solve this issue, run this command:
rpm -e dracut-kiwi-lib dracut-kiwi-live dracut-kiwi-oem-dump dracut-kiwi-oem-repart kiwi-systemdeps-bootloaders kiwi-systemdeps-core kiwi-systemdeps-disk-images kiwi-systemdeps-filesystems kiwi-systemdeps-iso-media kiwi-tools
FYI: this packages are not needed for grommunio.
Upgrade Appliance to opensuse 15.4
- Edited
crpb Nach einem zypper dup hat wieder alles funktioniert.
Sadly it doesn't work anymore like it did two weeks ago. Did try an Upgrade of my actual System which just broke it.
After that i tried the ova 2022.12.1 which was a bit odd with the different $repoversions. At least i upgraded it to 15.4 but haven't tried an actual installation yet as stuff like this is still a bit icky..
grommunio-2022121:~ # rpm -q -f /etc/php7/fpm/php-fpm.d/pool-grommunio-*
grommunio-dav-1.1.32.71acf2d-lp154.8.1.noarch
grommunio-sync-1.1.49-lp154.54.1.noarchAnd grommunio-dav is currently also broken and i'm not alone
That's actually still on 15.3..
gromi:~ # _grom_versions
grommunio-admin-api 1.9.19.ffb31e8
grommunio-admin-common 6.cb985db
grommunio-admin-web 2.6.0.30.3a13674
grommunio-antispam 3.4
grommunio-common 10.e94d08a
grommunio-cui 1.0.233.d95a532
grommunio-dav 1.1.32.71acf2d
grommunio-dav 1.1.32.71acf2d
grommunio-dbconf 1.1.1.da20a46
grommunio-error-pages 1.0.6.9c50afb
grommunio-imapsync 2.200
grommunio-index 0.1.14.f713867
grommunio-release 2022.05.2
grommunio-setup 1.0.67.98c18be
grommunio-sync 1.1.49
grommunio-web 3.1.141.491f865
gromox-debuginfo 1.37.82.4a94326
gromox-debugsource 1.37.82.4a94326
gromox 1.37.82.4a94326
grub2-theme-grommunio 1
libHX32 4.8
libexmdbpp0 1.10.0.3a4d93b
libfmt8 8.1.1
libgumbo1 0.10.1
libpff1 20211114
libtinyxml2-9 9.0.0
libvmime-suse5 0.9.2.175
mapi-header-php 1.0.1.705eff3
nginx-module-brotli 1.0.0rc+g1
nginx-module-vts 0.2.1+g1b
patterns-grommunio 1
perl-Authen-NTLM 1.09
perl-Encode-IMAPUTF7 1.05
perl-JSON-WebToken 0.10
perl-Sys-MemInfo 0.99
plymouth-theme-grommunio 1
prosody 0.11.13
python3-jsonschema 3.2.0
python3-lazy-object-proxy 1.2.2
python3-mattermostdriver 7.3.2
python3-more-itertools 8.12.0
python3-openapi-core 0.13.7
python3-openapi-schema-validator 0.1.5
python3-openapi-spec-validator 0.2.9
python3-pamela 1.0.0
python3-parse 1.19.0
python3-pyexmdb 1.10.0.3a4d93b
python3-rfc3339-validator 0.1.4
python3-strict-rfc3339 0.7
system-user-grodav 2
system-user-grommunio 2
system-user-gromox 2
system-user-grosync 1
system-user-groweb 2
systemd-presets-branding-grommunio 2022.12Wait with the update, grommunio will provide update instructions in near future.
- Edited
Joa, ich warte bis die Pakete gefixt sind. Dann kann ich es noch mal probieren :-).
Ist ja auch alles "gesichert" von daher kann nicht viel schief gehen.
35 1,5,9,13,17,21 * * * /bin/sh -c '/root/bin/grombak 2>&1 | systemd-cat -t grombak -p 5'PS: Ja, ich vertraue worseFS nicht so wirklich...
a month later
- Edited
Are the any news for the upgrade?
If I replace 15.3 with 15.4 in repo files I have unresolved dependencies:
vm3:~ # zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.
| Alias | Name | Enabled | GPG Check | Refresh | URI
--+-----------------------------+----------------------------------------------------------------------------+---------+-----------+---------+--------------------------------------------------------------------------------------------
1 | base | base | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.4/repo/oss
2 | debug | debug | Yes | (r ) Yes | No | http://download.opensuse.org/debug/distribution/leap/15.4/repo/oss
3 | debug-update | debug-update | Yes | (r ) Yes | No | http://download.opensuse.org/debug/update/leap/15.4/oss
4 | grommunio | grommunio | Yes | (r ) Yes | Yes | https://xxxxxxxxxxxxxxxx@download.grommunio.com/supported/openSUSE_Leap_15.4/?ssl_verify=no
5 | repo-backports-debug-update | repo-backports-debug-update | Yes | (r ) Yes | No | http://download.opensuse.org/update/leap/15.4/backports_debug/
6 | repo-backports-update | repo-backports-update | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.4/backports/
7 | repo-sle-debug-update | Update repository with debuginfo for updates from SUSE Linux Enterprise 15 | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.4/sle/
8 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.4/sle/
9 | update | update | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.4/ossvm3:~ # zypper --releasever=15.4 dup --download-in-heaps
Warning: Enforced setting: $releasever=15.4
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
3 Problems:
Problem: the to be installed gromox-2.0.10.6b64a7a-lp154.4.1.x86_64 requires 'php8-soap', but this requirement cannot be provided
Problem: the to be installed grommunio-sync-1.1.49-lp154.16.1.noarch requires 'php8-soap', but this requirement cannot be provided
Problem: the to be installed patterns-grommunio-1-lp154.8.1.x86_64 requires 'grommunio-web', but this requirement cannot be provided
Problem: the to be installed gromox-2.0.10.6b64a7a-lp154.4.1.x86_64 requires 'php8-soap', but this requirement cannot be provided
not installable providers: php8-soap-8.0.10-150400.2.7.x86_64[base]
php8-soap-8.0.10-150400.4.3.1.x86_64[repo-sle-update]
php8-soap-8.0.10-150400.4.8.1.x86_64[repo-sle-update]
php8-soap-8.0.24-150400.4.14.1.x86_64[repo-sle-update]
php8-soap-8.0.25-150400.4.17.1.x86_64[repo-sle-update]
php8-soap-8.0.25-150400.4.20.1.x86_64[repo-sle-update]
php8-soap-8.0.27-150400.4.23.1.x86_64[repo-sle-update]
Solution 1: Following actions will be done:
deinstallation of php7-smbclient-1.0.0-bp153.1.20.x86_64
deinstallation of php7-7.4.33-150200.3.46.2.x86_64
Solution 2: deinstallation of gromox-2.0.10.6b64a7a-lp153.4.1.x86_64
Solution 3: keep obsolete gromox-2.0.10.6b64a7a-lp153.4.1.x86_64
Solution 4: break gromox-2.0.10.6b64a7a-lp154.4.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c/d/?] (c):My versions
vm3:~ # rpm -qa |grep -E "(grommunio|gromox|mapi|libHX32|libexmdbpp|libfmt|libgumbo1|libpff1|libtinyxml|libvmime)" | sort
grommunio-admin-api-1.9.19.ffb31e8-lp153.9.1.noarch
grommunio-admin-common-6.cb985db-lp153.3.1.noarch
grommunio-admin-web-2.6.0.30.3a13674-lp153.5.1.noarch
grommunio-antispam-3.4-lp153.1.1.x86_64
grommunio-archive-1.3.12.g137.d1b0df1b-lp153.2.38.x86_64
grommunio-chat-6.2.2-lp153.2.1.x86_64
grommunio-common-10.e94d08a-lp153.5.1.x86_64
grommunio-cui-1.0.235.55d4960-lp153.9.1.noarch
grommunio-dav-1.1.32.71acf2d-lp153.8.1.noarch
grommunio-error-pages-1.0.6.9c50afb-lp153.3.1.noarch
grommunio-files-10.9.1-lp153.1.1.noarch
grommunio-imapsync-2.178-lp153.1.1.noarch
grommunio-index-0.1.15.d3ec048-lp153.4.1.x86_64
grommunio-office-7.0.0-lp153.1.8.x86_64
grommunio-office-fonts-7.0.0-lp153.1.8.noarch
grommunio-release-2022.05.2-lp153.2.1.x86_64
grommunio-setup-1.0.67.98c18be-lp153.5.1.noarch
grommunio-sync-1.1.49-lp153.16.1.noarch
grommunio-web-3.1.141.491f865-lp153.12.4.noarch
gromox-2.0.10.6b64a7a-lp153.4.1.x86_64
gromox-debuginfo-2.0.10.6b64a7a-lp153.4.1.x86_64
gromox-debugsource-2.0.10.6b64a7a-lp153.4.1.x86_64
grub2-theme-grommunio-1-lp153.11.4.noarch
jitsi-meet-branding-grommunio-2.0.6726-lp153.2.1.noarch
libHX32-4.8-lp153.2.1.x86_64
libexmdbpp0-1.10.0.3a4d93b-lp153.7.1.x86_64
libfmt7-7.1.3-bp153.1.17.x86_64
libfmt8-8.1.1-lp153.5.2.x86_64
libgumbo1-0.10.1-lp153.1.4.x86_64
libpff1-20211114-lp153.6.1.x86_64
libtinyxml2-9-9.0.0-lp153.3.1.x86_64
libvmime-suse5-0.9.2.175-lp153.13.1.x86_64
mapi-header-php-1.0.1.705eff3-lp153.2.1.noarch
patterns-grommunio-1-lp153.8.1.x86_64
plymouth-theme-grommunio-1-lp153.11.4.noarch
system-user-grommunio-2-lp153.11.1.noarch
system-user-gromox-2-lp153.13.1.noarch
systemd-presets-branding-grommunio-2022.12-lp153.1.1.noarch
Same to us - we also waiting for a stable time window in the supported channel to do the upgrade!
But every weekend we find new trouble and ending up in a not running appliance.
Here are our steps summary:
To fix the permanent warnings
The following 10 package updates will NOT be installed:
dracut-kiwi-lib dracut-kiwi-live dracut-kiwi-oem-dump dracut-kiwi-oem-repart kiwi-systemdeps-bootloaders kiwi-systemdeps-core kiwi-systemdeps-disk-images kiwi-systemdeps-filesystems kiwi-systemdeps-iso-media kiwi-tools
rpm -e dracut-kiwi-lib dracut-kiwi-live dracut-kiwi-oem-dump dracut-kiwi-oem-repart kiwi-systemdeps-bootloaders kiwi-systemdeps-core kiwi-systemdeps-disk-images kiwi-systemdeps-filesystems kiwi-systemdeps-iso-media kiwi-tools
Zypper refresh
zypper ref
Zypper update
zypper up
edit the repo files (replace 15.3 by 15.4)
sed -i "s/15.3/15.4/g" /etc/zypp/repos.d/base.repo
sed -i "s/15.3/15.4/g" /etc/zypp/repos.d/grommunio.repo
sed -i "s/15.3/15.4/g" /etc/zypp/repos.d/grommunio-base.repo
Opensuse Version Upgrade to 15.4
zypper --releasever=15.4 dup --download-in-heaps
The following just FYI - as most know i think :-)
Disable repository
zypper modifyrepo -d grommunio
Enable repository
zypper modifyrepo -e grommunio
Show the installed version
rpm -qa |grep -E "(grommunio|gromox|mapi|libHX32|libexmdbpp|libfmt|libgumbo1|libpff1|libtinyxml|libvmime)" | sort
Will be nice to get some comments how we can fix is in a short time !
ncoker If you have to to this: rpm -e dracut-kiwi-lib dracut-kiwi-live dracut-kiwi-oem-dump dracut-kiwi-oem-repart kiwi-systemdeps-bootloaders kiwi-systemdeps-core kiwi-systemdeps-disk-images kiwi-systemdeps-filesystems kiwi-systemdeps-iso-media kiwi-tools you have a very old installation. Yes, these packages are unused and needs to be removed.
WalterH If 2022.5.1 is very old, then yes. The packages came from the original applicance installation last year. I had to erase it too.
ncoker Here are our steps summary:
Thanks for your steps. After
ncoker zypper --releasever=15.4 dup --download-in-heaps
there is the error again, I've described in my post
I hope for any hints. At the moment I try to upgrade my test vm.
Thanks
Ulf
Im also very interested in this and wanted to ask this now.
It seems there are some strange problems since Christmas-Update. I also use the Appliance, since 2021 and always kept it up to date so far.
WalterH:
I also encountered this, but dont understand why it seems to be a problem to have an "old" installation like me. I always installed updates and everything. So it seems to be more of a problem of the update process?
I installed Christmas update but it always still says I have 2021.05.2 as said here. There seems to be something strange and I have the feeling I dont got all updates since then. For example: I still have the problem I described here, its not fixed for me.
So I dont know if this is all about wrong dependencies or the lack of the distribution upgrade until now - but would be happy if there is a solution soon.
Have you tried to setup a fresh ISO-Installation and just used your Backup?
I'm not done yet with all my Upgrade-Tests to 15.4 but i think this will just be my "Last-Resort" and it is always good to check if that is working anyhow 
.
I just did an ISO-Installation for tests this morning.
Only thing i had to do was an zypper modifyrepo --disable repo-backports-update and zypper in -y open-vm-tools so far. However i only use core and only test something else if i'm really bored....
I also opened an ticket because the OVA-Image does not align with the configured Repositorys in the ISO. Meaning that the OVA-Image sadly still uses a few 15.3 Repositorys.
For this "2021.05.2" the Package grommunio-release-$NUMBER is responsible to my knowledge.
What are your current Package-Versions?
rpm -qa *grom*
Is it not possible to choose another way than zypper dup?
I have experienced that for a first installation it is best to use only the ISO and not the OVA, without any update during their installation. What if the same method is used for an existing installation, installing the v2022.12.1 over the v2022.05.x?
Or would there be a way to do a fresh install for as major upgrade and then reliably migrate all user data from install to install, it means from v2022.05.x to v2022.12.1?
What I read here about zypper dup seems not process safe (!)
Andy Or would there be a way to do a fresh install for as major upgrade and then reliably migrate all user data from install to install, it means from v2022.05.x to v2022.12.1?
The reliable way is your Backup and Recovery strategy 
.
It isn't that much what you need to do.
My and others Notes about it here which i've basically done now a couple times..
https://community.grommunio.com/d/307-mailbox-backup/5
zypper dup is the way of doing an System-Upgrade in Suse. No way around it AFAIK..
OK. On the linked page I have seen the Restore way and what is the process for the Backup?
My way of backing up is stated directly above.
Sorry, I can't read anything from it, I'm not enough of an expert, so it's all unsure for me. Something like a summary is missing. It would be good if there was a kind of script of function for "normal users", or even better, a function in the admin "Save" and "Restore".
Backing up two directories completely and restoring them completely on the new installation is not the issue.
/etc/gromox/
/var/lib/gromox/
Then backup and restore the databases. I can't do anything with the shown restore sequence at "MYSQL-DB zurückspielen". Could I use it 1:1? Etc. and so on. You can see that these operations cause headaches for the not so experienced users.
I still have "Write a decent Backup-And-Restore-Utility in XYZ" on my ToDo but hadn't had the time for it 
.
You should definitely read this to get a Basic understanding and maybe think about how you could integrate an Backup which fits your needs.
https://docs.grommunio.com/admin/operations.html#backup-disaster-recovery
A VM-Snapshot can't be considered as an real backup.
It doesn't matter about which Software we are talking.
Just think about when you only want to restore Mailbox A but not B-Z...
Yes there is stuff like Mailstore/Benno/Whateverelse which i also use but this isn't working for e.g. Contacts or the Calendar.
For those i got an Script from another Community-User here which i haven't even came around to publish or integrate in my Systems. Notes and Tasks aren't covered with these either.
Andy I can't do anything with the shown restore sequence at "MYSQL-DB zurückspielen".
Take a look into the File /etc/gromox/mysql_adaptor.cfg
eval `sed 's/ //g' /etc/gromox/mysql_adaptor.cfg`and after the Command you can do something like echo $mysql_username in the Shell.
But you can do those just manually like the Link states.
The eval-Command will basically do the same as if you would have done by cat /etc/gromox/mysql_adaptor.cfg and copy/pasted this output in the same console. Note that eval can be considered "BAD" in many cases. But there is enough about that in the Internet.
Because i know which content it has i do that w/o worrying about it in any way.
And that's enough for now.
I run production and test VM's on Synology NAS. For backup & disaster recovery, I have the option there to export the shutdown VM and import it if necessary. For intermediate steps before updates I create snapshots. I use both of these on a regular basis.
However, when reading the contents of the linked Backup & Disaster Recovery website, I have doubts that such a backup is suitable for simply restoring after a major upgrade. What I read there rather leaves the impression to create a backup, which can be easily restored in a version clean installation, so I could do that with the above mentioned exports and snapshots. But our topic is something different because of major version jumps.
For example, if I have a directory in an installation that contains the complete setting and user data and only that, it is very easy to bridge a major version jump, because I copy the directory into the new installation and it runs as before. If the MariaDB would be the database that controls and maps everything, it would be a further simplification, because then the content could be transferred easily via a transfer script.
Now then, these are thought experiments for a simple handling of such upgrades. From the current point of view, I would not consider any of the given ways as applicable and safe. Maybe the easiest way could be to transfer user data between two running installations via a command sequence.
crpb
My current package versions:
grommunio:~ # rpm -qa *grom*
system-user-gromox-2-lp153.13.1.noarch
grommunio-setup-1.0.68.bb1014d-lp153.7.1.noarch
gromox-debuginfo-2.1.3.cb51757-lp153.54.1.x86_64
grommunio-antispam-3.4-lp153.2.1.x86_64
grommunio-admin-api-1.9.26.d9367fd-lp153.45.1.noarch
grommunio-common-10.e94d08a-lp153.7.1.x86_64
grommunio-release-2022.05.2-lp153.2.1.x86_64
grommunio-cui-1.0.239.ad62461-lp153.44.1.noarch
grommunio-chat-6.2.2-lp153.2.1.x86_64
grommunio-index-0.1.16.e01e06c-lp153.23.1.x86_64
grommunio-web-3.1.182.52d9180-lp153.139.1.noarch
grommunio-jicofo-2.0.5390-lp153.12.4.noarch
grommunio-imapsync-2.200-lp153.4.1.noarch
systemd-presets-branding-grommunio-2022.12-lp153.1.1.noarch
system-user-grommunio-2-lp153.11.1.noarch
grommunio-keycloak-20.0.2-lp153.18.1.noarch
grommunio-auth-21.c8473e9-lp153.12.1.noarch
gromox-2.1.3.cb51757-lp153.54.1.x86_64
grommunio-sync-1.1.55-lp153.61.1.noarch
grommunio-files-10.9.1-lp153.17.1.noarch
grommunio-error-pages-1.0.6.9c50afb-lp153.7.1.noarch
grommunio-admin-web-2.6.0.33.45689ef-lp153.31.1.noarch
grommunio-dav-1.1.33.a126414-lp153.1.1.noarch
plymouth-theme-grommunio-1-lp153.11.4.noarch
gromox-debugsource-2.1.3.cb51757-lp153.54.1.x86_64
grub2-theme-grommunio-1-lp153.11.4.noarch
grommunio-videobridge-2.1.508-lp153.16.4.noarch
grommunio-admin-common-6.cb985db-lp153.14.1.noarch