Upgrade Appliance to opensuse 15.4
- Edited
Work in Pro.. Upgrade
You might want to look at Update form Open SuSE 15.3 to 15.4
Update the Repositories
sed -i 's/15.3/15.4/g' /etc/zypp/repos.d/*
zypper --verbose refreshThen it got icky because of the PHP-Change and packages which made a fuzz'.
First Update just gromox which will take care of Package-Problems.
The question from zypper should be answered as "Uninstall all PHP7 Packages"
Take care of PHP..
zypper update gromoxThe actual Distupgrade
zypper dup
I basically got through all "Warnings" by always choosing the option to remove the PHP7-Package..
Be aware that the Number changes!I guess i should just have uninstalled the problematic packages before the
zypper dupbut about 10-15 Questions later i was already upgrading :-).
Enable PHP-FPM
mv /etc/php8/fpm/php-fpm.conf.default /etc/php8/fpm/php-fpm.conf
systemctl enable php-fpm.service
rebootI did that
mvmuch later after trying to determine what's wrong... but now i know that, i just should have done so from the start.. "Lucky you!"
Eventually reinstall missing Packages...
If the Package grommunio-index didn't make it. (This might happen because of the PKG grommunio [1])
zypper install -y grommunio-index
rm -Rf /var/lib/grommunio-web/sqlite-index/*
systemctl start grommunio-index.serviceI think this was all...
Here is my /var/log/zypp/history so you might see what will happen.
And FWIW: I'm using the Supported REPO!!!
EDIT: Added systemctl-call.
EDIT: index
EDIT: zypper update gromox after Release-Code-Change
Successfully upgraded: 3
[1] zypper info --requires grommunio
Thank you!
I'll give it a try with a clone of my community version and post the results.
I works for me, with your last post.
after the reboot php-fpm seems to be disabled and not running. There was a 502 Gateway message in the user-web-gui. Admin-web-gui works. In that i enabled php-fpm. At last everything is working now.
I've seen it in the history but wasn't sure if i was just doing nonsense at that moment :-).
That is an SuSe/Redhat-Behavior(not automatically enabling the Services)
In Debian the service is automatically enabled (which i might not want always but that's what it is..)
You can see that with systemctl list-unit-files --target enabled, it will look quite different depending on the OS
It was no problem, Admin-GUI was working. In there php-fpm enabled und started. 2 minutes later everything was working fine (Handy, Outlook etc.) I still use CORE and nothing else. After a secound reboot GRO runs without any further interaction smooth and gentle .
Thanks for the post
After the update from Leap 153 to Leap 15.4 i fond a difference next to "rpm -qa 'grom*'" in my native leap15.4 testinstall to the upgraded leap 153
in the upgraded VM two packets are missing: grommunio-index and grommunio-dbconf
the rest is similar. Should i install them manualy via rpm? The system ist running well without them!
The updatet VM was first installed in early 2021!
- Edited
At least grommunio-index and best to use these commands to refresh all "Webmail-Search-Indexes".
rm -Rf /var/lib/grommunio-web/sqlite-index/*
systemctl start grommunio-index.serviceYou don't need grommunio-dbconf if you don't miss it 
Done an running.
--- Aber jetzt mal ehrlich, bei meiner kleinen Familien-Installation kann ich keinen Zeit-Vorteil in der Suche finden.
Unsere Postfächer sind in der Regel ziemlich klein, Mail-Store sichert alle Mail on demand und löscht alles älter als 4 Monate. Der Zugriff auf dieses Archiv (auch per WEB eingebunden) ist für jeden User möglich und stellt ein Voll-Archiv seit 2005 zur Verfügung. Die Suche darin ist gefühlt noch schneller!
Ajo, kommt immer drauf an ob man es braucht oder nicht.
Ich persönlich verwende hauptsächlich IMAP aber die meisten anderen mit Linux benutzen des Webmail.. Da ist ne suche schon mal praktisch in nem geteilten Postfach.
Bin jetzt mal auf nem weiteren Server am Upgrade.
Sieht wohl so aus das man einfach ein zypper update gromox machen muss nach dem man auf 15.4 umgestellt hat und danach das zypper dup machen..
Ich hatte noch eine Nachfrage während des Upgrade zu einer nicht aufgelösten Abhängigkeit bei php8-soap.
Ich habe das upgrade erstmal angebrochen und manuell php8-soap installiert. Beim nächsten dup-start habe ich dann die Möglichkeit 1 (löschen aller alten php7 Abhangigkeiten) gewählt und schwupps lief es wie beschrieben.
Index läuft auch DB-Config habe ich nie benötigt!
Nochmals Danke für die Hinweise und Antworten
Hellau aus dem ruhrpott
..Auch bei mir! Die alte Test-VM mit Leap 15.3 ist gelöscht.
Danke für die kurzweilige und erfolgreiche Rückkopplung!
Eventuell kannst du den TAG noch auf finaly-solved setzen.
WalterH wird sich sicher auch freuen, das er zu diesem Thema nicht mehr zur geduld aufrufen muss!
Schönen Abend
- Edited
THE_FRICKLER WalterH wird sich sicher auch freuen, das er zu diesem Thema nicht mehr zur geduld aufrufen muss!
HAHAHA!!! HELAU!! ALAAF!! PROST!
Ich habe nur teilweise rechte auf die Tags
Das muss @mwilliams schöner machen.
Too bad, it did not work so well for me. I have worked through all the points and everything has worked so far.
However, I can not call the Admin Web UI or the User Web. Apparently I have a SQL problem.
In various logs (e.g. gromox-http) I find the following:
(gromox-http): "mysql_adaptor: Failed to connect to mysql server: Can't connect to local MySQL server through socket '/run/mysql/mysql.sock' (2)"
(gromox-http): "mysql_adaptor: failed to startup"
(gromox-http): "service: init of libgxs_mysql_adaptor.so not successful"
(gromox-http): "system: failed to run services"
Has anybody an idea to fix this? Thanks!
Check the contents of
/etc/gromox/mysql_adaptor.cfg- mysql_adaptor(4gx)- Remove the spaces "var = value" to "var=value"
Your MySQLD is working?
mysql -t <<< "use grommunio; show tables;"
should list you something/all tables.
If not, is the mysqld even running?
systemctl status mysql.service
I've checked the content of mysql_adaptor.cfg. There is no spaces inbetween the var and values
mysql -t .... is listing nothing, it just states:
Error 2002 (HY000): Can't connect to local server through socket '/run/mysql/mysql.sock' (2)
mysqld is not running:
# systemctl status mysql.service
x mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: (diabled)
Active: failed (Result: timeout) since datexxx
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 1555 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install (code=exited, status=0/SUCCESS)
Process: 1582 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade (code=killed, signal=TERM)
Feb 20 09:36:48 mail mysql-systemd-helper[1682]: mysql.time_zone_transition_type OK
Feb 20 09:36:48 mail mysql-systemd-helper[1682]: mysql.transaction_registry OK
Feb 20 09:36:48 mail mysql-systemd-helper[1682]: Phase 2/7: Installing used storage engines... Skipped
Feb 20 09:36:48 mail mysql-systemd-helper[1682]: Phase 3/7: Fixing views
Feb 20 09:36:48 mail mysql-systemd-helper[1682]: mysql.user OK
Feb 20 09:36:48 mail mysql-systemd-helper[1682]: Phase 4/7: Running 'mysql_fix_privilege_tables'
Feb 20 09:41:36 mail systemd[1]: mariadb.service: start-pre oeration timed out. Terminating
Feb 20 09:41:41 mail systemd[1]: mariadb.service: Control process exited, code=killed, status=15/TERM
Feb 20 09:41:41 mail systemd[1]: mariadb.service: Failed with result 'timeout'.
Feb 20 09:41:41 mail systemd[1]: Failed to start MariaDB database server.I use only core - nothing else