Cannot remove user from organization (MSSQL) #2354

Closed
opened 2025-11-02 04:33:39 -06:00 by GiteaMirror · 10 comments
Owner

Originally created by @vzro on GitHub (Sep 21, 2018).

  • Gitea version (or commit ref): 1.4.1 / 1.5.1
  • Git version: 2.17.0
  • Operating system: Windows Server 2016 (1607 / 14393.2430)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When trying to remove a member from an organization, the service freezes and has to be restarted.
...

Screenshots

Originally created by @vzro on GitHub (Sep 21, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.4.1 / 1.5.1 - Git version: 2.17.0 - Operating system: Windows Server 2016 (1607 / 14393.2430) - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [x] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description When trying to remove a member from an organization, the service freezes and has to be restarted. ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/bug label 2025-11-02 04:33:39 -06:00
Author
Owner

@lafriks commented on GitHub (Sep 21, 2018):

Do you get any errors in gitea.log?

@lafriks commented on GitHub (Sep 21, 2018): Do you get any errors in gitea.log?
Author
Owner

@vzro commented on GitHub (Sep 22, 2018):

This is all I got in it:

2018/09/22 00:50:36 [I] Log Mode: File(Info)
2018/09/22 00:50:36 [I] XORM Log Mode: File(Info)
2018/09/22 00:50:36 [I] Cache Service Enabled
2018/09/22 00:50:36 [I] Session Service Enabled
2018/09/22 00:50:36 [I] Mail Service Enabled
2018/09/22 00:50:36 [I] Register Mail Service Enabled
2018/09/22 00:50:36 [I] Notify Mail Service Enabled
2018/09/22 00:50:36 [I] Git Version: 2.17.0
2018/09/22 00:50:36 [I] SQLite3 Supported
2018/09/22 00:50:36 [I] Run Mode: Production
2018/09/22 00:50:36 [I] Listen: http://0.0.0.0:2199
2018/09/22 00:50:36 [I] LFS server enabled
2018/09/22 00:53:20 [...routers/org/teams.go:107 TeamsAction()] [E] Action(remove): AccessibleReposEnv: read tcp 10.0.75.1:55379->10.0.75.1:1433: i/o timeout
2018/09/22 00:53:38 [...s/context/context.go:235 func1()] [E] UserSignIn: sql: expected 9 destination arguments in Scan, not 1
2018/09/22 00:53:38 [...routers/repo/http.go:180 HTTP()] [E] Users with two-factor authentication enabled cannot perform HTTP/HTTPS operations via plain username and password. Please create and use a personal access token on the user settings page
2018/09/22 00:53:38 [...routers/repo/http.go:141 HTTP()] [E] invalid credentials

@vzro commented on GitHub (Sep 22, 2018): This is all I got in it: 2018/09/22 00:50:36 [I] Log Mode: File(Info) 2018/09/22 00:50:36 [I] XORM Log Mode: File(Info) 2018/09/22 00:50:36 [I] Cache Service Enabled 2018/09/22 00:50:36 [I] Session Service Enabled 2018/09/22 00:50:36 [I] Mail Service Enabled 2018/09/22 00:50:36 [I] Register Mail Service Enabled 2018/09/22 00:50:36 [I] Notify Mail Service Enabled 2018/09/22 00:50:36 [I] Git Version: 2.17.0 2018/09/22 00:50:36 [I] SQLite3 Supported 2018/09/22 00:50:36 [I] Run Mode: Production 2018/09/22 00:50:36 [I] Listen: http://0.0.0.0:2199 2018/09/22 00:50:36 [I] LFS server enabled 2018/09/22 00:53:20 [...routers/org/teams.go:107 TeamsAction()] [E] Action(remove): AccessibleReposEnv: read tcp 10.0.75.1:55379->10.0.75.1:1433: i/o timeout 2018/09/22 00:53:38 [...s/context/context.go:235 func1()] [E] UserSignIn: sql: expected 9 destination arguments in Scan, not 1 2018/09/22 00:53:38 [...routers/repo/http.go:180 HTTP()] [E] Users with two-factor authentication enabled cannot perform HTTP/HTTPS operations via plain username and password. Please create and use a personal access token on the user settings page 2018/09/22 00:53:38 [...routers/repo/http.go:141 HTTP()] [E] invalid credentials
Author
Owner

@vzro commented on GitHub (Sep 22, 2018):

I've also noticed that, in the log directory, an empty file called 'http' is created. I'm not sure whether or not this relates to the actual problem/bug, just thought it would be helpful to mention it.

@vzro commented on GitHub (Sep 22, 2018): I've also noticed that, in the log directory, an empty file called 'http' is created. I'm not sure whether or not this relates to the actual problem/bug, just thought it would be helpful to mention it.
Author
Owner

@vzro commented on GitHub (Sep 22, 2018):

A quick addendum: Every request inside Gitea, after trying to remove the user from the organization, results in a 404 page (screenshot attached).

capture

@vzro commented on GitHub (Sep 22, 2018): A quick addendum: Every request inside Gitea, after trying to remove the user from the organization, results in a 404 page (screenshot attached). ![capture](https://user-images.githubusercontent.com/23323304/45913123-45cc5b00-be03-11e8-9432-0040081beafd.PNG)
Author
Owner

@vzro commented on GitHub (Sep 22, 2018):

Apparently, a 500 also occurs:

capture

@vzro commented on GitHub (Sep 22, 2018): Apparently, a 500 also occurs: ![capture](https://user-images.githubusercontent.com/23323304/45913277-ddcb4400-be05-11e8-94a0-ce6e0cdc6409.PNG)
Author
Owner

@vzro commented on GitHub (Sep 22, 2018):

Can anyone, from Gitea or not, help me verify this?
Thanks!

@vzro commented on GitHub (Sep 22, 2018): Can anyone, from Gitea or not, help me verify this? Thanks!
Author
Owner

@sapk commented on GitHub (Sep 23, 2018):

@rzo you seems to have a request that timeout. read tcp 10.0.75.1:55379->10.0.75.1:1433: i/o timeout. It seems to have corrupt the database and leave it in an unstable state. Gitea should have catch it and revert to a stable state. Can you provide the exact commit or release of the log since line 107 of teams.go seems irrelevant on master? And any more logs of others errors after ?

@sapk commented on GitHub (Sep 23, 2018): @rzo you seems to have a request that timeout. `read tcp 10.0.75.1:55379->10.0.75.1:1433: i/o timeout`. It seems to have corrupt the database and leave it in an unstable state. Gitea should have catch it and revert to a stable state. Can you provide the exact commit or release of the log since line 107 of teams.go seems irrelevant on master? And any more logs of others errors after ?
Author
Owner

@vzro commented on GitHub (Sep 23, 2018):

@sapk I'm not sure if I understood you correctly.

The log I posted above is all there's to it. I mean, the only file with content inside the logs folder.

Every request after trying to remove the user results in 404 and 500 errors.

I'm not sure I could say the database is 'corrupted', given that it takes a service restart to make things work normally again.

I just can't remove any user from the organization.

@vzro commented on GitHub (Sep 23, 2018): @sapk I'm not sure if I understood you correctly. The log I posted above is all there's to it. I mean, the only file with content inside the logs folder. Every request after trying to remove the user results in 404 and 500 errors. I'm not sure I could say the database is 'corrupted', given that it takes a service restart to make things work normally again. I just can't remove any user from the organization.
Author
Owner

@vzro commented on GitHub (Oct 8, 2018):

Hey, guys... Can anyone help with this?
What else can I provide to further help the investigations?

@vzro commented on GitHub (Oct 8, 2018): Hey, guys... Can anyone help with this? What else can I provide to further help the investigations?
Author
Owner

@sapk commented on GitHub (Oct 8, 2018):

#4282 mssql integrations tests are near ready to be setup. Those show that some parts of gitea are not fully working on mssql. I didn't see at first glance failing user removal but that maybe the integrations tests that didn't cover this corner.

@sapk commented on GitHub (Oct 8, 2018): #4282 mssql integrations tests are near ready to be setup. Those show that some parts of gitea are not fully working on mssql. I didn't see at first glance failing user removal but that maybe the integrations tests that didn't cover this corner.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2354