[squid-users] using monitorurl with originservers

From: Benno Blumenthal <benno@dont-contact.us>
Date: Wed, 03 Jan 2007 16:06:28 -0500

Hello,

I am using squid 2.6r3
I would like to use monitorurl to have a reverse-proxy squid monitor my
originservers a bit more precisely than not-down means perfectly OK.
But I am not doing too well in the details.

Looking at one example line in particular:

cache_peer libby.ldeo.columbia.edu parent 8180 3130 no-query no-digest
originserver monitorurl=/sesame name=sesame_exp round-robin

This results in requests being passed to the server unless it is
actually down. I don't think the monitorurl is used.

cache_peer libby.ldeo.columbia.edu parent 8180 3130 no-query no-digest
originserver monitorsize=100-200 monitorinterval=30
monitorurl=/sesame/servlets/evaluateGraphQuery?repository=dl-rdfs&serialization=ntriples&queryLanguage=SeRQL&query=CONSTRUCT+*%0D%0AFROM%0D%0A%7Brdfcache%3ARDFCache%7D+rdfcache%3Aupload_complete+%7B%22true%22%5E%5E%3Chttp%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema%23boolean%3E%7D%0D%0AUSING+NAM\
ESPACE%0D%0A+rdfcache+%3D+%3Chttp%3A%2F%2Firidl.ldeo.columbia.edu%2Fontologies%2Frdfcache.owl%23%3E
name=sesame_exp round-robin

results in the cache being marked down immediately, despite that query
returning a 192 character response when used manually

cache_peer libby.ldeo.columbia.edu parent 8180 3130 no-query no-digest
originserver monitorsize=100-200
monitorurl=/sesame/servlets/evaluateGraphQuery?repository=dl-rdfs&serialization=ntriples&queryLanguage=SeRQL&query=CONSTRUCT+*%0D%0AFROM%0D%0A%7Brdfcache%3ARDFCache%7D+rdfcache%3Aupload_complete+%7B%22true%22%5E%5E%3Chttp%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema%23boolean%3E%7D%0D%0AUSING+NAMESPACE%0D%0A+rdfcach\
e+%3D+%3Chttp%3A%2F%2Firidl.ldeo.columbia.edu%2Fontologies%2Frdfcache.owl%23%3E
name=sesame_exp round-robin

results in requests being passed to the server unless actually down. I
don't think the monitorurl is used.

So,

1) default value of monitorinterval seems to be off rather than 300.
A bit confusing given what the squid.conf file says, or I have it wrong
somehow.

2) what is the monitoringurl for the originserver supposed to look like?

I am getting in the cache_log

peerMonitor sesame_exp: Failed, status != 200 (400)

So I take squid does not like the url, but why? If I simplify the url
to /sesame, it works. So do I need to escape more stuff, or is it
annoyed at something else (like the length)?

Thanks,

Benno
Received on Wed Jan 03 2007 - 14:06:35 MST

This archive was generated by hypermail pre-2.1.9 : Thu Feb 01 2007 - 12:00:00 MST