-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Upgrade error owncloud 9.1.6.2 -> 10.0.3.3 (broken local shares) #29209
Comments
So closing as a duplicate of #28763 which you have already found. |
Reopening as there are no federated shares involved, it seems to be related to broken local shares. |
@pep29 please pick one of the shares that are known to be broken and do a |
First i will tell you more about the duplicate case: A creates a directory xxx and share it with B. So B sees the directory xxx in his shared folder, but due to unknow issues to us (maybe during the synchronisation with owncloud client), a copy of xxx is created in the local shared directory of B, at the end B got xxx and xxx(2), only xxx(2) is shows as a shared folder while xxx is not |
@pep29 is only this one user affected or is there more ? |
@PVince81 There are more and most of them use owncloud client on Mac for the sync |
@PVince81 you mean these one:
|
@PVince81 Query: 1,3,4 return empty. However query 2 return some sets, the files with whom we have been having issues as well are show, these folder, files are wrongly coded (we suspected the user created it on their mac and uploaded it using the owncloud client. The special characters on the mac have a different code) e.g.: 151123_Liste_tats�?chlich_anwesende_TN_JT 16.11.15.pdf However not all files with those special char are affected, that why we suppected it must be the way mac works |
About encoding: If using the desktop client, uploading files that are encoded with NFD will be normalized to NFC, so I don't see how it could happen that you have these encoding issues. The weird chars "�?" look more like they are in ISO format, not NFD. NFD umlaut looks like this: #21365 (comment) Now I have no idea why some files would be ISO, unless maybe your server/apache/PHP was not configured properly to use en_US.UTF-8. That said, I'm not sure whether the encoding is causing the upgrade issue. About the SQL result: Since you got results it means there is likely some broken filecache entries that need repairing. The code for this is currently on the stable10 branch and not released yet: #29074. The problem I see here is that you're stuck at the update process, which means the repair should already be done on the previous version, 9.1, which is currently still in the works. Now there is also no guarantee that fixing these entries would unstuck the upgrade as the problem could still be related to broken shares. |
@PVince81 yes, the file "lib/private/Files/Utils/Scanner.php" still exist |
@PVince81 the "intl" module is enabled |
@PVince81 I also noticed there is an improvment with the above mentioned SQL result, before the upgrade attempt, the query gives 188 rows and after applying the patch, the query gives now 33 rows but then i am stuck using the command occ files:scan --all --repair |
I'm a bit out of ideas. I don't see why it couldn't find a class that clearly exists, unless you did something wrong when patching. How did you patch ? |
@PVince81 you were right, i indeed did something wrong with the patching. The scan now works as it should, however i still have to disable the files_sharing, in order for the upgrade to success. Otherwise i am still stuck in the above mentioned avatar step |
How long have you let the upgrade running ? It is likely that if you let it run long enough, the avatar step will finally exit at some point. A similar issue about long running upgrade was reported before and is still being investigated. It seemed that setting up the FS for a specific user who received many shares somehow run in a lot of unnecessary loops. |
All this time I was actually expecting SQLSessionInit to do this UTF-8 thing and now you discovered that it doesn't. I wonder whether it worked maybe with a previous version of Doctrine/DBAL and stopped working at some point. I remember that in the past we had "SET NAMES" explicitly and it seems we removed it because it was then done implicitly by Doctrine/DBAL. The reason could be that now DB tables have a collation so it would use UTF-8 anyway as said in #29209 (comment). However I wonder now whether the DB connection itself (the data transfer) is actually done with UTF-8 or whether some setups would still transfer the data with the wrong encoding... |
I don't know exactly where the problem might be with this utf8 issue, since the update worked before prior to version 10. But when i put SQLSessionInit back after the upgrade, i am again stuck in the while loop. I think, we could rename the ticket by now, since the update error was not actually due to the broken local shares, but some SQLSessionInit vs MysqlSessionInit issue :-D |
@DeepDiver1975 @butonic any idea why the change from #29209 (comment) would fix encoding ? I expected DB encoding to be enforced by collations already |
@pep29 what does <?php
include 'lib/base.php';
$result = \OC::$server->getDatabaseConnection()->executeQuery("SHOW VARIABLES WHERE Variable_Name LIKE 'collation%' OR Variable_Name LIKE 'character%'");
?>
<table>
<?php foreach ($result as $row) { ?>
<tr><td><?php echo $row['Variable_name']; ?></td><td><?=$row['Value']; ?></td></tr>
<?php } ?>
</table> show? In my case CLI shows
and via browser I get
@PVince81 I don't know if browser as client not being utf8mb4 is a problem ... need to check with my google fu ... |
@butonic, my settings appear to be different: CLI shows:
and via browser:
|
@pep29 ok, let us see what the colums look like: SELECT table_name, column_name, character_set_name FROM information_schema.`COLUMNS` WHERE table_schema = "owncloud" AND character_set_name IS NOT NULL; they are all |
They are all utf8 as well |
Hey, this issue has been closed because the label (This is an automated comment from GitMate.io.) |
@butonic is that enough or should all the DB settings have the correct collation ? |
Hey, this issue has been closed because the label (This is an automated comment from GitMate.io.) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps to reproduce
Expected behaviour
should upgrade smoothless
Actual behaviour
It all went well, but then i am stuck at the moving avatars step (keep showing 0%)
Server configuration
Operating system: opensuse 13.1
Web server: apache2
Database: mysql 5.6.12
PHP version: 5.6.9 (cli)
ownCloud version: 10.0.3.3
Updated from an older ownCloud or fresh install: 9.1.6.2
Where did you install ownCloud from: /srv/www/owncloud
Signing status (ownCloud 9.0 and above):
List of activated apps:
Disabled:
Are you using external storage, if yes which one: no
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
The text was updated successfully, but these errors were encountered: