gearmand doesn't start: "Address family not supported by protocol"

Bug #1271890 reported by Remco Bergervoet
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gearman
Invalid
Undecided
Unassigned

Bug Description

The gearman process doesn't start. The error:
    ERROR 2014-01-21 12:13:06.000000 [ main ] socket()(Address family not supported by protocol) -> libgearman-server/gearmand.cc:470

This is with rhel 6.4 and gearmand-1.1.11

Revision history for this message
Alessandro Ren (dirty-ren) wrote :

I am having the same problem, CentOS 5.x.

Revision history for this message
Brian Aker (brianaker) wrote :

Is IPV6 enabled? What are you using for command arguments to start up the server?

Changed in gearmand:
status: New → Incomplete
Revision history for this message
Remco Bergervoet (remco-bergervoet) wrote : Re: [Bug 1271890] Re: gearmand doesn't start: "Address family not supported by protocol"

Hello,

Thank you very much for your response. I managed to get it working, but
didn't find a way to remove my generated ticket. I guess it was the way I
compiled it under rhel6.4.

Kind regards,
Remco

On Sun, Feb 2, 2014 at 4:02 AM, Brian Aker <email address hidden> wrote:

> Is IPV6 enabled? What are you using for command arguments to start up
> the server?
>
> ** Changed in: gearmand
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1271890
>
> Title:
> gearmand doesn't start: "Address family not supported by protocol"
>
> Status in Gearman Server and Client Libraries:
> Incomplete
>
> Bug description:
> The gearman process doesn't start. The error:
> ERROR 2014-01-21 12:13:06.000000 [ main ] socket()(Address family
> not supported by protocol) -> libgearman-server/gearmand.cc:470
>
> This is with rhel 6.4 and gearmand-1.1.11
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gearmand/+bug/1271890/+subscriptions
>

Brian Aker (brianaker)
Changed in gearmand:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.