On 10/4/2012 12:06 PM, Tom H wrote:
> On Thu, Oct 4, 2012 at 7:23 AM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>> On 10/4/2012 3:46 AM, Rick Thomas wrote:
>>> On Oct 3, 2012, at 8:40 PM, Satoru Otsubo wrote:
>>>>
>>>> But the phenomena are same, that is,
>>>> When booting my PC, apache2 failed to start.
>>>> And when I executed the following:
>>>> # /etc/init.d/apache2 restart
>>>> apache2 started successfully with the dual stack.
>>>>
>>>> Why this phenomena happens ?
>>>>
>>>
>>> Is the apache2 daemon starting before the ipv6 part of the network
>>> configuration is completely up?
>>
>> His log error does seem to indicate Apache is starting before the ipv6
>> stack is available--one of the downsides of parallel init.
>
> Where did you see the log?
The OP pasted this in his 2nd post:
Starting web server: apache2[Thu Oct 04 01:02:03 2012]: [crit] (EAI
9)Address family for hostname not supported: Alloc_listener: failed to
set up sockaddr for pppp:qqqq:....:rrrr
Syntax error on line 2 of /etc/apache2/ports.conf
Listen setup failed.
Action 'start' failed.
The Apache error log may have more information.
failed!
I think Chris Bannister is onto something. I previously overlooked the
syntax error msg. A syntax error would explain the socket setup
failure. Probably something as simple as a typo in ports.conf.
--
Stan
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 506EBC4F.3060407@hardwarefreak.com">http://lists.debian.org/506EBC4F.3060407@hardwarefreak.com
10-05-2012, 04:42 PM
Satoru Otsubo
apache2's handling of IP version 6
Hi,
I'm initiator of this thread.
> On Thu, Oct 04, 2012 at 04:53:23AM +0900, Satoru Otsubo wrote:
> > Syntax error on line 2 of /etc/apache2/ports.conf
>
> What about this syntax error?
Syntax error on line 2 is the following:
Listen [pppp:qqqq:....:rrrr]:80
....................
By the way, I thought the following concerning the problem in my CGI PC (my server PC):
Internet-------------Router------Lan-----my PC
When booting PC, apache2 decides that ipv6 is Ok if it gets the ipv6's information and ipv6 is not Ok if it can't get the ipv6's information.
And apache2 gets the ipv6's information from the router's RA(Router Advertisements).
But the router can't send RA immediately.
Therefore when apache2 decides on whether ipv6 is Ok, it can't get the information yet.
Therefore it decides that ipv6 is not Ok.
Therefore in case of dual stack, apache2 issues an error because ports.conf is
as follows:
Listen a.b.c.d:80
Listen [pppp:qqqq:....:rrrr]:80
Listen a.b.c.d:443
Listen [pppp:qqqq:....:rrrr]:443
(Because ipv6 address explicitely exists, apache2 issues an error when it can't get ipv6's information.)
In case of ports.conf being the following:
Listen 80
Listen 443,
apache2 falls back to listen only ipv4 ports because no address format exists.
In fact, in boot sequence, I scroll locked by clicking the Scroll Lock key just before apache2's line appears, and after some moments, I again click the Scroll Lock to restart the boot sequence.
Then after booting completed, I executed,
# netstat -an
And I found there exists Listen 80 and Listen 443 in the tcp6 lines.
My thought is wrong ?
By the way, on the PC of Squeeze desktop install (my second PC),
After booting completed, on command of
# netstat -an ,
I can always find Listen 80 and Listen 443 in the tcp6 lines.
(Without # /etc/init.d/apache2 restart)
Why in the desktop environment, "# /etc/init.d/apache2 restart" is not needed ?
Is apache2 of the desktop environment executed in the other way than CGI environment ?
In fact, I found,
/etc/hosts of my GUI PC includes
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
whereas, /etc/hosts of my CUI PC only includes
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
Thanks,
Satoru
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20121006014214.0567fd4e.trnsnt@otip.jp">http://lists.debian.org/20121006014214.0567fd4e.trnsnt@otip.jp
10-06-2012, 11:08 AM
Tom H
apache2's handling of IP version 6
On Fri, Oct 5, 2012 at 6:54 AM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> On 10/4/2012 12:06 PM, Tom H wrote:
>> On Thu, Oct 4, 2012 at 7:23 AM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>>> On 10/4/2012 3:46 AM, Rick Thomas wrote:
>>>> On Oct 3, 2012, at 8:40 PM, Satoru Otsubo wrote:
>>>>> But the phenomena are same, that is,
>>>>> When booting my PC, apache2 failed to start.
>>>>> And when I executed the following:
>>>>> # /etc/init.d/apache2 restart
>>>>> apache2 started successfully with the dual stack.
>>>>>
>>>>> Why this phenomena happens ?
>>>>
>>>> Is the apache2 daemon starting before the ipv6 part of the network
>>>> configuration is completely up?
>>>
>>> His log error does seem to indicate Apache is starting before the ipv6
>>> stack is available--one of the downsides of parallel init.
>>
>> Where did you see the log?
>
> The OP pasted this in his 2nd post:
>
> Starting web server: apache2[Thu Oct 04 01:02:03 2012]: [crit] (EAI
> 9)Address family for hostname not supported: Alloc_listener: failed to
> set up sockaddr for pppp:qqqq:....:rrrr
> Syntax error on line 2 of /etc/apache2/ports.conf
> Listen setup failed.
> Action 'start' failed.
> The Apache error log may have more information.
> failed!
Thanks. I'd checked the archive before emailing you and missed it -
for the second time!
> I think Chris Bannister is onto something. I previously overlooked the
> syntax error msg. A syntax error would explain the socket setup
> failure. Probably something as simple as a typo in ports.conf.
I don't understand why there's a syntax error at boot but not when
apache's restarted but we'll see...
As I pointed out in an earlier post, "Listen 80" will enable both ipv4
and ipv6, and remove the possibility that there's a typo in the ip
address(es). Since Debian (and all distributions that I know) compile
apache with an option to map v4 to v6, running "ss -ntl" will show
just one ipv6 socket.
Maybe having both "Listen *:80" and "Listen [::]:80" will create two
sockets, if that's what the OP's after (or one of the things that he's
after). I can't check because I don't have ipv6 and I'm not sure that
apache'll interact the same way with an ipv6 link-local address as it
would with a "real" ipv6 address.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAOdo=SztX2Ye4edz8arZZEmqepbo+-x=E7vxDByap3pZvU_uYQ@mail.gmail.com
10-06-2012, 11:22 AM
Tom H
apache2's handling of IP version 6
On Fri, Oct 5, 2012 at 12:42 PM, Satoru Otsubo <trnsnt@otip.jp> wrote:
>> On Thu, Oct 04, 2012 at 04:53:23AM +0900, Satoru Otsubo wrote:
> By the way, I thought the following concerning the problem in my CGI PC (my server PC):
>
> Internet-------------Router------Lan-----my PC
>
> When booting PC, apache2 decides that ipv6 is Ok if it gets the ipv6's information
> and ipv6 is not Ok if it can't get the ipv6's information.
> And apache2 gets the ipv6's information from the router's RA(Router Advertisements).
That explains the at-boot v/s after-restart behavior...
Can be started later, based on a sysvinit "stage" like "$network", etc.
Does ipv6 come up cleanly if you do a soft or hard restart of apache
in rc.local?
> Then after booting completed, I executed,
> # netstat -an
> And I found there exists Listen 80 and Listen 443 in the tcp6 lines.
>
> My thought is wrong ?
>
> By the way, on the PC of Squeeze desktop install (my second PC),
> After booting completed, on command of
> # netstat -an ,
> I can always find Listen 80 and Listen 443 in the tcp6 lines.
> (Without # /etc/init.d/apache2 restart)
It's normal; apache listens on the ipv6 socket for both ipv4 and ipv6.
> In fact, I found,
> /etc/hosts of my GUI PC includes
> # The following lines are desirable for IPv6 capable hosts
> ::1 localhost ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> ff02::3 ip6-allhosts
>
> whereas, /etc/hosts of my CUI PC only includes
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
All that you really need for ipv6 is the "::1 ..." line. Having one
line less on your X-less box won't make a difference.
Is this your entire "/etc/hosts"? Don;t you have any ipv4 settings?!
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAOdo=Sz5N8ZFOE6K51g-QQz7piG1q8O1KC0RDSohYn4BMaCcYg@mail.gmail.com
10-06-2012, 07:01 PM
Satoru Otsubo
apache2's handling of IP version 6
Hi,
Tom H
>
> Does ipv6 come up cleanly if you do a soft or hard restart of apache
> in rc.local?
>
I can't understand "a soft or hard restart".
But I examined as follows:
..Case 1..
I editted /etc/rc.local as follows: (Do I have to add "exit 0" at end ?)
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
In this case, After booting finished, I was able to find port 80 in tcp6 lines
of "netstat -an".
I didn't need # /etc/init.d/apache2 restart.
But a few seconds elapse at the stage of exim4.
Therefore,
..Case 2..
/etc/rc.local is same as Case 1.
And I executed,
# mv /etc/rc2.d/{S20,K80}exim4
# update-rc.d exim4 defaults
In this case, After booting finished, I was unable to find port 80 in tcp6 lines.
I needed # /etc/init.d/apache2 restart.
>
> All that you really need for ipv6 is the "::1 ..." line. Having one
> line less on your X-less box won't make a difference.
>
> Is this your entire "/etc/hosts"? Don;t you have any ipv4 settings?!
>
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
Thanks,
Satoru
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20121007040120.3f9b3d6b.trnsnt@otip.jp">http://lists.debian.org/20121007040120.3f9b3d6b.trnsnt@otip.jp
10-08-2012, 06:51 PM
Tom H
apache2's handling of IP version 6
On Sat, Oct 6, 2012 at 3:01 PM, Satoru Otsubo <trnsnt@otip.jp> wrote:
>> Does ipv6 come up cleanly if you do a soft or hard restart of apache
>> in rc.local?
>
> I can't understand "a soft or hard restart".
soft:
service apache2 relaod
service apache2 graceful
hard:
service apache2 restart
>> All that you really need for ipv6 is the "::1 ..." line. Having one
>> line less on your X-less box won't make a difference.
>>
>> Is this your entire "/etc/hosts"? Don;t you have any ipv4 settings?!
>
> The entire text is the following:
>
> 127.0.0.1 localhost
> 192.168.xx.xx xxxx.xxx.xx xxxx
Is the "192.168..." line added by network-manager?
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAOdo=Sw5NxEZoWxfKr654YaaQrGg5MGbKDkqa5cuPb9LqjsYO Q@mail.gmail.com
10-09-2012, 05:20 PM
Satoru Otsubo
apache2's handling of IP version 6
Hi,
Tom H
>
> >> All that you really need for ipv6 is the "::1 ..." line. Having one
> >> line less on your X-less box won't make a difference.
> >>
> >> Is this your entire "/etc/hosts"? Don;t you have any ipv4 settings?!
> >
> > The entire text is the following:
> >
> > 127.0.0.1 localhost
> > 192.168.xx.xx xxxx.xxx.xx xxxx
>
> Is the "192.168..." line added by network-manager?
>
The "192.168..." line exists from the beginning after I installed Squeeze
by debian-6.0.3-i386-netinst.iso
(The package of network-manager is not installed. )
Thanks,
Satoru
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20121010022030.1c93f7e8.trnsnt@otip.jp">http://lists.debian.org/20121010022030.1c93f7e8.trnsnt@otip.jp
Tue Oct 9 19:30:01 2012
Return-Path: <devel-bounces@lists.fedoraproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
eagle542.startdedicated.com
X-Spam-Level:
X-Spam-Status: No, score=-4.3 required=5.0 tests=DKIM_ADSP_CUSTOM_MED,
DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MAT CHES_RCVD,SPF_PASS,
T_DKIM_INVALID autolearn=ham version=3.3.2
X-Original-To: tom@linux-archive.org
Delivered-To: tom-linux-archive.org@eagle542.startdedicated.com
Received: from bastion.fedoraproject.org (bastion01.fedoraproject.org [209.132.181.2])
by eagle542.startdedicated.com (Postfix) with ESMTP id 07A1520E008E
for <tom@linux-archive.org>; Tue, 9 Oct 2012 19:21:59 +0200 (CEST)
Received: from lists.fedoraproject.org (collab03.vpn.fedoraproject.org [192.168.1.70])
by bastion01.phx2.fedoraproject.org (Postfix) with ESMTP id F2FEA20CB9;
Tue, 9 Oct 2012 17:21:57 +0000 (UTC)
Received: from collab03.fedoraproject.org (localhost [127.0.0.1])
by lists.fedoraproject.org (Postfix) with ESMTP id 930F6409FA;
Tue, 9 Oct 2012 17:21:57 +0000 (UTC)
X-Original-To: devel@lists.fedoraproject.org
Delivered-To: devel@lists.fedoraproject.org
Received: from smtp-mm02.fedoraproject.org (smtp-mm02.fedoraproject.org
[66.35.62.164])
by lists.fedoraproject.org (Postfix) with ESMTP id 0F94F4078F
for <devel@lists.fedoraproject.org>;
Tue, 9 Oct 2012 17:21:55 +0000 (UTC)
Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51])
by smtp-mm02.fedoraproject.org (Postfix) with ESMTP id 9746F409F9
for <devel@lists.fedoraproject.org>;
Tue, 9 Oct 2012 17:21:54 +0000 (UTC)
Received: by mail-wg0-f51.google.com with SMTP id ed3so3082145wgb.20
for <devel@lists.fedoraproject.org>;
Tue, 09 Oct 2012 10:21:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=message-id:date:from:user-agent:mime-version:to:subject:references
:in-reply-to:content-type:content-transfer-encoding;
bh=5hjwePTrAfTkSf+6C5m0goccxlL15S7Q8vSGzE5HZ/Q=;
b=UoKyiuiZyCx+gjtKDPYUTdznsa20m1qZD0/guyop4+eUYPpF+cgDltAeb8bBqje65J
SuUaRzOv9KRoFNM+zdcOSPrshn165+ufJ/i76GBaWfUZ01VS+HKZcSjxVooWrDqMeB30
+Li3zkijuqF4JD2MgvPqV0LKcZb/Y0pUg81rm8YGW0vw10CqVY2UdhQm7BsZ55YIV6t4
MrG9NR+zAOzZU/isX3x5MMvH11XIuI32bTKlvQi5S0g03DDD9P62k2otHm8pCXAM 4+yy
V425UjRRB7aQc99mHw3P8s4i2gXRwi0jrkp9zf2CGuGBrYRmVe 4IIv9OHpQ0jBYdKjho
IndQ==
Received: by 10.180.100.35 with SMTP id ev3mr6168060wib.7.1349803313827;
Tue, 09 Oct 2012 10:21:53 -0700 (PDT)
Received: from localhost.localdomain ([217.28.190.130])
by mx.google.com with ESMTPS id b3sm25790750wie.0.2012.10.09.10.21.45
(version=TLSv1/SSLv3 cipher=OTHER);
Tue, 09 Oct 2012 10:21:53 -0700 (PDT)
Message-ID: <50745CB4.4080108@gmail.com>
Date: Tue, 09 Oct 2012 17:19:48 +0000
From: =?UTF-8?B?IkrDs2hhbm4gQi4gR3XDsG11bmRzc29uIg==?=
<johannbg@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:15.0) Gecko/20120911 Thunderbird/15.0.1
MIME-Version: 1.0
To: devel@lists.fedoraproject.org
Subject: Re: replacing rsyslogd in minimal with journald [was Re: systemd
requires HTTP server and serves QR codes]
References: <50740365.7050000@gmail.com> <20121009115304.GA24573@disco.bu.edu>
<20121009140404.GG19792@tango.0pointer.de>
<20121009144524.GB1337@disco.bu.edu>
<20121009150030.GD1337@disco.bu.edu> <507441BA.70508@redhat.com>
<20121009153036.GA5248@disco.bu.edu> <50744502.4050607@gmail.com>
<20121009161100.GA2750@disco.bu.edu> <50744D00.8030800@gmail.com>
<20121009164051.GA3441@disco.bu.edu>
In-Reply-To: <20121009164051.GA3441@disco.bu.edu>
X-BeenThere: devel@lists.fedoraproject.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Development discussions related to Fedora
<devel@lists.fedoraproject.org>
List-Id: Development discussions related to Fedora
<devel.lists.fedoraproject.org>
List-Unsubscribe: <https://admin.fedoraproject.org/mailman/options/devel>,
<mailto:devel-request@lists.fedoraproject.org?subject=unsubscrib e>
List-Archive: <http://lists.fedoraproject.org/pipermail/devel/>
List-Post: <mailto:devel@lists.fedoraproject.org>
List-Help: <mailto:devel-request@lists.fedoraproject.org?subject=help>
List-Subscribe: <https://admin.fedoraproject.org/mailman/listinfo/devel>,
<mailto:devel-request@lists.fedoraproject.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: devel-bounces@lists.fedoraproject.org
Errors-To: devel-bounces@lists.fedoraproject.org
apache2's handling of IP version 6
