On Tue, Feb 21, 2012 at 8:21 AM, Mark B <mlitt...@indiana.edu> wrote:
> I restarted the mcollective and I see the following in the logs: > > I, [2012-02-21T11:18:13.485565 #13326] INFO -- : stomp.rb:79:in > `on_connectfail' Connction to stomp://mcollect...@puppett.xxxx.xxx.xxx > :61613 > failed on attempt 11 > Note puppett (with two t's) - is that intentional? Can you ping that address? Firewall rules possibly? > > > On Feb 21, 11:12 am, Kenneth Lo <k...@paydiant.com> wrote: > > Just try restart the mcollective service on the agent and check if you > see > > any error there. > > > > You should also check if there are anything in-between your agent and > > master that's blocking traffic. Mcollective traffic goes from agent to > the > > master, not the other way around. > > > > --KL > > > > On 2/21/12 10:46 AM, "Mark B" <mlitt...@indiana.edu> wrote: > > > > > > > > > > > > > > > > > > > > >The pe-activemq is running on the server and the pe-mcollective is > > >running on the agent. The reports from the client are showing up on > > >the puppet console. Just not seeing the node on live management > > >screen. Is there a way to manually do a new puppet run to try and > > >force it? > > > > >On Feb 21, 10:17 am, Kenneth Lo <k...@paydiant.com> wrote: > > >> In PE, pe-activemq is the server service (master need that service) > and > > >> pe-mcollective is the client service (agents). > > > > >> If you don't see your agents listed in LM normally means that the > > >> pe-mcollective service is not running on the clients. > > > > >> What I've experienced with PE is that under normal turn-key config, > > >>after > > >> your agent initially connected to the master, by default it need to > wait > > >> for another puppet run for the mcollective class (in default) to > pickup > > >> the service. > > > > >> --KL > > > > >> On 2/21/12 8:08 AM, "Mark B" <mlitt...@indiana.edu> wrote: > > > > >> >Yes...I was able to do the mco ping and the only node that responded > > >> >was the puppet master ..not the client. Both activemq and mcollective > > >> >appear to be working. > > > > >> >is there a pe-users group? I thought that is what this was ? > > > > >> >On Feb 20, 2:58 pm, Justin Stoller <jus...@puppetlabs.com> wrote: > > >> >> Have you tried su-ing to thepeadminuser on the master node and > trying > > >> >> `mco ping`? > > > > >> >> Live Management is basically a front end for actions thepeadminuser > > >> >>can > > >> >> do. Dropping down to that level may let you debug the issue easier. > > > > >> >> Other things to check are that activemq is working and correctly > > >> >>configured > > >> >> on the master, as well as mcollective on all of your agent nodes. > > > > >> >> You may also find more users that understand your question on the > > >> >>pe-users > > >> >> list (I assume if you're using Live Management you're using PE) > > > > >> >> - Justin > > > > >> >> On Mon, Feb 20, 2012 at 11:35 AM, Littman, Mark B > > >> >><mlitt...@indiana.edu>wrote: > > > > >> >> > Yes it is in the default group. I am wondering if it is a > > >>permissions > > >> >> > issue for the puppet user account? Does that need anything > special > > >> >>for live > > >> >> > management ? > > > > >> >> > Reminder: it shows on all other tabs on the puppet console...just > > >>not > > >> >>live > > >> >> > management. > > > > >> >> > -----Original Message----- > > >> >> > From: puppet-users@googlegroups.com > > >> >>[mailto:puppet-users@googlegroups.com] > > >> >> > On Behalf Of Michael Stahnke > > >> >> > Sent: Monday, February 20, 2012 2:31 PM > > >> >> > To: puppet-users@googlegroups.com > > >> >> > Subject: Re: [Puppet Users] Cannot see node on Live Management > > > > >> >> > On Mon, Feb 20, 2012 at 4:29 AM, Mark B <mlitt...@indiana.edu> > > >>wrote: > > >> >> > > The node and reports show up on the dashboard but not on the > live > > >> >> > > management tab. > > > > >> >> > > Does anyone have any suggestions? is this a permissions issue? > > > > >> >> > Is the node in the default group in the dashboard? Puppet runs > > >>setup > > >> >>the > > >> >> > mcollective/live management bits. The class is called > > >>pe_mcollective. > > > > >> >> > > -- > > >> >> > > 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+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-users@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-users@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-users@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. > > > > >> This message is for the designated recipient only and may contain > > >>privileged, proprietary, or otherwise private information. If you have > > >>received it in error, please notify the sender immediately and delete > > >>the original. Any other use of the email by you is prohibited. > > > > >-- > > >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+unsubscr...@googlegroups.com. > > >For more options, visit this group at > > >http://groups.google.com/group/puppet-users?hl=en. > > > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise private information. If you have > received it in error, please notify the sender immediately and delete the > original. Any other use of the email by you is prohibited. > > -- > 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+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- Gary Larizza Professional Services Engineer Puppet Labs -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
