Migrating ownCloud from uberspace 6 to uberspace 7


#1

Steps to reproduce

Migration as featured in https://doc.owncloud.org/server/10.0/admin_manual/maintenance/migrating.html

  1. cleaninstall of oC on new server
  2. maintenance mode for old server
  3. export db/import db
  4. rsync data folder
  5. rsync config.php
    what’s missing in a.m. doc:
    adopt config.php: change db-credentials, change path-name to data-dir, log-dir, tmp-dir, disable redis, as not yet installed
    what also could be missing in a.m. doc:
    change db-entries showing to old paths ?
  6. set owncloud to maintenance
  7. change DNS-entry from old to new IP

Expected behaviour

Just get the owncloud up and running (at least show maintenance mode screen)

Actual behaviour

waiting, waiting, waiting, … 504 bad gateway/gateway timeout

Server configuration

List of activated apps:

But: as in 1. cleaninstall - no apps beside the included ones are really installed!

Are you using external storage, if yes which one: local/smb/sftp/…

S3

Are you using encryption: yes/no

no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/…

no


### Client configuration
**Browser:**
any
**Operating system:**
macOS

### Logs

#### ownCloud log (data/owncloud.log)
https://gist.github.com/stkjj/bac7177e3264a0b9c71ab5576394cfd8#file-owncloud-log```

#### Browser log

Cron job throws frequently errors
#2

Hey,

i think as well that this could be the problem here like currently discussed in Access to files not possible after upgrade.


#3

Moin,

… which leads to Access to files not possible after upgrade and the therein mentioned link to https://doc.owncloud.com/server/10.0/admin_manual/maintenance/manually-moving-data-folders.html

Update the oc_accounts table

says:
UPDATE oc_accounts SET home='/mnt/data/files/super-admin' WHERE id=1;

this of course has to be done for every single user account, as all home-dirs are in the new data-dir

Next:

Update the oc_jobs table

says:
UPDATE oc_jobs SET argument = '/your/new/data/path' WHERE id = <id of the incorrect record>;

at least in my db the “/” are espcaped by " \ " so path should read \/your\/new\/data\/path

I’m sure there’s a need for updating both the migration page as the How to Move Data-Dir page in the admin manual :wink:. /cc @settermjd

Besides that: what would be the suggestion to get the migrated instance up and running?

best regards Stefan


#4

Migration now succeded after editing db-entries and config.php.
Would be glad to read an updated migration doc with next release :wink:

thx for help @tom42