[Puppet Users] Puppet-Dashboard All Nodes "Unresponsive", Background Tasks
Hello There, I've been struggling the last days with this issue. The situation is happening since I've upgrade Puppet to 3.6.0. *- Problem:* On Puppet-Dashboard all Hosts are shown as *Unresponsive* and thousand of tasks are queued as *Failed*. *- Environment:* OS: Debian Wheezy Puppet-Dashboard: 1.2.23 Puppet: 3.6.0 Facter: 2.0.1 Hiera: 1.3.2 *- Applied Solutions:* * Solution 1: cd /usr/share/puppet-dashboard/ - Stop dashboard workers rm -v spool/* rake jobs:clear RAILS_ENV=production - Start dashboard workers. Good solution, but temporary, because the problem after a few days comes back. * Solution 2: I've also did the following update to the DB: mysql> ALTER TABLE delayed_job_failures MODIFY details BLOB; Which also did not work. Does anyone have any idea of what can be happening there? -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d5e90a32-e8d6-4883-9cd0-d7c6d89d7f5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet dashboard with \n\n\n
Hello, sorry to bring this back. I just have a question, did you just changed the path of /usr/bin/ruby or did you did something else to make it work? Thanks in advance, X. On Friday, 4 October 2013 01:04:22 UTC+2, Matt Zagrabelny wrote: > > On Thu, Oct 3, 2013 at 5:45 PM, Juan Sierra Pons > wrote: > > > > El 03/10/2013 14:00, "Matt Zagrabelny" > > escribió: > > > > > >> > >> Greetings, > >> > >> I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18. > >> > >> I am seeing many \n strings all over the place when looking at > >> reports. Specifically the \n's are in the Metrics, Log, Events links. > >> > >> My nodes are showing up okay, and it seems just to be a problem with > >> the reports. For instance, a Metrics page starts with: > >> > >> \n > >> \n > >> Metrics > >> \n > >> \n > >> Events > >> > >> \n\n\n\n\n\n\n\n\n > >> > >> Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not > >> yield any hints. > >> > >> Thanks! > >> > >> -mz > >> > >> -- > >> 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...@googlegroups.com . > >> To post to this group, send email to puppet...@googlegroups.com > . > >> Visit this group at http://groups.google.com/group/puppet-users. > >> For more options, visit https://groups.google.com/groups/opt_out. > > Hi > > > > I had the same problem and the problem was in the ruby version > > > > Which one are you using? > > realpath =ruby > /usr/bin/ruby1.9.1 > > > > Check the dashboard webpage to find out wich one is the right one. > > Looks like 1.8 is what is needed. > > Looks like that worked! > > Thanks! > > -mz > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c83279b6-b99b-4ec9-b915-93f3c884df78%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Dashboard showing "newline" character
Hello There, have you found a solution for this? I'll appreciate your help. Regards, X. On Friday, 31 May 2013 09:04:12 UTC+2, Thomas Dahlberg wrote: > > I found the solution. Dashboard does not play well with ruby 1.9.3. > I will try the rails3 branch and see if it works better. > > /Thomas > > On Wednesday, May 22, 2013 7:48:52 PM UTC+2, Jordan Hayes wrote: >> >> I am having this exact same issue. >> I installed Puppet this past April, from the PuppetLabs repository on a >> Debian Wheezy box. >> I see these new line characters under the reports, as you have shown. >> >> I am also new to Puppet and new to Ruby, which makes this problem even >> more frustrating. >> >> On Thursday, April 4, 2013 7:46:34 AM UTC-7, Kevin Squire wrote: >>> >>> I just completed the install of dashboard on a Debian Wheezy box, using >>> the deb package provided by puppetlabs repository. After following the >>> directions >>> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html I >>> now have it up and running (collecting reports only at the moment) >>> >>> I am noticing that on all my reports page, I get a ton of "\n" >>> characters showing up. Since I am new to Ruby as well as Puppet, I am >>> having a hard time finding WHY these are getting inserted. Any help would >>> be appreciated. >>> >>> Attached is a screenshot showing the issue... same image is also >>> available at http://www.wikiak.org/temp/dashboard.png >>> >>> >>> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/599435d0-2a35-44d9-9a1d-2cdb6e0fc71d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet dashboard with \n\n\n
Me again, I've changed the link of /etc/alternatives/ruby (Debian) to point to ruby1.8 and everything looks good now on the Dashboard! Thanks! :) On Monday, 23 June 2014 15:37:59 UTC+2, Ximena Cardinali wrote: > > Hello, sorry to bring this back. > > I just have a question, did you just changed the path of /usr/bin/ruby or > did you did something else to make it work? > > Thanks in advance, > X. > > On Friday, 4 October 2013 01:04:22 UTC+2, Matt Zagrabelny wrote: >> >> On Thu, Oct 3, 2013 at 5:45 PM, Juan Sierra Pons >> wrote: >> > >> > El 03/10/2013 14:00, "Matt Zagrabelny" escribió: >> > >> > >> >> >> >> Greetings, >> >> >> >> I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18. >> >> >> >> I am seeing many \n strings all over the place when looking at >> >> reports. Specifically the \n's are in the Metrics, Log, Events links. >> >> >> >> My nodes are showing up okay, and it seems just to be a problem with >> >> the reports. For instance, a Metrics page starts with: >> >> >> >> \n >> >> \n >> >> Metrics >> >> \n >> >> \n >> >> Events >> >> >> >> \n\n\n\n\n\n\n\n\n >> >> >> >> Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not >> >> yield any hints. >> >> >> >> Thanks! >> >> >> >> -mz >> >> >> >> -- >> >> 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...@googlegroups.com. >> >> To post to this group, send email to puppet...@googlegroups.com. >> >> Visit this group at http://groups.google.com/group/puppet-users. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > Hi >> > >> > I had the same problem and the problem was in the ruby version >> > >> > Which one are you using? >> >> realpath =ruby >> /usr/bin/ruby1.9.1 >> >> >> > Check the dashboard webpage to find out wich one is the right one. >> >> Looks like 1.8 is what is needed. >> >> Looks like that worked! >> >> Thanks! >> >> -mz >> > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8885ddc7-8627-4078-9303-616383bb253c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Dashboard showing "newline" character
Me again, I've changed the link of /etc/alternatives/ruby (Debian) to point to ruby1.8 and everything looks good now on the Dashboard! Thanks! :) On Monday, 23 June 2014 15:45:06 UTC+2, Ximena Cardinali wrote: > > Hello There, have you found a solution for this? > > I'll appreciate your help. > > Regards, > X. > > On Friday, 31 May 2013 09:04:12 UTC+2, Thomas Dahlberg wrote: >> >> I found the solution. Dashboard does not play well with ruby 1.9.3. >> I will try the rails3 branch and see if it works better. >> >> /Thomas >> >> On Wednesday, May 22, 2013 7:48:52 PM UTC+2, Jordan Hayes wrote: >>> >>> I am having this exact same issue. >>> I installed Puppet this past April, from the PuppetLabs repository on a >>> Debian Wheezy box. >>> I see these new line characters under the reports, as you have shown. >>> >>> I am also new to Puppet and new to Ruby, which makes this problem even >>> more frustrating. >>> >>> On Thursday, April 4, 2013 7:46:34 AM UTC-7, Kevin Squire wrote: >>>> >>>> I just completed the install of dashboard on a Debian Wheezy box, using >>>> the deb package provided by puppetlabs repository. After following the >>>> directions >>>> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html I >>>> now have it up and running (collecting reports only at the moment) >>>> >>>> I am noticing that on all my reports page, I get a ton of "\n" >>>> characters showing up. Since I am new to Ruby as well as Puppet, I am >>>> having a hard time finding WHY these are getting inserted. Any help would >>>> be appreciated. >>>> >>>> Attached is a screenshot showing the issue... same image is also >>>> available at http://www.wikiak.org/temp/dashboard.png >>>> >>>> >>>> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d17b6d2a-609c-4798-9bcc-7e8459c47fd0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Puppet-Dashboard All Nodes "Unresponsive", Background Tasks
Hello, I had to apply also this other Solution: mysql> describe report_logs; +---+--+--+-+-++ | Field | Type | Null | Key | Default | Extra | +---+--+--+-+-++ | id| int(11) | NO | PRI | NULL| auto_increment | | report_id | int(11) | NO | MUL | NULL|| | level | varchar(255) | YES | | NULL|| | message | blob | YES | | NULL|| | source| text | YES | | NULL|| | tags | text | YES | | NULL|| | time | datetime | YES | | NULL|| | file | text | YES | | NULL|| | line | int(11) | YES | | NULL|| +---+--+--+-+-++ 9 rows in set (0.00 sec) mysql> ALTER TABLE report_logs MODIFY message VARCHAR(65536); Query OK, 46574 rows affected, 2 warnings (0.97 sec) Records: 46574 Duplicates: 0 Warnings: 2 mysql> describe report_logs; +---+--+--+-+-++ | Field | Type | Null | Key | Default | Extra | +---+--+--+-+-++ | id| int(11) | NO | PRI | NULL| auto_increment | | report_id | int(11) | NO | MUL | NULL|| | level | varchar(255) | YES | | NULL|| | message | mediumtext | YES | | NULL|| | source| text | YES | | NULL|| | tags | text | YES | | NULL|| | time | datetime | YES | | NULL|| | file | text | YES | | NULL|| | line | int(11) | YES | | NULL|| +---+--+--+-+-++ 9 rows in set (0.00 sec) mysql> For now, everything is working as expected. We will see in a few days, or after puppetdb Upgrade. X. On Monday, 16 June 2014 16:55:25 UTC+2, Ximena Cardinali wrote: > > Hello There, > > I've been struggling the last days with this issue. The situation is > happening since I've upgrade Puppet to 3.6.0. > > *- Problem:* > On Puppet-Dashboard all Hosts are shown as *Unresponsive* and thousand of > tasks are queued as *Failed*. > > *- Environment:* > OS: Debian Wheezy > Puppet-Dashboard: 1.2.23 > Puppet: 3.6.0 > Facter: 2.0.1 > Hiera: 1.3.2 > > *- Applied Solutions:* > > * Solution 1: > cd /usr/share/puppet-dashboard/ > - Stop dashboard workers > rm -v spool/* > rake jobs:clear RAILS_ENV=production > - Start dashboard workers. > > Good solution, but temporary, because the problem after a few days comes > back. > > * Solution 2: > I've also did the following update to the DB: > mysql> ALTER TABLE delayed_job_failures MODIFY details BLOB; > Which also did not work. > > Does anyone have any idea of what can be happening there? > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/da0290f9-5120-4040-b1f4-227878317ebc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Puppet-Dashboard All Nodes "Unresponsive", Background Tasks
Hello Ramin, thanks for your answer. I just wanted to say that varchar(65536) is mediumtext. As you can see in the table descriptions: mysql> describe report_logs; +---+--+--+-+-++ | Field | Type | Null | Key | Default | Extra | +---+--+--+-+-++ | id| int(11) | NO | PRI | NULL| auto_increment | | report_id | int(11) | NO | MUL | NULL|| | level | varchar(255) | YES | | NULL|| | message | mediumtext | YES | | NULL|| | source| text | YES | | NULL|| | tags | text | YES | | NULL|| | time | datetime | YES | | NULL|| | file | text | YES | | NULL|| | line | int(11) | YES | | NULL|| +---+--+--+-+-++ 9 rows in set (0.00 sec) mysql> Also, thanks a lot for letting me know that BLOB and TEXT are 64kb while MEDIUMTEXT is 16MB. I did not have that in my mind. Cheers, X. On Wednesday, 9 July 2014 19:25:12 UTC+2, Ramin K wrote: > > It looks like you did this command 'alter table report_logs column > message mediumtext;' rather than varchar(65536). mediumtext is what it > should be changed to. Both BLOB and TEXT are 64kb while MEDIUMTEXT is > 16MB. > > Ramin > > On 7/9/2014 4:48 AM, Ximena Cardinali wrote: > > Hello, > > > > I had to apply also this other Solution: > > > > mysql> describe report_logs; > > +---+--+--+-+-++ > > | Field | Type | Null | Key | Default | Extra | > > +---+--+--+-+-++ > > | id| int(11) | NO | PRI | NULL| auto_increment | > > | report_id | int(11) | NO | MUL | NULL|| > > | level | varchar(255) | YES | | NULL|| > > | message | blob | YES | | NULL|| > > | source| text | YES | | NULL|| > > | tags | text | YES | | NULL|| > > | time | datetime | YES | | NULL|| > > | file | text | YES | | NULL|| > > | line | int(11) | YES | | NULL|| > > +---+--+--+-+-++ > > 9 rows in set (0.00 sec) > > > > mysql> ALTER TABLE report_logs MODIFY message VARCHAR(65536); > > Query OK, 46574 rows affected, 2 warnings (0.97 sec) > > Records: 46574 Duplicates: 0 Warnings: 2 > > > > mysql> describe report_logs; > > +---+--+--+-+-++ > > | Field | Type | Null | Key | Default | Extra | > > +---+--+--+-+-++ > > | id| int(11) | NO | PRI | NULL| auto_increment | > > | report_id | int(11) | NO | MUL | NULL|| > > | level | varchar(255) | YES | | NULL|| > > | message | mediumtext | YES | | NULL|| > > | source| text | YES | | NULL|| > > | tags | text | YES | | NULL|| > > | time | datetime | YES | | NULL|| > > | file | text | YES | | NULL|| > > | line | int(11) | YES | | NULL|| > > +---+--+--+-+-++ > > 9 rows in set (0.00 sec) > > > > mysql> > > > > For now, everything is working as expected. We will see in a few days, > > or after puppetdb Upgrade. > > > > X. > > > > On Monday, 16 June 2014 16:55:25 UTC+2, Ximena Cardinali wrote: > > > > Hello There, > > > > I've been struggling the last days with this issue. The situation is > > happening since I've upgrade Puppet to 3.6.0. > > > > _- Problem:_ > > On Puppet-Dashboard all Hosts are shown as *Unresponsive* and > > thousand of tasks are queued as *Failed*. > > > > _- Environment:_ > > OS: Debian Wheezy > > Puppet-Dashboard: 1.2.23 > > Puppet: 3.6.0 > > Fact
[Puppet Users] Update package (latest) only if installed in Debian
Hello There,
I'm trying to write a module to update certain vulnerable packages in
Debian Systems.
My idea is to update them only and only if they are *installed*. Is there
any exec command or any other tricks that you may know to do that?
So far, I've got the basics: :$
package { '$package_update':
name=> $package_update,
ensure => latest,
}
Can anyone throw me an idea? I will really appreciate it!
Cheers,
Ximena.
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d31b5644-478e-4d83-8606-6086479da507%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Update package (latest) only if installed in Debian
I just want to upgrade specific Packages.
The idea is something like : ensure=>latest, onlyif=>present
Cheers,
Ximena.
On Tuesday, 24 February 2015 16:43:06 UTC+1, David Schmitt wrote:
>
> On 2015-02-24 16:28, Ximena Cardinali wrote:
> > Hello There,
> >
> > I'm trying to write a module to update certain vulnerable packages in
> > Debian Systems.
> > My idea is to update them only and only if they are *installed*. Is
> > there any exec command or any other tricks that you may know to do that?
> >
> > So far, I've got the basics: :$
> >
> > package { '$package_update':
> > name=> $package_update,
> > ensure => latest,
> > }
> >
> > Can anyone throw me an idea? I will really appreciate it!
>
> What about "aptitude full-upgrade"?
>
> Regards, David
>
> --
> * Always looking for people I can help with awesome projects *
> Twitter: @dev_el_ops G+: https://plus.google.com/+DavidSchmitt
> Blog: http://club.black.co.at/log/
> LinkedIn: http://at.linkedin.com/in/davidschmitt
>
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/72682c9d-5194-4cf9-9b65-729eebd77645%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Update package (latest) only if installed in Debian
Thanks a lot everyone for the answers!
I will try to go for the "/usr/bin/apt-get install --only-upgrade
" but maybe outside of puppet.
Cheers,
Ximena.
---
*Ximena E. Cardinali *| Linux Systems Administrator
Mobile: +49-1514-72-96-542 | Skype: ximena_cardinali
E-mail: ximenacardin...@gmail.com | Blog: http://ximunix.blogspot.com/
On 25 February 2015 at 11:49, Raphink wrote:
> Hello,
>
>
> It seems that you're trying to use Puppet for actions (upgrading packages
> not managed by Puppet) instead of state. This is not what Puppet is for.
> You might want to setup unattended-upgrades with the proper Allowed-Origins
> and let the system upgrade the packages for you.
>
>
> Cheers,
>
> Raphaël
>
>
> On Tuesday, February 24, 2015 at 4:28:32 PM UTC+1, Ximena Cardinali wrote:
>>
>> Hello There,
>>
>> I'm trying to write a module to update certain vulnerable packages in
>> Debian Systems.
>> My idea is to update them only and only if they are *installed*. Is
>> there any exec command or any other tricks that you may know to do that?
>>
>> So far, I've got the basics: :$
>>
>> package { '$package_update':
>> name=> $package_update,
>> ensure => latest,
>> }
>>
>> Can anyone throw me an idea? I will really appreciate it!
>>
>> Cheers,
>> Ximena.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/MhmLUXre2CI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/ebbcf94b-079f-4ea3-9bb4-7f35b45672a9%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/ebbcf94b-079f-4ea3-9bb4-7f35b45672a9%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAJsWqD2Q2drBsNrE0Gu7eMFQ_QpnPLwqiksSffQaBAbmwE79mw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: [Puppet-dev] Debian Testing and Debian Stable leaving apt.puppetlabs.com
Hi, is it possible that the packages for Debian Jessie are still not available on the repository? Please see: http://apt.puppetlabs.com/dists/jessie/main/binary-amd64/Packages I'm trying to install puppet on some new installed servers, and I couldn't find the packages related to Debian Jessie. Regards, Ximena. On Thursday, 13 August 2015 20:12:57 UTC+2, Daniel Parks wrote: > > On Thu, Aug 13, 2015 at 9:46 AM, Melissa Stone > wrote: > >> In an effort to reduce duplication and confusion in the packages we >> provide, we will no longer be providing packages for Debian Testing or >> Debian Stable. We want to ensure we deliver tested and reliable packages, >> which includes deliberately adding new platforms that have been vetted. >> This change is part of an effort to ensure that is always the case with the >> packages we make available. >> > > To clarify, because this has confused other people too: does this mean > that you won’t be able to run Puppet from an official package on Debian > Stable? > > Or is there another repo that can be added, that’s just not specific to > Debian Testing/Stable? > > Thanks, > Daniel > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3cdb75cd-ef41-48a6-af21-e29a7b73aa52%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
