Update from 17 to 18 failed

Nextcloud version (eg, 18.0.2): 18.0.10
Operating system and version (eg, Ubuntu 20.04): No idea, shared hosting
Apache or nginx version (eg, Apache 2.4.25): No idea shared hosting at all-inkl.com
PHP version (eg, 7.1): 7.3

The issue you are facing:

I tried to update from 17 to 18 using the auto updater, it failed with errors

Is this the first time you’ve seen this error? (Y/N):

Yes

Steps to replicate it:

  1. start the auto updater

The output of your Nextcloud log in Admin > Logging:

I can only give you the updater log:

Update vorbereiten

Log-Level auf "debug" gesetzt

Wartungsmodus eingeschaltet

Reparaturschritt: Repair MySQL collation

Reparaturinformation: All tables already have the correct collation -> nothing to do

Reparaturschritt: Repair SQLite autoincrement

Reparaturschritt: Copy data from accounts table when migrating from ownCloud

Reparaturschritt: Drop account terms table when migrating from ownCloud

Das Datenbankschema wird aktualisiert

Datenbank aktualisiert

Reparaturschritt: Migrate old user config

[1 / 0]: Migrate old user config

[1 / 1]: Migrate old user config

"accessibility" aktualisiert auf 1.4.0

"federatedfilesharing" aktualisiert auf 1.8.0

"files_pdfviewer" aktualisiert auf 1.7.0

"files_rightclick" aktualisiert auf 0.15.2

"files_videoplayer" aktualisiert auf 1.7.0

"logreader" aktualisiert auf 2.3.0

"password_policy" aktualisiert auf 1.8.0

"privacy" aktualisiert auf 1.2.0

"provisioning_api" aktualisiert auf 1.8.0

"recommendations" aktualisiert auf 0.6.0

"serverinfo" aktualisiert auf 1.8.0

Reparaturschritt: Switches from default updater server to the customer one if a valid subscription is available

Reparaturinformation: Repair step already executed

"support" aktualisiert auf 1.1.1

"survey_client" aktualisiert auf 1.6.0

"text" aktualisiert auf 2.0.0

Reparaturschritt: Add background job to check for backup codes

"twofactor_backupcodes" aktualisiert auf 1.7.0

"updatenotification" aktualisiert auf 1.8.0

"federation" aktualisiert auf 1.8.0

"lookup_server_connector" aktualisiert auf 1.6.0

Reparaturschritt: Update OAuth token expiration times

"oauth2" aktualisiert auf 1.6.0

"files" aktualisiert auf 1.13.1

"activity" aktualisiert auf 2.11.1

"cloud_federation_api" aktualisiert auf 1.1.0

Reparaturschritt: Fix component of birthday calendars

Reparaturinformation: 2 birthday calendars updated.

Reparaturschritt: Regenerating birthday calendars to use new icons and fix old birthday events without year

Reparaturinformation: Repair step already executed

Reparaturschritt: Fix broken values of calendar objects

[0 / 0]: Fix broken values of calendar objects

Reparaturschritt: Registering building of calendar search index as background job

Reparaturinformation: Repair step already executed

Reparaturschritt: Registering background jobs to update cache for webcal calendars

Reparaturinformation: Added 0 background jobs to update webcal calendars

Reparaturschritt: Registering building of calendar reminder index as background job

Reparaturinformation: Repair step already executed

Reparaturschritt: Clean up orphan event and contact data

Reparaturinformation: 0 events without a calendar have been cleaned up

Reparaturinformation: 0 properties without an events have been cleaned up

Reparaturinformation: 0 changes without a calendar have been cleaned up

Reparaturinformation: 0 cached events without a calendar subscription have been cleaned up

Reparaturinformation: 0 changes without a calendar subscription have been cleaned up

Reparaturinformation: 0 contacts without an addressbook have been cleaned up

Reparaturinformation: 0 properties without a contact have been cleaned up

Reparaturinformation: 0 changes without an addressbook have been cleaned up

Reparaturschritt: Remove activity entries of private events

Reparaturinformation: Removed 0 activity entries

"dav" aktualisiert auf 1.14.0

Reparaturschritt: Fix the share type of guest shares when migrating from ownCloud

Reparaturschritt: Copy the share password into the dedicated column

Reparaturschritt: Set existing shares as accepted

"files_sharing" aktualisiert auf 1.10.1

"files_trashbin" aktualisiert auf 1.8.0

"files_versions" aktualisiert auf 1.11.0

"sharebymail" aktualisiert auf 1.8.0

InvalidArgumentException: Column name "hEzDO_flow_operations"."entity" is NotNull, but has empty string or null as default.

Das Update ist fehlgeschlagen. Bitte melden Sie dieses Problem an die Nextcloud Community.

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

<?php
$CONFIG = array (
  'instanceid' => 'ocy7xj2kmo4e',
  'passwordsalt' => 'obscured',
  'secret' => 'obscured',
  'trusted_domains' => 
  array (
    0 => 'nc.mydomain',
  ),
  'datadirectory' => '/www/htdocs/w01882f8/nc/data',
  'dbtype' => 'mysql',
  'version' => '17.0.10.1',
  'overwrite.cli.url' => 'http://nc.mydomain',
  'dbname' => 'obscured',
  'dbhost' => 'obscured',
  'dbport' => '',
  'dbtableprefix' => 'hEzDO_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'obscured',
  'dbpassword' => 'obscured',
  'installed' => true,
  'tempdirectory' => '/www/htdocs/w01882f8/nc/tmp/',
  'mail_smtpmode' => 'sendmail',
  'mail_sendmailmode' => 'pipe',
  'mail_from_address' => 'castillo',
  'mail_domain' => 'web.de',
  'maintenance' => false,
  'theme' => '',
  'loglevel' => 2,
  'app_install_overwrite' => 
  array (
    0 => 'calendar',
  ),
  'updater.release.channel' => 'stable',
  'updater.secret' => 'obscured',
);

The output of your Apache/nginx/system log in /var/log/____:

I dont have it

I understand now that I do not get any support whatsoever if anything goes wrong. Way to go, NextCloud. We thought about using this as a professional solution for the company, but after what I experienced here I will advise against it.

It’s always helpful to update in time. 17 is way outdated. I always update to the most recent version, actual 19.0.5 on stable and 20.0.2 on beta. I never had serious update problems.

Thast is completely beside the point. I did not update from 17 to 20, I did update from 17 to 18 and that should work. Frankly I don’t care if you have no problems, as that does not help me, because I have them. I delivered a complete and concise error report and still the only thing you come up with is this arrogant non-answer? Seriously? This is not helpful and you should not have commented as you cannot add anything helpful to the thread.