Over a million developers have joined DZone.

PHP and Gearman: Unable to Connect after Upgrade

DZone's Guide to

PHP and Gearman: Unable to Connect after Upgrade

· Web Dev Zone ·
Free Resource

Learn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.

I upgraded PHP and related pecl modules on my development machine today, and ran into a problem with Gearman. Actually I ran into more than one! Firstly the challenge of getting the newest pecl version working with a gearman version. Then an error where my existing PHP application couldn't connect to gearman after upgrade.

Installing Gearmand and Pecl Gearman on Ubuntu 12.10

First up: the version of gearman in aptitude isn't new enough to match the (lovely, shiny) new version in pecl. This problem will solve itself with future releases and is just the result of the different speeds that releases get to users via different channels. To get this all set up, I used the excellent tutorial I found here: http://www.phamviet.net/2012/10/10/ubuntu-php-5-4-x-and-gearman-troubleshooting.

After working through this tutorial, I was able to install the pecl gearman extension at the newest version (1.1.1) successfully.

Dealing with "Unable to connect" error

The code I was trying to run is pretty hardened, it's been in production for nearly two years - yet it just did not work after upgrade and the error "unable to connect" made it sound more like a gearman problem than a PHP one, so I didn't spot the issue straight away. The exact error from my logs:

PHP Warning: GearmanClient::doBackground(): send_packet(GEARMAN_COULD_NOT_CONNECT) Failed to send server-options packet -> libgearman/connection.cc:430

In fact, what happened was that the GearmanClient::addServers() method now requires that the port also be specified with an IP address, in the format whereas previously it would take an IP address and assume the default port number. I simply changed my previous code:


To the updated version like this:


And all was well. It's a tricky thing to track down so I hope this helps if it happened to you! I also went back and edited the previous code samples on this blog in attempt to have other people avoid the issue.

What’s the best way to boost the efficiency of your product team and ship with confidence? Check out this ebook to learn how Sentry's real-time error monitoring helps developers stay in their workflow to fix bugs before the user even knows there’s a problem.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}