4 / 4
Mar 2022

I’m in the process of (finally) decommissioning an EGW 1.8 system on Centos 6 and Postgres.

I have a VM of Rocky 8.5, PHP 7.4, PHP-FPM, Postgres 10 and EGW 17.1 configured. I needed to make some adaptations to accommodate FPM. For now SELinux is set permissive.

Its almost working.

Most significantly I get this error pop up in my browser.

Database error

Invalid SQL: INSERT INTO egw_preferences () VALUES ()
ERROR:  syntax error at or near ")"
LINE 1: INSERT INTO egw_preferences () VALUES ()
                                     ^ (-2)

Is this easy to fix? I’ve attached log entries from the PHP-FPM error log at the end.

OR, would I be better to go straight to one of the Docker versions. I’ve not used docker before, are there any issues with using a Postgresql database with those versions?

Any guidance most welcome

:slight_smile: Ken

[04-Mar-2022 21:32:59 Europe/London] # Instance=default, User=kens, Request=POST http://172.16.0.13?menuaction=home.home_ui.index&ajax=true, User-agent=Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:97.0) Gecko/20100101 Firefox/97.0
[04-Mar-2022 21:32:59 Europe/London] PHP Fatal error: Uncaught EGroupware\Api\Db\Exception\InvalidSql: Invalid SQL: UPDATE egw_access_log SET WHERE
ERROR: syntax error at or near "WHERE"
LINE 1: UPDATE egw_access_log SET WHERE
^ (-2) in /usr/share/egroupware/api/src/Db.php:798
Stack trace:
#0 /usr/share/egroupware/api/src/Db/Deprecated.php(64): EGroupware\Api\Db->query()
#1 /usr/share/egroupware/api/src/Db.php(1980): EGroupware\Api\Db\Deprecated->query()
#2 /usr/share/egroupware/api/src/Session.php(1497): EGroupware\Api\Db->update()
#3 /usr/share/egroupware/api/src/Session.php(278): EGroupware\Api\Session->update_dla()
#4 [internal function]: EGroupware\Api\Session->__destruct()
#5 {main}
thrown in /usr/share/egroupware/api/src/Db.php on line 798
[04-Mar-2022 21:32:59 Europe/London] PHP Warning: Creating default object from empty value in /usr/share/egroupware/api/src/Db.php on line 510
[04-Mar-2022 21:32:59 Europe/London] #1 /usr/share/egroupware/api/src/Db.php(344): EGroupware\Api\Db->_connect()
[04-Mar-2022 21:32:59 Europe/London] #2 /usr/share/egroupware/api/src/Db.php(604): EGroupware\Api\Db->connect()
[04-Mar-2022 21:32:59 Europe/London] #3 [internal function]: EGroupware\Api\Db->__wakeup()
[04-Mar-2022 21:32:59 Europe/London] #4 /usr/share/egroupware/api/src/loader.php(80): unserialize()
[04-Mar-2022 21:32:59 Europe/London] #5 /var/lib/egroupware/header.inc.php(81): require_once(’/usr/share/egro…’)
[04-Mar-2022 21:32:59 Europe/London] #6 /usr/share/egroupware/json.php(106): include_once(’/var/lib/egroup…’)
[04-Mar-2022 21:32:59 Europe/London] #7 {main}
[04-Mar-2022 21:32:59 Europe/London] # Instance=default, User=kens, Request=GET http://172.16.0.13/egroupware/json.php?menuaction=EGroupware\Api\Framework::ajax_get_preference&json_data={“request”%3A{“parameters”%3A[“home”]}}, User-agent=Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:97.0) Gecko/20100101 Firefox/97.0

  • created

    Mar '22
  • last reply

    Mar '22
  • 3

    replies

  • 896

    views

  • 3

    users

  • 1

    like

  • 6

    links

Hi Ken.

Yes, of course Definitely!
We also don’t want to support versions as old as 17.1. We really have more important and meaningful things to do.

17.1 ???

Otherwise, you can run current EGroupware on Docker with PostgreSQL. Have several…
But keep in mind: We do not actively test with PostgreSQL.

Search the forum and start reading here:

Stefan

Thank you Stefan. I’ll explore the Docker route.

:slight_smile: Ken

If you come from 1.8, you need additional measures for the update to succeed:

We (EGroupware GmbH) also offer to support you with the update:

Ralf