Service Not Running When Running 1.23.1 for Update from 1.22.6 to 1.23.1 in Windows OS

[Jang-Haemin]

Description

Hello?
This is a user who installs and uses Gitea on the company's Windows OS server.
I'm running Gitea as a Windows service, and I've enabled https using ACME.

Currently, the version of our instance is 1.22.6 and is running using the gitea-1.22.6-gogit-window-4.0-amd64.exe file.
The size of this file is 210mb.
Please remember the size of this file.

I downloaded the gitea-1.23.1-gogit-window-4.0-amd64.exe file and ran it as a service, as I had previously updated.
However, the service fails to run, and nothing is recorded in the gitea.log.
Instead, Windows Event Viewer experiences an error with the attachment.

• Event Viewer File
  gitea_1_23_1_windows_event_log.txt

The file size of the updated 1.23.1 version is 113mb, which is nearly 100mb smaller than before.
Is there an execution problem because there is a missing file due to this update?
Or is there anything else I need to work on as it gets updated from 1.22.6 to 1.23?

I entered it using a translator, so the content may be awkward.
Thank you for reading, and I would appreciate it if you could let me know how I can solve this problem.

Gitea Version

1.23.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

1.22.6

Operating System

Windows Server 2019 v17763.6659

How are you running Gitea?

Download the gitea-version-gogit-window-4.0-amd64.exe file and run it as a Windows service.

Database

SQLite

[lunny]

The binary reduction is by design because we removed some unused packages and some new build parameters have ben enabled.

Can you run gitea web in a command line and get some errors log?

[Jang-Haemin]

이진 감소는 일부 사용되지 않는 패키지를 제거하고 일부 새로운 빌드 매개변수를 활성화했기 때문에 의도적으로 수행되었습니다.

명령줄에서 실행해서 gitea web오류 로그를 얻을 수 있나요?

When I run the command as you said, I get an error like below.

...ules/setting/time.go:21:loadTimeFrom() [F] Load time zone failed: unknown time zone Asia/Shanghai

The locale of the PC running gitea is Korean, and I wanted to use the time appropriate for Korea, so I specified the following in the app.ini file.

[time]
DEFAULT_UI_LOCATION = Asia/Shanghai

[lunny]

Can you try changing Asia/Shanghai to Asia/Seoul?

[wxiaoguang]

The locale of the PC running gitea is Korean, and I wanted to use the time appropriate for Korea, so I specified the following in the app.ini file.

You can leave it empty then it should use OS's timezone IIRC

[Jang-Haemin]

Thank you for your quick response.
The symptoms were the same even when I changed to Asia/Seoul.

However, as wxiaoguang said, I removed the DEFAULT_UI_LOCATION property and it works well.

We hope this will be fixed for users who want to specify a timezone.
Thank you all.

[lunny]

Thank you for your quick response. The symptoms were the same even when I changed to Asia/Seoul.

However, as wxiaoguang said, I removed the DEFAULT_UI_LOCATION property and it works well.

We hope this will be fixed for users who want to specify a timezone. Thank you all.

I think it depends on your system, maybe there is no zoneinfo data for those time locations.

[Jang-Haemin]

I see. The odd thing is that it worked fine before version 1.22.6.

[wxiaoguang]

Maybe it's related to the build.

The timezone info should be packed into the binary. But maybe the new build misses that? @techknowlogick

[wxiaoguang]

Maybe it's related to the build.

The timezone info should be packed into the binary. But maybe the new build misses that? @techknowlogick

@techknowlogick is it related?

[wxiaoguang]

Maybe it's related to the build.
The timezone info should be packed into the binary. But maybe the new build misses that? @techknowlogick

@techknowlogick is it related?

@techknowlogick is it related?

[techknowlogick]

@wxiaoguang looking at the workflows, it seems they have not included the additional build tag for sometime (if at all), but to align with the docker image tags I added the tz tag to the binary release files too #33463 as even if it doesn't help with this issue, it at least ensures a consistent binary between docker and non-docker.