Re: [squid-users] Help with accelerated site

Hi All,

I get this in my cache log, does anyone know what it means please?
Unlinkd pipe opened on FD 13
Everytime I get this I know something is going pear shape again
Thank you all
Regards
Adam
----- Original Message -----
From: "Ron Wheeler" <rwheeler_at_artifact-software.com>
To: "Adam_at_Gmail" <adbasque_at_googlemail.com>
Sent: Saturday, March 27, 2010 5:07 PM
Subject: Re: [squid-users] Help with accelerated site

>I sent you my working config.
> My squid is proxying Apache on its own machine
>
> http_port 192.168.1.3:81 is the port that squid is listening on it
> should just be "80" no host so it gets the incoming http requests.
> http_port 80 accel vhost defaultsite=www.mysite.org
>
> The host specification is why it can not bind.
>
> Adam_at_Gmail wrote:
>> Hi Ron,
>> Thanks for your reply and thanks for your time
>>
>> This is perhaps the 10th time I uninstalled it and reinstalled it
>> And this is the very first time I could access my websites internally,
>> externally nothing yet, I am still getting the error
>> The following error was encountered while trying to retrieve the URL: /
>>
>> Invalid URL
>>
>> Some aspect of the requested URL is incorrect.
>>
>> Some possible problems are:
>>
>> a.. Missing or incorrect access protocol (should be http:// or similar)
>>
>> b.. Missing hostname
>>
>> c.. Illegal double-escape in the URL-Path
>>
>> d.. Illegal character in hostname; underscores are not allowed.
>>
>> Your cache administrator is webmaster.
>>
>>
>>
>> My clients can all access the internet, Yes I am sure that there's a
>> misconfiguration in my config file but I followed every tutorial
>>
>> trying desperately to get something up, after a while you're saturated
>> and very tired, bouncing from on issue to another
>>
>> I checked and triple checked my iptables rules everything looks fine so
>> far
>>
>> For instance, my backend server is listening right now on port 81, why
>> did I put it on port 81 because I was getting
>>
>> Cannot bind to .... in the log file
>>
>> so I changed it to 81 and I am getting the same error, there's absolutely
>> nothing else in my entire network that is using that port
>>
>> So why can't it bind to port 81? You see the type of things that can
>> drive you through the wall
>>
>> at the moment I have only three machines
>>
>> A is Running the Proxy and the Router (IPTABLES)
>>
>> B is the back end server
>>
>> C is the DNS/DHCP servers
>>
>> And only the backend server that is currently listening on port 81 and
>> before that it was listening on port 80
>>
>> no matter which port I put in my config I get the "Cannot bind to ...."
>> in the log file
>>
>> here is a bit of my config
>>
>> *********************************************************************
>>
>> http_port 192.168.1.3:81 accel parent vhost defaultsite=www.mysite.org
>>
>> cache_peer 192.168.1.3 parent 81 0 no-query originserver name=main
>>
>> acl dstdomain our_sites dstdomain www.mysite1.org www.mysite2.com
>> www.mysite3.net
>>
>> http_allow_access main allow our_sites
>>
>> http_peer_access main deny all
>>
>> At the moment all of these sites are running on the same server
>> (virtualhost)
>>
>> The only thing I am not sure of is probably the cache_peer directive
>>
>> "cache_peer 192.168.1.3 parent 81 0 no-query originserver name=main"
>>
>> If it's wrong then I don't know what to put in there
>>
>> Regards
>>
>> Adam
>>
>> ----- Original Message ----- From: "Ron Wheeler"
>> <rwheeler_at_artifact-software.com>
>> To: "Adam_at_Gmail" <adbasque_at_googlemail.com>
>> Cc: <squid-users_at_squid-cache.org>
>> Sent: Saturday, March 27, 2010 4:34 PM
>> Subject: Re: [squid-users] Help with accelerated site
>>
>>
>>> It is a very stable piece of software that is used in production all the
>>> time.
>>>
>>> You have made a small mistake somewhere in your setup.
>>>
>>> One of your errors in a previous e-mail seemed to indicate that you had
>>> programmed a loop into your setup.
>>>
>>> You might try uninstalling and starting over with an out of the box
>>> configuration.
>>>
>>> I would also start with only one way proxying and get that working.
>>> If you are trying to act as an accelerator for your website, just do
>>> that.
>>>
>>> That is a trivial setup.
>>> You might also use Webmin to do the configuring since it gives you a gui
>>> and avoids fiddling with configuration file syntax.
>>>
>>> In my case, I have the proxy running on the same machine as the apache
>>> webserver
>>> accel defaultsite=www.artifact-software.com vhost
>>>
>>> Squid listens on port 80 and tries to satisfy requests from its cache.
>>>
>>> If it can not, it passes the request to port 127.0.0.1:81 where Apache
>>> is listening with about 20 vhost sites including 2 proxies for Tomcats
>>> on other backend servers.
>>>
>>> Works great so I would not ge at all concerned that you will have
>>> problems after you get your little misconfiguring fixed.
>>>
>>> Ron
>>>
>>>
>>> Adam_at_Gmail wrote:
>>>> Hello All.
>>>> I have to say since I started using Squid I get thrown from one problem
>>>> to another, followed every suggestion and every tutorial
>>>> and I could not get through to my my backend server
>>>> This is ridiculous now, I honestly start to believe that this whole
>>>> project is a joke or the software isn't at all mature to deal with what
>>>> it is supposed to deal with, it's still in a teething stages, and I
>>>> believe that we are the guinea pigs of this project where they made us
>>>> believe that it works, I do not believe for one second that it
>>>> acctually works.
>>>>
>>>> I have read so many questions regarding this particular issue and
>>>> "nobody" could come up with a straight answer, are we the only people
>>>> with this issue? are we the only people with no luck?
>>>>
>>>> The questions that was asked time and time again was never been
>>>> answered, so please don't tell me that this thing works, I'd like to
>>>> see it
>>>> and don't tell me this whole site runs on a proxy Squid I'd like to see
>>>> it aswell.
>>>>
>>>> I was getting this before:
>>>> ERROR
>>>> The requested URL could not be retrieved
>>>>
>>>> While trying to retrieve the URL: /
>>>>
>>>> The following error was encountered:
>>>>
>>>> * Invalid URLAnd I followed a suggestion I read on the mailing list,
>>>> that maybe I needed to add a vhost after the http_port 3128Now I am
>>>> getting this instead:The requested URL could not be
>>>> retrieved--------------------------------------------------------------------------------The
>>>> following error was encountered while trying to retrieve the URL:
>>>> http://www.mysite.org/Access Denied.Access control configuration
>>>> prevents your request from being allowed at this time. Please contact
>>>> your service provider if you feel this is incorrect.Your cache
>>>> administrator is webmaster.It's not acctually working at all, all it
>>>> does is taking you from one problem to another, and so forth it's a
>>>> none stop it'a bag of problems and nasty surprises, not to mention
>>>> things you need to tweak on my system to make Mr Squid happierI am
>>>> sorry guys but this thing doesn't work and I believe it when I see it
>>>> and even if I see it working it's still ridiculousto spend as much time
>>>> to get one piece of software to work.I have followed the tutorials to
>>>> the letter and many suggestions, not to mention the amount of time I
>>>> wasted on this thingnever before in my life I have spent as much time
>>>> on any programme, this is the first time and I am not willing to spend
>>>> the rest of my life trying to figure out something that doesn't
>>>> work.Sorry guys but I am very very disapointed with this, I am just
>>>> going to completely uninstall the whole thingAnd go back to the way it
>>>> was before or perhaps look for an alternative for something that
>>>> works.Thanks to all of you who tried to helpBest of luck to anyone
>>>> who's still trying to solve Squid's never ending issues.Thank
>>>> you.RegardsAdam----- Original Message ----- From: "Ron Wheeler"
>>>> <rwheeler_at_artifact-software.com>
>>>> To: "Adam_at_Gmail" <adbasque_at_googlemail.com>
>>>> Cc: "Amos Jeffries" <squid3_at_treenet.co.nz>;
>>>> <squid-users_at_squid-cache.org>
>>>> Sent: Thursday, March 25, 2010 1:58 AM
>>>> Subject: Re: [squid-users] Help with accelerated site
>>>>
>>>>
>>>>> Adam_at_Gmail wrote:
>>>>>> Hello there,
>>>>>> Thanks for the reply Ron and Amos
>>>>>>
>>>>>>
>>>>>> Maybe my original e-mail wasn't clear a bit confusing I am sorry if I
>>>>>> confused you
>>>>>>
>>>>>> I have squid running on Machine A with let's say local ip 192.168.1.4
>>>>>> the backend server is running on machine B and ip address 192.168.1.3
>>>>>>
>>>>>> Now, instead of getting the website that is located on Machine B
>>>>>> 192.168.1.3 which is listening on port 81 not 80.
>>>>>> I am getting the default Apache Page on the Proxy server Machine
>>>>>> which is 192.168.1.4
>>>>>>
>>>>>> And I do have the vhost in my configuration
>>>>>> Well there are two apaches running on the two machines, the proxy
>>>>>> machine and the web-server machine, except the web-server apache
>>>>>> listens on port 81, logically (technically) speaking it should work,
>>>>>> but for some reason it doesn't.
>>>>>> I hope it makes more sense to you what I am trying to describe here
>>>>>
>>>>> Very helpful.
>>>>> You can not have apache listening for port 80 on 192.168.1.4 and Squid
>>>>> trying to do the same thing.
>>>>> Only one process can have port 80.
>>>>> You will very likely find a note in the squid logs that says something
>>>>> to the effect that squid can not bind to port 80.
>>>>> If you shutdown apache on 192.168.1.4 and restart squid, your proxy
>>>>> will work (if the rest of the configuration is correct)
>>>>> If you then try to start apache on 192.168.1.4 it will certainly
>>>>> complain loudly about port 80 not being free.
>>>>>
>>>>> If you want to use Apache on both 192.168.1.4 and 192.168.1.3 you need
>>>>> to set the apache on 192.168.1.4 to listen on port 81 and set squid to
>>>>> proxy to the apache on 192.168.1.4 and use apache's proxy and vhost
>>>>> features to reach 192.168.1.5 which can be set to listen on port 80.
>>>>> This will support
>>>>> browser=>Squid on 192.168.1.4 ==> Apache on 192.168.1.4:81 (vhost)
>>>>> ==>Apache 192.168.1.3:80
>>>>> That is a pretty common approach.
>>>>>
>>>>> Ron
>>>>>
>>>>>
>>>>>>
>>>>>> Thank you all for your help
>>>>>> Regards
>>>>>> Adam
>>>>>>
>>>>>> ----- Original Message ----- From: "Amos Jeffries"
>>>>>> <squid3_at_treenet.co.nz>
>>>>>> To: <squid-users_at_squid-cache.org>
>>>>>> Sent: Thursday, March 25, 2010 1:01 AM
>>>>>> Subject: Re: [squid-users] Help with accelerated site
>>>>>>
>>>>>>
>>>>>>> On Wed, 24 Mar 2010 19:48:27 -0400, Ron Wheeler
>>>>>>> <rwheeler_at_artifact-software.com> wrote:
>>>>>>>> What is squid proxying?
>>>>>>>> Usually the normal behaviour is exactly what you are getting since
>>>>>>>> squid
>>>>>>>
>>>>>>>> normally proxies Apache on 80.
>>>>>>>> Browser ==> Squid on 80==>proxied to Apache on port 81.
>>>>>>>>
>>>>>>>>
>>>>>>>> If Squid is not proxying Apache, then it looks like you have Apache
>>>>>>>> running on 80.
>>>>>>>>
>>>>>>>> If you are trying to redirect port 80 to another program that is
>>>>>>>> not
>>>>>>>> Apache, then you need to get Apache off port 80.
>>>>>>>> You can not have 2 programs listening to port 80.
>>>>>>>>
>>>>>>>> If Apache is running and owns port 80, Squid will not start.
>>>>>>>>
>>>>>>>> If this is the case, You likely have errors in the logs to this
>>>>>>>> effect.
>>>>>>>>
>>>>>>>> Shut down Apache and and restart Squid.
>>>>>>>>
>>>>>>>> Try to start Apache and now it should howl with anger (or log in
>>>>>>>> anger)
>>>>>>>> at not getting port 80.
>>>>>>>>
>>>>>>>>
>>>>>>>> Ron
>>>>>>>>
>>>>>>>> Adam_at_Gmail wrote:
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> I have followed this configuration, but when I try and access the
>>>>>>>>> website from outside my network
>>>>>>>>> All I get is the default page of the apache on the machine where
>>>>>>>>> the
>>>>>>>>> Squid proxy is installed
>>>>>>>>>
>>>>>>>>> Here is the link:
>>>>>>>>>
>>>>>>>>> http://wiki.squid-cache.org/ConfigExamples/Reverse/BasicAccelerator
>>>>>>>>>
>>>>>>>>> here is the configuration I followed
>>>>>>>>>
>>>>>>>>> http_port 80 accel defaultsite=your.main.website.name(changed my
>>>>>>>>> port
>>>>>>>>> to 81 my backend server listens on port 81)I havehttp_port 81
>>>>>>>>> accel
>>>>>>>>> defaultsite=www.my.website.org vhostand then used thiscache_peer
>>>>>>>>> ip.of.webserver parent 80 0 no-query originserver
>>>>>>>>> name=myAccelcache_peer 192.168.1.5 parent 81 0 no query
>>>>>>>>> originserver
>>>>>>>>> name=myAccel(myAccel I have put a name)and then acl our_sites
>>>>>>>>> dstdomain my.website.org
>>>>>>>>> http_access allow our_sites
>>>>>>>>> cache_peer_access myAccel allow our_sites
>>>>>>>>> cache_peer_access myAccel deny all Anybody with any suggestions
>>>>>>>>> please?Any help would be appreciated thank youRegardsAdam
>>>>>>>>>
>>>>>>>
>>>>>>> Sorry, took me a while to un-mangle that original email text.
>>>>>>>
>>>>>>> You are missing the "vhost" option on https_port 80. All traffic
>>>>>>> Squid
>>>>>>> receives on port 80 will go to Apache's default virtual host.
>>>>>>>
>>>>>>> Amos
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
Received on Sat Mar 27 2010 - 18:54:06 MDT