RE: [squid-users] IPv6 error prevents Squid start

Added debug_options 28,9 to squid.conf

May 19 11:20:08 splprx01 ntpd[1593]: synchronized to 10.226.0.19, stratum 3
May 19 11:20:08 splprx01 ntpd[1593]: time reset -0.311298 s
May 19 11:20:08 splprx01 ntpd[1593]: kernel time sync status change 2001
May 19 11:29:01 splprx01 ntpd[1593]: synchronized to 10.226.0.19, stratum 3
May 19 11:32:14 splprx01 squid[2018]: Squid Parent: will start 1 kids
May 19 11:32:14 splprx01 squid[2018]: Squid Parent: (squid-1) process 2021 started
May 19 11:32:14 splprx01 squid[2021]: Starting Squid Cache version 3.2.0.17 for x86_64-unknown-linux-gnu...
May 19 11:32:15 splprx01 squid[2021]: Address.cc(958) GetSockAddr: Ip::Address::GetSockAddr : Cannot convert non-IPv4 to IPv4. from [::]
May 19 11:32:15 splprx01 squid[2018]: Squid Parent: (squid-1) process 2021 exited due to signal 6 with status 0
May 19 11:32:18 splprx01 squid[2018]: Squid Parent: (squid-1) process 2025 started
May 19 11:32:18 splprx01 squid[2025]: Starting Squid Cache version 3.2.0.17 for x86_64-unknown-linux-gnu...
May 19 11:32:19 splprx01 squid[2025]: Address.cc(958) GetSockAddr: Ip::Address::GetSockAddr : Cannot convert non-IPv4 to IPv4. from [::]
May 19 11:32:19 splprx01 squid[2018]: Squid Parent: (squid-1) process 2025 exited due to signal 6 with status 0
May 19 11:32:22 splprx01 squid[2018]: Squid Parent: (squid-1) process 2028 started
May 19 11:32:22 splprx01 squid[2028]: Starting Squid Cache version 3.2.0.17 for x86_64-unknown-linux-gnu...
May 19 11:32:23 splprx01 squid[2028]: Address.cc(958) GetSockAddr: Ip::Address::GetSockAddr : Cannot convert non-IPv4 to IPv4. from [::]
May 19 11:32:23 splprx01 squid[2018]: Squid Parent: (squid-1) process 2028 exited due to signal 6 with status 0
May 19 11:32:26 splprx01 squid[2018]: Squid Parent: (squid-1) process 2033 started
May 19 11:32:26 splprx01 squid[2033]: Starting Squid Cache version 3.2.0.17 for x86_64-unknown-linux-gnu...
May 19 11:32:27 splprx01 squid[2033]: Address.cc(958) GetSockAddr: Ip::Address::GetSockAddr : Cannot convert non-IPv4 to IPv4. from [::]
May 19 11:32:27 splprx01 squid[2018]: Squid Parent: (squid-1) process 2033 exited due to signal 6 with status 0
May 19 11:32:30 splprx01 squid[2018]: Squid Parent: (squid-1) process 2037 started
May 19 11:32:30 splprx01 squid[2037]: Starting Squid Cache version 3.2.0.17 for x86_64-unknown-linux-gnu...
May 19 11:32:31 splprx01 squid[2037]: Address.cc(958) GetSockAddr: Ip::Address::GetSockAddr : Cannot convert non-IPv4 to IPv4. from [::]
May 19 11:32:31 splprx01 squid[2018]: Squid Parent: (squid-1) process 2037 exited due to signal 6 with status 0
May 19 11:32:31 splprx01 squid[2018]: Squid Parent: (squid-1) process 2037 will not be restarted due to repeated, frequent failures
May 19 11:32:31 splprx01 squid[2018]: Exiting due to repeated, frequent failures

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Thursday, May 17, 2012 9:08 PM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] IPv6 error prevents Squid start

On 18/05/2012 12:56 p.m., Zill, Gregory (OMA-GIS) wrote:
> We have several squid hosts promised to deliver quickly to some LATAM sites. These locations started with a yum installed squid and then moved to the 3.2.0.16/17 for features. I know have another site that is throwing the Ip::Address::GetSockAddr error and squid will not start at all. Is it possible some library or squid dependency may have got updated with "yum update" and upset the apple cart? I appreciate your time. Please advise.

Squid is written to operate on hybrid dual-stack systems (dual stack with v4-mapping abilities). Split-stack and non-mapping dual-stack system support is still incomplete, but should be working in 3.2.0.17.

I will need the backtrace to know where the trouble component is and what it is trying to do with an IPv6 [::] / "*" address.

For now pause the updates cycle and possbly check the system IPv6 settings on the barfing machines are either enabled, or disabled in a way Squid can detect (IPv6 socket() creation disabled).

Amos

>
> -----Original Message-----
> From: Zill, Gregory (OMA-GIS)
>
> I get the same error when I revert to Squid 3.2.0.16.
>
> squid[7989]: Address.cc(958) GetSockAddr: Ip::Address::GetSockAddr :
> Cannot convert non-IPv4 to IPv4. from [::]
>
> context from line 958 of Address.cc
>
> void
> Ip::Address::GetSockAddr(struct sockaddr_in&buf) const {
> if ( IsIPv4() ) {
> buf.sin_family = AF_INET;
> buf.sin_port = m_SocketAddr.sin6_port;
> Map6to4( m_SocketAddr.sin6_addr, buf.sin_addr);
> } else {
>>> debugs(14, DBG_CRITICAL, HERE<< "Ip::Address::GetSockAddr :
>>> Cannot convert non-IPv4 to IPv4. from "<< *this );
> memset(&buf,0xFFFFFFFF,sizeof(struct sockaddr_in));
> assert(false);
> }
>
> -----Original Message-----
> From: Zill, Gregory (OMA-GIS)
>
> Has anyone seen this error? Should I revert to 3.2.0.16? Please advise.
>
> -----Original Message-----
> From: Zill, Gregory (OMA-GIS)
> Sorry for the lack of info:
>
> Linux 32-bit 2.6.32-220.13.1.el6.i686 CentOS 6.2
>
> Squid Cache: Version 3.2.0.17
> configure options: --enable-ltdl-convenience
> - no patching
>
> From ifcfg-eth0:
> ...
> IPV4_FAILURE_FATAL=yes
> IPV6INIT=no
>
> -----Original Message-----
> From: Amos Jeffries
> On 11/05/2012 12:14 a.m., Zill, Gregory (OMA-GIS) wrote:
>> I have some references from a google search, but no actual fix seen. Has anyone overcome this?
>>
>> Address.cc(958) GetSockAddr: Ip::Address::GetSockAddr : Cannot
>> convert non-IPv4 to IPv4. from [::]
>>
>> I appreciate your time.
> That is the equivaent of failing to convert between upper and lower case letters 'A' and 'a'. There is absolutely no reason for it to fail.
>
> What Squid is this happening in? what operating system is it built for?
> and what has been patched into it?
>
> Amos
> This message contains information which may be confidential and privileged. Unless you are the intended recipient (or authorized to receive this message for the intended recipient), you may not use, copy, disseminate or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail, and delete the message. Thank you very much.
>
Received on Sat May 19 2012 - 14:34:25 MDT