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

[Infor Mation < >]

Quoting Daniel DeLeo 
<
 >:

> 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.

this taught me that chef.couch was what i needed to blow away.

So I reupgraded couchdb to 1.1.1 and let chef-server run the  
initialization of the database.

I got different results than I've ever gotten (because chef is smart  
enough to initialize a db if one doesn't exist, that's cool) but, it  
proceeded to get a compilation_error on  
localhost:5984/chef/_design/id_map/_view/name_to_id again

...and again...

# 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], doc._id);\\n                 
}\\n\")))"}


> Off the top of my head, the only environmental bit that seems like  
> it could bite is if you have crazy encoding/locale settings.
The output from locale seems pretty normal:

mamabear:~# locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=


> > any help would be appreciated, tia.
> > -m
>
>
>
> --
> Dan DeLeo
Square one again. It was a good clue tho, thanks.
-m