Puppet users - Mar 2012 - Issue with pe-dashboard-workers

I''ve almost gotten PE running --

Based on tips from a recent Webinar, I''ve started on a minimal RHEL 6
system, and have installed the PE 2.03 packages. Once I set up /etc/
hosts (DNS will come later), I started the PE services. Given past
problems (possibly just me), I was pleasantly surprised that the
puppet-enterprise-updater script was so accommodating as I remembered
which systems to update.

So I''m to the point where the pe-puppet-dashboard-workers script
(from /etc/init.d) borks a bit with the following message:

Starting pe-dashboard-workers: Database isn''t the current migration
version: expected 20111118204121, got 0
You must either run ''rake db:migrate'' or set environmental
variable
NO_MIGRATION_CHECK

To confirm, the service pe-puppet-dashboard workers status command
returns the following message:

pe-dashboard-workers dead but pid file exists

Given the suggestions, (and a bit of online help) I then navigated to /
opt/puppet/share/puppet-dashboard and ran the rake db:migrate command
and got the following message:

DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks
are deprecated. Use lib/tasks instead. (called from /opt/puppet/share/
puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10)
rake aborted!
no such file to load -- sinatra/base

Since I couldn''t figure out how to get sinatra/base loaded (perhaps
that''s a solution), I went back and worked on setting the environment
variable with the export NO_MIGRATION_CHECK=1 command. I then tried
restarting the pe-puppet-dashboard-workers script, and seemed to get
further:

Stopping pe-dashboard-workers: pid-file for killed process 3520 found
(/opt/puppet/share/puppet-dashboard/tmp/pids/delayed_job.0.pid),
deleting.
pid-file for killed process 3524 found (/opt/puppet/share/puppet-
dashboard/tmp/pids/delayed_job.1.pid), deleting.
                                                           [  OK  ]
Starting pe-dashboard-workers:                             [  OK  ]

But that wasn''t enough, as a status check still shows

pe-dashboard-workers dead but pid file exists

I''ve tried rerunning with the PID files deleted from the /var/opt/
cache/pe-puppet-dashboard/pids/
 directory, without any changes to the result.

Any advice would be appreciated.

Thanks,
Mike

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I don''t get it, but a clean uninstall (including db files in 
/var/lib/mysql) followed by a reinstall seems to have worked.

Thanks for listening.

On Tuesday, March 6, 2012 10:19:37 AM UTC-8, mic...@linuxexam.com
wrote:
>
> I''ve almost gotten PE running -- 
>
> Based on tips from a recent Webinar, I''ve started on a minimal
RHEL 6
> system, and have installed the PE 2.03 packages. Once I set up /etc/ 
> hosts (DNS will come later), I started the PE services. Given past 
> problems (possibly just me), I was pleasantly surprised that the 
> puppet-enterprise-updater script was so accommodating as I remembered 
> which systems to update. 
>
> So I''m to the point where the pe-puppet-dashboard-workers script 
> (from /etc/init.d) borks a bit with the following message: 
>
> Starting pe-dashboard-workers: Database isn''t the current
migration
> version: expected 20111118204121, got 0 
> You must either run ''rake db:migrate'' or set
environmental variable
> NO_MIGRATION_CHECK 
>
> To confirm, the service pe-puppet-dashboard workers status command 
> returns the following message: 
>
> pe-dashboard-workers dead but pid file exists 
>
> Given the suggestions, (and a bit of online help) I then navigated to / 
> opt/puppet/share/puppet-dashboard and ran the rake db:migrate command 
> and got the following message: 
>
> DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks 
> are deprecated. Use lib/tasks instead. (called from /opt/puppet/share/ 
> puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10) 
> rake aborted! 
> no such file to load -- sinatra/base 
>
> Since I couldn''t figure out how to get sinatra/base loaded
(perhaps
> that''s a solution), I went back and worked on setting the
environment
> variable with the export NO_MIGRATION_CHECK=1 command. I then tried 
> restarting the pe-puppet-dashboard-workers script, and seemed to get 
> further: 
>
> Stopping pe-dashboard-workers: pid-file for killed process 3520 found 
> (/opt/puppet/share/puppet-dashboard/tmp/pids/delayed_job.0.pid), 
> deleting. 
> pid-file for killed process 3524 found (/opt/puppet/share/puppet- 
> dashboard/tmp/pids/delayed_job.1.pid), deleting. 
>                                                            [  OK  ] 
> Starting pe-dashboard-workers:                             [  OK  ] 
>
> But that wasn''t enough, as a status check still shows 
>
> pe-dashboard-workers dead but pid file exists 
>
> I''ve tried rerunning with the PID files deleted from the /var/opt/
> cache/pe-puppet-dashboard/pids/ 
>  directory, without any changes to the result. 
>
> Any advice would be appreciated. 
>
> Thanks, 
> Mike
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/8vjhuC0oMmsJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.