Re: [Puppet Users] Centralised source repository for Puppetforge
On Wed, Nov 17, 2010 at 8:30 AM, lisa th3...@googlemail.com wrote: Is there a centralized git (or other SCM) repository for user- contributed Puppet modules? That is, does Puppetlabs operate a repository on github or elsewhere so that users can be granted commit access for specific modules which they contribute? No, but the Forge encourages module authors to specify the source code repository containing their module's source code. This gives module authors complete control over which SCM, hosting service and collaboration model they choose for producing their modules. E.g., if you specify a github repo for your module, others can easily fork it, and submit patches to you using github's pull request system. Is this sufficient for your needs? -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet-dashboard does not show last 30 puppet runs.
On Tue, Nov 9, 2010 at 6:36 AM, Jeremy Carroll phobos...@gmail.com wrote: The list is totally blank. I see no errors in production.log. Does anybody know of a way I can troubleshoot this problem? Here is a screenshot of the issue. http://imgur.com/Lt2fn.png Thanks! This undesirable behavior is happening because Puppet Dashboard doesn't fully support Puppet 2.6 reports. It can accept the new reports just fine, but doesn't know how to extract much of their data and you get screens like the one you posted. Work is currently underway to address this in Bug #4514 Puppet 2.6 reports should be fully supported -- http://projects.puppetlabs.com/issues/4514 -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: No report named 'puppet_dashboard'
On Wed, Nov 3, 2010 at 9:04 AM, theirpuppet theirpup...@gmail.com wrote: I'm unable to integrate puppet dashboard as I keep getting the following error: No report named 'puppet_dashboard' [...] I even tried moving the symlink for puppet_dashboard.rb from /var/lib/ puppet/reports to /var/lib/puppet/lib; no change. If you `cat` the symlinked file as the `puppet` user, can you see its contents to confirm that your symlink and permissions are correct? Are you sure that you're putting the file into the right directory? For me, the directory is `/var/lib/puppet/lib/puppet/reports/`. The Live report aggregation section of the Puppet Dashboard README describes how to identify the right directory and put the file there: http://github.com/puppetlabs/puppet-dashboard/blob/master/README.markdown If you're using pluginsync, you may want to look at this ticket for a workaround: http://projects.puppetlabs.com/issues/4345 -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: ANNOUNCE: Puppet Dashboard 1.0.4 released!
Andreas, This error message indicates that the Puppet Dashboard won't start because your application version is older than your database schema. Specifically, your Puppet Dashboard code is expecting the schema shipped with v1.0.3 (schema 20100726070117), but your actual database schema is the one used by v1.0.4rc2 and v1.0.4 (schema 20100916183948). I strongly suspect that you have two different copies of the Puppet Dashboard installed: the v1.0.4 that you ran `rake db:migrate` against, and the v1.0.3 that Apache is configured to use. Please check the paths your webserver is using to ensure that they point to the expected version by checking the VERSION file in the Puppet Dashboard directory. At the very least, you should be able to go into the Puppet Dashboard directory, confirm that it's v1.0.4, and then run `./script/server -e production` to get it running again until you figure out what's going on with your webserver. -igal On Wed, Oct 20, 2010 at 4:42 AM, Andreas Paul a.p...@enbw.com wrote: I get the following error: Database isn't the current migration version: expected 20100726070117, got 20100916183948 You must either run 'rake db:migrate' or set environmental variable NO_MIGRATION_CHECK I upgraded from 1.0.4rc2 and did run 'rake RAILS_ENV=production db:migrate' before restarting apache. On Oct 20, 1:59 am, James Turnbull ja...@puppetlabs.com wrote: We're pleased to announce the availability of Puppet Dashboard 1.0.4! This is a maintenance release, it fixes a number of bugs, improves the user interface, significantly boosts performance and includes better RPM and DEB packages. The source code of 1.0.4 is identical to 1.0.4rc2. Please upgrade to this stable release and let us know about any issues on the mailing list (http://groups.google.com/group/puppet-users/), or in the ticket tracker with an Affected Version of 1.0.4 (http://projects.puppetlabs.com/projects/dashboard/). If you're interested in what we're hoping to work on next, please see our roadmap (http://projects.puppetlabs.com/projects/dashboard/roadmap/). We would also appreciate it if you watched and commented on those tickets that are important to you. INSTALLING AND UPGRADING: New installation and upgrading instructions are available in the included README, which you can also read online at: http://github.com/puppetlabs/puppet-dashboard/blob/v1.0.4/README.mark... IMPORTANT: This release involves database migrations. Please see the README.markdown for instructions on applying them. USING RPM AND DEB PACKAGES: Install an the software using packages, which will put the files into your /usr/share/puppet-dashboard directory: Install the RPM package for CentOS or RHEL 5.5 by running: sudo sh -c rpm -Uvhhttp://yum.puppetlabs.com/base/puppetlabs-repo-3.0-2.noarch.rpm;\ rpm -Uvhhttp://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.no... \ yum install puppet-dashboard Or install the DEB package for Ubuntu 10.04: 1. Put the following in your /etc/apt/sources.list.d/puppet-labs.list file: debhttp://apt.puppetlabs.com/ubuntulucid main deb-srchttp://apt.puppetlabs.com/ubuntulucid main 2. Run the command: sudo sh -c wget -q -O -http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs| sudo apt-key add - \ apt-get update apt-get install puppet-dashboard USING THE SOURCE: You can download the release candidate from: http://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.0.4.tgz Or check it out using git: git clone git://github.com/puppetlabs/puppet-dashboard.git \ cd puppet-dashboard \ git checkout v1.0.4 RELEASE NOTES: v1.0.4 -- * MIGRATION: Fixed truncation of long reports and deleted these invalid records. Please reimport your reports (see README) after migrating to readd these deleted reports. * MIGRATION: Fixed slow database queries and improved table indexes to speed up the home page, reports listing page, site-wide sidebar, nodes counts, and selection of nodes over time. * MIGRATION: Fixed orphaned records left behind when classes or groups were deleted, and removed these orphans from the database. * MIGRATION: Fixed duplicate membership records by removing them and preventing new ones from being added, e.g. a node belongs to the same class or group multiple times. * Fixed user interface for specifying classes and groups to work with standards-compliant browsers, autocomplete on keystroke rather than submitting, etc. * Fixed default node search, it was incorrectly using the ever failed node query rather than the all nodes query. * Fixed .rpm and .deb packages to include all required files, declare all dependencies, set correct permissions and include working startup scripts. * Fixed run-failure chart to correctly count the reports by day. * Fixed run-time chart to correctly display its unit-of-measure labels as seconds, not milliseconds. * Fixed report display and sorting to use
[Puppet Users] Re: ANNOUNCE: Puppet Dashboard 1.0.4 Release Candidate 2!
The Puppet Labs development team would really appreciate your feedback on Puppet Dashboard v1.0.4rc2, described below. Please try it out and report your experiences, even if it's just, It works great! Puppet Dashboard 1.0.4 is a big step forward in improving the application's reliability, user interface, performance and documentation. We've done a lot of testing and think this is solid. We'd like to ship the final release this week. Upgrading from this release candidate to the final release will be trivial. Thanks! -igal On Sat, Oct 9, 2010 at 3:01 PM, James Turnbull ja...@puppetlabs.com wrote: We're pleased to announce the availability of Puppet Dashboard 1.0.4rc2! The 1.0.4 release is a maintenance release, it fixes a number of bugs, improves the user interface, significantly boosts performance and includes better RPM and DEB packages. Please try this release candidate and let us know about any issues on the mailing list (http://groups.google.com/group/puppet-users/), or in the ticket tracker with an Affected Version of 1.0.4 (http://projects.puppetlabs.com/projects/dashboard/). If you're interested in what we're hoping to work on next, please see our roadmap and watch or comment on those tickets that are important to you: http://projects.puppetlabs.com/projects/dashboard/roadmap INSTALLING AND UPGRADING: New installation and upgrading instructions are available in the included README, which you can also read online at: http://github.com/puppetlabs/puppet-dashboard/blob/v1.0.4rc2/README.markdown IMPORTANT: This release involves database migrations. Please see the README.markdown for instructions on applying them. USING PACKAGES: We're making 1.0.4rc2 packages available for download. The final released packages for 1.0.4 will be available in the Puppet Labs package repository. You can install the RPM package for CentOS or RHEL 5.5 by running the following from your shell: sudo sh -c rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm; \ cd /tmp/ \ wget -c http://www.puppetlabs.com/downloads/dashboard/puppet-dashboard-1.0.4rc2-1.noarch.rpm \ gpg --keyserver x-hkp://pgp.mit.edu --recv-keys 4bd6ec30 \ gpg --armor --export 4bd6ec30 /tmp/puppetlabs.asc \ rpm --import /tmp/puppetlabs.asc \ yum install ./puppet-dashboard-1.0.4rc2-1.noarch.rpm Or install the DEB package for Ubuntu 10.04 by running: sudo sh -c cd /tmp/ \ wget -c http://www.puppetlabs.com/downloads/dashboard/puppet-dashboard_1.0.4rc2-1_all.deb; \ dpkg -i puppet-dashboard_1.0.4rc2-1_all.deb; \ apt-get install -f USING THE SOURCE: You can download the release candidate from: http://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.0.4rc2.tgz Or check it out using git: git clone git://github.com/puppetlabs/puppet-dashboard.git \ cd puppet-dashboard \ git checkout v1.0.4rc2 RELEASE NOTES: v1.0.4rc2 - * MIGRATION: Fixed slow database queries and improved table indexes when counting nodes and selecting nodes over time. * Fixed node's reports listing page to not throw exceptions. * Fixed .rpm and .deb packages to include all required files, declare all dependencies, set correct permissions and include working startup scripts. * Fixed views to display all dates and times in the same timezone and format. * Fixed views to generate all internal links relative to RAILS_ROOT enabling the site to be served from sub-URIs (Ex: example.com/dashboard/). * Added documentation describing some simple ways to improve the application's performance, see README. * Added task to optimize the database tables which can be run using `rake RAILS_ENV=production db:raw:optimize`. v1.0.4rc1 - * MIGRATION: Fixed truncation of long reports and deleted these invalid records. Please reimport your reports (see README) after migrating to readd these deleted reports. * MIGRATION: Fixed slow database queries on the home page, reports listing page, and site-wide sidebar. * MIGRATION: Fixed orphaned records left behind when classes or groups were deleted, and removed these orphans from the database. * MIGRATION: Fixed duplicate membership records by removing them and preventing new ones from being added, e.g. a node belongs to the same class or group multiple times. * Fixed user interface for specifying classes and groups to work with standards-compliant browsers, autocomplete on keystroke rather than submitting, etc. * Fixed default node search, it was incorrectly using the ever failed node query rather than the all nodes query. * Fixed run-failure chart to correctly count the reports by day. * Fixed run-time chart to correctly display its unit-of-measure labels as seconds, not milliseconds. * Fixed report display and sorting to use the time the report was created by a client, rather than the time it was imported. * Fixed class validations to accept valid Puppet class names,
Re: [Puppet Users] puppet-dashboard - where do I put the .htaccess file?
On Thu, Sep 30, 2010 at 3:58 AM, Tim Lank timl...@timlank.com wrote: puppet-users: I've got puppet-dashboard 1.0.3-3 setup using the rpm from here: http://yum.puppetlabs.com/base/ Everything seems to work fine using the instructions from here: http://github.com/reductivelabs/puppet-dashboard I'm trying to setup basic security with the .htaccess file described in the Security section - item#3. Where exactly do I need to put this? Thanks in advance for your help. You can create a /usr/share/puppet-dashboard/public/.htaccess file with contents similar to this: AuthName Puppet Dashboard AuthType Basic AuthUserFile /usr/share/puppet-dashboard/config/htpasswd Require valid-user ,,.and then create the AuthUserFile specified above using `htpasswd` (run `htpasswd -h` for help). I've created issue #4890 to add some more documentation on this topic. -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Change date format in puppet-dashboard
Regarding the timezone and date-time format discussion: we'd like to resolve this and have an issue assigned to one of the next releases. Do the details below capture the intended behavior? http://projects.puppetlabs.com/issues/4605 Application should use the timezone and format set in a site-specific configuration Currently: * Timezone is set in |config/environment.rb| and this file must be edited to alter it. This is bad because this file is versioned and is part of the app. Worse still, not everything in the application uses it — such as Status::by_interval uses the timezone that’s set on the operating system instead. * Time/date formats are set in |config/initializers/time_formats.rb|. These now use international format, but we should accommodate people with other preferences. * Charts use their own format, ignoring the timezone and formatting used in the rest of the application.. Desired behavior: * Site-wide settings should be implemented, see #4604 http://projects.puppetlabs.com/issues/4604 * Timezone setting should be added to the site-wide settings * Date-time format setting should be added to the site-wide settings * Everything should use the timezone settings, e.g. the views, Status::by_interval, charts, etc. * Everything should use the date-time formatting settings, e.g. the Rails views and charts. -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet does not include errors in reports
On 08/26/2010 01:28 AM, Kenneth Holter wrote: I'm setting up Puppet Dashboard for external node and reporting purposes, and notice that errors on the puppet client side doesn't get reported. For example, one of my classes lack a parameter, which results in the typical Error 400 on server [...] Could not find value for [...], but still the report indicates that everything is working perfectly. I've found this behavior on the reports on the local file system, so it's not a dashboard issue. Can you please confirm that you've looked at the YAML report file and did not find the error listed in there? If there's no error listed in there, then there's probably something wrong with Puppet. But if the error is there and Dashboard didn't display it, then the bug's with Dashboard. My guess is that you're using Puppet 2.6, which Dashboard doesn't fully support yet. As of Dashboard 1.0.3, it's able to save Puppet 2.6 reports and display some of their contents -- but much of their content (e.g. statuses, runtimes and even success) aren't displayed correctly. We plan to add this functionality in one of the next Dashboard releases, here's the ticket: http://projects.puppetlabs.com/issues/4514 If you're using Puppet 0.25, then something else is going on. Please file an issue, along with the Puppet and Dashboard versions, the complete error messages and a full example of the report YAML so we can debug this. Thanks! -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet does not include errors in reports
Kenneth, Thanks for filing the detailed bug report. I can confirm that your report file describes no errors and even its Failed count is 0. Strange. -igal On 08/26/2010 02:17 AM, Kenneth Holter wrote: Thanks for the quick reply. Both master and client are running version 0.25.4, and I can confirm that the YAML report file (found under the /var/lib/puppet/reports folder) does not list the error. I've created a ticket on the issue: http://projects.reductivelabs.com/issues/4628 - Kenneth On Thu, Aug 26, 2010 at 10:50 AM, Igal Koshevoy i...@pragmaticraft.com mailto:i...@pragmaticraft.com wrote: On 08/26/2010 01:28 AM, Kenneth Holter wrote: I'm setting up Puppet Dashboard for external node and reporting purposes, and notice that errors on the puppet client side doesn't get reported. For example, one of my classes lack a parameter, which results in the typical Error 400 on server [...] Could not find value for [...], but still the report indicates that everything is working perfectly. I've found this behavior on the reports on the local file system, so it's not a dashboard issue. Can you please confirm that you've looked at the YAML report file and did not find the error listed in there? If there's no error listed in there, then there's probably something wrong with Puppet. But if the error is there and Dashboard didn't display it, then the bug's with Dashboard. My guess is that you're using Puppet 2.6, which Dashboard doesn't fully support yet. As of Dashboard 1.0.3, it's able to save Puppet 2.6 reports and display some of their contents -- but much of their content (e.g. statuses, runtimes and even success) aren't displayed correctly. We plan to add this functionality in one of the next Dashboard releases, here's the ticket: http://projects.puppetlabs.com/issues/4514 If you're using Puppet 0.25, then something else is going on. Please file an issue, along with the Puppet and Dashboard versions, the complete error messages and a full example of the report YAML so we can debug this. Thanks! -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: How to change the node's class or groups
Timo,
Thanks for the details. So if you type the name of a known class or
group into a class or group UI field in Firefox, nothing happens?
I primarily use Firefox on Linux and it works for me, although the tags
are rendered incorrectly, like this:
http://projects.puppetlabs.com/attachments/1092/dashboard-tag2.png
Anyway, we'd like to fix or replace the class-group UI widget because of
the issues that you encountered:
* http://projects.puppetlabs.com/issues/3470
* http://projects.puppetlabs.com/issues/3427
-igal
On 08/23/2010 10:49 PM, Timo Seven wrote:
HI igal:
I find the ajax only work in windows IE. It don't work in the
Firefox 3.6.8 under Ubuntu 10.04.
I think this is a bug.
###
Best regards
Timo Seven
blog: http://zauc.wordpress.com
twitter: http://twitter.com/zauc
Linux System Admin MySQL DBA
2010/8/23 Igal Koshevoy i...@pragmaticraft.com:
On Wed, Aug 18, 2010 at 10:47 PM, Timo Seven gre...@gmail.com wrote:
I install puppet version 2.6 and puppet dashboard 1.0.3.
When I change one node's class or groups, it is invalid。 I also can
add new class and groups. But no nodes can be in these class or
groups.
So I insert a node in a class under mysql like insert into
node_class_memberships values (1,1,1,'2010-08-17','2010-08-17');,
Then I can see the first node has been in the first class.
[...]
follow is the log
Processing NodesController#update (for 10.1.41.81 at 2010-08-19 13:45:53)
[PUT]
Parameters: {node={name=puppet.timo.com,
node_group_names=[ ], parameter_attributes=[{value=,
key=}], node_class_names=[ ], description=},
action=update, _method=put,
authenticity_token=sV1FfxR5EAatq+BW/ApH7/JPEK9LLwmKCtBEDIvYmQI=,
id=puppet.timo.com, controller=nodes}
Redirected to http://10.10.83.193:3000/nodes/puppet.timo.com
Completed in 40ms (DB: 0) | 302 Found
[http://10.10.83.193/nodes/puppet.timo.com]
Timo,
The Puppet Dashboard currently uses a quirky AJAX autocomplete system.
You need to type the first few characters of the group field, then click
the desired group name in the popup selector list, which will then add
it as text within a rounded box to the groups text input field, and then
you can click the create/save button for the form to save it. Simply
typing the name in is not enough, you must click the name of the group
in that popup selector list.
There's a strong desire to either fix or replace the autocompletion
system with something that's more user friendly. Here's the related
ticket: http://projects.puppetlabs.com/issues/3427
Can you please confirm that what I just described is the issue you were
having?
-igal
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: How to change the node's class or groups
On Wed, Aug 18, 2010 at 10:47 PM, Timo Seven gre...@gmail.com wrote:
I install puppet version 2.6 and puppet dashboard 1.0.3.
When I change one node's class or groups, it is invalid。 I also can
add new class and groups. But no nodes can be in these class or
groups.
So I insert a node in a class under mysql like insert into
node_class_memberships values (1,1,1,'2010-08-17','2010-08-17');,
Then I can see the first node has been in the first class.
[...]
follow is the log
Processing NodesController#update (for 10.1.41.81 at 2010-08-19 13:45:53)
[PUT]
Parameters: {node={name=puppet.timo.com,
node_group_names=[ ], parameter_attributes=[{value=,
key=}], node_class_names=[ ], description=},
action=update, _method=put,
authenticity_token=sV1FfxR5EAatq+BW/ApH7/JPEK9LLwmKCtBEDIvYmQI=,
id=puppet.timo.com, controller=nodes}
Redirected to http://10.10.83.193:3000/nodes/puppet.timo.com
Completed in 40ms (DB: 0) | 302 Found
[http://10.10.83.193/nodes/puppet.timo.com]
Timo,
The Puppet Dashboard currently uses a quirky AJAX autocomplete system.
You need to type the first few characters of the group field, then click
the desired group name in the popup selector list, which will then add
it as text within a rounded box to the groups text input field, and then
you can click the create/save button for the form to save it. Simply
typing the name in is not enough, you must click the name of the group
in that popup selector list.
There's a strong desire to either fix or replace the autocompletion
system with something that's more user friendly. Here's the related
ticket: http://projects.puppetlabs.com/issues/3427
Can you please confirm that what I just described is the issue you were
having?
-igal
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: RHEL4 puppet-dashboard 1.0.3
On 08/11/2010 12:26 AM, ScubaDude wrote: On Aug 10, 8:22 pm, Igal Koshevoy i...@pragmaticraft.com wrote: On 08/10/2010 06:58 AM, ScubaDude wrote: Packages I needed to get dashboard running on a RHEL4 Server: Thanks for describing this, we'll incorporate these into a future release of the Puppet Dashboard's documentation. I've added a feature ticket for this athttp://projects.puppetlabs.com/issues/4510 If you or others have other OS-specific instructions, please feel free to submit a patch against the docs. augeas-0.7.2-1 augeas-libs-0.7.2-1 facter-1.5.7 ruby-augeas-0.3.0.1 The Puppet Dashboard doesn't require these packages -- I suspect these were required as part of installing Puppet. Your quite correct, the server I'm using also hosts the puppet-master. Thanks for the confirmation. From the Extra Packages for Enterprise Linux repository: ruby-mysql-2.7.3-1 [...] I tried to install the mysql gem the same way, but got errors because ruby needed to be a higher revision. [...] [Instead installed from] http://rubyworks.rubyforge.org/redhat/4.9/RPMS/x86_64/rubygem-mysql-2... The ruby-mysql package from EPEL is recommended by the documentation for newer versions of CentOS and provides a pre-compiled library that's tricky to to build otherwise. Did the EPEL package work for you? If so, there shouldn't have been a need to install it via `gem install ruby-mysql` or from rubyworks. If not, can you please summarize what happened? The EPEL ruby-mysql package installed fine, however if I try to run the server without the mysql gem I get: !!! The bundled mysql.rb driver has been removed from Rails 2.2. Please install the mysql gem and try again: gem install mysql. /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- mysql (MissingSourceFile) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' from /usr/share/puppet-dashboard/vendor/rails/activesupport/lib/ active_support/dependencies.rb:158:in `require' from /usr/share/puppet-dashboard/vendor/rails/activesupport/lib/ active_support/core_ext/kernel/requires.rb:7:in `require_library_or_gem' from /usr/share/puppet-dashboard/vendor/rails/activesupport/lib/ active_support/core_ext/kernel/reporting.rb:11:in `silence_warnings' from /usr/share/puppet-dashboard/vendor/rails/activesupport/lib/ active_support/core_ext/kernel/requires.rb:5:in `require_library_or_gem' from /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/ active_record/connection_adapters/mysql_adapter.rb:61:in `mysql_connection' from /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/ active_record/connection_adapters/abstract/connection_pool.rb:223:in `send' from /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/ active_record/connection_adapters/abstract/connection_pool.rb:223:in `new_connection' ... 26 levels... from /usr/share/puppet-dashboard/vendor/rails/railties/lib/commands/ server.rb:84 from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' from script/server:3 That might be caused by some other issue, or a version conflict. I removed the ruby-mysql RPM (--nodeps as puppet-dashboard requires it) and all continued to function so that RPM maybe a red herring. Trying to install the gem with 'gem' I get: # gem install mysql ERROR: Error installing mysql: mysql requires Ruby version = 1.8.6 Hence using the RPM version of the mysql gem. The rubyworks Ruby package probably reads libraries from different directories than the EPEL ruby-mysql package is installed into and thus can't be loaded, so your approach of installing the rubyworks version of rubygems-mysql seems correct and necessary. Thank you for the details, this will make it easier to write the installation instructions for these older RHEL and CentOS releases. -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet dashboard not working for node group
On 08/11/2010 07:37 AM, hai wu wrote: I am using puppet-dashboard 1.0.3 for Ubuntu 10.04. It is not working for node group. I can add a node group via Add Group. After this, from Edit node page, after trying to add this group to a node, the group field would still be empty, and if looking at the log, it shows for this update _method: node_group_names=[ ] I put group value to the group editing page, why it is still empty when the NodesController receiving the request? The Puppet Dashboard currently uses a quirky AJAX autocomplete system. You need to type the first few characters of the group field, then click the desired group name in the popup selector list, which will then add it as text within a rounded box to the groups text input field, and then you can click the create/save button for the form to save it. Simply typing the name in is not enough, you must click the name of the group in that popup selector list. There's a strong desire to either fix or replace the autocompletion system with something that's more user friendly. Here's the related ticket: http://projects.puppetlabs.com/issues/3427 Can you please confirm that what I just described is the issue you were having? -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: RHEL4 puppet-dashboard 1.0.3
On 08/10/2010 06:58 AM, ScubaDude wrote: Packages I needed to get dashboard running on a RHEL4 Server: Thanks for describing this, we'll incorporate these into a future release of the Puppet Dashboard's documentation. I've added a feature ticket for this at http://projects.puppetlabs.com/issues/4510 If you or others have other OS-specific instructions, please feel free to submit a patch against the docs. augeas-0.7.2-1 augeas-libs-0.7.2-1 facter-1.5.7 ruby-augeas-0.3.0.1 The Puppet Dashboard doesn't require these packages -- I suspect these were required as part of installing Puppet. From the Extra Packages for Enterprise Linux repository: ruby-mysql-2.7.3-1 [...] I tried to install the mysql gem the same way, but got errors because ruby needed to be a higher revision. [...] [Instead installed from] http://rubyworks.rubyforge.org/redhat/4.9/RPMS/x86_64/rubygem-mysql-2.7-2 The ruby-mysql package from EPEL is recommended by the documentation for newer versions of CentOS and provides a pre-compiled library that's tricky to to build otherwise. Did the EPEL package work for you? If so, there shouldn't have been a need to install it via `gem install ruby-mysql` or from rubyworks. If not, can you please summarize what happened? Finally install puppet-dashboard from rpm: http://yum.puppetlabs.com/base/puppet-dashboard-1.0.3-3.norarch.rpm --nodeps required. The package appears to use an rpm query to check dependencies, the rake gem wasn’t installed as an RPM, neither was rubygems so it fails. rpm –Uvh --nodeps puppet-dashboard-1.0.3-3.norarch.rpm The packages assume you're running a newer version of CentOS. Your `--nodeps` workaround for this is fine. Another approach would have been to use a source-only version of the software downloaded from github. Anyway, thank you for working through this and describing your experiences. -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet dashboard takes a long time to display
On 08/04/2010 01:50 PM, Steven L. Seed wrote: I've been noticing my puppet dashboard is taking longer and longer to load up in my we browser the longer I've used it. I have roughly 1300 nodes being managed by puppet. It's almost as if there is too much data for it to process. I have about 1 month worth of data in my mysql database now. I've recently upgraded to version 1.0.3 but it hasn't improved the performance. It's taking typically around 60 - 90 seconds for the page to load...the browser sits waiting for a response from the server. Some things that you can do to make Dashboard run faster: 1. Run it in `production` mode, which is explained further in application's README. 2. Remove older reports from the database, e.g. keep only the last 15 days: `rake RAILS_ENV=production reports:prune upto=15 unit=day` 3. Run the Dashboard and its database on the same machine, and give them enough CPU cycles and RAM to run comfortably. If these don't help, it's likely that you're running into performance problems with how Dashboard is currently implemented. Resolving these issues is a high priority because it affects sites like yours with many nodes and reports and is on the schedule for the next major release. -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released
On 08/03/2010 06:01 AM, Rob McBroom wrote:
On Aug 2, 2010, at 5:39 PM, James Turnbull wrote:
Is there anything in /var/log/apache/error.log?
What the…? Yes. Why isn’t it going to the ErrorLog for that virtual host?
Anyway, there were a number of these:
Rails Error: Unable to access log file. Please ensure that
/opt/puppet-dashboard/log/production.log exists and is chmod 0666. The log
level has been raised to WARN and the output directed to STDERR until the
problem is fixed.
So I chowned that directory and it’s files to the ‘apache’ user and now I’m
seeing:
ActionView::TemplateError (Permission denied -
/opt/puppet-dashboard/public/stylesheets/all.css) on line #14 of
app/views/layouts/application.html.haml:
11: var relative_url_root =
'#{ActionController::Base.relative_url_root}';
12: $.noConflict();
13:
14: = stylesheet_link_tag 'reset', 'layout', 'forms', 'tables',
'jquery.ui.autocomplete.css', 'typography', 'links', 'fcbkcomplete', 'tipsy',
'application', :cache = 'all'
15: = javascript_include_tag 'prototype', 'jrails', 'fcbkcomplete',
'excanvas.min', 'raphael-min', 'grafico.min', 'jquery.form',
'jquery.placeholders', 'jquery.ui.autocomplete',
'jquery.ui.autocomplete.ext', 'jquery.tipsy', 'search', 'application', :cache
= ‘all’
…followed by a trace through the application. The `production.log`, though
it’s now writable, contains nothing.
So I guess it’s trying to cache all the stylesheets and JavaScript into one
file? I chowned the `stylesheets` directory to apache:apache, but I still see
the error. Is there a list of paths that Passenger expects write-access to
somewhere? Why wasn’t this an issue before?
The application was failing at startup because it couldn't write its own
log files, and now it's failing because it can't write its caches.
Please give ownership of the puppet-dashboard directory and everything
in it to the same user, and grant this user read and write access to all
of this.
For example:
chown -R apache:apache /opt/puppet-dashboard
chmod -R ug+rwX /opt/puppet-dashboard
-igal
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released
On 08/03/2010 10:19 AM, Rob McBroom wrote: On Aug 3, 2010, at 10:40 AM, Igal Koshevoy wrote: The application was failing at startup because it couldn't write its own log files, and now it's failing because it can't write its caches. Please give ownership of the puppet-dashboard directory and everything in it to the same user, and grant this user read and write access to all of this. For example: chown -R apache:apache /opt/puppet-dashboard chmod -R ug+rwX /opt/puppet-dashboard OK, that plus a restart of Apache seems to have brought the web interface back. Thanks. Great. Now, some questions: 1. Is that a good idea; For the web server to have write access to the application itself? This is normal for Ruby on Rails applications like Puppet Dashboard and those written in some other web frameworks. This isn't a big deal for typical Rails deployments because each app is often run in a separate user account with write access to all its files, and the apps' code is managed locally with something like git or externally with something like Capistrano. However, this design causes hardship to those trying to distribute such apps as OS packages and annoys sysadmins because it intermingles read-only source code with configuration and variable files. Rails doesn't provide a straightforward way to separate these, although this could be addressed with some surgery. 2. Why wasn’t this necessary with previous versions? All previous versions of Dashboard needed write access to the db, log and tmp directories. Writing to the public directory is new to this version. 3. If it is necessary, should it be mentioned in the installation instructions? Thanks for the suggestion, I've added issue #4455 to address this. -igal -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
