Re: [Puppet Users] Re: Disabling Certificates
Hi Derek, 2010/11/12 Derek J. Balling > [...] > Nope. Because "autosign" doesn't also "auto-overwrite". > > - New Host "foo001.domain.tld" is created > - Certs are exchanged for foo001 with the puppetmaster, life is good, > autosigned > - Host foo001.domain.tld is retired > - Replacement Host "foo001.domain.tld" is created > - foo001 tries to talk to puppetmaster, presenting brand new certs. They > don't match what the master has for that host. It tells foo001 to > pound-sand. > > At that point, I have to manually log into the CA and clean out the > certificates for foo001. I also have to go out to foo001, and blow away all > ITS certs, since it's been given a cert it has no idea what to do with. > removing the certificate is part of the retirement process, as well as removing the DNS entry, free up the IP in the CMDB, remove hardware from rack and what else needs to be done when a box is retired. Nearly all of this stuff could be scripted except the removal from the rack. Kind regards, Thomas -- 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: Disabling Certificates
Derek J. Balling wrote: > It's just ugly. Like I said in my ticket notes, I'll concede that for > some people, it's a necessity, but there's clearly also a set of > people for whom it is just unnecessary pain and suffering. > It's been my experience that SSL (or the requirement for some form of this type of security even if they disliked SSL) is actually required by the vast majority of people using Puppet. Certainly if you have any security requirements you need some kind of encryption/authentication mechanism. Without one - anyone can compromise your configuration and a daemon generally running with root privileges. But I concede there might be shops out there who don't care about this issue. I doubt it will change in a hurry - removing SSL from Puppet or abstracting it into a module as part of a refactor of security would be a large undertaking. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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.
[Puppet Users] Re: Multiple CA / Puppet master environment
Excellent, thanks for that Dan I'll take a look. On Nov 11, 5:42 pm, Dan Bode wrote: > Hi, > > On Thu, Nov 11, 2010 at 9:17 AM, luke.bigum wrote: > > > Hi, > > > Does anyone know if this document is up to date (besides the comment > > at the top saying it's not): > > >http://projects.puppetlabs.com/projects/1/wiki/Multiple_Certificate_A... > > > Or does anyone who has a load balanced multi puppet master with some > > kind of shared CA confirm that the procedure is accurate? > > I would not follow this document unless you need to use chained CAs (which > is a huge pain to get working), if you just need some instructions for > configuring multiple puppetmasters to share a single CA, I have written some > instructions here: > > http://bodepd.com/wordpress/?p=7 > > -Dan > > > -- > > 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.
[Puppet Users] Problem with service :Resource type....
hi all,
i m tring to use Service resource type as following...
service { 'tomcat':
ensure => running,
}
as I know , It will first stop tomcat , then start tomcat..
but my requirement is like that i do not want to restart it ..
, i want that if tomcat is allready running , then there is no need to
do anything.
and if stoped then , start it
Can anybody tell how can I get this functionality ?
Guide me if I had any missconception...
--
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.
[Puppet Users] Re: Problem with service :Resource type....
Hi Sanjiv,
This *should* not happen. Puppet will not restart a service if it's
already running properly. I'm going to guess that the problem is
Puppet does not KNOW that Tomcat is running properly and so thinks it
needs to restart Tomcat every run.
Does your Tomcat LSB/init script (/etc/init.d/tomcat or wherever it is
on your distro) support the status command correctly?
If it does, it should return zero if the tomcat service is running. If
this is the case you can add "hasstatus => true" to your
Service[Tomcat] declaration like so:
service { "tomcat":
ensure => running,
hasstatus => true,
}
Puppet will execute the 'status check' and use it's return value to
determine if the service is running (zero is running). For example,
here is mysqld's script:
# /etc/init.d/mysqld status
mysqld (pid x) is running...
# echo $?
0
#
The script returns zero as you can see, and Puppet does not restart
this service every time it runs.
According to the documentation (http://docs.puppetlabs.com/references/
latest/type.html#service), if you don't specify hasstatus then Puppet
will try determine the status of the service on it's own, usually by
checking the process table, so if your tomcat service does not run as
a process name of 'tomcat' this might cause problems.
One last way is to manually specify a "status => cmd" and write your
own check to determine if tomcat is running or not, but "hasstatus" is
the way most people would go I think.
-Luke
On Nov 12, 11:10 am, "sanjiv.singh"
wrote:
> hi all,
>
> i m tring to use Service resource type as following...
>
> service { 'tomcat':
> ensure => running,
>
> }
>
> as I know , It will first stop tomcat , then start tomcat..
>
> but my requirement is like that i do not want to restart it ..
>
> , i want that if tomcat is allready running , then there is no need to
> do anything.
> and if stoped then , start it
>
> Can anybody tell how can I get this functionality ?
>
> Guide me if I had any missconception...
--
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.
[Puppet Users] Re: Emulating Debians tasksel
On 12 Nov., 02:42, Joel Merrick wrote: > > However, what if the selection of packages changes? Is there a more > > clever way to install tasks with tasksel, without listing each and > > every package the tasksel task is made of? > Have you tried the meta-package gnome-desktop-environment? The package you mention is one of the 55 packages installed by the tasksel tasks. I guess tasksel tasks have to be installed with exec then. MFG, Karsten Kruse -- 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.
[Puppet Users] Re: User type password_max_age not working
Ruby shadow 1.4.1-7 was already installed so it has to be something else I will report it as a bug On Nov 11, 11:26 pm, Daniel Pittman wrote: > rvlinden writes: > > I have a virtual user (mqm) in puppet (v2.6.2 on CentOS 5.5 with Ruby > > 1.8.6.383-6) > > [...] > > > and it does get created on the server when I realze it, but each time > > I run puppet again, it reports the max_age is not set > > > notice: /Stage[main]/User::Virtual/User[mqm]/password_max_age: is > > absent, should be 9 (noop) > > notice: Finished catalog run in 0.14 seconds > > [...] > > > please help > > Mmmm. It looks to me like the adduser provider requires the Ruby 'shadow' > library to be able to get the "age" field - or it unconditionally returns > "absent" without any additional information. > > Which would explain your problem. Can you verify my guess, please? > > 1. Install the ruby shadow library, confirm if the problem goes away. > 2. If so, file a bug complaining that isn't entirely reasonable. > (At least, not silently. :) > > http://projects.puppetlabs.com/projects/puppet > > Regards, > Daniel > > -- > ✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707 > ♽ made with 100 percent post-consumer electrons -- 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] Monitor puppet runs on clients with nagios
I use tmz's puppetstatus scripts [1] [2] and they work great for checking the last run time from Nagios. I also have reports setup w/ tagmail to send me anything with "err" in it. -Doug [1] http://markmail.org/message/m6xi34aljso4w5qq [2] http://tmz.fedorapeople.org/scripts/puppetstatus/ On 11/11/2010 09:09 AM, Tim wrote: > Hi, > > I was wondering how people here monitor puppet runs on the clients. > For puppet 0.25.x I enabled reporting and then wrote a nagios plugin > to parse the YAML report files that each client returned after a run. > Specifically I was looking for any 'failures' or 'failed_restarts'. > > Unfortunately with 2.6.2 the format of those YAML files has not only > changed but also varies hugely for different hosts depending on how > the run went. Plus the sheer size of these files now means it takes > too long for PyYAML to parse them (even for only 40 odd hosts). > > In fact, I don't understand what the YAML reports are useful for - > they don't appear to realistically be either human or machine > readable. > > Anyway what other approaches are there? I'd like to simply see 2 > things: > 1) If there were any failures during the puppet run on the client > 2) When the last puppet run on each client was (ie. if it was more > than 50 mins ago raise a warning) > signature.asc Description: OpenPGP digital signature
[Puppet Users] Re: Disabling Certificates
Derek, I agree with you that the certificates are unnecessary for some people, myself included. Since we're behind a large corporate firewall, we don't need this type of security for in house management. As we upgrade our engineers workstations, the new workstation almost always has the same name as the old, and we get the same issue. I've found that I can just move the certificate on the puppet master out of the default directory with a cronjob (I move them elsewhere instead of deleting them), that way, when we upgrade the workstation, it just submits a new certificate request. This seems to work well for us, and doesn't cause any problems with the workstations connecting to the master. Jason On Nov 12, 4:28 am, James Turnbull wrote: > Derek J. Balling wrote: > > It's just ugly. Like I said in my ticket notes, I'll concede that for > > some people, it's a necessity, but there's clearly also a set of > > people for whom it is just unnecessary pain and suffering. > > It's been my experience that SSL (or the requirement for some form of > this type of security even if they disliked SSL) is actually required by > the vast majority of people using Puppet. > > Certainly if you have any security requirements you need some kind of > encryption/authentication mechanism. Without one - anyone can > compromise your configuration and a daemon generally running with root > privileges. But I concede there might be shops out there who don't care > about this issue. > > I doubt it will change in a hurry - removing SSL from Puppet or > abstracting it into a module as part of a refactor of security would be > a large undertaking. > > Regards > > James Turnbull > > -- > Puppet Labs -http://www.puppetlabs.com > C: 503-734-8571 -- 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.
[Puppet Users] Re: Realizing wrong ssh key for the wrong user
On Nov 12, 1:50 am, "Tobias Lott" wrote: > Only the correct keys are actually distributed, however this Problem > occurs only on some Machines weather its Ubuntu (10.10) 32 or 64 Bit. > Additionally the authorized_key files are being flooded with the same keys > over and over again. > F.e. if one user has only 1 Key its appended almost every run, whats the > problem there? I speculate that puppetd is being prevented from reading (some of the) authorized_keys files when it attempts to determine which keys are already installed. That would explain the error messages you reported. Somehow it can still create or update at least some of the files, however; that would explain the key duplication. Being able to write but not read a file would be very screwy, but by no means impossible. Since the problem appears only on some systems, comparing systems on which it works to systems on which it doesn't may be illuminating. Particular things to consider: * Is the Puppet client running as root? * Is SELinux enabled in enforcing mode? * Are user home directories mounted via NFS with root-squashing, such that the local root user does not have privileged accss to them? * Do any relevant files or directories (including parent directories) have strange permissions? For instance, directories with execute (or read) permission disabled? * Generally, is there some other mechanism that may be denying puppetd access to the authorized_keys files? Altthough the key duplication could easily be a symptom of the same underlying issue as the error messages, it could also reflect a separate issue. Compare the keys as installed on the client to the definitions in your manifest -- do you see anything that could explain Puppet not recognizing the installed key as the same one it wants to ensure present? > I've tried to remove the file and let puppet create it, but its still the > same. Is there anything unusual about the authorized_key files that result from this treatment? For example, unexpected UID/GID or permissions? -- 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.
[Puppet Users] Failed to generate additional resources using 'eval_generate': wrong header line format
I've upgraded to puppet v2.6.2 on ubuntu (clients and server) and now I get this error messages related to pluginsync: info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': wrong header line format err: /File[/var/lib/puppet/lib]: Could not evaluate: wrong header line format Could not retrieve file metadata for puppet://mcp.c42/plugins: wrong header line format this seems to be related to bug #4830. there was a 'workaround' to add some lib directories to my modules. I did that and it didn't work. There was another workaround that involves creating a bogus plugins mount in fileserver.conf and setting pluginsource to that mount. While that does eliminate the error, it also breaks pluginsync (not cool). my fileserver.conf looks like this: [plugins] # path /var/lib/puppet/plugins allow * my puppet.conf looks like this: [main] vardir = /var/lib/puppet logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl server = mcp.c42 factpath = $vardir/lib/facter # client = false [user] vardir = /var/lib/puppet logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl [agent] pluginsync=true #pluginsource=puppet:///plugins/ listen = true report = true classfile = $vardir/classes.txt localconfig = $vardir/localconfig runinterval = 1800 # runinterval = 21600 # Run every 6 hours It looks to me like either: a) a bug... but it doesn't seem to be a common problem which leads me to believe that it's... b) configuration related... but dudes, I've tried everything. any ideas? does anything look really, really wrong in my config? -- 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.
[Puppet Users] Re: pkgutil package provider (solaris)
On Nov 3, 4:39 pm, Nigel Kersten wrote: > We really need community testing with this provider. There are some > questions Rudy has in the ticket log that we need to get answered. > > http://projects.puppetlabs.com/issues/4258 Hi, I'm the author of pkgutil, I'm glad you're about to support it in Puppet since I get quite many requests for that. Unfortunately, I know nothing of Puppet or Python so I haven't been able to help out my users there but if there's anything you want to know about pkgutil or if you want something added/changed I will do my best to help. The (much faster) --single option came from such a request by Maciej Blizinski who contributed a new provider. I think the issue with "Not installed" vs. "notinst" is probably from converting the pkg-get provider, if I'm not mistaken pkg-get prints "Not installed" so that should just be "notinst" instead. I'm thinking about adding an option for machine parseable output to make these things better. I have changed the exit code to 0 (Rudy #10). /peter -- 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] Failed to generate additional resources using 'eval_generate': wrong header line format
Steve Neuharth wrote: > I've upgraded to puppet v2.6.2 on ubuntu (clients and server) and now > I get this error messages related to pluginsync: How did you upgrade? I've seen this when files from previous versions hung around on the master/client too. Regards James -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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] preferred directory structure for multiple environments
Thanks Daniel,
in puppet.conf on the server: (we are just trying to get a file installed to
the int environment client)
[main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
pidfile=$rundir/puppetmaster.pid
[int]
#modulepath = /etc/puppet/modules/int
#manifest = /etc/puppet/manifests/int/site.pp
manifest = /etc/puppet/int/site.pp
modulepath = /etc/puppet/int/modules
[pfm]
modulepath = /etc/puppet/modules/pfm
manifest = /etc/puppet/manifests/pfm/site.pp
[site2]
modulepath = /etc/puppet/modules/site2
manifest = /etc/puppet/manifests/site2/site.pp
[agent]
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
# libdir =
/usr/local/puppet-dashboard/lib:/usr/local/puppet-dashboard/lib/puppet
[master]
reports = http, store
environments = pfm,int,site2
#environment = pfm
---
the client puppet.conf:
[main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
[agent]
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
runinterval = 300
environment=int
report = true
# /etc/puppet/int/site.pp
import "modules"
import "nodes"
node default {
include barfoo
}
#/etc/puppet/int/modules/barfoo/manifests/init.pp
class barfoo {
file { "/tmp/myFile":
owner => root,
group => root,
mode=> 666,
source => "puppet:///modules/barfoo/myFile"
}
}
/etc/puppet/int/modules/barfoo/files/myFile exists but it doesn't get put on
the agent in the int environment. There must be something we are not seeing
here.
On Thu, Nov 11, 2010 at 4:27 PM, Daniel Pittman wrote:
> techn0gichida writes:
>
> > Moving from 2.5 to 2.6.2 and I was wondering if there is a preferred
> > directory structure for using multiple environments? Does it work much
> > different in 2.6 than in 2.5?
>
> Not really substantially, no.
>
> > When I made the move I assumed (I know) that my current structure and
> > configurations would just roll over but that isn't the case.
>
> It would be super-great if you could let us know what the problems were.
> (Perhaps you have in other messages, but better to ask twice than never
> hear
> what problems folks are hitting, I figure. :)
>
> Regards,
>Daniel
> --
> ✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155
> 707
> ♽ made with 100 percent post-consumer electrons
>
> --
> 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.
>
>
--
“Twenty years from now you will be more disappointed by the things that you
didn’t do than by the ones you did do. So throw off the bowlines. Sail away
from the safe harbor. Catch the trade winds in your sails. Explore. Dream.
Discover.”
– Mark Twain
--
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] Large hierarchy of files?
* ericlee748 [2010/11/10 14:09]: > I have a large hierarchy of files that are set up to recursively > copy from my puppet master. It takes a long while to copy these > files over to the clients - roughly 1 hour. Only 1 or 2 files in > the hierarchy will ever change. Is there a better way to do what > I'm doing? rsync in an exec ? -- When I am working on a problem I never think about beauty. I only think about how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong. -- R. Buckminster Fuller -- 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.
[Puppet Users] Re: Large hierarchy of files?
On Nov 10, 2:09 pm, ericlee748 wrote: > Hey guys, > > I have a large hierarchy of files that are set up to recursively copy > from my puppet master. It takes a long while to copy these files over > to the clients - roughly 1 hour. Only 1 or 2 files in the hierarchy > will ever change. Is there a better way to do what I'm doing? > > Thanks Someone suggested to me that we try vcsrepo and git to manage files. This has worked out very well for large file hierarchies. Git is fast, we can add config files deep in the tree if we've set up .gitignore properly and it's versioned. So far it has done the job. -- 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.
[Puppet Users] Re: Failed to generate additional resources using 'eval_generate': wrong header line format
jeez, sorry... gentoo. This is on gentoo, not ubuntu, so I used portage. I suppose I could try to scrub my puppetmaster of everything puppet related and reinstall... definitely not the ideal solution. I'll look through the ruby libs and see if I can find any dupes first. thanks James. On Nov 12, 10:06 am, James Turnbull wrote: > Steve Neuharth wrote: > > I've upgraded to puppet v2.6.2 on ubuntu (clients and server) and now > > I get this error messages related to pluginsync: > > How did you upgrade? I've seen this when files from previous versions > hung around on the master/client too. > > Regards > > James > > -- > Puppet Labs -http://www.puppetlabs.com > C: 503-734-8571 -- 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.
[Puppet Users] Dashboard throwing undefined method `to_time' for nil:NilClass error on page view
Using 1.0.4 release on Solaris 10 with Ruby 1.8.7.
Starting the server in production mode works fine until I request a
page from the web browser then I get the following errors on the
console. I'm running as user puppet (have also tried as user root but
same output). All files are owned by user/group puppet/puppet.
I have dropped and recreated the database multiple times just to see
if that was the issue.
I have removed the dashboard software and reinstalled it multiple
times to double check that I didn't mess something up.
I have no data in the DB just whatever would be there after the rake
migrate steps in the readme.
The rake migration steps run to completion without error so I know the
mysql connector is setup and working properly.
Any help would be greatly appreciated.
-bash-3.00$ ./script/server -e production
=> Booting WEBrick
=> Rails 2.3.5 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
[2010-11-12 11:51:18] INFO WEBrick 1.3.1
[2010-11-12 11:51:18] INFO ruby 1.8.7 (2010-08-16) [sparc-
solaris2.10]
[2010-11-12 11:51:18] INFO WEBrick::HTTPServer#start: pid=3348
port=3000
Processing PagesController#home (for 192.168.0.20 at 2010-11-12
11:51:54) [GET]
Parameters: {"action"=>"home", "controller"=>"pages"}
NoMethodError (undefined method `to_time' for nil:NilClass):
app/models/status.rb:7:in `initialize'
app/models/status.rb:76:in `new'
app/models/status.rb:76:in `execute'
app/models/status.rb:76:in `map'
app/models/status.rb:76:in `execute'
app/models/status.rb:66:in `by_interval'
app/controllers/pages_controller.rb:3:in `home'
haml (3.0.13) [v] rails/./lib/sass/plugin/rack.rb:41:in `call'
/opt/puppet/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/opt/puppet/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/opt/puppet/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/opt/puppet/lib/ruby/1.8/webrick/server.rb:162:in `start'
/opt/puppet/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/opt/puppet/lib/ruby/1.8/webrick/server.rb:95:in `start'
/opt/puppet/lib/ruby/1.8/webrick/server.rb:92:in `each'
/opt/puppet/lib/ruby/1.8/webrick/server.rb:92:in `start'
/opt/puppet/lib/ruby/1.8/webrick/server.rb:23:in `start'
/opt/puppet/lib/ruby/1.8/webrick/server.rb:82:in `start'
Rendering /opt/puppet-dashboard-1.0.4/public/500.html (500 Internal
Server Error)
--
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.
[Puppet Users] Re: preferred directory structure for multiple environments
I found the problem in /etc/sysconfig/puppetmaster. The MANIFEST
directive wasn't commented out. Shouldn't this be commented on that it
needs to be commented out for multiple environment use?
Thanks
On Nov 12, 10:52 am, James Louis wrote:
> Thanks Daniel,
>
> in puppet.conf on the server: (we are just trying to get a file installed to
> the int environment client)
>
> [main]
> vardir = /var/lib/puppet
> logdir = /var/log/puppet
> rundir = /var/run/puppet
> ssldir = $vardir/ssl
> pidfile=$rundir/puppetmaster.pid
>
> [int]
> # modulepath = /etc/puppet/modules/int
> # manifest = /etc/puppet/manifests/int/site.pp
> manifest = /etc/puppet/int/site.pp
> modulepath = /etc/puppet/int/modules
>
> [pfm]
> modulepath = /etc/puppet/modules/pfm
> manifest = /etc/puppet/manifests/pfm/site.pp
>
> [site2]
> modulepath = /etc/puppet/modules/site2
> manifest = /etc/puppet/manifests/site2/site.pp
>
> [agent]
> classfile = $vardir/classes.txt
> localconfig = $vardir/localconfig
>
> # libdir =
> /usr/local/puppet-dashboard/lib:/usr/local/puppet-dashboard/lib/puppet
>
> [master]
> reports = http, store
> environments = pfm,int,site2
> # environment = pfm
>
> ---
>
> the client puppet.conf:
>
> [main]
> vardir = /var/lib/puppet
> logdir = /var/log/puppet
> rundir = /var/run/puppet
> ssldir = $vardir/ssl
>
> [agent]
> classfile = $vardir/classes.txt
> localconfig = $vardir/localconfig
>
> runinterval = 300
> environment=int
> report = true
>
>
>
> # /etc/puppet/int/site.pp
>
> import "modules"
> import "nodes"
>
> node default {
> include barfoo
>
> }
>
>
>
> #/etc/puppet/int/modules/barfoo/manifests/init.pp
>
> class barfoo {
>
> file { "/tmp/myFile":
> owner => root,
> group => root,
> mode => 666,
> source => "puppet:///modules/barfoo/myFile"
> }
>
> }
>
>
>
> /etc/puppet/int/modules/barfoo/files/myFile exists but it doesn't get put on
> the agent in the int environment. There must be something we are not seeing
> here.
>
>
>
> On Thu, Nov 11, 2010 at 4:27 PM, Daniel Pittman wrote:
> > techn0gichida writes:
>
> > > Moving from 2.5 to 2.6.2 and I was wondering if there is a preferred
> > > directory structure for using multiple environments? Does it work much
> > > different in 2.6 than in 2.5?
>
> > Not really substantially, no.
>
> > > When I made the move I assumed (I know) that my current structure and
> > > configurations would just roll over but that isn't the case.
>
> > It would be super-great if you could let us know what the problems were.
> > (Perhaps you have in other messages, but better to ask twice than never
> > hear
> > what problems folks are hitting, I figure. :)
>
> > Regards,
> > Daniel
> > --
> > ✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155
> > 707
> > ♽ made with 100 percent post-consumer electrons
>
> > --
> > 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.
>
> --
> “Twenty years from now you will be more disappointed by the things that you
> didn’t do than by the ones you did do. So throw off the bowlines. Sail away
> from the safe harbor. Catch the trade winds in your sails. Explore. Dream.
> Discover.”
> – Mark Twain
--
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.
[Puppet Users] File type failing how to avoid this?
Hello, Up to right now everything is working great with puppet. I just have one questions. Is there a way to tell a type (like file) not to fail if something specific happens. Let's say I have a directory which it needs to be created if its not there and then I mount a file system "ro" on top of that. The first time it'll work but the second time it will fail with an error saying the directory is "ro" and it will fail on recursion. There has to be a way to tell puppet that when is a "ro" just check if the file is there don't create it (if you ar elooking for a file inside a "ro" direcotry) I don't know if its clear what I'm trying to achieve. Thank you. -- 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 2.6.3 - Release Candidate 3 available!
James Turnbull wrote: > We're back with a maintenance release: 2.6.3. This > release addresses some issues in the 2.6.2 release. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The worst thing about history is that every time it repeats itself, the price goes up. -- Pillar pgpKXIrbzIb9q.pgp Description: PGP signature
[Puppet Users] Re: Failed to generate additional resources using 'eval_generate': wrong header line format
OK, I unmerged and re-emerged the package and I get the same message. I also verified that all remnants of the ruby puppet stuff was gone from site_ruby before I reinstalled. I'm fairly certain that it's not my manifests as this error seems to occur in the phase where puppet is gathering it's plugins and I tried running puppetd on a server with no node defs, no classes, etc... same thing I'll cc: the package maintainer. Maybe he's seen it before. Maybe the gem at http://distfiles.gentoo.org/distfiles/puppet-2.6.2.gem is bad? On Nov 12, 11:57 am, Steve Neuharth wrote: > jeez, sorry... gentoo. This is on gentoo, not ubuntu, so I used > portage. > > I suppose I could try to scrub my puppetmaster of everything puppet > related and reinstall... definitely not the ideal solution. I'll look > through the ruby libs and see if I can find any dupes first. > > thanks James. > > On Nov 12, 10:06 am, James Turnbull wrote: > > > Steve Neuharth wrote: > > > I've upgraded to puppet v2.6.2 on ubuntu (clients and server) and now > > > I get this error messages related to pluginsync: > > > How did you upgrade? I've seen this when files from previous versions > > hung around on the master/client too. > > > Regards > > > James > > > -- > > Puppet Labs -http://www.puppetlabs.com > > C: 503-734-8571 > > -- 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.
[Puppet Users] Re: Dashboard throwing undefined method `to_time' for nil:NilClass error on page view
I have figured out that an empty database allows the dashboard to work
without failure but as soon a report from a node is added the whole
thing breaks with the to_time errors.
Clients and master are running Puppet 2.6.3.
On Nov 12, 10:01 am, Kent wrote:
> Using 1.0.4 release on Solaris 10 with Ruby 1.8.7.
> Starting the server in production mode works fine until I request a
> page from the web browser then I get the following errors on the
> console. I'm running as user puppet (have also tried as user root but
> same output). All files are owned by user/group puppet/puppet.
> I have dropped and recreated the database multiple times just to see
> if that was the issue.
> I have removed the dashboard software and reinstalled it multiple
> times to double check that I didn't mess something up.
> I have no data in the DB just whatever would be there after the rake
> migrate steps in the readme.
> The rake migration steps run to completion without error so I know the
> mysql connector is setup and working properly.
>
> Any help would be greatly appreciated.
>
> -bash-3.00$ ./script/server -e production
> => Booting WEBrick
> => Rails 2.3.5 application starting onhttp://0.0.0.0:3000
> => Call with -d to detach
> => Ctrl-C to shutdown server
> [2010-11-12 11:51:18] INFO WEBrick 1.3.1
> [2010-11-12 11:51:18] INFO ruby 1.8.7 (2010-08-16) [sparc-
> solaris2.10]
> [2010-11-12 11:51:18] INFO WEBrick::HTTPServer#start: pid=3348
> port=3000
>
> Processing PagesController#home (for 192.168.0.20 at 2010-11-12
> 11:51:54) [GET]
> Parameters: {"action"=>"home", "controller"=>"pages"}
>
> NoMethodError (undefined method `to_time' for nil:NilClass):
> app/models/status.rb:7:in `initialize'
> app/models/status.rb:76:in `new'
> app/models/status.rb:76:in `execute'
> app/models/status.rb:76:in `map'
> app/models/status.rb:76:in `execute'
> app/models/status.rb:66:in `by_interval'
> app/controllers/pages_controller.rb:3:in `home'
> haml (3.0.13) [v] rails/./lib/sass/plugin/rack.rb:41:in `call'
> /opt/puppet/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
> /opt/puppet/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
> /opt/puppet/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
> /opt/puppet/lib/ruby/1.8/webrick/server.rb:162:in `start'
> /opt/puppet/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
> /opt/puppet/lib/ruby/1.8/webrick/server.rb:95:in `start'
> /opt/puppet/lib/ruby/1.8/webrick/server.rb:92:in `each'
> /opt/puppet/lib/ruby/1.8/webrick/server.rb:92:in `start'
> /opt/puppet/lib/ruby/1.8/webrick/server.rb:23:in `start'
> /opt/puppet/lib/ruby/1.8/webrick/server.rb:82:in `start'
>
> Rendering /opt/puppet-dashboard-1.0.4/public/500.html (500 Internal
> Server Error)
--
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.
