SEO

#1 (**permalink**) 02-21-2008, 05:45 AM

Another problem which I cannot pass myself is with my apache2 - after
downgrade to kernel 2.4 I get:
root@piotr piotr # /etc/init.d/apache2
start
* Starting apache2...
[Fri Nov 28 21:26:53 2003] [crit] (92)Protocol not available: make_sock:
for address [::]:80, apr_socket_opt_set: (IPV6_V6ONLY) no listening
sockets available, shutting down Unable to open logs

WTF? I even check the log and added socket filtering to the kernel,
recomiled iproute iptable, apache itself and still the same message

--
PiotrAF
icq#19392046 gadu-gadu#66915

#2 (**permalink**) 02-21-2008, 05:45 AM

PiotrAF <piotraf@nospam.poczta.onet.pl> writes:

> Another problem which I cannot pass myself is with my apache2 - after
> downgrade to kernel 2.4 I get:
> root@piotr piotr # /etc/init.d/apache2
> start
> * Starting apache2...
> [Fri Nov 28 21:26:53 2003] [crit] (92)Protocol not available: make_sock:
> for address [::]:80, apr_socket_opt_set: (IPV6_V6ONLY) no listening
> sockets available, shutting down Unable to open logs

The IPV6_ONLY is suspicious, although I don't really know.

Are you trying to use IPV6 and not IPV4 ?

You might want to do 'sysctl -a | grep only' and see if net.ipv6.bindv6only=1.

#3 (**permalink**) 02-21-2008, 05:45 AM

On Fri, 28 Nov 2003 14:23:10 -0800, walt wrote:

> PiotrAF <piotraf@nospam.poczta.onet.pl> writes:
>
>> Another problem which I cannot pass myself is with my apache2 - after
>> downgrade to kernel 2.4 I get:
>> root@piotr piotr # /etc/init.d/apache2
>> start
>> * Starting apache2...
>> [Fri Nov 28 21:26:53 2003] [crit] (92)Protocol not available: make_sock:
>> for address [::]:80, apr_socket_opt_set: (IPV6_V6ONLY) no listening
>> sockets available, shutting down Unable to open logs
>
> The IPV6_ONLY is suspicious, although I don't really know.
>
> Are you trying to use IPV6 and not IPV4 ?
>

No, i.e. I have somethings standard and in previous installation played
with it but all I did now was downgrade the kernel and that also was done
with my previous working for months config

> You might want to do 'sysctl -a | grep only' and see if
> net.ipv6.bindv6only=1.
nothing 'only'
/sbin/sysctl -a|grep bind
net.ipv4.ip_nonlocal_bind = 0

I read thati tmight be cause by something ohter than apache listenning on
that port - do you now how to check waht is listenning on what port?

--
PiotrAF
icq#19392046 gadu-gadu#66915

#4 (**permalink**) 02-21-2008, 05:45 AM

PiotrAF <piotraf@nospam.poczta.onet.pl> writes:

> I read thati tmight be cause by something ohter than apache listenning on
> that port - do you now how to check waht is listenning on what port?

The usual is 'netstat -l' and there is always 'netstat -a' for everything
that has a socket open.

#5 (**permalink**) 02-21-2008, 05:45 AM

So anyway, it was like, 01:42 CET Nov 29 2003, you know? Oh, and, yeah,
walt was all like, "Dude,
> PiotrAF <piotraf@nospam.poczta.onet.pl> writes:

>> I read thati tmight be cause by something ohter than apache
>> listenning on that port - do you now how to check waht is
>> listenning on what port?
>
> The usual is 'netstat -l' and there is always 'netstat -a' for
> everything that has a socket open.

Add a '-p' and it'll do what the op wants.

'netstat -lp', in particular.

hth.

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
02:38:20 up 7:55, 5 users, load average: 2.78, 2.35, 2.61
$ cat /dev/bollocks Registered Linux user #261729
enable bleeding-edge e-services

#6 (**permalink**) 02-21-2008, 05:45 AM

On Sat, 29 Nov 2003 02:41:44 +0100, Johan Lindquist wrote:

> So anyway, it was like, 01:42 CET Nov 29 2003, you know? Oh, and, yeah,
> walt was all like, "Dude,
>> PiotrAF <piotraf@nospam.poczta.onet.pl> writes:
>
>>> I read thati tmight be cause by something ohter than apache listenning
>>> on that port - do you now how to check waht is listenning on what port?
>>
>> The usual is 'netstat -l' and there is always 'netstat -a' for
>> everything that has a socket open.
>
> Add a '-p' and it'll do what the op wants.
>
> 'netstat -lp', in particular.
>
thnx to both of you. I found something like that:
tcp 0 0 ::ffff:217.113.23:51538 ::ffff:216.239.37.10:80 ESTABLISHED
tcp 0 0 ::ffff:217.113.23:60303 ::ffff:216.239.37.10:80 ESTABLISHED
so I changed the /etc/rc.conf and /etc/hosts and hashed everything
concerning IPv6 - I even pulled out the net cables just to be sure no one
is connected. no more of the above but the apache doesn't start and the
same message appears

--
PiotrAF
icq#19392046 gadu-gadu#66915

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Apache2 problem after kernel downgrade 2.6 >2.4 ]no listening sockets available]