It looks like there is a stack trace in your logs. Can you get the full error message?
On Jan 16, 2012 9:39 AM, "Till Brinkmann" < " target="_blank"> > wrote:Re,
ls -la /etc/chef
total 20
drwx------ 2 chef root 4096 Jan 16 13:12 certificates
-rw-r----- 1 root root 2985 Jan 16 13:04 client.rb
lrwxrwxrwx 1 root root 17 Jan 16 13:12 expander.rb -> /etc/chef/solr.rb
-rw------- 1 chef root 927 Jan 16 13:12 server.rb
-rw-r--r-- 1 root root 74 Jan 16 13:05 solo.rb
-rw------- 1 chef root 404 Jan 16 13:12 solr.rb
lrwxrwxrwx 1 root root 19 Jan 16 13:12 webui.rb -> /etc/chef/server.rb
All Ports open nothing blocked
:/etc/chef# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
_________________________________________
@Bryan that could be the issu
012-01-16_14:35:46.19881 /usr/lib/ruby/1.8/rubygems/remote_fetcher.rb:14: uninitialized constant Gem::UserInteraction (NameError)
2012-01-16_14:35:46.20391 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
2012-01-16_14:35:46.20394 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
2012-01-16_14:35:46.20398 from /usr/lib/ruby/1.8/rubygems/spec_fetcher.rb:4
2012-01-16_14:35:46.20400 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
2012-01-16_14:35:46.20403 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
2012-01-16_14:35:46.20405 from /usr/lib/ruby/vendor_ruby/chef/provider/package/rubygems.rb:32
2012-01-16_14:35:46.20409 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
2012-01-16_14:35:46.20411 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
2012-01-16_14:35:46.20414 from /usr/lib/ruby/vendor_ruby/chef/providers.rb:59
2012-01-16_14:35:46.20416 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
2012-01-16_14:35:46.20420 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
2012-01-16_14:35:46.20423 from /usr/lib/ruby/vendor_ruby/chef.rb:25
2012-01-16_14:35:46.20425 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
2012-01-16_14:35:46.20428 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
2012-01-16_14:35:46.20431 from /usr/lib/ruby/gems/1.8/gems/chef-server-api-0.10.8/bin/chef-server:38
2012-01-16_14:35:46.20434 from /usr/bin/chef-server:19:in `load'
2012-01-16_14:35:46.20436 from /usr/bin/chef-server:19
Thanks TillAm 16. Januar 2012 15:35 schrieb Bryan McLellan < " target="_blank"> >:
Those key files should be created in /etc/chef when the servers start up.
Look at the logs created by runit in the in the /etc/ac/SERVICE/log/main/current files as well.
Bryan
On Jan 16, 2012 9:18 AM, "Till Brinkmann" < " target="_blank"> > wrote:Hi chef-list,
after I successful finished the bootstrap installation on debian 6.0.3 I´m trying to configure the command line client.
First step on chef-wiki is to provide the certificates validation.pem and webui.pem from /etc/chef......
I´m searched the hole hard disk without a positive match of validation and web.pem.
I´m not very familiar with runit but searching the web I think server api is up and running.
#>sv s /etc/sv/chef-server
run: /etc/sv/chef-server: (pid 7138) 0s; run: log: (pid 1275) 1702s
.. other chef components
run: /etc/sv/chef-server-webui/: (pid 7155) 1s; run: log: (pid 1281) 1707s
run: /etc/sv/chef-expander/: (pid 1280) 1710s; run: log: (pid 1279) 1710s
run: /etc/sv/chef-solr/: (pid 1278) 1713s; run: log: (pid 1277) 1713s
Q: Why does server-api does not create validation.pem and webui.pem ?
May corresponding to that I´m not sure but does after the installation of chef the system have to provide open ports for webaccess ?
Nmap scan from admin workstation to chef server
____________________________________________________
nmap 10.111.91.119
Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2012-01-16 15:13 CET
Nmap scan report for 10.111.91.119
Host is up (0.0017s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind
Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
____________________________________________________
Thanks for helping me to understand chef :-/
Till
Archive powered by MHonArc 2.6.16.