[chef] Re: Re: Re: RE: Chef WebUI doesn´t work

[Eduardo Dias < >]

Thanks all,

Eduardo

2013/11/12 George Miranda < " target="_blank"> >

Eduardo,

Any existing nodes already managed by Chef have their own private client key for authenticating API requests.  The validator is only needed by new nodes which aren't yet controlled by Chef.  So hopefully you shouldn't need to redistribute the validator to too many nodes.

-George

On Tue, Nov 12, 2013 at 8:39 AM, Eduardo Dias < " target="_blank"> > wrote:

Hi Nico,

thanks.

I have recreated the chef-webui client and it works now, I am with a problem to restore the chef-validator keys to avoid to redistribute it for all systems that I have.

Regards.

Eduardo

2013/11/12 Kadel-Garcia, Nico < " target="_blank"> >

Like any other web based service, start from the top.

       What version of chef are you running?
       What''s the base operating system?
       How did you install it? (RPM package from Opscode, gem instlalation, or what?)
       Since chef by default runs as a web service on port 443, do you have another web server running?
       Are your chef clients still working?   

---

From: Eduardo Dias [ " target="_blank"> ]
Sent: Tuesday, November 12, 2013 4:42 AM
To: " target="_blank">
Subject: [chef] Chef WebUI doesn´t work

Hi Chefs,

the WEBUI of my Chef server is not working, showing the error "We're sorry, but something went wrong.", the commands knife works. What I can see is that the clients "chef-validator & chef-webui" are not there.

How can I recover it?

Regards,

Eduardo

--

Atenciosamente,

Eduardo

--

George Miranda
Consultant, Evangelist, Trainer, *:* | Opscode Inc.

" target="_blank"> | (512) 481-2876

Twitter, IRC, GitHub, Most IMs: gmiranda23

--

Atenciosamente,

Eduardo