jemmorey
2013-Jan-02 21:29 UTC
[Puppet Users] puppet-dashboard load balanced report processing issues.
I just upgraded the second half of a two node puppetmaster cluster and now I am having issues with puppet-dashboard report processing. If I have workers running on both servers, they try to process each others reports, but since the report data file is not there, it fails. I would have assumed this data was local, not in the database. Does anyone else have this issue, or have a suggestion of how to fix. I really don''t want to go the dirty route and have an NFS share of the /usr/share/puppet-dashboard/spool directory between my two masters. Any suggestions are appreciated! -- 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/-/YHXxZ4TVMgcJ. 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.
jemmorey
2013-Jan-02 21:32 UTC
[Puppet Users] Re: puppet-dashboard load balanced report processing issues.
I haven''t tried using the puppet-dashboard.rb processor, I''m
using the
following:
reports = http,store
reporturl = http://localhost/reports/upload/
I''m guessing that the puppet-dashboard.rb processor exhibits the same
behavior by queuing the processing.
Thanks!
On Wednesday, January 2, 2013 4:29:23 PM UTC-5, jemmorey
wrote:>
> I just upgraded the second half of a two node puppetmaster cluster and now
> I am having issues with puppet-dashboard report processing. If I have
> workers running on both servers, they try to process each others reports,
> but since the report data file is not there, it fails. I would have
> assumed this data was local, not in the database. Does anyone else have
> this issue, or have a suggestion of how to fix. I really don''t
want to go
> the dirty route and have an NFS share of the
> /usr/share/puppet-dashboard/spool directory between my two masters.
>
> Any suggestions are appreciated!
>
--
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/-/xJ3IbzoG8qsJ.
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.
jemmorey
2013-Jan-02 21:56 UTC
[Puppet Users] Re: puppet-dashboard load balanced report processing issues.
Looks like there is no current method to prevent multiple dashboard nodes from stomping on each others reports, the delayed_jobs table does have a locked_by, but that is only used during the actual event processing. mysql> describe delayed_jobs; +------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +------------+--------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | priority | int(11) | YES | MUL | 0 | | | attempts | int(11) | YES | | 0 | | | handler | longtext | YES | | NULL | | | last_error | text | YES | | NULL | | | run_at | datetime | YES | | NULL | | | locked_at | datetime | YES | | NULL | | | failed_at | datetime | YES | | NULL | | | locked_by | varchar(255) | YES | | NULL | | | created_at | datetime | YES | | NULL | | | updated_at | datetime | YES | | NULL | | +------------+--------------+------+-----+---------+----------------+ 11 rows in set (0.00 sec) I suppose I will open this as an RFE. If anyone has any other ideas how to do this (other than the dreaded NFS share) please let me know. Thanks! -- 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/-/KufkHt4fpc8J. 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.
Aaron Grewell
2013-Jan-03 17:03 UTC
Re: [Puppet Users] Re: puppet-dashboard load balanced report processing issues.
Even an nfs share will not fix this. We tried it. We had to make dashboard active - passive to fix it. Otherwise lots of dashboard errors result which must be cleared via rake task or the dashboard slows to a crawl. On Jan 2, 2013 1:56 PM, "jemmorey" <jordan@obsecurities.com> wrote:> Looks like there is no current method to prevent multiple dashboard nodes > from stomping on each others reports, the delayed_jobs table does have a > locked_by, but that is only used during the actual event processing. > > mysql> describe delayed_jobs; > +------------+--------------+------+-----+---------+----------------+ > | Field | Type | Null | Key | Default | Extra | > +------------+--------------+------+-----+---------+----------------+ > | id | int(11) | NO | PRI | NULL | auto_increment | > | priority | int(11) | YES | MUL | 0 | | > | attempts | int(11) | YES | | 0 | | > | handler | longtext | YES | | NULL | | > | last_error | text | YES | | NULL | | > | run_at | datetime | YES | | NULL | | > | locked_at | datetime | YES | | NULL | | > | failed_at | datetime | YES | | NULL | | > | locked_by | varchar(255) | YES | | NULL | | > | created_at | datetime | YES | | NULL | | > | updated_at | datetime | YES | | NULL | | > +------------+--------------+------+-----+---------+----------------+ > 11 rows in set (0.00 sec) > > I suppose I will open this as an RFE. If anyone has any other ideas how > to do this (other than the dreaded NFS share) please let me know. > > Thanks! > > -- > 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/-/KufkHt4fpc8J. > 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. >-- 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.