similar to: change puppet dashboard listen interfac

I''m currently running a dashboard as a separate process and have a proxy in apache with authentication to access as http://puppet.ourhost.com/dashboard/ I have to start the dashboard with "-P /dashboard" option to make it work. I''m wondering how to achieve this with passenger. The config I found in ext/passanger seems to run the dashboard under the root of the virtual

Hello, I''m trying to get puppet-dashboard installed on a CentOS 6.3 machine running puppet v3.0.1. I''m following the puppet-dashboard documentation here: http://docs.puppetlabs.com/dashboard/manual/1.2/configuring.html In the documentation page linked above, it says: Puppet uses SSL certificates to control who can make requests to the puppet > master, so Dashboard has

Hey All, I see that a number of Admins have experienced this same issue, but no one has posted a workable solution. I have about 200 agents, but on any given day I''ll see 5-10 failed tasks in Dashboard as follows: *Importing report report-21248-180.yaml* at 10-18-2013 11:10 EDTValidation failed: Host already has a report for time and kind Backtrace

This is a maintenance release of Puppet Dashboard. This release resolves issues #7405, #9101, #8878, and #8803. More details below. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

I get this error can''t activate rack (~> 1.0.1), already activated rack-1.2.2 It appears that puppet-dashboard uses rack 1.0.1 but passenger 3.0.7 needs to use rack1.2.2 Is there a way around this or make dashboard use rack 1.2.2? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hello I have just installed puppet dashboard from git. everything seems to load ok except it seems as though background tasks are not being run. According to the code README: running: # env CPUS=4 RAILS_ENV=production /.../script/delayed_job -p dashboard -n $CPUS -m start will start the worker. however it seems as though it is not running (or if it is how can I check?) and the back ground

Puppet Dashboard 1.2.15 is a bugfix release of the 1.2 series of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.15.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com Please report feedback via the Puppet Labs Redmine site, using an affected

Hello Everyone, I am new to puppet and want to set puppet dashboard. I don''t have a database for puppet dashboard, My question is that can i use PuppetDB as database for puppet dashboard ?? If yes then please tell me how to configure it. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and

Hi All, I have somehow managed to configure the puppet dashboard, but it is not displaying the nodes and the classes in the dashboard. It is completely empty. Any one has any idea of configuring puppet dashboard so that it displays all the nodes, classes, and reports/ I am newbie so please explain in a little brief. Regards Niraj K. -- You received this message because you are subscribed

Puppet Dashboard 1.2.23-rc3 is a maintenance release candidate of the 1.2 series of Puppet Dashboard with bug fixes and minor features. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23-rc3.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For

This release of Puppet Dashboard addresses CVE-2013-0277 and CVE-2013-0269. These are vulnerabilities that affect Ruby on Rails, specifically around YAML serialization and JSON handling. They expose vulnerable systems to SQL Injection, Denial of Service Attacks, and arbitrary YAML deserialization. Additionally, CVE-2013-0276 and CVE-2013-0263 affect vendored components of Puppet Dashboard, but by

Dear All, I already deploy puppet-dashboard with passanger. i''m want to try puppet-dasboard work in like myserver.com/puppet-report using apache proxy reverse, but still getting work, its just show the index then when i try to click some link like nodes, its will be goto myserver.com/nodes, not to myserver.com/puppet-report/nodes its just work if i try to reverse to myserver.com.

This is a maintenance release of Puppet Dashboard. This release resolves issues #10198, #10270, and #10543. More details below. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Hi, Iam a newbie to puppet, iam trying to set my local puppet master and dashboard running on same server. Iam also using https to connect to dashboard. I can launch the dashboard on https://IP fine but i see only one report on the webpage, When i tried to import all the previous reports iam getting this error # cd /usr/share/puppet-dashboard/ ]# sudo -u puppet-dashboard rake

I''m having all sorts of trouble getting our new puppet-dashboard install to connect/get the facts/inventory from the puppet master. These are separate boxes, and I''m getting (testing): root@puppetdash puppet-dashboard]# curl -k -H "Accept: yaml" https://puppet:8140/production/facts/hero0304.rc.fas.harvard.edu Forbidden request:

Hi guys, I have a strange situation. I''ve got 1 dashboard MySQL DB accessed from 3 different dashboard hosts. Strangely enough, 2 of them show the right node statuses, and the third one just shows all nodes as unresponsive. As far as I know, the status comes from the "nodes" table in the DB, so how can this happen? Is there some cache I need to clear? Is there another

I''m trying to setup dashboard as a node classifier w/puppet 2.6.14. Not sure why this is not working... In puppet.conf on the master I have: node_terminus = exec external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http:// localhost /usr/share/puppet-dashboard/bin/external_node The agent''s return: err: Could not retrieve catalog from remote server: Error 400 on SERVER:

Hi, I''ve installed Dashboard on my server and I aim to remotely request the MySQL Database. All documentations read explain the way to roll out using Dashboard and MySQL Database on the same server. I am looking for any information to achieve that because I haven''t found any from the time being and I wonder if it''s just possible. Thanks you, David -- You received

Hi： When I start the dashboard server，but all ways failed . Someone can help me ? #sudo -u puppet-dashboard ./script/server -e production Missing these required gems: rack >= 0 You''re running: ruby 1.8.7.174 at /usr/bin/ruby1.8 rubygems 1.8.24 at /usr/lib/ruby/gems/1.8, /root/.gem/ruby/1.8 Run `rake gems:install` to

Excuse me When I add node from the dashboard is there any possibility to push puppet-agent to the client ?? Thank you in advance!!! Francesco -- 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