After migration OC>NC a yum update back to OC

Support intro

Sorry to hear you’re facing problems :slight_frown:

If you’re urgently looking for support to keep your business running, consider checking out our paid support options.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:


Or for longer, use three backticks above and below the code snippet:


Remember, the below information may be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Please delete everything above when creating your topic, just provide the following:

Nextcloud version (eg, 12.0.2):
Operating system and version (eg, Ubuntu 17.04): CentOS Linux release 7.4.1708 (Core)
Apache or nginx version (eg, Apache 2.4.25): Apache/2.4.6 (CentOS)
PHP version (eg, 7.1): PHP 7.0.25

The issue you are facing:
I had OC, then I migrated to Nextcloud. BUT I left my YUM repo of Owncloud enabled.
Today I just executed a ‘yum update’ and promptly I got the message in the browser:
Downgrading is not supported and is likely to cause unpredictable issues (from to
How do I go back to nextcloud? How do I save the data (the data is still there!) in case I have to reinstall the server?

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

Steps to replicate it:

  1. Install OC using e YUM repo
  2. Migrate to NC
  3. execute yum update

The output of your Nextcloud log in Admin > Logging:

No function is accessible now

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

# cat config/config.php 
$CONFIG = array (
  'updatechecker' => false,
  'instanceid' => 'XXX',
  'passwordsalt' => 'XXX',
  'secret' => 'XXX',
  'trusted_domains' => 
  array (
    0 => '',
    1 => 'srv009',
  'datadirectory' => '/var/www/html/owncloud/data',
  'overwrite.cli.url' => 'http://srv009/owncloud',
  'dbtype' => 'mysql',
  'version' => '',
  'dbname' => 'owncloud',
  'dbhost' => 'localhost',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'oc_user',
  'dbpassword' => 'XXX',
  'logtimezone' => 'UTC',
  'installed' => true,
  'mail_from_address' => 'cloud',
  'mail_smtpmode' => 'php',
  'mail_domain' => '',
  'maintenance' => false,
  'theme' => '',
  'loglevel' => 2,

The output of your Apache log in /var/log/httpd/error_log:

[Mon Jan 08 03:49:10.037312 2018] [auth_digest:notice] [pid 21182] AH01757: generating secret for digest authentication ...
[Mon Jan 08 03:49:10.039414 2018] [lbmethod_heartbeat:notice] [pid 21182] AH02282: No slotmem from mod_heartmonitor
[Mon Jan 08 03:49:10.142157 2018] [mpm_prefork:notice] [pid 21182] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.0.22 configured -- resuming normal operations
[Mon Jan 08 03:49:10.142181 2018] [core:notice] [pid 21182] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Tue Jan 09 14:51:08.701065 2018] [mpm_prefork:notice] [pid 21182] AH00170: caught SIGWINCH, shutting down gracefully
[Tue Jan 09 14:51:45.178975 2018] [core:notice] [pid 1084] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Tue Jan 09 14:51:45.182391 2018] [suexec:notice] [pid 1084] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Jan 09 14:51:45.237644 2018] [auth_digest:notice] [pid 1084] AH01757: generating secret for digest authentication ...
[Tue Jan 09 14:51:45.239157 2018] [lbmethod_heartbeat:notice] [pid 1084] AH02282: No slotmem from mod_heartmonitor
[Tue Jan 09 14:51:45.385335 2018] [mpm_prefork:notice] [pid 1084] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.0.25 configured -- resuming normal operations
[Tue Jan 09 14:51:45.385445 2018] [core:notice] [pid 1084] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[root@srv009 owncloud]# find -cmin -45


My (=beginner) considerations:

  • no change to the data directory
  • because of the error message (migration not possible) => no change to the database
  • no change to config.php (because the version was still

Thus I downloaded 12.0.4 (the php application was the only changed part of NC) and proceeded as for an update from to 12.0.4. After the first check every thing seems to be very good, up too the following error by integrity check, that I solved by deleting the market app. (Before that I also deleted 3 other app that come with 12.0.4 and caused integrity check errors)

Technical information
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix

- market
		- OC\IntegrityCheck\Exceptions\InvalidSignatureException
		- Certificate is not valid.

Raw output
    [market] => Array
            [EXCEPTION] => Array
                    [class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
                    [message] => Certificate is not valid.



You should deinstall or disable the owncloud package of CentOS. If not, it does run such an upgrade each time there is a new version of owncloud.

In your case it probably replaced all the code files and wasn’t able to run the update script, so your database and data folder weren’t modified and your idea to put back the nextcloud code was good. However, it is better to delete the owncloud code first, so only keep the data and config folder and delete all the code first (if not you risk to have a mixture of Nextcloud and ownCloud code, the integrity checker was exactly build to spot such issues). Then place the Nextcloud code.

To remove the packet, I don’t know CentOS if it is possible to delete a package without deleting user data (therefore do a backup). And check in your webserver configuration if there are specific modifications to run owncloud/Nextcloud.