Update in process - Instance not available

ℹ️ Support
1

I started an update from 22.2.5.1. It started but ended with “Update in process.”. I have no access to the system via console; there is no chance to restart the update with the web based updater. The instance is not available anymore. What can I do?

Apache (Version not known)
PHP version: 7.4.28

I cannot find any logging on FTP… :_(

config.php

<?php
$CONFIG = array (
  'instanceid' => 'XXXXXX',
  'passwordsalt' => 'XXXXXX',
  'secret' => 'XXXXXX',
  'trusted_domains' => 
  array (
    0 => 'XXXXXX',
  ),
  'datadirectory' => 'XXXXXX',
  'dbtype' => 'mysql',
  'version' => '22.2.5.1',
  'overwrite.cli.url' => 'XXXXXX',
  'dbname' => 'XXXXXX',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'XXXXXX_',
  'dbuser' => 'XXXXXX',
  'dbpassword' => 'XXXXXX^',
  'installed' => true,
  'mail_from_address' => 'XXXXXX',
  'mail_smtpmode' => 'smtp',
  'mail_sendmailmode' => 'smtp',
  'mail_domain' => 'XXXXXX',
  'mail_smtphost' => 'XXXXXX',
  'maintenance' => true,
  'theme' => '',
  'loglevel' => 0,
  'updater.secret' => 'XXXXXX',
);

Thanks a lot for your help!
Jwh

2

Normally, you have the nextcloud logfile in the data folder.

From the config.php, it seems that the update has not been carried out. You can check the file versions.php in the main folder to see if the code base has already been updated.

Before you do anything, backup what you currently have (files and database)!!!

If there is newer code, you can find the code of the 22.2.5 version here: https://nextcloud.com/changelog/#latest22 (scroll down to your version). You can do the inverse of an update, remove the new code files, but keep the data and config folder! Then place the code of the 22.2.5 version.

The big question is why the update didn’t work. So if you have time, you can go through the nextcloud.log, in the data folder you have a updater-xxxxx - folder which belongs to the updater app. Perhaps you find more information about the update problems.

Systems without console access can be very tricky. For large setups, it’s better to run the update from console where you don’t have timeouts.

3

There is a file

/path/to/nextcloud/data/updater-***/.step

Sometimes it helps to manipulate this entry or rename .step to .step-not-used.

4

Hi @tflidd tflidd und @devnull,

Thank you very much for your support.
For some reason the update folder was missing, also step files and version identification are not available. Something seems to have gone wrong in general.
I just reinstalled via web installer; so:

  • Deleted everything except the Data folder and the database.
  • Executed the web installer again
  • Everything works again

Thanks a lot!