[chef] Re: Re: Re: Re: Re: Re: Chef::Exceptions::Conte ntLengthMism atch ‏


Chronological Thread 
  • From: Greg Barker < >
  • To: " " < >
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Chef::Exceptions::Conte ntLengthMism atch ‏
  • Date: Wed, 28 Jan 2015 11:30:19 -0800

Just wanted to tie up this one on the mailing list: it was a permissions issue on the /opt/nginx-1.6.2/proxy_temp directory:

2015/01/28 18:42:02 [crit] 1005#0: *21 open() "/opt/nginx-1.6.2/proxy_temp/0/01/0000000010" failed
 (13: Permission denied) while reading upstream, client: 127.0.1.1, server: jenkins, request: "GET
 //jnlpJars/jenkins-cli.jar HTTP/1.1", upstream: "http://127.0.0.1:8080//jnlpJars/jenkins-cli.jar"
, host: "jenkins.mycorp.com", referrer: "rsbose"

Thanks for the help!

On Tue, Jan 27, 2015 at 7:02 PM, Greg Barker < " target="_blank"> > wrote:
Running into this one again. I was able to reproduce the issue on a local VM (corporate network) as well as on an EC2 instance. I tried using curl to download the file and it seemed to work just fine. Tried another test with Chef::HTTP::Simple and that also seemed to work fine.

I filed a bug here: https://github.com/opscode-cookbooks/jenkins/issues/322

Not sure if that's the appropriate place for the bug though.

Any ideas on why I keep hitting this?

Thanks!
Greg

On Wed, Oct 8, 2014 at 11:09 AM, Greg Barker < " target="_blank"> > wrote:
I ran into the same issue, I think it was for something on download.jetbrains.com. The download worked fine when I tried it locally on my machine. I'm also running chef-client 11.16.2. I fixed it by mirroring all external files on my own S3 bucket and I haven't run into the issue since.

On Wed, Oct 8, 2014 at 10:05 AM, Lamont Granquist < " target="_blank"> > wrote:
On Wed Oct  8 02:37:45 2014, " target="_blank"> wrote:

Hi Lamont,

I'm new to chef can you help me where i need to change configuration to fix
this issue.

Thanks in advance :)

I'm not sure where there's a configuration to change.  It downloads from that URL fine for me, and it looks like there was an individual request that got truncated somehow.  If you repeat it and its reliably failing for you there, then you've got a networking issue on your end -- something like a proxy server that only allows 4MB downloads or something else that would have that same effect.  It doesn't look like a Chef issue, it looks like the code we put there is working correctly and raising an exception about an external problem.






Archive powered by MHonArc 2.6.16.

§