Puppet users - Mar 2013 - PuppetDB: Upgraded to 1.1.1, Dashboard empty

I''m running PuppetDB installed from yum on CentOS 6, with a Postgres 
backend. After upgrading from 1.0.5 to 1.1.1, my dashboard 
(http://puppetdb/dashboard/index.html) is full of question marks with empty 
graphs, and the top right displays "PuppetDB (unknown version)". Other
than
that the upgrade was fine, and I didn''t see any other errors in nodes 
applying their catalogs, so I didn''t pay it much attention.
It''s bugging
me, though, as it''d be nice to see some stats and at least know 
everything''s healthy. Any insights?

On a related note, I''d like to run Nagios checks against PuppetDB, but
what
should I be checking? Is there a Puppet Face for querying PuppetDB''s
status?

-- 
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

It sounds like the dashboard Javascript can''t access the HTTP
end-points which is strange. The way it works is that it hits a series
of REST end-points on the web server.

As the dashboard is updated using background Javascript, it can still
keep trying to access backend data even though the web server is down
or not accessible. Are you sure the web-server is still listening
publicly on port 8080 still?

What does your jetty.ini look like?

What do you see in your puppetdb.log when you try to hit the dashboard?

In your browser if you enable the javascript console - do you get any
errors that might be helpful?

ken.

On Tue, Mar 5, 2013 at 8:31 AM, Stephen Price <steeef@gmail.com>
wrote:
> I''m running PuppetDB installed from yum on CentOS 6, with a
Postgres
> backend. After upgrading from 1.0.5 to 1.1.1, my dashboard
> (http://puppetdb/dashboard/index.html) is full of question marks with empty
> graphs, and the top right displays "PuppetDB (unknown version)".
Other than
> that the upgrade was fine, and I didn''t see any other errors in
nodes
> applying their catalogs, so I didn''t pay it much attention.
It''s bugging me,
> though, as it''d be nice to see some stats and at least know
everything''s
> healthy. Any insights?
>
> On a related note, I''d like to run Nagios checks against PuppetDB,
but what
> should I be checking? Is there a Puppet Face for querying
PuppetDB''s status?
>
> --
> 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+unsubscribe@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
-- 
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Sorry, I should have done some more digging. I''m using nginx as the
front
end, and I had specific location rules to forbid invalid requests. I 
allowed GET on this location:
location ~ ^/(facts|resources|dashboard|nodes|status|metrics|version)
I should have read the 1.1 release notes more closely. It''s now:
location ~ 
^/(v2\/)?(facts|resources|dashboard|nodes|status|metrics|version|experimental)

Not sure if it''s necessary to have the (v2/) optional, but I''d
rather keep
it backwards-compatible for now. As soon as I made that change, the 
dashboard started working just fine. Thanks for the tips!

On Tuesday, March 5, 2013 10:44:48 AM UTC-8, Ken Barber
wrote:
>
> It sounds like the dashboard Javascript can''t access the HTTP 
> end-points which is strange. The way it works is that it hits a series 
> of REST end-points on the web server. 
>
> As the dashboard is updated using background Javascript, it can still 
> keep trying to access backend data even though the web server is down 
> or not accessible. Are you sure the web-server is still listening 
> publicly on port 8080 still? 
>
> What does your jetty.ini look like? 
>
> What do you see in your puppetdb.log when you try to hit the dashboard? 
>
> In your browser if you enable the javascript console - do you get any 
> errors that might be helpful? 
>
> ken. 
>
> On Tue, Mar 5, 2013 at 8:31 AM, Stephen Price
<ste...@gmail.com<javascript:>>
> wrote: 
> > I''m running PuppetDB installed from yum on CentOS 6, with a
Postgres
> > backend. After upgrading from 1.0.5 to 1.1.1, my dashboard 
> > (http://puppetdb/dashboard/index.html) is full of question marks with 
> empty 
> > graphs, and the top right displays "PuppetDB (unknown
version)". Other
> than 
> > that the upgrade was fine, and I didn''t see any other errors
in nodes
> > applying their catalogs, so I didn''t pay it much attention.
It''s bugging
> me, 
> > though, as it''d be nice to see some stats and at least know
everything''s
> > healthy. Any insights? 
> > 
> > On a related note, I''d like to run Nagios checks against
PuppetDB, but
> what 
> > should I be checking? Is there a Puppet Face for querying
PuppetDB''s
> status? 
> > 
> > -- 
> > 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...@googlegroups.com <javascript:>. 
> > To post to this group, send email to
puppet...@googlegroups.com<javascript:>.
>
> > Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> > For more options, visit https://groups.google.com/groups/opt_out. 
> > 
> > 
>
-- 
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.