act_runner is not execute!

[zhangbaojia]

Description

@yp05327 Let me explain my operation in detail. Best if I can help. Shut it down if can't help!

Screenshots

1、the server does not have an external network

2、download gite and act_runner from another server with a network, docker load them ;

3、run

4、docker network agents

5、installation and configuration is complete

6、create “demo.yaml”

7、 did not run after push

Gitea Version

1.21.7

Can you reproduce the bug on the Gitea demo site?

No

Operating System

Screenshots

Browser Version

Microsoft Edge 122.0.2365.66

[techknowlogick]

What do the logs of the act_runner say?

[zhangbaojia]

gitea logs

runner logs

[lunny]

What's your ROOT_URL on app.ini ?

[zhangbaojia]

gite app.ini

runner config.yaml

[lunny]

So you can try ping 192.168.71.202 from act_runner docker to test whether the network works between act_runner and gitea. If not, change your ROOT_URL to the correct one.

[zhangbaojia]

see Setp 4 【figure 2】 ping gitea:3000

[zhangbaojia]

ping 192.168.71.202

[lunny]

I'm confused that why the act_runner is connected to 172.20.0.3's 3000 but not 192.168.71.202's 9197

[wolfogre]

Please hold on, I think it has nothing to do with the runner.

The problem is that the push operations do not trigger any runs, instead of runs that are not executed by the runner. So I believe it's also caused by broken git hooks.

Since the problem seems related to the network, I guess maybe the Git hooks cannot connect to the gitea internal API. Please check what happened if you attach to the gitea container and run curl 192.168.71.202:9197, wait, let me check ... it should be curl http://localhost:3000 according to your config.

Or it's not caused by the network, but I do think it's related to git hooks instead of runners.

[zhangbaojia]

this?

[zhangbaojia]

docker network:

gitea curl:

runner curl:

[zhangbaojia]

runner config.yaml

runner restart and no log

[wolfogre]

I still believe the problem is not about the runner, but with the git hook. Maybe you can wait for #29494.

[yp05327]

I also think the problem is not about the runner, it is from Gitea side, as there are no waiting runs listed here.
If it is the problem of the runner, there should be some waiting runs listed, then Gitea will send these tasks to the runner.

@wolfogre
If it is because of the git hook, so webhook should also not work?
Then we can create a webhook, and push commits, then see whether the webhook is triggered by checking the webhook history?

[charles7668]

My test results indicate that if the port specified in your ROOT_URL is different from the HTTP_PORT, then the Action runner will receive a "connection refused" message. However, if I change it to the same port, then it works fine.

[charles7668]

Hmm... if I use a reverse proxy, then ROOT_URL = 9197 and HTTP_PORT = 3000 work fine.

[zhangbaojia]

I still believe the problem is not about the runner, but with the git hook. Maybe you can wait for

i agree!!!

My reasoning is that this server push code that can be submitted even with read-only permission.

[zhangbaojia]

ROOT_URL = 9197

ROOT_URL configured

[GiteaBot]

We close issues that need feedback from the author if there were no new comments for a month. 🍵

[yp05327]

@zhangbaojia
Does git hook fix solved your problem?