Start runner with systemd, it doesn't work, #28
Labels
No Label
kind
bug
kind
build
kind/compatible
kind
dependencies
kind
docs
kind
enhancement
kind
feature
kind
help wanted
kind
proposal
kind
refactor
related
act
related
environment
related
exec
related
gitea
related
workflow
reviewed
confirmed
reviewed
duplicate
reviewed
invalid
reviewed
needs feedback
reviewed
wontfix
reviewed
workaround
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/act_runner#28
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Systemd run as git
When I use the command line to run, he is normal
Thanks for reporting.
Could you please add a line to echo $PATH like:
And check the outputs in different running way?
i use nvm install node
systemd runs the service not a shell like bash, so your
PATH
is different. Tell act_runner your env variables you expect in the systemd file.Thank you so much
But gitea doesn't work
Log:
Do you have a custom template for login?
no
Not only login page, but also explore and more
Symtoms remind me to a fixed deadlock https://github.com/go-gitea/gitea/pull/21937#discussion_r1062332555 like Gitea Actions or another go routine doesn't close a db lock.
I cannot say more, without attaching a debugger to debuggable gitea instance with this issue. I'm not aware of any log helping here.
I suggest you to disable gitea actions in your ini file and restart gitea, this should be able to regain access to your instance. Althought without gitea actions
We have a test for that situation in
TestRepoCommitsStatusParallel
.that is right
so I can't start the action with Systemd now?
This doesn't mean there isn't another problem with the same symtoms in another function. Literally every page of the gitea instance has timedout and returned http 500. Disabling actions or deleting the database has returned the instance to working behavior, this was a pain for debugging my own runner for gitea actions.
You cannot use gitea actions now and your systemd runner cannot be used.
Systemd is not the problem, it's a server side problem of gitea itself.
I don't know how to get into your broken state of actions.
I execute the action of this repository
I think the problem is:
Trying to figure it out. ?
@hiifong
I probably know what's the problem, I guess you enabled actions for a mirror repo, right?
yes, I mirrored this repository
Now as long as I enable action in the app.ini file, no matter whether I have started the runner or not, a 500 error code will appear
Thank you so much for reporting. They should fix it:
Closed as the above two PRs merged.