search

linuxserver / docker-nextcloud

GNU General Public License v3.0
697 stars 128 forks source link

[BUG] Database Errors after automatic upgrade #457

Open redxon opened 1 month ago

redxon commented 1 month ago

Is there an existing issue for this?

Current Behavior

After Upgrade to container version 29.0.3.4 from 28.0.0.11 the upgrader breaks.

It throws DB errors and stays in Maintenance mode (see error log below)

After that is done, the instance stays in maintenance mode. If the command occ upgrade is run the following appears:

root@cc6570f10033:/# occ upgrade
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug

In DbalException.php line 71:

  An exception occurred while executing a query: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'lazy' in 'field list'  

In ExceptionConverter.php line 67:

  An exception occurred while executing a query: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'lazy' in 'field list'  

In Exception.php line 28:

  SQLSTATE[42S22]: Column not found: 1054 Unknown column 'lazy' in 'field list'  

In Statement.php line 130:

  SQLSTATE[42S22]: Column not found: 1054 Unknown column 'lazy' in 'field list'  

upgrade

Removing the maintenance mode just reveals the "Upgrade needed" page on the WebUI.

occ:db-add-missing-indicies does not solve the issue.

occ:maintenance repair is running all green except for this line: `- migrate lazy config values

Expected Behavior

No response

Steps To Reproduce

  1. Upgrade Docker Container from 28.0.0.11 to 29.0.3.4
  2. Let the upgrader run
  3. Encounter the errors above
  4. Not fixable with occ maintenance:mode --off, occ maintenance:repair or occ db:add-missing-indecies

Environment

- OS: Unraid 6.12.3
- How docker service was installed: Unraid
- MariaDB Linuxserver.io version: 10.11.8-r0-ls150

CPU architecture

x86-64

Docker creation

docker template from unraid app store

Container logs

Linuxserver.io version: 29.0.3-ls330
Build-date: 2024-07-14T17:27:42+00:00
───────────────────────────────────────

using keys found in /config/keys
Initializing nextcloud 29.0.3.4 (this can take a while) ...
Upgrading nextcloud from 28.0.0.11 ...
Setting permissions
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug

In DbalException.php line 71:

  An exception occurred while executing a query: SQLSTATE[42S22]: Column not   
  found: 1054 Unknown column 'lazy' in 'field list'                            

In ExceptionConverter.php line 67:

  An exception occurred while executing a query: SQLSTATE[42S22]: Column not   
  found: 1054 Unknown column 'lazy' in 'field list'                            

In Exception.php line 28:

  SQLSTATE[42S22]: Column not found: 1054 Unknown column 'lazy' in 'field lis  
  t'                                                                           

In Statement.php line 130:

  SQLSTATE[42S22]: Column not found: 1054 Unknown column 'lazy' in 'field lis  
  t'                                                                           

upgrade

Initializing finished
**** The following site-confs have extensions other than .conf ****
**** This may be due to user customization. ****
**** You should review the files and rename them to use the .conf extension or remove them. ****
**** nginx.conf will only include site-confs with the .conf extension. ****
/config/nginx/site-confs/default.conf.bak
[custom-init] No custom files found, skipping...
[ls.io-init] done.
github-actions[bot] commented 1 month ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

aptalca commented 1 month ago

https://help.nextcloud.com/t/unknown-column-lazy-in-field-list-when-upgrading-from-28-0-1-1-to-29-0-3-4/196263

LinuxServer-CI commented 3 weeks ago

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.