php / pecl-networking-gearman Goto Github PK

Got an error
php: symbol lookup error: /usr/lib/php/20210902/gearman.so: undefined symbol: ZVAL_NEW_ARR
while trying to run reverse_worker.php

libgearman8:amd64 1.1.18+ds-3.1ubuntu1

pecl extension: gearman 2.1.0 (stable)

Linux 5.11.0-41-generic #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

PHP 8.1.0 (cli) (built: Nov 25 2021 20:22:03) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.0, Copyright (c) Zend Technologies
with Zend OPcache v8.1.0, Copyright (c), by Zend Technologies

I have looked everywhere (even tried reading the C source but that didn't help) but I can't find the answer to that.

When will GearmanWorker::work be false? What can/will cause it to "fail" basically?
The PHP manual over at php.net says:

Waits for a job to be assigned and then calls the appropriate callback function. Issues an E_WARNING with the last Gearman error if the return code is not one of GEARMAN_SUCCESS, GEARMAN_IO_WAIT, or GEARMAN_WORK_FAIL.

If the return code of what is not one of GEARMAN_SUCCESS, GEARMAN_IO_WAIT or GEARMAN_WORK_FAIL?

Is there a way to see the Gearman Worker class as a PHP code? I.e. as if it was a class written in PHP?

I've seen that a new version (2.1.0) has been published at https://pecl.php.net/package/gearman

Is this repository (https://github.com/php/pecl-networking-gearman) the source of the 2.1.0 version?

If so, the "Browse Source" link in that page still points to https://github.com/hjr3/pecl-gearman and should be updated.

PS: I also reported this to https://bugs.php.net/bug.php?id=80636

Hello,
I'm new to Gearman. I've been able to write worker and client PhP scripts that successfully execute tasks.

Background:
I have also been trying to implement crontab on my gearman server so that the worker php scripts are loaded automatically on restarting the machine.

ie.
crontab -e
@reboot php /var/www/scripts_gearman/worker_one.php
@reboot php /var/www/scripts_gearman/worker_two.php

Observation (Using crontab)
While the scripts do load via crontab (see initial status) they are not stable. For example after running the client (ie. client_one) for worker_one the worker produces no result and upon reviewing its status (see reviewed status) no available workers are report.

Reboot
(crontab initializes gearman workers)

Initial status (on reboot):
gearadmin -h 127.0.0.1 -p 4730 --status
one 0 0 1
two 0 0 1

client one now called (triggering a worker one process)

Reviewed status (after client one called):
gearadmin -h 127.0.0.1 -p 4730 --status
one 0 0 0
two 0 0 1

Observation (using tutorial example)
The getting started tutorial here shows the php cli method for running a worker. This method is stable. For example after running the same client (ie. client_one) for worker_one the worker successfully produces a result and upon reviewing its status the worker continues to be available.

Initialize worker one
php /var/www/scripts_gearman/worker_one.php &

Initial status (after initializing worker one):
gearadmin -h 127.0.0.1 -p 4730 --status
one 0 0 1
two 0 0 1

client one now called (triggering a worker one process)

Reviewed status (after client one called):
gearadmin -h 127.0.0.1 -p 4730 --status
one 0 0 1
two 0 0 1

Question:
Is the crontab behavior expected? How can gearman workers be run correctly from crontab? What is the best way to initialize a worker on restarting a machine? Note the machine is a fresh ubuntu 24.04 server.

Hello,

Some background and then the error followed by an observation:

Background:
I am running php 8.3 on a fresh ubuntu 24.04 lts server, hosted at AWS. After successfully installing Gearman and receiving the version per the php getting started instructions given here. I tried to run the first demo and received the following output.

Error:
_PHP Warning: Module "gearman" is already loaded in Unknown on line 0
PHP Fatal error: Uncaught Error: Call to undefined method GearmanClient::do() in /var/www/gc_gearman.php:4
Stack trace:
#0 {main}

Observation:
I then tried another example (the reverse example) from here, which worked without a problem. I believe there is a bug in the extension or the "do" command is old and requires updating.

Hello,

Some background, the error, and the client code used (ie. modification to add remote client).

Background:
I am a new Gearman user. I have a fresh machine running Ubuntu 24.04 on AWS with Gearman installed successfully as per the version test given here. I am running PHP 8.3.

I can run all the provided Gearman php demos on the server (note a recent issue logged about "do" as opposed to "doNormal"). I am now trying to send a Gearman job (the reverse hello world string demo) to a second server for processing. The servers are on the same subnet and can ping each other, there are no firewalls blocking traffic.

When sending the job I receive the following error:

Error:
PHP Fatal error: Uncaught GearmanException: Failed to set exception option in /var/www/client.php:7
Stack trace:
#0 /var/www/client.php(7): GearmanClient->addServer()
#1 {main}

Client code used (note modification to add remove client via addServer):
`<?php

// Create our client object
$client = new GearmanClient();

// Add a server (modified where X.X.X.X is the actual IP address of given machine)

$client->addServer('X.X.X.X','4730'); // by default host/port will be "localhost" & 4730

echo "Sending job\n";

// Send reverse job
$result = $client->doNormal("reverse", "Hello!");
if ($result) {
echo "Success: $result\n";
}
?>`

Observation:
Help is greatly appreciated. I do not know if this is an error from my end or a possible bug.

see #12

I'm trying to install gearman and receive the result below.

RUN pecl install gearman-2.1.0
4.260 pecl/gearman requires PHP (version >= 7.0.0, version <= 8.1.99, excluded versions: 6.0.0), installed version is 8.2.9
4.260 No valid packages found
4.260 install failed

Could you please relase a version with support for php 8.2 or help me how to proceed .

thank you.

See wcgallego/pecl-gearman#72 for a patch. Any thoughts? I could rebase and submit a PR....

The master branch contains the fix 7da13e4

Without that patch, we can't use this extension on PHP 8.1, since we have this issue:

Warning: PHP Startup: Unable to load dynamic library 'gearman' [...]
Error relocating [...]/gearman.so: ZVAL_NEW_ARR: symbol not found

Could you explain please, what happened

libgearman/packet.cc:253 Assertion "packet->universal" failed for function "gearman_packet_free" likely for "Packet that is being freed has not been allocated, most likely this is do to freeing a gearman_task_st or other object twice"

Begin stack trace, frames found: 34
?0  0x7efcd4cf7f0f in /usr/local/lib/libgearman.so.8(+0x7f0f) [0x7efcd4cf7f0f]
?1  0x7efcd4d028e0 in /usr/local/lib/libgearman.so.8(+0x128e0) [0x7efcd4d028e0]
?2  0x7efcd4cfbf8d in /usr/local/lib/libgearman.so.8(+0xbf8d) [0x7efcd4cfbf8d]
?3  0x7efcd4cfbfed in /usr/local/lib/libgearman.so.8(+0xbfed) [0x7efcd4cfbfed]
?4  0x7efcd4d058a0 in /usr/local/lib/libgearman.so.8(+0x158a0) [0x7efcd4d058a0]
?5  0x7efcd4d058dd in /usr/local/lib/libgearman.so.8(+0x158dd) [0x7efcd4d058dd]
#6  0x7efcd4d08898 in gearman_worker_free at /usr/local/lib/libgearman.so.8
#7  0x7efcd4d2f831 in zim_GearmanWorker___destruct at /usr/lib/php/20200930/gearman.so
?8  0x7efcd7065499 in /usr/lib/php/20200930/xdebug.so(+0x16499) [0x7efcd7065499]
#9  0x5612e5d09452 in zend_call_function at php8.0
#10  0x5612e5d09705 in zend_call_known_function at php8.0
#11  0x5612e5d99a84 in zend_objects_destroy_object at php8.0
#12  0x5612e5d9e474 in zend_objects_store_del at php8.0
#13  0x5612e5d7dc7f in execute_ex at php8.0
?14  0x7efcd7064e3a in /usr/lib/php/20200930/xdebug.so(+0x15e3a) [0x7efcd7064e3a]
?15  0x5612e5b6007c in php8.0(+0x10a07c) [0x5612e5b6007c]
#16  0x5612e5d7fd89 in execute_ex at php8.0
?17  0x7efcd7064e3a in /usr/lib/php/20200930/xdebug.so(+0x15e3a) [0x7efcd7064e3a]
?18  0x5612e5b6007c in php8.0(+0x10a07c) [0x5612e5b6007c]
#19  0x5612e5d7fd89 in execute_ex at php8.0
?20  0x7efcd7064e3a in /usr/lib/php/20200930/xdebug.so(+0x15e3a) [0x7efcd7064e3a]
?21  0x5612e5b6007c in php8.0(+0x10a07c) [0x5612e5b6007c]
#22  0x5612e5d7fd89 in execute_ex at php8.0
?23  0x7efcd7064e3a in /usr/lib/php/20200930/xdebug.so(+0x15e3a) [0x7efcd7064e3a]
?24  0x5612e5b6007c in php8.0(+0x10a07c) [0x5612e5b6007c]
#25  0x5612e5d7fd89 in execute_ex at php8.0
?26  0x7efcd7064e3a in /usr/lib/php/20200930/xdebug.so(+0x15e3a) [0x7efcd7064e3a]
#27  0x5612e5d800fc in zend_execute at php8.0
#28  0x5612e5d16b6d in zend_execute_scripts at php8.0
#29  0x5612e5cb361b in php_execute_script at php8.0
?30  0x5612e5da5dce in php8.0(+0x34fdce) [0x5612e5da5dce]
?31  0x5612e5b69aeb in php8.0(+0x113aeb) [0x5612e5b69aeb]
#32  0x7efcd960f09b in __libc_start_main at /lib/x86_64-linux-gnu/libc.so.6
#33  0x5612e5b69c4a in _start at php8.0

Hi, we moved our workers into a dockerized autoscaled environment, but we started seeing this error: "Unable to add worker function".

Our setup: X gearman servers, Y gearman workers that listen on each server.

If we were to publish 400 messages, this error occurs for the last 10% of our messages.

I started a post on gearmand about order of tasks being reverse to which they were added.
I see no note on the PHP docs that its LIFO instead of FIFO.

gearman/gearmand#319

The ZVAL_NEW_ARR() macro has been removed as of PHP 8.1. It is advised to use array_init() or ZVAL_ARR with zend_new_array() instead.

Refer link to internal API changes: https://github.com/php/php-src/blob/PHP-8.1/UPGRADING.INTERNALS

Hello,
I have a question regarding the behavior of Gearadmin.

Background
I am running Gearman on an AWS instance (ie. Instance A) with the private ip 10.0.3.1

Observation
I have noticed that Gearadmin will only return errors when performing a status query without the localhost ip of 127.0.0.1

ie.
gearadmin -h 127.0.0.1 -p 4730 --status
reverse 0 0 1

ie.
gearadmin -h 10.0.3.1 -p 4730 --status
Error: Error connecting to 10.0.3.1.

Why does this happen?

Hello,

Background:
I am using Gearman with PHP and am having difficulty successfully adding Gearman clients with ports other than default. Documentation [ here ] suggests the following:
ie.
`<?php

// Create our client object.
$gmclient= new GearmanClient();

// Add two job servers, the first on the default 4730 port
$gmclient->addServer("10.0.0.1");
$gmclient->addServer("10.0.0.2", 7003);

?>`

Observation:
I am using two AWS instances as a testing environment. I have confirmed with AWS that the instances are connecting. I can successfully add a server in the default configuration or by specifying the localhost ip.
ie.
`<?php

// Create our client object.
$gmclient= new GearmanClient();

// Add two job servers, the first on the default 4730 port
$gmclient->addServer("127.0.0.1");
$gmclient->addServer("127.0.0.1", 4730); // note port update

?>`

However I cannot successfully add a server when departing from the the default host value.
ie.
`<?php

// Create our client object.
$gmclient= new GearmanClient();

// Add two job servers, the first on the default 4730 port
$gmclient->addServer("10.0.3.1");
$gmclient->addServer("10.0.3.1", 4730); // note port update

?>`

Php error:
Fatal error: Uncaught GearmanException: Failed to set exception option in /var/www/html/gearman_test.php:7 Stack trace: #0 /var/www/html/gearman_test.php.php(7): GearmanClient->addServer() #1 {main} thrown in /var/www/html/gearman_test.php.php on line 7

Machine Observations:
2x Fresh AWS Ubuntu 24 instances running PHP 8.3 and Apache.
No VPC security group rules are blocking communications.
No firewalls are enabled.
No iptables are enabled.
And the following listener is enabled on each machine:
ie.
sudo netstat -tulpn | grep LISTEN
tcp 0 0 127.0.0.1:4730 0.0.0.0:* LISTEN 775/gearmand

Question:
At this point I am unsure if the underlying problem is a bug, a Gearman configuration issue, or a documentation issue. I am a new Gearman user. I think Gearman is the solution I am looking for however I do need help resolving this issue because my application really must leverage Gearman servers beyond localhost.

Please assist and many sincere thanks in advance.

Hello,

In the previous repository, there was an issue around addServer making connections for \GearmanClient which was resolved with a new 3rd parameter. (See wcgallego/pecl-gearman#59)

Is there any plan to also support this for addServer() and addServers() for the \GearmanWorker class as well? I was able to migrate my code to use the 3rd parameter for \GearmanClient and avoided the GearmanException: Failed to set exception option for that case.

However, for \GearmanWorker I'm still getting an error.

PHP Fatal error:  Uncaught GearmanException: Failed to set exception option in Gearman.php:33                                                                  
Stack trace:                                                                              
#0 /home/dev/app/Util/Gearman.php(33): GearmanWorker->addServer('127.0.0.1', 4730)

And trying to add the 3rd parameter (set to false), I am getting:

Warning: GearmanWorker::addServer() expects at most 2 parameters, 3 given in /home/dev/app/Util/Gearman.php on line 33

gearman extension version => 2.1.0
libgearman version => 1.1.19.1

Thanks for any input!

As recently as version 2.0.6, (with PHP 7.4, libgearman 1.1.12) if PHP exited with a non-zero value while a worker was working on a job, the job would be returned to the stack, and would be retried as soon as it started up again. We recently upgraded to PHP 8, libgearman 1.1.19.1 and 2.1.2 of the Gearman extension, and it seems as if this is no longer the case; now if a PHP process crashes in the middle of a job, it seems that the job is essentially lost--it does not go back on the queue. If this is a change in the behavior, was it intentional?

The (old) behavior is discussed here:
https://stackoverflow.com/questions/8870132/error-conditions-and-retries-in-gearman/10348461#10348461
and here:
https://stackoverflow.com/questions/15790531/delay-a-gearman-job-in-php

In a few days PHP 8.2 will be released, is it possible to get the extension to support PHP 8.2?