gearmand close connection with Connection timed out

[huamxu]

We using gearmand 1.1.21.0 in a docker contianer which base on image docker.io/library/python:3.11.4

libev-libevent-dev/oldstable 1:4.33-1 all
libevent-2.1-7/oldstable,now 2.1.12-stable-1 amd64 [installed,automatic]
libevent-core-2.1-7/oldstable,now 2.1.12-stable-1 amd64 [installed,automatic]

Gearmand start with "gearmand -t 10 --job-retries 1 --verbose DEBUG -p 4730"

ERROR 2024-02-26 00:01:26.998647 [ 11 ] closing connection due to previous errno error(Connection timed out) -> libgearman-server/io.cc:221
ERROR 2024-02-26 00:14:33.430740 [ 13 ] closing connection due to previous errno error(Connection timed out) -> libgearman-server/io.cc:221
ERROR 2024-02-26 00:14:33.430775 [ 14 ] closing connection due to previous errno error(Connection timed out) -> libgearman-server/io.cc:221

Is any know good solutions about this issue

[esabol]

@huamxu wrote:

Is any know good solutions about this issue

Could you try the suggestion in the following comment?

#150 (comment)

You might have to do that both on the Docker host and inside the Docker container. (I'm not sure.)

If that doesn't solve the problem, try changing "-t 10" to "-t 0" in your gearmand arguments. It's not an ideal solution, but it worked for the person in #150 (comment).

You could also try removing "--job-retries 1" from your gearmand arguments.

[esabol]

Note: This is a duplicate of issue #150.

[huamxu]

Thanks, I will have a try

[esabol]

@huamxu, it has been 3 weeks. Did either of my two suggestions address your problem? Just wondering!

[huamxu]

@huamxu, it has been 3 weeks. Did either of my two suggestions address your problem? Just wondering!

Thanks for your kindly support @esabol
My issue was not resolved after diable multi-thread feature, but new findings in our production result to not sure the problem with gearmand configuration.

In our production, Jenkins gearman plugin works as gearman worker, each executor as a worker
but after the plugin disable/enable in Jenkins, there are some duplicated executor worker exist.
I will post here once have some conclusion,

[esabol]

Latest updates found in the other thread:

#150 (comment)

#150 (comment)