James,
Thanks so much for the reply.
I recall when I stood up Puppet-Dashboard 1.2 with my earlier Puppet
instance. It was by no means a trivial task! However, I succeeded, and
found it a useful reporting tool. Hence my wish to make it work with my
new Puppet set-up. Howvever, despite following the book's instructions
faithfully (and they appear to be the most complete and explanatory), and
hacking mightily, I'm stuck at the one-yard line, in American football
parlance. The UI presents itself, but there are no data in it. And since,
as you correctly point out, there's not much of a community around
Dashboard, getting troubleshooting help is tough. So, while your post
isn't of direct help, it is appreciated.
Before I give up on it (a thought I really hate, but I have to cut my
losses, at some point), let me mention that if I shut down Apache, and run
Dashboard via the built-in webrick, I get the same results - a data-less
UI. It's useful, however, if only for the fact that the following is
output while webrick is running (hope no one minds this long snippet):
Invalid request: Invalid HTTP format, parsing fails.
/opt/puppet-dashboard/vendor/bundle/ruby/gems/thin-1.6.3/lib/thin/request.rb:84:in
`execute'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/thin-1.6.3/lib/thin/request.rb:84:in
`parse'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/thin-1.6.3/lib/thin/connection.rb:39:in
`receive_data'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/eventmachine-1.0.4/lib/eventmachine.rb:187:in
`run_machine'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/eventmachine-1.0.4/lib/eventmachine.rb:187:in
`run'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/thin-1.6.3/lib/thin/backends/base.rb:73:in
`start'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/thin-1.6.3/lib/thin/server.rb:162:in
`start'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/rack-1.4.5/lib/rack/handler/thin.rb:13:in
`run'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/rack-1.4.5/lib/rack/server.rb:268:in
`start'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/railties-3.2.21/lib/rails/commands/server.rb:70:in
`start'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/railties-3.2.21/lib/rails/commands.rb:55:in
`block in <top (required)>'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/railties-3.2.21/lib/rails/commands.rb:50:in
`tap'
/opt/puppet-dashboard/vendor/bundle/ruby/gems/railties-3.2.21/lib/rails/commands.rb:50:in
`<top (required)>'
script/rails:6:in `require'
script/rails:6:in `<main>'
Invalid HTTP format, eh? I have no idea what that, or the succeeding Ruby
errors, mean. Perhaps someone will look at this, and shed some light?
Here's hoping. In the meantime, I'll start looking at alternatives.
Again, thanks.
On Friday, February 10, 2017 at 3:06:23 PM UTC-5, Dimitri Yioulos wrote:
>
> Hi, All.
>
> Previously, I had a Puppet server running version 3.x, and Puppet
> Dashboard 1.2. Worked a treat. Now, I created a new Puppet server version
> 4. I got that all working fine. I also installed Dashboard 2.0.0. While
> I can see the Dashboard, there are no nodes reported. Has anyone else
> installed Puppet Dashboard 2.0.0 to work with Puppet 4 that might give me
> some help?
>
> Thanks.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/43b21145-36ec-403d-98fa-6fe7b6b98326%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
