Upgrade 12.0.0 -> failed. "Update in process"

Nextcloud version :
Operating system and version : Ubuntu Server 16.04.1 AMD64
Apache or nginx version : Apache 2.4.18 (But I can apparently use nginx commands too)
PHP version : 7.0.22
Is this the first time you’ve seen this error?: Yes

Can you reliably replicate it? (If so, please outline steps):
1: Start upgrade from the admin panel.
2: Abort it during the update process.

The issue you are facing:

This is everything that shows up when attempting to connect to the server again. Restarting services/rebooting doesn’t seem to work.

I’ve toggled maintenance mode to see if that was the issue, but there were no change to that page (even with maintenance mode on).

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

$CONFIG = array (
  'trusted_domains' =>
  array (
    0 => 'localhost',
    1 => 'mentaloutcastgames.no',
    2 => '',
    3 => '/REDACTED\',
  'overwrite.cli.url' => '/REDACTED\',
  'htaccess.RewriteBase' => '/nextcloud',
  'datadirectory' => '/var/www/nextcloud/data',
  'dbtype' => 'mysql',
  'dbhost' => 'localhost:3306',
  'dbname' => 'nextcloud',
  'dbuser' => 'nextcloud',
  'dbpassword' => '/REDACTED\',
  'passwordsalt' => '/REDACTED\',
  'secret' => '/REDACTED\',
  'version' => '',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'installed' => true,
  'instanceid' => 'ocbjubhrs5rs',
  'force_language' => 'en',
  'default_language' => 'en',
  'knowledgebaseenabled' => 'true',
  'allow_user_to_change_display_name' => 'false',
  'remember_login_cookie_lifetime' => '60*60*24*15',
  'mail_domain' => 'mentaloutcastgames.no',
  'mail_smtpmode' => 'smtp',
  'mail_smtphost' => 'smtp.domeneshop.no',
  'mail_smtpport' => 587,
  'mail_smtpsecure' => 'ssl',
  'mail_smtpauth' => 'true',
  'mail_smtpauthtype' => 'LOGIN',
  'mail_smtpname' => '/REDACTED\',
  'mail_smtppassword' => '/REDACTED\',
  'loglevel' => 2,
  'maintenance' => false,

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

Neither of those logs contain any useful information, and I don’t have a nginx log.

Have anyone encountered this issue yet and know of a fix that would not involve re-installing if possible? I’m getting lazy after three weeks of work on the server.

I’ve tried doing a manual upgrade but that didn’t work. I suspect there are some files holding on to old information that causes this issue, but I have no idea where to find that file.
My (possibly lazy 20min) search for any files in the apache folder didn’t uncover any suspects.

sharing the logs (nextcloud log, which are in nextcloudbasedir/data/updater.log and / or nextcloudbasedir/data/nextcloud.log) would help.

Meanwhile, if it is locked into maintenance mode - you can probably unlock it with occ

I’ve already enabled and disabled the maintenance mode in combination with other settings to see if it would help.

Regardig the updater.log, that got reset when I did the manual upgrade it seems.

2017-12-08T17:05:05+0000 PNLOJ6pKEt [info] updater cli is executed
2017-12-08T17:05:05+0000 PNLOJ6pKEt [info] currentStep()
2017-12-08T17:05:05+0000 PNLOJ6pKEt [info] current version: 12.0.4 build time: 2017-12-04T07:21:01+00:00 c772810ecabce06f45dea16b7c67185c90df4a0d
2017-12-08T17:05:05+0000 PNLOJ6pKEt [info] getUpdateServerResponse()
2017-12-08T17:05:05+0000 PNLOJ6pKEt [info] updaterServer: https://updates.nextcloud.org/updater_server/
2017-12-08T17:05:05+0000 PNLOJ6pKEt [info] releaseChannel: stable
2017-12-08T17:05:05+0000 PNLOJ6pKEt [info] internal version:
2017-12-08T17:05:05+0000 PNLOJ6pKEt [info] updateURL: https://updates.nextcloud.org/updater_server/?version=12x0x4x3xxxstablexx2017-12-04T07%3A21%3A01%2B00%3A00+c772810ecabce06f45dea16b7c67185c90df4a0dx7x0x22
2017-12-08T17:05:06+0000 PNLOJ6pKEt [info] checkForUpdate() Array

2017-12-08T17:05:06+0000 PNLOJ6pKEt [info] end of checkForUpdate() No update available.
2017-12-08T17:10:20+0000 nokhOxYlie [info] updater cli is executed
2017-12-08T17:10:20+0000 nokhOxYlie [info] currentStep()
2017-12-08T17:10:20+0000 nokhOxYlie [info] current version: 12.0.4 build time: 2017-12-04T07:21:01+00:00 c772810ecabce06f45dea16b7c67185c90df4a0d
2017-12-08T17:10:20+0000 nokhOxYlie [info] getUpdateServerResponse()
2017-12-08T17:10:20+0000 nokhOxYlie [info] updaterServer: https://updates.nextcloud.org/updater_server/
2017-12-08T17:10:20+0000 nokhOxYlie [info] releaseChannel: stable
2017-12-08T17:10:20+0000 nokhOxYlie [info] internal version: 12.0.0
2017-12-08T17:10:20+0000 nokhOxYlie [info] updateURL: https://updates.nextcloud.org/updater_server/?version=12x0x0xxxstablexx2017-12-04T07%3A21%3A01%2B00%3A00+c772810ecabce06f45dea16b7c67185c90df4a0dx7x0x22
2017-12-08T17:10:21+0000 nokhOxYlie [info] checkForUpdate() Array

2017-12-08T17:10:21+0000 nokhOxYlie [info] end of checkForUpdate() No update available.



I’ve now re-installed Nextcloud using the manual installation method with the occ and terminal.

But this issue is still there. I have moved the other folders in /var/www to an “OLD” folder, so there is just my new install in there. I’ve created a new MySQL database and user for the new install too in case there were something stuck in the databases from the updater. So this issue is not directly connected to the home directory of Nextcloud (In my case; /var/www/nextcloud).

I’ve spent quite a few hours reading forums and instructions in hopes of fixing this, but it ended up just wasting my sleep hours. There are quite a few others who have similar issues to mine, and there are a few who seem to have the exact same issue as the one I got.

Does anyone know the file(s) that might contain the configs/settings that make my web server display this “update in process” page?

This is getting really frustrating now.

Alright, I’m on a tight schedule so I did a totally clean reinstall of Nextcloud and a total reconfiguration of all related files in the apache2 and php directories, so I finally managed to upgrade to 12.0.4.

But there really should be some documentation to solve this issue, as I didn’t manage to fix this issue, I simply avoided it alltogether.