Thanks again for the links, they helped get me (initially) past the
certificate issues.
I'm trying to start the webui and, although it seems to start correctly, I
cannot seem to log in when presented with a login form. My chef-server is
on port 4020 and the webui is on port 4050.
Which step is responsible for populating the database with the initial
admin user?
Mark
Some of the log:
[Thu, 15 Mar 2012 00:45:53 +0000] DEBUG: Sending HTTP Request via GET to
localhost:5984/chef/_design/users/_view/all_id
[Thu, 15 Mar 2012 00:45:53 +0000] DEBUG: Sending HTTP Request via GET to
localhost:5984/chef/_design/id_map/_view/name_to_id
Logging to file at /var/log/chef/server-webui-qa.log
[Thu, 15 Mar 2012 00:46:24 +0000] DEBUG: Signing the request as
chef-webui-qa
[Thu, 15 Mar 2012 00:46:24 +0000] DEBUG: Sending HTTP Request via GET to
localhost:4020/environments
[Thu, 15 Mar 2012 00:46:25 +0000] DEBUG: Signing the request as
chef-webui-qa
[Thu, 15 Mar 2012 00:46:25 +0000] DEBUG: Sending HTTP Request via GET to
localhost:4020/environments
[Thu, 15 Mar 2012 00:46:36 +0000] DEBUG: Signing the request as
chef-webui-qa
[Thu, 15 Mar 2012 00:46:36 +0000] DEBUG: Sending HTTP Request via GET to
localhost:4020/environments
[Thu, 15 Mar 2012 00:46:37 +0000] DEBUG: Signing the request as
chef-webui-qa
[Thu, 15 Mar 2012 00:46:37 +0000] DEBUG: Sending HTTP Request via GET to
localhost:4020/users/a
[Thu, 15 Mar 2012 00:46:37 +0000] INFO: HTTP Request Returned 404 Not
Found: Cannot load user a
[Thu, 15 Mar 2012 00:46:37 +0000] ERROR: 404 "Not Found"
From server-webui-qa.log:
merb : chef-server-webui : worker (port 4050) ~ Started request handling:
Thu Mar 15 00:46:36 +0000 2012
merb : chef-server-webui : worker (port 4050) ~ Routed to:
{"action"=>"login_exec", "form_submit"=>"login", "name"=>"a",
"password"=>"[FILTERED]",
"controller"=>"users"}
merb : chef-server-webui : worker (port 4050) ~ Params:
{"action"=>"login_exec", "form_submit"=>"login", "name"=>"a",
"password"=>"[FILTERED]", "co
ntroller"=>"users"}
merb : chef-server-webui : worker (port 4050) ~ {:dispatch_time=>0.115816,
:action_time=>0.114778, :after_filters_time=>2.8e-05, :before_filters_ti
me=>0.077609}
merb : chef-server-webui : worker (port 4050) ~
On Wed, Mar 14, 2012 at 4:13 PM, Bryan McLellan btm@loftninjas.org wrote:
On Wed, Mar 14, 2012 at 3:54 PM, mark bradley gopearls42@gmail.com
wrote:
Well, it -was- going pretty well; I got one server up and running from a
repository and, while getting the second one going, I'm running into
certificate issues. Which highlights to me that I don't know enough about
how certificates are generated and consumed in the Chef architecture. Are
there any good pointers to documentation on this?
What kind of certificates? They're used for client authentication,
which is briefly described here:
http://wiki.opscode.com/display/chef/API+Clients
Make sure you set the path to the validation_key to a different value
for each server. This is the special client that can be used to
automate creating new clients. If the file specified by validation_key
does not exist it is recreated, but keep in mind that client keys are
actually stored internally in the database. This file on the server is
mostly a convenient way for you to get a couple of the validation
clients key. See
http://wiki.opscode.com/display/chef/Chef+Configuration+Settings#ChefConfigurationSettings-certificatesettings
Bryan