[gentoo-user] sendmail: warning: inet_protocols: disabling IPv6

[Joseph]

Every time I compile a package I get a message:

sendmail: warning: inet_protocols: disabling IPv6 name/address support: Address family not supported by protocol

What is it looking for?

--
Joseph

[Mick]

Probably it is looking for a router (DNS repeater) that resolves DNS queries
to IPv6.

--
Regards,
Mick

[Joseph]

It never did it before, it start doing it when I upgraded to new "portage"

--
Joseph

[Stroller]

On 18 June 2013, at 16:00, Joseph wrote:

> Every time I compile a package I get a message:
>
> sendmail: warning: inet_protocols: disabling IPv6 name/address support: Address family not supported by protocol

1. Could you post the output of `grep -i mail /etc/make.conf` please?

2. Could you show us some relevant output indicating the status of the "ipv6" USE flag on your system, please? Please show us all packages installed with it activated.

I don't have an uptodate Gentoo system handy right now, so I'm not immediately sure the best way to perform that latter. There must be something cleaner and faster than `emerge -ep world | grep -i ipv6`, probably something in Gentoolkit.

You get the message when you compile packages, and the error message begins with "sendmail" - this makes me think you have portage configured (in your make.conf) to send you its output by email (the ewarn, eerror &c messages), and that it is your mailer which is giving this warning.

Googling the message suggests that your mailer might be Postfix: http://www.google.com/search?q=sendmail:+warning:+inet_protocols:+disabling+IPv6

If so, the second hit looks promising: http://unix.stackexchange.com/a/70962

Stroller.

[Joseph]

You are correct, I'm using postfix and after emerge system is emailing me the notification.
grep -i mail /etc/make.conf

PORTAGE_ELOG_SYSTEM="mail"
PORTAGE_ELOG_MAILURI="root /usr/sbin/sendmail"
PORTAGE_ELOG_MAILSUBJECT="package \${PACKAGE} merged on \${HOST} with notice"

I've tried to edit /etc/postfix/main.cf
but it does not contain any statement such as "inet_protocols"

It could be something to do with a new portage :-/

--
Joseph

[Joseph]

On 06/18/13 16:57, Stroller wrote:
>

Update.
Putting: inet_protocols = ipv4 in main.cf
and it help the message no longer appears.

According to postifix "inet_protocols = ipv4" is a default option but I could not find it anywhere "inet_protocols" in main.cf.

What surprises me is that this only happens on my x86 machine my other amd64 is not effected by it.

--
Joseph

[Randy Barlow]

On Tue, 18 Jun 2013 12:39:12 -0400, Joseph <sysc...@gmail.com> wrote:
> I've tried to edit /etc/postfix/main.cf
> but it does not contain any statement such as "inet_protocols"
>
> It could be something to do with a new portage :-/

I use inet_protocols = all on my mail system (that way it's dual stack). I
bet if you add that line, you'll be good to go.

--
R

[Joseph]

I just used inet_protocols = ipv4 nad problem is solved.
I think if I use "inet_protocols = all" I'll be getting the same error message.

--
Joseph

[J. Roeleveld]

Do you have IPV6 enabled in your kernel and for the network interfaces?
Simple and quick way to check, do you see IPV6-addresses when you type
"ifconfig -a" in a console?

I get this warning for all services that have IPV6 support on systems that
don't have IPV6 enabled.

--
Joost

[Walter Dnes]

On Tue, Jun 25, 2013 at 07:48:12AM +0200, J. Roeleveld wrote

A few years ago the developers, "in their infinite wisdom", decided to
enable the ipv6 USE flag by default. I found out "the hard way", when
internet-enabled apps like Firefox sat there, spinning their wheels for
a minute, before timing out the IPV6 lookup and falling back to IPV4.
Since then, I have always done a --pretend update run and check the
output, before doing the real update. And I've switched to beginning my
USE variable with "-*".

There is the option of setting USE="-ipv6" the more timid users. I
don't understand the point of defaulting to IPV6. The vast majority of
Gentoo users probably still run IPV4-only.

--
Walter Dnes <walt...@waltdnes.org>
I don't run "desktop environments"; I run useful applications

[Stroller]

On 25 June 2013, at 23:31, Walter Dnes wrote:
> … I have always done a --pretend update run and check the

> output, before doing the real update. And I've switched to beginning my
> USE variable with
>

> There is the option of setting USE="-ipv6" the more timid users. I
> don't understand the point of defaulting to IPV6.

On a Gentoo system one should *always* perform a --pretend update run and check the output, before doing the real update

I'm pretty sure replies have been made to you in the past about why USE="-*" is a Bad Idea™.

It's not "timid" to disable IPv6 support is by setting USE="-ipv6" - that's just the right way to do it.

Most people disabling IPv6 probably want to keep support for jpeg, png and *all* the other defaults.

I'm pretty sure that setting USE="-*" creates just as much work, on average, if not more.

You have just shifted the work from occasionally having to set -ipv6 (and similar) in your make.conf, to regularly having to add +mp3 +jpeg +vlc +minimal every time you emerge a new package.

Stroller.

[Neil Bothwick]

On Tue, 25 Jun 2013 18:31:05 -0400, Walter Dnes wrote:

> A few years ago the developers, "in their infinite wisdom", decided to
> enable the ipv6 USE flag by default. I found out "the hard way", when
> internet-enabled apps like Firefox sat there, spinning their wheels for
> a minute, before timing out the IPV6 lookup and falling back to IPV4.
> Since then, I have always done a --pretend update run and check the
> output, before doing the real update. And I've switched to beginning my
> USE variable with "-*".

So, on the basis of one decision that affected you slightly adversely
some years ago, you have exposed yourself to several years of extra work
and breakage by disabling a key portage feature?

I don't understand why your IPv4 only system had problems with apps
trying to use IPv6, as that couldn't happen unless you had enabled IPv6
in the kernel.

This problem was commonplace a few years ago with binary distros, caused
by crappy router firmware that couldn't handle IPv6, so the thing just
hung until the kernel timed out and fell back to IPv4.

I don't see how USE="-*" would fix either your router or your kernel
configuration.

> There is the option of setting USE="-ipv6" the more timid users. I
> don't understand the point of defaulting to IPV6. The vast majority of
> Gentoo users probably still run IPV4-only.

Because it only has an effect if you have already enabled IPv6 in your
kernel, and then only causes a problem with broken hardware. So a pretty
sensible option, although one I chose not to take when I noticed the
change in the output of emerge --ask.

As has already been said, you should always check such output, but it is
even more important to do so after switching profiles, which is the only
way the default USE flags change.


--
Neil Bothwick

Oxymoron: Reagan memoirs.

[staticsafe]

>
> FYI, this is no longer an issue as br
>
> --
> staticsafe
> O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
> Please don't top post - http://goo.gl/YrmAb
> Don't CC me! I'm subscribed to whatever list I just posted on.

Oops, hit send prematurely.

Most modern browsers make use of the "Happy Eyeballs" algorithm.

http://en.wikipedia.org/wiki/Happy_Eyeballs>
--
staticsafe
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Please don't top post.
Please don't CC! I'm subscribed to whatever list I just posted on.

[staticsafe]

[Walter Dnes]

On Wed, Jun 26, 2013 at 12:32:04AM +0100, Stroller wrote

> I'm pretty sure that setting USE="-*" creates just as much work,
> on average, if not more.
>
> You have just shifted the work from occasionally having to set -ipv6
> (and similar) in your make.conf, to regularly having to add +mp3
> +jpeg +vlc +minimal every time you emerge a new package.

I said I *START* the USE variable with "-*". Here's my USE setup...

USECPU="mmx mmxext sse sse2 sse3 ssse3"
USEOTHER=" X a52 aac bzip2 cxx dga dri exif ffmpeg flac fortran gallium gif intel jpeg mng mp3 mpeg ncurses nptl nptlonly nsplugin offensive ogg opengl openrc png posix readline ssl theora threads tiff tools truetype vim-syntax vorbis xcomposite webm x264 xpm xv xvid zlib"
USE="-* ${USECPU} ${USEOTHER}"

In /etc/portage/package.use I have the following, much of which I
would need regardless of the "-*" USE flag...

app-misc/mc -X
dev-lang/python xml
dev-libs/libxml2 python
games-emulation/dosbox alsa
mail-mta/ssmtp mta
media-gfx/ufraw gimp
media-libs/libsdl alsa audio joystick video
media-libs/libtheora encode
media-libs/mesa classic egl shared-glapi xorg
media-video/mplayer alsa iconv quicktime rtmp
sys-fs/eudev kmod
x11-libs/cairo glib svg
x11-wm/icewm imlib
x11-base/xorg-server suid xorg
x11-drivers/xf86-video-intel sna
x11-libs/libdrm libkms
www-client/midori deprecated
www-client/w3m -X -imlib
www-plugins/adobe-flash 64bit

# Firefox-specific
dev-lang/python sqlite
media-libs/libpng apng
dev-db/sqlite extensions

I select the flags that I want/need. When I have to add a flag to
package.use, I check whether that flag shows up multiple times. If so,
I consider moving it to USE in make.conf. Recently I did try an install
without "-*" under the default amd64 no-multilib profile (*NOT* the
"desktop" profile). Only part way through, I already had a larger USE
and package.use to exclude flags I don't want/need. For me, starting
USE with "-*" and adding additional necessary stuff in USE and
package.use is simpler than not starting USE with "-*".