additionally a lot of this in /var/log/trafficserver/error.log 20130809.10h32m19s RESPONSE: sent 127.0.0.1 status 502 (Cannot find server.) for 'http://127.0.0.1:8083/synthetic.txt' 20130809.10h32m39s RESPONSE: sent 127.0.0.1 status 502 (Cannot find server.) for 'http://127.0.0.1:8083/synthetic.txt' 20130809.10h32m59s RESPONSE: sent 127.0.0.1 status 502 (Cannot find server.) for 'http://127.0.0.1:8083/synthetic.txt' 20130809.10h33m19s RESPONSE: sent 127.0.0.1 status 502 (Cannot find server.) for 'http://127.0.0.1:8083/synthetic.txt' 20130809.10h33m39s RESPONSE: sent 127.0.0.1 status 502 (Cannot find server.) for 'http://127.0.0.1:8083/synthetic.txt' 20130809.10h33m59s RESPONSE: sent 127.0.0.1 status 502 (Cannot find server.) for 'http://127.0.0.1:8083/synthetic.txt'
Am 09.08.2013 09:39, schrieb Reindl Harald: > Hmm > > these is something completly broken with DNS > > my whole infrastructure is built the way that "remap.conf" and > "/etc/hosts.dnsmasq" is auto-generated by webservices and this > way the outside DNS record decides if requests of whatever > domain are going through the load balancer or directly to > a origin server in case of small sites > > map http://rhsoft.testserver.rhsoft.net http://rhsoft.testserver.rhsoft.net > reverse_map http://rhsoft.testserver.rhsoft.net > http://rhsoft.testserver.rhsoft.net > __________________________________________________________________ > > "Unknown Host" Unable to locate the server named > "rhsoft.testserver.rhsoft.net" > The server does not have a DNS entry > > [root@testserver:~]$ cat /etc/trafficserver/records.config | grep -i dns > CONFIG proxy.config.http.no_dns_just_forward_to_parent INT 0 > CONFIG proxy.config.dns.search_default_domains INT 1 > CONFIG proxy.config.dns.splitDNS.enabled INT 0 > CONFIG proxy.config.dns.max_dns_in_flight INT 2048 > CONFIG proxy.config.dns.url_expansions STRING NULL > CONFIG proxy.config.dns.round_robin_nameservers INT 0 > CONFIG proxy.config.dns.nameservers STRING 127.0.0.1 > CONFIG proxy.config.dns.resolv_conf STRING NULL > CONFIG proxy.config.dns.validate_query_name INT 0 > CONFIG proxy.config.diags.debug.tags STRING http.*|dns.* > > [root@testserver:~]$ nslookup rhsoft.testserver.rhsoft.net 127.0.0.1 > Server: 127.0.0.1 > Address: 127.0.0.1#53 > > Name: rhsoft.testserver.rhsoft.net > Address: 127.0.0.1 > __________________________________________________________________ > > BTW: > could someone please have a look why TS still consumes a lot of CPU in idle > state? > 8% of a Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz inside a VMware guest and > caused by that 30% for the vmware-vmx process on the host is really bad > > usually idle virtual machines have 0% CPU load > > Am 07.08.2013 19:22, schrieb Leif Hedstrom: >> Hi all, >> >> I've prepared a release for v3.3.4, which resolved a large number of bugs >> since v3.3.4. Please see the CHANGES file for more details: >> >> https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;a=blob_plain;f=CHANGES;hb=3.3.x >> >> >> Assuming no show-stopper bugs are found in this release, v3.3.5 is also >> going to be the base for our next stable release, v3.4.0. Hence, everyone >> should test this release as much as possible. >> >> The artifacts are available at >> http://people.apache.org/~zwoop/rel-candidates/: >> >> -rw-r--r-- 1 zwoop zwoop 6076077 Aug 7 16:49 >> trafficserver-3.3.5-dev.tar.bz2 >> -rw-r--r-- 1 zwoop zwoop 836 Aug 7 16:49 >> trafficserver-3.3.5-dev.tar.bz2.asc >> -rw-r--r-- 1 zwoop zwoop 66 Aug 7 16:49 >> trafficserver-3.3.5-dev.tar.bz2.md5 >> -rw-r--r-- 1 zwoop zwoop 74 Aug 7 16:49 >> trafficserver-3.3.5-dev.tar.bz2.sha1 >> >> MD5: e2ee980906c23ceca292a884b3c37c16 >> SHA1: 3b284572368cddda01ec02ac267cefff3a11b71a >> >> >> The vote is open until Monday August 12th, but please don't lolligag. We are >> over 2 months behind schedule, and we need to make a v3.4.0 release. Please >> test and vote, on as many systems and configurations as possible. >> >> Cheers, >> >> -- leif
signature.asc
Description: OpenPGP digital signature
