Gitea Actions no longer logging #29013
Description
Description
Since migrating my gitea instance to a different server, gitea actions does no longer generate logs for build steps.
Prior to migrating it looked like this:
Now no build step shows any log output anymore:
I noticed that no new folders are created in the /data/gitea/actions_log/username/reponame/ directory. It only contains folders of actions that have been run prior to migrating.
File permissions on the data/gitea directory are the same as on my old server: drwxr-xr-x.
While running an action I can see the following reoccuring set of log entries in the gitea container:
2024/02/01 12:00:48 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/artifacts for 217.88.92.141:0, 200 OK in 13.7ms @ actions/view.go:494(actions.ArtifactsView)
gitea | 2024/02/01 12:00:48 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/jobs/0 for 217.88.92.141:0, 200 OK in 17.0ms @ actions/view.go:127(actions.ViewPost)
gitea | 2024/02/01 12:00:49 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/artifacts for 217.88.92.141:0, 200 OK in 11.5ms @ actions/view.go:494(actions.ArtifactsView)
gitea | 2024/02/01 12:00:49 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/jobs/0 for 217.88.92.141:0, 200 OK in 15.7ms @ actions/view.go:127(actions.ViewPost)
gitea | 2024/02/01 12:00:50 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/artifacts for 217.88.92.141:0, 200 OK in 13.5ms @ actions/view.go:494(actions.ArtifactsView)
gitea | 2024/02/01 12:00:50 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/jobs/0 for 217.88.92.141:0, 200 OK in 16.6ms @ actions/view.go:127(actions.ViewPost)
gitea | 2024/02/01 12:00:51 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/jobs/0 for 217.88.92.141:0, 200 OK in 14.6ms @ actions/view.go:127(actions.ViewPost)
gitea | 2024/02/01 12:00:51 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/artifacts for 217.88.92.141:0, 200 OK in 12.2ms @ actions/view.go:494(actions.ArtifactsView)
gitea | 2024/02/01 12:00:52 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/artifacts for 217.88.92.141:0, 200 OK in 13.0ms @ actions/view.go:494(actions.ArtifactsView)
gitea | 2024/02/01 12:00:52 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/jobs/0 for 217.88.92.141:0, 200 OK in 15.9ms @ actions/view.go:127(actions.ViewPost)
gitea | 2024/02/01 12:00:53 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/jobs/0 for 217.88.92.141:0, 200 OK in 14.9ms @ actions/view.go:127(actions.ViewPost)
gitea | 2024/02/01 12:00:53 ...eb/routing/logger.go:102:func1() [I] router: completed POST /username/reponame/actions/runs/45/artifacts for 217.88.92.141:0, 200 OK in 13.6ms @ actions/view.go:494(actions.ArtifactsView)
gitea | 2024/02/01 12:00:54 ...eb/routing/logger.go:102:func1() [I] router: completed POST /api/actions/runner.v1.RunnerService/UpdateLog for 217.xx.xx.xxx..:0, 500 Internal Server Error in 41.0ms @ <autogenerated>:1(http.Handler.ServeHTTP-fm)
I feel like the last line might have something to do with it?
What can I do to investigate further?
Gitea Version
1.21.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Debian 12
How are you running Gitea?
Unchanged docker image: gitea/gitea:1.21.3
Database
MySQL/MariaDB