Updating from v6.8.73 to v6.8.74

[APachLv]

Dear Team.

After updating from v6.8.73 to v6.8.74, I get the error.

Please point me how to sort out this & how to properly update step by step.

After complete installation, does the directory /usr/share/groupoffice/install stay as is or need to be removed?

root@mx:/usr/share/groupoffice# root@mx:/usr/share/groupoffice# sudo -u www-data php cli.php core/System/upgrade Fatal error: Could not write to log file root@mx:/usr/share/groupoffice#

From WEB interface Error: Exception in /usr/share/groupoffice/go/core/Installer.php at line 455: Fatal error: Could not write to log file

root@mx:~# apt-get autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up groupoffice (6.8.74-sixeight) ... Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. dbconfig-common: writing config to /etc/dbconfig-common/groupoffice.conf dbconfig-common: flushing administrative password apache2_invoke groupoffice: already enabled Upgrade output will be logged into: log/upgrade/20241001_071408.log Rebuilding cache Registering all entities SQLSTATE[42S02]: Base table or view not found: 1146 Table 'groupoffice.su_visible_calendars' doesn't exist dpkg: error processing package groupoffice (--configure): installed groupoffice package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: groupoffice E: Sub-process /usr/bin/dpkg returned an error code (1) root@mx:~#

[derjoachim]

Please point me how to sort out this & how to properly update step by step.

The upgrade procedure would depend on your installation method: https://groupoffice.readthedocs.io/en/latest/upgrade/upgrade.html . Upgrading from 6.8.73 to .74 should be a breeze though. The number of changes is small.

After complete installation, does the directory /usr/share/groupoffice/install stay as is or need to be removed?

It does not need to be removed. Normally, if you run the install script, it detects whether there is an existing installation with the current config file and moves into upgrade mode if it finds one.

Could not write to log file

The log file should be writable by the www-data user. Your upgrade logs are stored in your Group-Office data directory. I think that the log subdirectory or one of its subdirectories cannot be written by the www-data user. A simple chown should solve that.

database error

Now that error is weird. Does the database named 'groupoffice' still exist and does it have a table named 'su_visible_calendars'?

[APachLv]

Update from v6.8.74 to v6.8.75 the same error, but when 6.8.74 freshly installed and updated right after no error.

Yes database named 'groupoffice' exist.

In config.php i add $config['register_visible_user_groups'] = 'Internal';maybe this cause error?

Scr. attached.

[derjoachim]

Hmmm... Is the calendar module installed and enabled? By default, this happens automatically. Does the table su_visible_calendars exist?

I do not think that the configuration option should have any impact on that particular error. The system simply cannot find a certain table (and possibly several others, but the script stops at the first fatal error).

Could you set the $config['debug'] option to true please and retry the upgrade? That may help us pinpoint what exactly triggers this error.

[APachLv]

Ok, I found it.

How to reproduce.

Install the previous release, do basic config. From the admin interface, "System settings -> Modules" disable & delete "Start page"

Then "apt upgrade" or from .php update result fail. Fresh original install database has 174 rows, after module deletion 171.

• one more, fresh install IPV6 disabled completely by Bios, Dovecot fail & install fail. To sort out, disable Dovecot IPV6 listener and run install.