# CONFIG_IPV6 is not set

Bug #1134534 reported by pippoppo
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Gearman
Fix Released
Undecided
Unassigned

Bug Description

Hi,
I know we are in 2013, but at the moment we're not setting IPV6 in our own custom kernels.

So it seems we can't start gearman, with this error:

  DEBUG 2013-02-27 16:29:56.827105 [ main ] Trying to listen on :::4730 -> libgearman-server/gearmand.cc:576
  ERROR 2013-02-27 16:29:56.827810 [ main ] socket()(Address family not supported by protocol) -> libgearman-server/gearmand.cc:442
  ERROR 2013-02-27 16:29:56.827833 [ main ] gearmand_sockfd_close() called with an invalid socket -> libgearman-server/io.cc:914

Am I wrong or we're hitting a "bug"? I couldn't find a way to disable IPV6 support....

thanks,
corrado

Revision history for this message
Keyur (keyurdg) wrote :

Hi,

Error handling in version 1.0.3 has changed such that not being able to bind to an IPV6 socket is now fatal.

I'd suggest downgrading and using v1.0.2 until this bug https://bugs.launchpad.net/gearmand/+bug/1127347 is fixed. Once fixed, you'll need to start passing in the argument "-L 0.0.0.0" to limit the socket binding to IPV4.

Revision history for this message
pippoppo (pippoppo) wrote :

Thanks,
1.0.2 isn't affected, you're right.
Not really intuitive, the "-L 0.0.0.0" argument, but ok. I'm closing the bug as a duplicate of 1127347

Thanks for your time.

Changed in gearmand:
status: New → Fix Released
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.