Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[oc6->oc7] DB upgrade failed for a single user #13998

Closed
cdamken opened this issue Feb 9, 2015 · 4 comments
Closed

[oc6->oc7] DB upgrade failed for a single user #13998

cdamken opened this issue Feb 9, 2015 · 4 comments

Comments

@cdamken
Copy link
Contributor

cdamken commented Feb 9, 2015

Steps to reproduce

  1. in ownCloud 6 create a folder and share it with another internal user all users are managed in external LDAP
  2. upgrade to ownCloud 7

Expected behavior

all data should be accessible after upgrade

Actual behavior

The user does not see the folders that have been shared anymore.
running "occ files:scan" make the files accessible again, but all sharing information are lost.

Note: I have done different reproduction scenarios with public shared folders, public uploads and time-limited shares.
The internal share seems to be the way for the easiest and most reliable reproduction. The problem was occurring 2 times when using the same set of demo-data.

Server configuration

Operating system: UCS 3.2-4

Web server: Apache 2.2.16-6.79

Database: MySQL

PHP version: 5.4.4-14

ownCloud version: 7.0.4

Updated from an older ownCloud or fresh install:
upgraded from 6.0.6

List of activated apps:

  • activity
  • enterprise_key
  • files
  • files_sharing
  • files_texteditor
  • files_trashbin
  • files_versions
  • firstrunwizard
  • user_ldap

The content of config/config.php:

$CONFIG = array (
'instanceid' => 'xxxxxxxx',
'passwordsalt' => 'removed',
'trusted_domains' =>
array (
0 => 'xxxxxxxxxxx',
1 => '192.168.133.11',
),
'datadirectory' => '/var/lib/owncloud',
'dbtype' => 'mysql',
'version' => '7.0.4.2',
'dbname' => 'owncloud',
'dbhost' => 'localhost',
'dbtableprefix' => 'oc_',
'dbuser' => 'oc_owncloudadmin',
'dbpassword' => 'removed',
'installed' => true,
'license-key' => 'xxxxxxxxxxx',
'ldapIgnoreNamingRules' => false,
'loglevel' => '0',
'appstoreenabled' => false,
'has_internet_connection' => false,
'supportedDatabases' =>
array (
0 => 'mysql',
1 => 'pgsql',
2 => 'oci',
3 => 'mssql',
),
'maintenance' => false,
'secret' => 'removed',
'share_folder' => '/Shared',
'overwritewebroot' => '/owncloud',

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

Are you using encryption: yes/no
no

Client configuration

Browser:
FF and Chromium

Operating system:
Linux Mint 17.1

Logs

Web server error log

nothing related to ownCloud

ownCloud log (data/owncloud.log)

{"reqId":"54cf6e54a8338","app":"user_ldap","message":"No DN found for
on
m.test3single.it25.de","level":0,"time":"2015-02-02T12:32:20+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/js\/oc.js?v=5a99a2a3eb17097c5fd4b4edf41aaef2"}
{"reqId":"54cf6e5c06935","app":"user_ldap","message":"initializing paged
search for Filter objectClass=* base Array\n(\n [0] =>
uid=test11,cn=users,dc=it25,dc=de\n)\n attr Array\n(\n [0] =>
uid\n)\n limit 1 offset
0","level":0,"time":"2015-02-02T12:32:28+00:00","method":"GET","url":"\/owncloud\/index.php\/apps\/files\/ajax\/list.php?dir=%2F&sort=name&sortdirection=asc"}
{"reqId":"54cf6e5c06935","app":"user_ldap","message":"Ready for a paged
search","level":1,"time":"2015-02-02T12:32:28+00:00","method":"GET","url":"\/owncloud\/index.php\/apps\/files\/ajax\/list.php?dir=%2F&sort=name&sortdirection=asc"}

Browser log

not applicable

@MorrisJobke
00002421

@PVince81
Copy link
Contributor

Very likely to be the same as: #12801

Any user who were recipients of shares would see their files/shares lost and a bogus "local::" entry created for them. To confirm if this is the same issue, check oc_storages and see if there is a new bogus local:: entry that was created for the affected users.

@LukasReschke
Copy link
Member

@cdamken Please comment on above statement. THX.

@DeepDiver1975
Copy link
Member

no feedback -> close

@cdamken
Copy link
Contributor Author

cdamken commented Apr 17, 2015

Just a new comment: the behavior does not happens when upgrade from 6.0.7 to 7.0.5, well then its probably fixed.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants