- From: Dikang Gu <
>
- To:
- Subject: [chef] Re: Re: Re: 500 "Internal Server Error" (Net::HTTPFatalError) when running chef client.
- Date: Wed, 16 Dec 2009 00:46:11 +0800
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=YvMug3fP8qru/I+qYKwR14Zye9/HhCnwTjzww+//HwK2pKwcqaHRXgt2cidahw75YY ql1Yn3ur2LX9fL7Sjv97r9aRqUnwSGNyqCWAEU8b0CkeH4RG58yeZ1IXgfMF+OiY01lR e7+YR8zj+1M2NOkiX2JnLHHgregwq9boq45gM=
Just as said in the wiki:
http://wiki.opscode.com/display/chef/FAQ+-+When+Trouble+StrikesThe chef server does not know how to deal with the _provider_files and _resource_files, so I manually comment the sync_provider_files and sync_resource_files functions, then the client seems to work well.
Is this a bug for 0.7.14?
Dikang
On Tue, Dec 15, 2009 at 11:32 PM, Dikang Gu
<
">
> wrote:
on the chef server:
:~# apt-cache policy chef-server
chef-server:
Installed: 0.7.14-2
Candidate: 0.7.14-2
Version table:
*** 0.7.14-2 0
500 http://apt.opscode.com jaunty/universe Packages
100 /var/lib/dpkg/status
on the chef client:
:~$ apt-cache policy chef
chef:
Installed: 0.7.14-2
Candidate: 0.7.14-2
Version table:
*** 0.7.14-2 0
500 http://apt.opscode.com jaunty/universe Packages
100 /var/lib/dpkg/status
So, the chef-server and chef-client should have the same version, 0.7.14, right?
Dikang
On Tue, Dec 15, 2009 at 10:57 PM, Bryan McLellan
<
" target="_blank">
> wrote:
On Tue, Dec 15, 2009 at 6:29 AM, Dikang Gu <
" target="_blank">
> wrote:
> I do the apt upgrade on both chef server and client. I think at least
> the sever is 7.14
Run: apt-cache policy chef-server
Archive powered by MHonArc 2.6.16.