Re: [squid-users] Error making squid-3.1.0.7-20090412 on Mac OS X 10.4
vollkom...@gmx.net wrote: Please find below the output of make -w -d against the 3.HEAD-20090519 source. ... rm -f .libs/squid.nm .libs/squid.nmS .libs/squid.nmT creating .libs/squidS.c (cd .libs gcc -g -O2 -c -fno-builtin squidS.c) rm -f .libs/squidS.c .libs/squid.nm .libs/squid.nmS .libs/squid.nmT g++ -Werror -Wall -Wpointer-arith -Wwrite-strings -Wcomments -g -O2 .libs/squidS.o -g -o squid AclRegs.o AuthReg.o access_log.o AsyncEngine.o cache_cf.o ProtoPort.o CacheDigest.o cache_manager.o carp.o cbdata.o ChunkedCodingParser.o client_db.o client_side.o client_side_reply.o client_side_request.o BodyPipe.o clientStream.o CompletionDispatcher.o comm_select.o comm_select_win32.o comm_poll.o comm_epoll.o comm_kqueue.o ConfigOption.o ConfigParser.o debug.o delay_pools.o DelayId.o DelayBucket.o DelayConfig.o DelayPool.o DelaySpec.o DelayTagged.o DelayUser.o DelayVector.o NullDelayId.o disk.o DiskIO/DiskIOModule.o DiskIO/ReadRequest.o DiskIO/WriteRequest.o dlink.o dns_internal.o errorpage.o ETag.o event.o EventLoop.o external_acl.o ExternalACLEntry.o fd.o fde.o filemap.o forward.o fqdncache.o ftp.o gopher.o helper.o htcp.o http.o HttpStatusLine.o HttpHdrCc.o HttpHdrRange.o HttpHdrSc.o HttpHdrScTarget.o HttpHdrContRange.o HttpHeader.o HttpHeaderTools.o HttpBody.o HttpMsg.o Htt pReply.o HttpRequest.o HttpRequestMethod.o icp_v2.o icp_v3.o int.o internal.o ipc.o ipcache.o list.o logfile.o main.o mem.o mem_node.o MemBuf.o MemObject.o mime.o multicast.o neighbors.o Packer.o Parsing.o pconn.o peer_digest.o peer_select.o peer_sourcehash.o peer_userhash.o redirect.o referer.o refresh.o RemovalPolicy.o send-announce.o snmp_core.o snmp_agent.o SquidNew.o ssl_support.o stat.o StatHist.o String.o stmem.o store.o StoreFileSystem.o store_io.o StoreIOState.o store_client.o store_digest.o store_dir.o store_key_md5.o store_log.o store_rebuild.o store_swapin.o store_swapmeta.o store_swapout.o StoreMeta.o StoreMetaMD5.o StoreMetaSTD.o StoreMetaSTDLFS.o StoreMetaUnpacker.o StoreMetaURL.o StoreMetaVary.o StoreSwapLogData.o Server.o SwapDir.o time.o tools.o tunnel.o unlinkd.o url.o URLScheme.o urn.o useragent.o wccp.o wccp2.o whois.o wordlist.o LoadableModule.o LoadableModules.o DiskIO/DiskIOModules_gen.o repl_modules.o globals.o string_arrays.o DiskIO/Blocking/Blocking DiskIOModule.o -Wl,-bind_at_load ./.libs/libsquid.a auth/.libs/libacls.a acl/.libs/libacls.a acl/.libs/libstate.a auth/.libs/libauth.a acl/.libs/libapi.a base/.libs/libbase.a ip/.libs/libip.a fs/.libs/libfs.a icmp/.libs/libicmp.a icmp/.libs/libicmp-core.a -L/Users/raymont/squid-3.HEAD-20090519/lib repl/libheap.a repl/liblru.a libBlocking.a ../snmplib/libsnmp.a adaptation/.libs/libadaptation.a -lssl -lcrypto -lmiscutil -lm -lresolv ../lib/libLtdl/.libs/libltdlc.a -ldl /usr/libexec/gcc/i686-apple-darwin8/4.2.1/ld: multiple definitions of symbol CbDataListint::CBDATA_CbDataList acl/.libs/libacls.a(Asn.o) definition of CbDataListint::CBDATA_CbDataList in section (__DATA,__data) acl/.libs/libacls.a(SslErrorData.o) definition of CbDataListint::CBDATA_CbDataList in section (__DATA,__data) collect2: ld returned 1 exit status rm -f .libs/squidS.o Got a SIGCHLD; 1 unreaped children. Reaping losing child 0x00350220 PID 360 make[3]: *** [squid] Error 1 Removing child 0x00350220 PID 360 from chain. Original-Nachricht We do have to wait unfortunately. The autotools bootstrapping is not part of the patches. The snapshot is out now. Amos Alright, we do have to bite the bullet then. I've removed the ssl_error_t templating in patch http://www.squid-cache.org/Versions/v3/HEAD/changesets/b9692.patch Amos -- Please be using Current Stable Squid 2.7.STABLE6 or 3.0.STABLE15 Current Beta Squid 3.1.0.7
Re: [squid-users] Error making squid-3.1.0.7-20090412 on Mac OS X 10.4
This patch got it built successfully, so I installed it twice: once afresh into /usr/local/squid31, then reconfigured and installed over 3.0STABLE16-RC1 in /usr/local/squid. I also tweaked the latter's squid.conf for IPv6. However, both copies of squid-3.HEAD-20090519 are crashing (simply squid -v will do) with the same Bus error I posted back on May 10, pointing to the same AuthReg.cc:21: http://marc.info/?l=squid-devm=124198980600328w=2 Original-Nachricht Alright, we do have to bite the bullet then. I've removed the ssl_error_t templating in patch http://www.squid-cache.org/Versions/v3/HEAD/changesets/b9692.patch Amos -- Please be using Current Stable Squid 2.7.STABLE6 or 3.0.STABLE15 Current Beta Squid 3.1.0.7 -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-aktionspreis/?ac=OM.AD.PD003K11308T4569a
Re: [squid-users] Error making squid-3.1.0.7-20090412 on Mac OS X 10.4
This patch got it built successfully, so I installed it twice: once afresh into /usr/local/squid31, then reconfigured and installed over 3.0STABLE16-RC1 in /usr/local/squid. I also tweaked the latter's squid.conf for IPv6. However, both copies of squid-3.HEAD-20090519 are crashing (simply squid -v will do) with the same Bus error I posted back on May 10, pointing to the same AuthReg.cc:21: http://marc.info/?l=squid-devm=124198980600328w=2 Ah, possibly the init failure someone posted a fix for: http://www.squid-cache.org/Versions/v3/HEAD/changesets/b9689.patch Amos Original-Nachricht Alright, we do have to bite the bullet then. I've removed the ssl_error_t templating in patch http://www.squid-cache.org/Versions/v3/HEAD/changesets/b9692.patch Amos -- Please be using Current Stable Squid 2.7.STABLE6 or 3.0.STABLE15 Current Beta Squid 3.1.0.7 -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-aktionspreis/?ac=OM.AD.PD003K11308T4569a
Re: Is it really necessary for fatal() to dump core?
Patch at: http://www.squid-cache.org/bugs/show_bug.cgi?id=2673 On 19/05/2009, at 1:50 PM, Mark Nottingham wrote: tools.c:fatal() dumps core because it calls abort. Considering that the core can be quite large (esp. on a 64bit system), and that there's fatal_dump() as well if you really want one, can we just make fatal() exit(1) instead of abort()ing? Cheers, -- Mark Nottingham m...@yahoo-inc.com -- Mark Nottingham m...@yahoo-inc.com
Re: [squid-users] Error making squid-3.1.0.7-20090412 on Mac OS X 10.4
Thanks! It's finally up and running. But, it's not quite smooth sailing yet: 1. DNS lookups fail completely. 204.127.198.4 is among a handful of external DNS servers I use, whether defined as dns_nameservers in squid.conf or picked by squid automatically from /etc/resolv.conf: 2009/05/20 21:44:49| comm_udp_sendto: FD 8, (family=2) 204.127.198.4:53: (22) Invalid argument 2009/05/20 21:44:49| idnsSendQuery: FD 8: sendto: (22) Invalid argument 2009/05/20 21:46:10| comm_set_tos: setsockopt(IP_TOS) on FD 7: (22) Invalid argument Is IPv6 dual-stack enabled in your OS? it looks like the v6 sockets are unable to do the v4-mapping they need to handle v4 traffic. I find it a bit weird that setting TOS also fails, its one of the older functionality and shared between both IP protocols. 2. Does that above have anything to do with the failure to apply this patch? patch -p0 b9691.patch patching file src/dnsserver.cc Hunk #1 FAILED at 427. Hunk #2 FAILED at 436. 2 out of 2 hunks FAILED -- saving rejects to file src/dnsserver.cc.rej I hope not. That patch does not alter anything functionally and is internal to the obsolete dnsserver helper. 3. I see the following in cache.log. I realize they're warnings, but is there any way to make squid happy? I thought the slash format is a CIDR mask. WARNING: Netmasks are deprecated. Please use CIDR masks instead. WARNING: IPv4 netmasks are particularly nasty when used to compare IPv6 to IPv4 ranges. squid.conf: acl sitelocalsrc src fec0::/48 acl linklocalsrc src fe80::/64 The conf is correct, if the warnings are appearing on that line something has definitely broken. Tomorrow is my actually scheduled day for squid maintenance. I will have to look at these closer after the maintenance work. Amos Original-Nachricht Ah, possibly the init failure someone posted a fix for: http://www.squid-cache.org/Versions/v3/HEAD/changesets/b9689.patch Amos -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-aktionspreis/?ac=OM.AD.PD003K11308T4569a
Re: [squid-users] Error making squid-3.1.0.7-20090412 on Mac OS X 10.4
Original-Nachricht 1. DNS lookups fail completely. 204.127.198.4 is among a handful of external DNS servers I use, whether defined as dns_nameservers in squid.conf or picked by squid automatically from /etc/resolv.conf: 2009/05/20 21:44:49| comm_udp_sendto: FD 8, (family=2) 204.127.198.4:53: (22) Invalid argument 2009/05/20 21:44:49| idnsSendQuery: FD 8: sendto: (22) Invalid argument 2009/05/20 21:46:10| comm_set_tos: setsockopt(IP_TOS) on FD 7: (22) Invalid argument Is IPv6 dual-stack enabled in your OS? it looks like the v6 sockets are unable to do the v4-mapping they need to handle v4 traffic. I find it a bit weird that setting TOS also fails, its one of the older functionality and shared between both IP protocols. I'd think so. I'm using 6to4, if that matters. Here's the snippet from config.log:t configure:25519: checking whether to enable IPv6 configure:25534: result: yes configure:25548: checking if PF_INET6 is available configure:25583: g++ -o conftest -g -O2 -g conftest.cpp 5 configure:25587: $? = 0 configure:25593: ./conftest configure:25597: $? = 0 configure:25599: result: yes configure:25624: result: configure:25643: checking for IPv6 split-stack requirement configure:25666: result: no configure:25672: checking for sin6_len field in struct sockaddr_in6 configure:25703: g++ -c -g -O2 conftest.cpp 5 configure:25710: $? = 0 configure:25727: result: yes ... #define USE_IPV6 1 #define IPV6_SPECIAL_V4MAPPED 1 #define IPV6_SPECIAL_SPLITSTACK 0 Here's cache.log with debug_options 0,5 78,9: 2009/05/20 23:36:23.570| idnsALookup: buf is 36 bytes for www.ipv6.sixxs.net, id = 0x7fca 2009/05/20 23:36:23.570| comm_udp_sendto: FD 7, (family=2) 18.70.0.160:53: (22) Invalid argument 2009/05/20 23:36:23.570| idnsSendQuery: FD 7: sendto: (22) Invalid argument 2. Does that above have anything to do with the failure to apply this patch? patch -p0 b9691.patch patching file src/dnsserver.cc Hunk #1 FAILED at 427. Hunk #2 FAILED at 436. 2 out of 2 hunks FAILED -- saving rejects to file src/dnsserver.cc.rej I hope not. That patch does not alter anything functionally and is internal to the obsolete dnsserver helper. 3. I see the following in cache.log. I realize they're warnings, but is there any way to make squid happy? I thought the slash format is a CIDR mask. WARNING: Netmasks are deprecated. Please use CIDR masks instead. WARNING: IPv4 netmasks are particularly nasty when used to compare IPv6 to IPv4 ranges. squid.conf: acl sitelocalsrc src fec0::/48 acl linklocalsrc src fe80::/64 The conf is correct, if the warnings are appearing on that line something has definitely broken. Tomorrow is my actually scheduled day for squid maintenance. I will have to look at these closer after the maintenance work. Amos Turns out my previous conjecture was wrong. Those warnings appear even after I've commented out all the IPv6 bits in the ACLs. Here' the complete lines from cache.log, in case it matters: 2009/05/20 23:46:02| WARNING: Netmasks are deprecated. Please use CIDR masks instead. 2009/05/20 23:46:02| WARNING: IPv4 netmasks are particularly nasty when used to compare IPv6 to IPv4 ranges. 2009/05/20 23:46:02| WARNING: For now we assume you meant to write /12 2009/05/20 23:46:02| WARNING: Netmasks are deprecated. Please use CIDR masks instead. 2009/05/20 23:46:02| WARNING: IPv4 netmasks are particularly nasty when used to compare IPv6 to IPv4 ranges. 2009/05/20 23:46:02| WARNING: For now we assume you meant to write /12 -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-aktionspreis/?ac=OM.AD.PD003K11308T4569a
Re: More patches for squid2-HEAD
On 2-HEAD. On 14/05/2009, at 6:36 PM, Mark Nottingham wrote: On 23/04/2009, at 10:38 AM, Mark Nottingham wrote: http://www.squid-cache.org/bugs/show_bug.cgi?id=2643 http://www.squid-cache.org/bugs/show_bug.cgi?id=2631 These are the last two remaining. There's been some discussion on them, but I believe the issues have been resolved in the most recent patches attached to them; if I don't hear otherwise soon, I'll go ahead and apply to 2-HEAD. Cheers, -- Mark Nottingham m...@yahoo-inc.com -- Mark Nottingham m...@yahoo-inc.com
