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!

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.service

You 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!

  • crpb replied to this.

    THE_FRICKLER

    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..

      • crpb replied to this.

        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

        crpb

        Und schon fertig. And another one.. - But enough for now, the rest will be done from someone who might actually learn something from it 😛..

          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

          • crpb replied to this.

            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

              • crpb replied to this.

                Grummel Process: 1582 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade (code=killed, signal=TERM)

                hmm.. check the file /var/log/mysql/mysqld.log

                  BTW: if you have an mysqldump from before the upgrade you can just drop all databases and import that dump

                  mysqldump --all-databases > dump.sql

                  something like this should do the trick

                  grommunio-2022121:~ # #zypper remove mariadb ; rm -Rf /var/lib/mysql/* ; zypper install mariadb ;systemctl enable --now mariadb.service ; mysql < dump.sql

                  I will create a dump of the database of my backup machine and will give it a try.
                  Thank's so far!

                  The reinstallation of MariaDB wasn't sucessfull. I'm getting a timeout failure and I cannot import the dump of my database.
                  On removing MariaDB I get following message:
                  warning: /etc/my.cnf saved as /etc/my.cnf.rpmsave
                  rm: cannot remove '/var/lib/systemd/migrated/mariadb': No such file or directory
                  rm: cannot remove '/var/lib/systemd/migrated/mariadb': No such file or directory
                  rm: cannot remove '/var/lib/systemd/migrated/mariadb-extra': No such file or directory
                  rm: cannot remove '/var/lib/systemd/migrated/mariadb': No such file or directory

                  The reinstallation is successful but starting the service stops with:
                  Job for mariadb.service failed because a timeout was exceeded.
                  See "systemctl status mariadb.service" and "journalctl -xeu mariadb.service" for details.
                  ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysql/mysql.sock' (2)
                  Running journalctl gives this output:
                  ....
                  Feb 20 18:20:07 mail mysql-systemd-helper[1937]: Phase 2/7: Installing used storage engines... Skipped
                  Feb 20 18:20:07 mail mysql-systemd-helper[1937]: Phase 3/7: Fixing views
                  Feb 20 18:20:07 mail mysql-systemd-helper[1937]: mysql.user OK
                  Feb 20 18:20:07 mail mysql-systemd-helper[1937]: Phase 4/7: Running 'mysql_fix_privilege_tables'
                  Feb 20 18:29:57 mail systemd[1]: mariadb.service: start-pre operation timed out. Terminating.
                  Feb 20 18:29:57 mail systemd[1]: mariadb.service: Control process exited, code=killed, status=15/TERM
                  Subject: Unit process exited
                  ...
                  Obviously running the task 'mysql_fix_privilege_tables' crashes
                  I increased the timeout to 600 sec. via systemctl edit mariadb.service but this had no effect.

                  Thanks for any help.

                  Also bei mir sieht das unter systemctl so aus:

                  mariadb.service - MariaDB database server
                  Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
                  Active: active (running) since Tue 2023-02-21 03:01:06 CET; 15h ago
                  Docs: man:mysqld(8)
                  https://mariadb.com/kb/en/library/systemd/
                  Process: 1263 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install (code=exited, status=0/SUCCESS)
                  Process: 1284 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade (code=exited, status=0/SUCCESS)
                  Main PID: 1295 (mysqld)
                  Status: "Taking your SQL requests now..."
                  Tasks: 25 (limit: 4915)
                  CGroup: /system.slice/mariadb.service
                  └─ 1295 /usr/sbin/mysqld --defaults-file=/etc/my.cnf --user=mysql

                  Feb 21 03:01:05 mail systemd[1]: Starting MariaDB database server...
                  Feb 21 03:01:05 mail mysql-systemd-helper[1295]: 2023-02-21 3:01:05 0 [Note] /usr/sbin/mysqld (server 10.6.10-MariaDB) starting as process 1295 ...
                  Feb 21 03:01:06 mail systemd[1]: Started MariaDB database server.

                  und der status der Maria gibt:

                  MariaDB [(none)]> status

                  mariadb Ver 15.1 Distrib 10.6.10-MariaDB, for Linux (x86_64) using EditLine wrapper

                  Connection id: 121
                  Current database:
                  Current user: root@localhost
                  SSL: Not in use
                  Current pager: less
                  Using outfile: ''
                  Using delimiter: ;
                  Server: MariaDB
                  Server version: 10.6.10-MariaDB MariaDB package
                  Protocol version: 10
                  Connection: Localhost via UNIX socket
                  Server characterset: utf8mb4
                  Db characterset: utf8mb4
                  Client characterset: utf8mb3
                  Conn. characterset: utf8mb3
                  UNIX socket: /run/mysql/mysql.sock
                  Uptime: 15 hours 13 min 26 sec

                  Threads: 22 Questions: 46134 Slow queries: 0 Opens: 44 Open tables: 37 Queries per second avg: 0.841

                  Damit lÀuft es bei mir einwandfrei!

                  Luckily I finally got it back running!!
                  Sometimes you have just to be patient. :-)
                  After setting the TimeoutStartSec=infinity option in mariadb.service and then systemctl enable --now mariadb.service and let MariaDB take the time it needs (...having a beer) finally the service started.
                  Import of the database dump and a reboot as final steps and Grommunio is back up and running with 2022.12.1.
                  Thanks for the support! Great community here!

                    © 2020-2024 grommunio GmbH. All rights reserved. | https://grommunio.com | Data Protection | Legal notice