21.1.20220905 - Fehler nach Update

[jtd]

Folgende Meldung erhalte ich nach dem manuellen Update:
An error happened Failed opening required '/usr/share/egroupware/vendor/egroupware/adodb-php/adodb.inc.php' (include_path='.:/usr/share/php')

Ich habe kein Docker. Läuft auf Ubuntu 22.04 mit PHP 8.1.

[jtd]

Habe komplett über CLI-Install neu installiert, jedoch bekomme nach der Wiederherstelllung meines DB Backups folgenden Fehler:

Invalid default value for ‘acc_imap_port’

/usr/share/egroupware/api/src/Db.php (821)
Database error
Duplicate entry ‘127-1146438000’ for key ‘egw_cal_dates.PRIMARY’

---

Führe ich dann Aktuliserung der DB Struktur durch, erhalte ich folgenden Fehler:

/usr/share/egroupware/setup/inc/class.setup_detection.inc.php (398)
An error happened!
count(): Argument #1 ($value) must be of type Countable|array, null given

Zudem ändert sich ein Eintrag der Installation:

[jtd]

Habe jetzt auf Testsystem Egroupware in Docker am laufen, jedoch selber Fehler nach Restore des Backups.

Zudem folgende Meldung :

An error happened!
EGroupware\Api\Cache::get_system_config(install_id) $GLOBALS[‘egw_info’][‘server’][‘install_id’] is NOT set!

[RalfBecker]

First of all, from which version are you updating, AND was everything working before?

count(): Argument #1 ($value) must be of type Countable|array, null given

I fixed that one, to give an other error, that nothing is configured. Which is probably also the cause of:

EGroupware\Api\Cache::get_system_config(install_id) $GLOBALS[‘egw_info’][‘server’][‘install_id’] is NOT set!

Somehow your DB lacks the configuration / content of egw_config table.

Your new installation is a default Docker based installation via Linux DEB or RPM packages?
Was it working before you restored your old DB?

Ralf

[jtd]

Hi Ralf,

it was working before, and hopefully it is on an ESXI Server, so I could go back to:
egroupware-docker (21.1.20220408) hardy; urgency=low

My working Installation is an old Installation on an Ubuntu Server (now named CLI).

I also setup a docker installation, but same issues.

Kind Regards Jan Tino

[RalfBecker]

Sorry jtd,

I still don’t understand your setup and your problem:

egroupware-docker (21.1.20220408) hardy; urgency=low

egroupware-docker is the name of the Linux package installing EGroupware via docker-compose internally.

What exactly are you using on the machine you have the problem after updating from 21.1.20220408 to 21.1.20220905?

Ralf

[jtd]

It’s on a Vsphere Ubuntu 22.04 System installed in path /usr/share/egroupware with local PHP8.1 and MYSQL. I just upgraded everytime on bash since Version 1.6.

Now I’ve spend to much time for a small family installation.

So please don’t bother. I think I’ll migrate to nextcloud in the next few days.
It was a really good time with eGroupware. Thank you for your great work the past years.

[RalfBecker]

It’s on a Vsphere Ubuntu 22.04 System installed in path /usr/share/egroupware with local PHP8.1 and MYSQL. I just upgraded everytime on bash since Version 1.6.

An error happened Failed opening required ‘/usr/share/egroupware/vendor/egroupware/adodb-php/adodb.inc.php’

Hmm, have you checked the file from your first error is there?

Depending on how you installed, you might have forgotten to run composer?

Ralf

[jtd]

Done all things that are described on github/egroupware. Also fresh install. Running fine, until import DB Backup.

[RalfBecker]

Done all things that are described on github/egroupware

There are several different ways to install EGroupware, thought only one recommended way for a supported Linux.

Which way you use AND does that file exist?

Btw. when you tried fixing the problem, you always got a different error, not the same as you claim!

It does not make sense to focus on 3 different scenarios.

Ralf

[jtd]

apt install nodejs
npm install -g grunt-cli
cd /usr/share/
git clone https://github.com/EGroupware/egroupware.git
cd egroupware
./install-cli.php

I got egroupware running…
than tried to use Backup and I got errors.

Don’t waste your time. Thanks so much Ralf.

[RalfBecker]

ok, das ist eine master Installation, sprich unsere aktuelle Entwicklungsversion, nicht die stabile 21.1 oder das letzte Maintenance Release, das erklärt natürlich einiges …

Mach’ mal bei dem clone ein -b 21.1 rein, damit Du das stabile release bekommst.

Welche Composer Version hast Du installiert (composer --version)?
Wir unterstützen UND benötigen inzwischen den aktuellen Composer 2.x, sprich must Du evtl. updaten.

Mit der Installationsmethode, musst Du zum Update auch nur einfach ./install-cli.php laufen lassen und nicht immer alles neu machen. Für das Update auf die nächste Major Version verwendest Du dann ./install-cli.php 22.1

Mit ./install-cli.php 21.1 kommt Du auch von master auf die stabile 21.1, vorher aber unbedingt die Composer Version checken und ggf. updaten.

Ralf

[jtd]

Danke - werde es gern nochmal testen.

[jtd]

-b 21.1

-b 21 war die Lösung - nach 5 Minuten alles OK.
Danke für die Mühe.