[chef] Re: Re: Re: chef-server(-api) not starting on starting after fresh install [CHEF-2827]

[Daniel DeLeo < >]

On Thursday, December 22, 2011 at 1:13 AM, Infor Mation wrote:

> Quoting Daniel DeLeo 
> <
 
>  
> (mailto:
 )>:
> 
> > 
> > 
> > On Wednesday, December 21, 2011 at 5:08 PM, Infor Mation wrote:
> > 
> > > Hi,
> > > 
> > > I've been trying to learn chef for two days now, and can't get it to 
> > > run.
> > > 
> > > I'm installing chef on Debain (Wheezy/sid) on bare iron, and from the
> > > repositories opscodes provides. (I'm a package manager junkie, shoot me)
> > > 
> > > I'm using the world's most generic x86_64 hardware.
> > > 
> > > chef-server will.not.start.
> > > # curl
> > > http://localhost:5984/chef/_design/id_map/_view/name_to_id?include_docs=true\&amp;key=[%22client%22,%22chef-validator%22]
> > > {"error":"compilation_error","reason":"Expression does not eval to a
> > > function. ((new String(\" function(doc) {\\n
> > > emit([ doc.chef_type, doc.name (http://doc.name)], doc._id);\\n
> > > }\\n\")))"}
> > 
> > 
> > 
> > 
> > CouchDB is for some reason choking on the javascript views that the 
> > chef-server creates. What version of CouchDB is this?
> 
> 
> 1.1.1
> 
> this got me to thinking.. so I downgraded to the only other version 
> according to apt-cache show, which was 0.11.0-2.3
> 
> i had different results, it seemed to crash in the same place upon 
> creation of the chef.couch database, but failed because of a 
> depreciated gem or call.. "Gem.activate", I believe.

I think you're on the right track, and there is probably a bug either on our 
end or CouchDB's end with 1.1.1.

As for the Gem.activate error, I _believe_ it's a packaging bug. We've 
delayed upgrading Merb to keep everything compatible with the versions of 
libraries in the Ubuntu/Debian releases we were targeting, and now the world 
has moved on. Downgrading rubygems may be an effective workaround until we 
can figure it out.
> The output from locale seems pretty normal:

Yeah, I was wondering if there were encoding shenanigans causing newlines to 
get mangled and make the js code invalid, but it's probably a CouchDB version 
thing.
 
> 
> Square one again. It was a good clue tho, thanks.
Actually, you were getting warmer. 
> -m



-- 
Dan DeLeo