Re: AW: [squid-users] ident auth problem with squid 3.1.0.6
Michael Kastinger wrote: Hi Amos, thanks for your patch, i patched the source (patch -p1 ident_2.patch) and recompiled squid. but now squid is dying after the first request from the client: 2009/04/17 10:53:10| Starting Squid Cache version 3.1.0.7 for i686-pc-linux-gnu... FATAL: Received Segment Violation...dying. after disabling ident auth in squid.conf, its working fine. whats wrong? -p0 is the patch type. Maybe something else going wrong now, can we get a back trace? and lets shove this to squid-dev since its getting code deep. Amos 2009/4/17 Amos Jeffries squ...@treenet.co.nz: michael.kastin...@spar.at wrote: Hi Amos, what dou you mean with: This thread started with Same problem in 3.1.0.6 no reference to _which_ problem. The thread was started with detailed information regarding this ident issue (strace, cache.log) see posting with Subject [squid-users] ident auth problem with squid 3.1.0.6 Which additional informations do you need? Please let me know. Actual quoted content about the earlier problem would have helped, or at least a link to the thread in archives. This thread? http://www.mail-archive.com/squid-users@squid-cache.org/msg63339.html (something about squid failing to lookup ident) or this one? http://www.mail-archive.com/squid-users@squid-cache.org/msg63174.html (squid trying to open a port twice) Assuming you mean the second. Does the attached patch work? Amos -- Please be using Current Stable Squid 2.7.STABLE6 or 3.0.STABLE14 Current Beta Squid 3.1.0.7 -- Please be using Current Stable Squid 2.7.STABLE6 or 3.0.STABLE14 Current Beta Squid 3.1.0.7
Re: AW: [squid-users] ident auth problem with squid 3.1.0.6
Hi Amos, thanks for your patch, i patched the source (patch -p1 ident_2.patch) and recompiled squid. but now squid is dying after the first request from the client: 2009/04/17 10:53:10| Starting Squid Cache version 3.1.0.7 for i686-pc-linux-gnu... FATAL: Received Segment Violation...dying. after disabling ident auth in squid.conf, its working fine. whats wrong? 2009/4/17 Amos Jeffries squ...@treenet.co.nz: michael.kastin...@spar.at wrote: Hi Amos, what dou you mean with: This thread started with Same problem in 3.1.0.6 no reference to _which_ problem. The thread was started with detailed information regarding this ident issue (strace, cache.log) see posting with Subject [squid-users] ident auth problem with squid 3.1.0.6 Which additional informations do you need? Please let me know. Actual quoted content about the earlier problem would have helped, or at least a link to the thread in archives. This thread? http://www.mail-archive.com/squid-users@squid-cache.org/msg63339.html (something about squid failing to lookup ident) or this one? http://www.mail-archive.com/squid-users@squid-cache.org/msg63174.html (squid trying to open a port twice) Assuming you mean the second. Does the attached patch work? Amos -- Please be using Current Stable Squid 2.7.STABLE6 or 3.0.STABLE14 Current Beta Squid 3.1.0.7
Re: AW: [squid-users] ident auth problem with squid 3.1.0.6
michael.kastin...@spar.at wrote: Hi Amos, what dou you mean with: This thread started with Same problem in 3.1.0.6 no reference to _which_ problem. The thread was started with detailed information regarding this ident issue (strace, cache.log) see posting with Subject [squid-users] ident auth problem with squid 3.1.0.6 Which additional informations do you need? Please let me know. Actual quoted content about the earlier problem would have helped, or at least a link to the thread in archives. This thread? http://www.mail-archive.com/squid-users@squid-cache.org/msg63339.html (something about squid failing to lookup ident) or this one? http://www.mail-archive.com/squid-users@squid-cache.org/msg63174.html (squid trying to open a port twice) Assuming you mean the second. Does the attached patch work? Amos -- Please be using Current Stable Squid 2.7.STABLE6 or 3.0.STABLE14 Current Beta Squid 3.1.0.7 === modified file 'src/ident.cc' --- src/ident.cc 2009-02-01 10:09:23 + +++ src/ident.cc 2009-04-17 01:16:02 + @@ -220,9 +220,12 @@ return; } +IpAddress addr = me; +addr.SetPort(0); // NP: use random port for outbound to IDENT_PORT + fd = comm_open(SOCK_STREAM, IPPROTO_TCP, - me, + addr, COMM_NONBLOCKING, ident);
AW: [squid-users] ident auth problem with squid 3.1.0.6
Same issue with latest 3.1.0.7 :-( --- SPAR Osterreichische Warenhandels-AG Hauptzentrale A - 5015 Salzburg, Europastrasse 3 FN 34170 a Tel: +43 662 4470 24245 Mobile: +43 664 8159150 E-Mail: michael.kastin...@spar.at Internet: http://www.spar.at Wichtiger Hinweis: Der Inhalt dieser E-Mail kann vertrauliche und rechtlich geschutzte Informationen, insbesondere Betriebs- oder Geschaftsgeheimnisse, enthalten, zu deren Geheimhaltung der Empfanger verpflichtet ist. Die Informationen in dieser E-Mail sind ausschlie?lich fur den Adressaten bestimmt. Sollten Sie die E-Mail irrtumlich erhalten haben so ersuchen wir Sie, die Nachricht von Ihrem System zu loschen und sich mit uns in Verbindung zu setzen. Uber das Internet versandte E-Mails konnen leicht manipuliert oder unter fremdem Namen erstellt werden. Daher schlie?en wir die rechtliche Verbindlichkeit der in dieser Nachricht enthaltenen Informationen aus. Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn er von uns schriftlich bestatigt und gezeichnet wird. Sollte trotz der von uns verwendeten Virus-Schutzprogramme durch die Zusendung von E-Mails ein Virus in Ihre Systeme gelangen, haften wir nicht fur evtl. hieraus entstehende Schaden. Wir danken fur Ihr Verstandnis. Important notice: The contents of this e-mail may contain confidential and legally protected information that is in particular related to operational and trade secrets, which the recipient is obliged to treat as confidential. The information in this e-mail is made available exclusively for use by the addressee. In the event that the e-mail may have been sent to you in error, we would ask you to kindly delete this communication from your system and to contact us. E-mails sent via the Internet can be easily manipulated or sent out under someone else's name. We therefore do not accept legal liability for the information contained in this communication. The contents of the e-mail are only legally binding if they have been confirmed and signed by us in writing. If, in spite of our using Antivirus protection software, a virus may have penetrated your system through the sending of this e-mail, we do not accept liability for any damage that may possibly arise as a result of this. We trust that you appreciate our position. ---
