-
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
Users administration page does not load after update to 9.1.0 #25594
Comments
Any error in data/owncloud.log? How many users do you have in the system? |
I'm logging into syslog, so theres no output in owncloud.log. In syslog I see debug messages for most of the page calls, but nothing if I open the users page. |
hmmmm ... hard to tell what's going on here. I cannot reproduce this. |
Maybe I can elaborate this a little with your help... I had a look into the javascript debugging and as mentioned before, I can create two cases: So I used the js error log I posted before and set some debugging points in users.js(starting in line 403) and js.js with the following result:
if I'm displaying the whole list, it skips the whole `function (result) {...}`` part
(each line for each call of the function) Unfortunately I dont see, where the data for the actual users is extracted, as it could may fail there, but maybe we can work this out together... |
I think I've nailed down the problem: Could the @ be the issue? |
hmmm .... I quickly tested this with a user having a @ in the user name:
this is really strange |
It definitely is! Does anyone know by chance, if it is save to alter the username via mysql or will this screw things up? Another addition: The desktop clients for the affected person are also not working (MacOS & iOS) - So it seems to be deeper than just an ajax problem |
I'm also seeing this issue. None of the users have an @-symbol in it. |
For my case it all traced back to one user (the only one with an @ in username, but I'm not sure, if this was the reason) - Users who had shared folders with him had problems (not able to login, failures while display data), When he was in the user list the list failed to display etc. |
I also have this issue....my user directory is ldap server..but list of users does not show up..when I search for a user name, it shows up! |
Same problem here some users can Best Regards |
This is more information from my instance: ssl_access.log from apache: error.log from apache: Best Regards |
I'm not being able to reproduce this. Upgraded from stable9 to stable9.1, different situations, no problems with users admin page or users login. |
Hey Developers: You need add to delete file function first disable share and later delete. So problem is with delete shared files without unsharing. |
Hi, I've tested that case.
No problems found, user1 can login correctly and all users appear in user management. |
@takenek I asked my "problematic user" and he had created exactly the same situation you're describing - it seems like you solved the case! |
@SergioBertolinSG Interesting what You say because i check few times and exacly working like i say.... @SergioBertolinSG Please do something like this:
Best Regards |
Retested following this steps #25594 (comment), no errors at all. |
BTW, when doing the upgrade you can't miss the X.X versions. 7.0->8.0->8.1->8.2->9.0->9.1 are you having into account 8.1 and 8.2 ? |
@SergioBertolinSG I use Debian apt so i don`t remember what exacly was version when i update to next.... but i use apt everytime... if You skip something in line that will be a fault. So mayby this is a way of problem? |
OK thanks @takenek |
I've tried the upgrade using deb packages stable9 to current stable (9.1). And there is something different. It is working fine, I can login and see user management without problems, but in the logs I am seeing this:
Those errors corresponds to deleted shares from user1. @jnweiger do you know if there is something different between upgrading using packages and tarballs regarding deleted shares? |
I've tried this again using deb packages from 8.0->8.1->8.2->9.0->9.1 No problems, sorry I cannot reproduce this. |
I think the best way is just take from someone dump database and check what is wrong. This is 100% problem with DB. I got exacly same instances on 2 server and one got problem another one working... difference between them is database. |
The content or the engine? |
Hmmm, some of the comments here remind me of #25557. |
Can you try applying https://patch-diff.githubusercontent.com/raw/owncloud/core/pull/25754.patch on top of v9.1.0 ? |
Please try again with 9.1.1 RC1 that contains that patch fixing shares. If the problem persists, please reopen. |
Hi @PVince81 , |
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
Page should load and display the users
Actual behaviour
Page loads, but instead of the user list, there's a running circle - after a couple seconds I get a notification bubble that there's a problem loading the page and it will be reloaded in 5 seconds.
If you select a group on the left side, I get a glimpse of the list and then the error reoccurs.
Server configuration
Operating system: Ubuntu 16.04.1 LTS
**Web server:**Apache/2.4.18 (Ubuntu)
**Database:**10.0.25-MariaDB-0ubuntu0.16.04.1 Ubuntu 16.04
**PHP version:**7.0.8-0ubuntu0.16.04.1
ownCloud version: 9.1.0
**Updated from an older ownCloud or fresh install:**upgraded version
Where did you install ownCloud from:
owncloud official Ubuntu repository
(http://download.owncloud.org/download/repositories/stable/Ubuntu_16.04/)
Signing status (ownCloud 9.0 and above):
List of activated apps:
The content of config/config.php:
Are you using external storage, if yes which one: no
Are you using encryption: yes
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Chrome, Firefox
Operating system: Ubuntu 16.04 LTS
Logs
Web server access log
There's only output in apache access log - even with log_level = 0 theres no log output, while calling the users site.
Browser log
It does not seem to be a duplicate of 24734, as users.js is the patched version
The text was updated successfully, but these errors were encountered: