I have a real issue with many of my users. The users can be seen in admin panel like this: [Screenshot from 2019-12-12 20-00-31] But when I try to reveal their email address, It wont show anything to me. And also their public profile gives a 404 error. As far as I see, all of these users are almost inactive (they are active in terms of activation but inactive in terms of activity in forum). So I think maybe its been caused by a broken automatic inactive user removal in the very long past.

Another thing I notice: If I inactivate, and then activate them, they get fixed!

If a user is inactive for a certain length of time (730 days by default) they are automatically inactivated. The setting is in your dashboard under Settings/Users and scroll almost down to the bottom. That is where you’ll see that. But, it’s not necessary to make any changes for the sake of making a change. If those users haven’t logged in for 2 years, it makes no sense to reactivate them unless they start showing up again. :wink:

No. My problem is not this. The dashboard says the users are activated.

Seems similar to the issue I’m having. Could you check if the affected names have duplicates or ‘very near matches’ in your database? For example user.user and useruser.

Yes affected users are among those usernames that are very popular. so discourse suggest a near match username. I signup users with api. so I get a username from user. then I check it against discourse api and if its already taken, I would automatically use whatever discourse suggest.

btw with help of @RGJ we nailed the problem down to this two condisions: [Bild]On another topic there are two different problems: users that cannot be found by username but can be found by id (like mojtaba11) users that cannot be found by username_lower but can be found by username (like alireza6) see: irb(main):002:0> User.username_available?('Alireza6') => true irb(main):004:0> User.username_exists?('alireza6') => false irb(main):006:0> DB.exec(User::USERNAME_EXISTS_SQL, username: 'alireza6') => 0 discourse=> select username, username_lower from users where username_lower='alireza6'; username | username_lower ----------+---------------- (0 rows) discourse=> select username, username_lower from users where username='Alireza6'; username | username_lower ----------+---------------- Alireza6 | alireza6 (1 row)

To add to that, the issue @hosna is having is clearly an issue on the database level. It seems like there is some corruption in the users table. Copying the contents to a new table solves these issues. That said, I did see two occurrences of @bartv’s issue in @hosna’s database (those were the two duplicates before Sept 22 and they both had a dot in their username) but I am not sure if these two issues are related. They just have the same symptoms.

Sounds like a corrupt database index. REINDEX TABLE users should solve the problem.

What about the duplicate usernames? I have many same usernames being used for 2 distinct users. The issue is acknowledged here: [Bild] Critical Error: changed username, user got broken Support That’s an interesting observation! Usernames are effectively case-insensitive, so you shouldn’t be able to have two users with the same username. However: [54%20PM] You can see what appears to be two distinct usernames returned when searching for fatemeh12. This shouldn’t have been able to happen (I’m not able to reproduce it). Both go to the same profile it seems. I’m at a loss on where to go from here. If someone doesn’t chime in by around this time tomorrow, I’ll see if I can track someo…

That’s probably a side effect of a corrupt index. You might need to clean that up manually before the reindexing works.

So viele defekte Benutzer aufgrund einer beschädigten Datenbank

Produktunterstützung

bartv (Bart ) 14. Dezember 2019 um 08:24 5

Sieht ähnlich aus wie das Problem, das ich habe. Könntest du prüfen, ob die betroffenen Namen Duplikate oder „sehr ähnliche Übereinstimmungen

Thema		Antworten	Aufrufe
Critical Error: changed username, user got broken Product Support	18	2017	15. März 2020
Upgrade issue with duplicate username in DB Self-hosting	2	556	29. Januar 2021
2.7.0.beta2 upgrade failed with ERROR: duplicate key Self-hosting	24	2581	26. Januar 2021
Duplicate 'Names' Product Support	10	889	8. März 2020
Username already exist error Self-hosting	3	1232	11. Dezember 2019

So viele defekte Benutzer aufgrund einer beschädigten Datenbank

Verwandte Themen