(MANITU) Upgrade (& Repair) from 28.0.6 -> 29.0.2 hangs: Remove activity of private events

Nextcloud version (eg, 29.0.5): 28.0.6
Operating system and version (eg, Ubuntu 29.04): gentoo 2.14
Apache or nginx version (eg, Apache 2.4.25): replace me
PHP version (eg, 8.3): 8.1

Upgrade/Repair hangs at Remove activity of private events:

  • Repair MySQL collation
    • All tables already have the correct collation → nothing to do
  • Repair mime types
  • Clean tags and favorites
    • 0 tags of deleted users have been removed.
    • 0 tags for delete files have been removed.
    • 0 tag entries for deleted tags have been removed.
    • 0 tags with no entries have been removed.
  • Repair invalid shares
  • Move .step file of updater to backup location
  • Add move avatar background job
    • Repair step already executed
  • Add preview cleanup background jobs
  • Migrate oauth2_clients table to nextcloud schema
    • Update the oauth2_access_tokens table schema.
    • Update the oauth2_clients table schema.
    • Delete clients (and their related access tokens) with the redirect_uri starting with oc:// or ending with *
  • Fix potential broken mount points
    • No mounts updated
  • Repair language codes
  • Add log rotate job
  • Clear frontend caches
    • Image cache cleared
    • JS cache cleared
  • Clear every generated avatar
  • Add preview background cleanup job
  • Queue a one-time job to cleanup old backups of the updater
  • Cleanup invalid photocache files for carddav
  • Add background job to cleanup login flow v2 tokens
  • Remove potentially over exposing share links
    • No need to remove link shares.
  • Clear access cache of projects
  • Reset generated avatar flag
  • Keep legacy encryption enabled
  • Check encryption key format
  • Remove old dashboard app config data
  • Add job to cleanup the bruteforce entries
  • Queue a one-time job to check for user uploaded certificates
  • Repair DAV shares
  • Add background job to set the lookup server share state for users
  • Add token cleanup job
  • Clean up abandoned apps
  • Add possibly missing system config
  • Add AI tasks cleanup job
  • Queue a job to generate metadata
  • migrate lazy config values
  • Upgrading Circles App
  • Fix component of birthday calendars
    • 5 birthday calendars updated.
  • Regenerating birthday calendars to use new icons and fix old birthday events without year
    • Repair step already executed
  • Fix broken values of calendar objects
    0 [->--------------------------]
  • Registering building of calendar search index as background job
    • Repair step already executed
  • Register building of social profile search index as background job
  • Registering background jobs to update cache for webcal calendars
    • Added 0 background jobs to update webcal calendars
  • Registering building of calendar reminder index as background job
    • Repair step already executed
  • Clean up orphan event and contact data
    • 0 events without a calendar have been cleaned up
    • 0 properties without an events have been cleaned up
    • 0 changes without a calendar have been cleaned up
    • 0 cached events without a calendar subscription have been cleaned up
    • 0 changes without a calendar subscription have been cleaned up
    • 0 contacts without an addressbook have been cleaned up
    • 0 properties without a contact have been cleaned up
    • 0 changes without an addressbook have been cleaned up
  • Remove activity entries of private events

Any idea?

Best Regards

Gerhard

I’m seeing the same problem on v27.1.11 and also before this version there was always a bigger delay when doing this repair job.
On my instance after a long waiting time the job finishes without a problem, but it would be interesting why this takes so much time: about 15 minutes, also if the same repair job has run directly before an other try.

The repair steps are registered by various apps. So the steps will vary and the answer could be different across environments.

@schla Unless you’re seeing it at the exact same step @Vegisto the cause may be completely differently for you.

As an aside, from a general database access performance perspective, you should both confirm you don’t have missing indices under Administration settings->Overview.

Hi and thanks,

The long delay appears on exactly the same step Remove activity entries of private events. I have no missing indices that could cause performance problems on instance…