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

Gitea 1.6.2 failed to start after restart with error Invalid object name 'SYS.INDEXES' #6201

Closed
2 of 7 tasks
eMuonTau opened this issue Feb 27, 2019 · 9 comments
Closed
2 of 7 tasks
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented issue/stale

Comments

@eMuonTau
Copy link

eMuonTau commented Feb 27, 2019

  • Gitea version (or commit ref):gitea-1.6.2-windows-4.0-amd64
  • Git version: 2.21.0.windows.1
  • Operating system: Windows Server 2012 R2
  • 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:
    2019/02/27 19:59:03 [I] Log Mode: File(Info)
    2019/02/27 19:59:03 [I] XORM Log Mode: File(Info)
    2019/02/27 19:59:03 [I] Cache Service Enabled
    2019/02/27 19:59:03 [I] Session Service Enabled
    2019/02/27 19:59:03 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: sync database struct error: mssql: Invalid object name 'SYS.INDEXES'.

Description

This happened after i restarted my server. If there is any other way that i can provide more info please let me know.

Screenshots

@techknowlogick
Copy link
Member

Hi @Noderino, first thing is you'll likely want to upgrade to the latest version as we've fixed some major security vulnerabilities, also the DB library has been updated which might solve the problem.

Are you able to connect directly to MSSQL to run queries manually against it?

@eMuonTau
Copy link
Author

Yes i can connect to MSSQL without a problem. I also tried to replace gitea.exe with newer versions and latest but i am still getting same error.

@eMuonTau
Copy link
Author

This is the log before first "Invalid object name" error.

2019/01/29 18:45:40 [...routers/repo/http.go:137 HTTP()] [E] invalid credentials
2019/01/29 18:45:40 [...routers/repo/http.go:137 HTTP()] [E] invalid credentials
2019/01/29 18:46:15 [...routers/repo/http.go:137 HTTP()] [E] invalid credentials
2019/01/29 18:46:15 [...routers/repo/http.go:137 HTTP()] [E] invalid credentials
2019/02/27 13:10:07 [I] Log Mode: File(Info)
2019/02/27 13:10:07 [I] XORM Log Mode: File(Info)
2019/02/27 13:10:07 [I] Cache Service Enabled
2019/02/27 13:10:07 [I] Session Service Enabled
2019/02/27 13:10:08 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: Unable to open tcp connection with host '127.0.0.1:1433': dial tcp 127.0.0.1:1433: connectex: No connection could be made because the target machine actively refused it.
2019/02/27 13:11:07 [I] Log Mode: File(Info)
2019/02/27 13:11:07 [I] XORM Log Mode: File(Info)
2019/02/27 13:11:07 [I] Cache Service Enabled
2019/02/27 13:11:07 [I] Session Service Enabled
2019/02/27 13:11:22 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: sync database struct error: mssql: Invalid object name 'SYS.INDEXES'.

@lunny
Copy link
Member

lunny commented Feb 28, 2019

Which version of your database?

@eMuonTau
Copy link
Author

SQL Server 2014

@eMuonTau
Copy link
Author

eMuonTau commented Mar 8, 2019

@lunny Do you mean version number in dbo.version table? It is 74

@lunny
Copy link
Member

lunny commented Mar 8, 2019

@Noderino No. I means your SQL Server.

@stale
Copy link

stale bot commented May 7, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label May 7, 2019
@stale
Copy link

stale bot commented May 21, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed May 21, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label May 22, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented issue/stale
Projects
None yet
Development

No branches or pull requests

3 participants