On Friday, October 26, 2012 at 5:01 PM, wrote:
hi. this is wierd. today i brought a few ec2 clients out of a stoppedstate and attempted to put them thru their chef-client run, as usual.suddenly they are trying to access a URI on the chef server that doesn'texist: /en-US/* .. thus they're failing with 404.all my other nodes use this same chef server, same chef-client version(chef-full-0.10.10-1, CentOS 5.8), and are not exhibiting this behaviorcurrently.here's a bit of log from one of the failing clients. you can see the last timechef ran back in August, it was accessing the correct URI. upon its first runtoday, it tried the right URI, then suddenly, inexplicably tried prependingthat URI with "/en-US".10/26 23: chef]# grep "via GET to chef.prod.gogiants.com" /var/log/chef/client.log | tail -6[Wed, 08 Aug 2012 20:25:18 +0000] DEBUG: Sending HTTP Request via GET to chef.prod.gogiants.com:443/data/secrets/creds-prod[Wed, 08 Aug 2012 20:25:18 +0000] DEBUG: Sending HTTP Request via GET to chef.prod.gogiants.com:443/data/yum/yum-tasks[Fri, 26 Oct 2012 23:31:46 +0000] DEBUG: Sending HTTP Request via GET to chef.prod.gogiants.com:443/nodes/test-mobile.prod.gogiants.com[Fri, 26 Oct 2012 23:31:46 +0000] DEBUG: Sending HTTP Request via GET to chef.prod.gogiants.com:443/en-US/nodes/test-mobile.prod.gogiants.com[Fri, 26 Oct 2012 23:31:48 +0000] DEBUG: Sending HTTP Request via GET to chef.prod.gogiants.com:443/en-US/nodes[Fri, 26 Oct 2012 23:35:12 +0000] DEBUG: Sending HTTP Request via GET to chef.prod.gogiants.com:443/en-US/clientsdoes anyone know what's going on here? what to look for?more complete log output is in a gist:thanks!kallen
Archive powered by MHonArc 2.6.16.