1.1.0 can't start again when I use SQLite

[papiorasu]

• Gitea version (or commit ref):1.1.0
• Git version:
• Operating system: Windows 7 pro / 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:

Description

A database file of SQLite not exists:
The file of the default is generated, and Gitea starts.

A database file of SQLite exists:
The service of Gitea does not start. (system error 1067)

System error 1067　is MySQL error.
I think that Gitea choose a database unlike setting.

[lunny]

@andreynering maybe you can confirm this one.

[pgaskin]

Not happening to me

[lunny]

@papiorasu please give more detail since @geek1011 and I cannot reproduce it.

[pgaskin]

@papiorasu could you show your config file?

[papiorasu]

I see.
I am using gitea at the company so I will present it on Monday.

[papiorasu]

APP_NAME = Gitea: Git with a cup of tea
RUN_USER = PAPIORASU$
RUN_MODE = prod

[database]
DB_TYPE  = sqlite3
HOST     = 127.0.0.1:3306
NAME     = gitea
USER     = gitea
PASSWD   = 
SSL_MODE = disable
PATH     = C:/gitea/data/gitea.sqlite3

[repository]
ROOT = C:/gitea/gitea-repositories

[server]
SSH_DOMAIN       = localhost
HTTP_PORT        = 3000
ROOT_URL         = http://localhost:3000/
DISABLE_SSH      = false
SSH_PORT         = 22
LFS_START_SERVER = false
OFFLINE_MODE     = false

[mailer]
ENABLED = false

[service]
REGISTER_EMAIL_CONFIRM     = false
ENABLE_NOTIFY_MAIL         = false
DISABLE_REGISTRATION       = false
ENABLE_CAPTCHA             = false
REQUIRE_SIGNIN_VIEW        = false
DEFAULT_KEEP_EMAIL_PRIVATE = false
NO_REPLY_ADDRESS           = noreply.example.org

[picture]
DISABLE_GRAVATAR        = false
ENABLE_FEDERATED_AVATAR = false

[session]
PROVIDER = file

[log]
MODE      = file
LEVEL     = Info
ROOT_PATH = C:/gitea/log

[security]
INSTALL_LOCK = true
SECRET_KEY   = 34T7KAqOzV

And MySQL is not installed in my environment.

Furthermore I did a more detailed test.
I tested whether it can be started with 1.0.2 and 1.1.0.

		Gitea Version
		1.0.2	1.1.0
Generate Database Version	1.0	1/30	30/30
	1.0.2	2/30	1/30
	1.1.0	2/30	2/30

I prepared a database that is running (generated by 1.0) and newly generated one (generated by 1.0.2 and 1.1.0).
This is the number of times an error occurred after starting the service 30 times.

I used the following files.
Gitea-1.0.2-windows-4.0-amd64.exe
Gitea-1.1.0-windows-4.0-amd64.exe

[lunny]

Are you running a windows service?

[papiorasu]

Yes. I referred to Gitea 's blog.
https://docs.gitea.io/en-us/windows-service/

[papiorasu]

I confirmed that Gitea can be started by changing the "Version" table of the used SQLite database.
I changed "Version" from 15 to 22.
In the case of a newly created database, this process was performed automatically by Gitea.
However, Gitea of Ver.1.1.0 has not executed this processing in my used database.
So I manually fixed the database. And Gitea started.

The above-mentioned problem that does not start "30/30 times" has been solved.
However, the problems caused by Windows services remain.

[lunny]

So what's the issue it is?

[papiorasu]

First, It is a bug that Gitea has failed to change the "Version" of the used database.

Second, Windows services often do not start up.
I think this is the same as Issue 821.
Windows 7 Fails to start as a service, Web command works #821
I do not know the cause of this issue.

[lunny]

So let's discuss there.