[Puppet Users] Re: apt.puppetlabs.com to slow
I've been constantly seeing errors from apt-get update being unable to connect to apt.puppetlabs.com for months. It is very confusing because apt tries the ipv4 address first. It times out. Then, it tries the ipv6 address which for must of us results in a network unreachable; however, it doesn't display an error about the timeout and only display's the network unreachable from the ipv6 attempt. Annoying! On Wednesday, December 11, 2013 11:00:20 AM UTC-8, Rob Braden wrote: Something was up... We were running out of available http server threads. There was one particular client being a bit aggressive with the number of concurrent requests. The http server config has been tweaked a bit and that client has been throttled. At the moment, everything appears to be working normally. We will continue to monitor, but don't hesitate to speak up if you see further issues, either here or in #puppet. Thanks! Rob Braden On Wednesday, December 11, 2013 8:06:40 AM UTC-8, Tony McMahon wrote: I'm seeing this with yum.puppetlabs.com as well. Something's up, me thinks... On Wednesday, December 11, 2013 1:29:38 PM UTC, Tudor Rogoz wrote: Hello, The apt.puppetlabs.comhttp://www.google.com/url?q=http%3A%2F%2Fapt.puppetlabs.comsa=Dsntz=1usg=AFQjCNFk90AQS60pAc3n6oOj_2Lh5u6XFw repository is not responding, or is responding to slow. [0] Is a temporary issue or was moved to a different address? Tudor [0] wget http://apt.puppetlabs.com/puppetlabs-release-stable.deb --2013-12-11 13:23:30-- http://apt.puppetlabs.com/puppetlabs-release-stable.deb Resolving apt.puppetlabs.com (apt.puppetlabs.com)... 198.58.114.168, 2600:3c00::f03c:91ff:fe69:6bf0 Connecting to apt.puppetlabs.com (apt.puppetlabs.com)|198.58.114.168|:80... failed: Connection timed out. Connecting to apt.puppetlabs.com (apt.puppetlabs.com)|2600:3c00::f03c:91ff:fe69:6bf0|:80... failed: Network is unreachable. -- 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/a74b6b29-2ea3-4d79-809c-d0ab78d5a2da%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Freebsd + Puppet 3.2.2 pkg_add -f ?
I've had a little time to look at this. What looks to be happening is that
the URI class adds a hard leading slash to ftp:// uri path components which
fetch(1) doesn't handle well.
You can work around this by setting the package resource's 'source'
parameter to use the http:// scheme. Set it globally using a resource
default in your site.pp.
if $operatingsystem == 'FreeBSD' {
$majorversion = regsubst($kernelversion, '^([0-9]+)\.([0-9]+)$', '\1')
$scheme = 'http'
$host = 'ftp2.us.freebsd.org'
$urlpath =
/pub/FreeBSD/ports/${hardwareisa}/packages-${majorversion}-stable/
Package { source = ${scheme}://${host}/${urlpath} }
}
On Tuesday, August 20, 2013 12:15:38 PM UTC-7, joel johnston wrote:
So I think the core issue at this point is that no matter where I try
to set PACKAGESITE (on the server via rc, on the client via rc, on the
shell via overrides) the path to the ftp server always returns:
Error: /Stage[main]/Rsync/Package[net/rsync]/ensure: change from
absent to present failed: Execution of '/usr/sbin/pkg_add -f
ftp://ftp.freebsd.org/%2Fpub/FreeBSD/ports/amd64/packages-9-stable/All/rsync-3.0.9_3.tbz'
returned 1: pkg_add: unable to fetch 'ftp://ftp.freebsd.org/
The url is bad/wrong. For some reason it is injecting this %2F in
front of pub where it SHOULD just be /pub/
How and where is this getting set and how can I change it?
On Mon, Aug 12, 2013 at 5:54 PM, badgerious
badg...@hotmail.comjavascript:
wrote:
I should disclaim that I'm not a huge FreeBSD guy, but do have a couple
of
FreeBSD boxes around. I've been content getting all packages with
'pkg_add
-r' (which seems to work fine with the unpatched freebsd provider); no
idea
about the interactions with ports you've mentioned.
Couple of others things regarding the patch (semi tangential):
1) If you do an install of puppet 3.2.3 from ports with ruby 1.9.3, you
get
piles of warnings during puppet runs due to some class variable use in
the
freebsd provider. This is fixed in vanilla puppet 3.2.3, but undone by
the
patch.
2) If the freebsd provider is broken, seems like it should be going back
upstream rather than patching in the port (forgive my ignorance if this
is
in fact happening and the patch is interim).
Eric
On Monday, August 12, 2013 3:35:41 PM UTC-5, Russell Jackson wrote:
The standard provider doesn't work with packages that have multiple
origins (the apache ports for instance) because the package name
doesn't
match was is recorded in the package database. So, what will happen is
that
puppet will think the package isn't installed on every run and attempt
to
install it.
The only sane way around that was to use the package origin as a key
and
duplicated the '-r' functionality in the provider; this is what the
patch
does. Passing '-f' to pkg_add was questionable, but I remember there
being
problems without it.
--
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/1CqH0u84u6g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
puppet-users...@googlegroups.com javascript:.
To post to this group, send email to
puppet...@googlegroups.comjavascript:.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
___
Joel Johnston
760.437.5116
www.metaband.net
www.j03l.com
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Freebsd + Puppet 3.2.2 pkg_add -f ?
The standard provider doesn't work with packages that have multiple origins (the apache ports for instance) because the package name doesn't match was is recorded in the package database. So, what will happen is that puppet will think the package isn't installed on every run and attempt to install it. The only sane way around that was to use the package origin as a key and duplicated the '-r' functionality in the provider; this is what the patch does. Passing '-f' to pkg_add was questionable, but I remember there being problems without it. On Thursday, August 8, 2013 6:09:07 AM UTC-7, badgerious wrote: Did you install puppet from ports? I did a 3.2.3 install recently and noticed that there is a patchhttp://svnweb.freebsd.org/ports/head/sysutils/puppet/files/optpatch-package_origin?revision=311088view=markupin that port that reverts back to an older version of the freebsd package provider, apparently for ruby 1.8 compatibility. I got rid of the optpatch-package_origin file and reinstalled the port to get the proper package provider, which does indeed use '-r'. Eric -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Announcing Razor
On 05/23/2012 05:10 PM, James Turnbull wrote: Puppet Labs is really thrilled to announce, in conjunction with EMC, our new open source bare metal provisioning tool: Razor. Razor is next generation provisioning software that handles bare metal hardware and virtual server provisioning with inventory discovery and tagging, rule-based policy management, and extensible broker plugin integration. It integrates closely with Puppet and Facter. The full announcement and a module to install it is on the Puppet Labs blog: http://puppetlabs.com/blog/puppet-razor-module/ This excellent post from Nick Weaver, the EMC guy behind the original idea, takes you through the history, background and workflow of Razor: http://nickapedia.com/2012/05/21/lex-parsimoniae-cloud-provisioning-with-a-razor/ And finally - being open source - you can find the code at: https://github.com/puppetlabs/Razor Regards James Turnbull I take it the actual microkernel isn't open source? All I can find is a ISO image. -- Russell A. Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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.
Re: [Puppet Users] Dashboard Delayed Workers Error: Mysql::Error: MySQL server has gone away
On 08/05/2011 02:59 AM, dave-stfu wrote: Hello Recently, I've upgraded the Dashboard from 1.2rc3 to 1.2rc5. Now, the delayed workers are dying right after I start them. The production.log says: Delayed::Backend::ActiveRecord::Job Update (0.0ms) Mysql::Error: MySQL server has gone away: UPDATE `delayed_jobs` SET locked_by = null, locked_at = null WHERE (locked_by = 'delayed_job.1 host:puppet pid:16839') #ActiveRecord::StatementInvalid: Mysql::Error: MySQL server has gone away: UPDATE `delayed_jobs` SET locked_by = null, locked_at = null WHERE (locked_by = 'delayed_job.1 host:puppet pid:16839') The Dashboard itself is running smoothly. Also, running rake jobs:work runs without any problems - it does the delayed jobs. The settings are the same as in rc3 (user, permissions, db config). Could this be the result of updated gems in rc5? Cheers! Dave This issued was fixed for me after I did a pull on the 1.2rc branch this morning. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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.
Re: [Puppet Users] PC EU feedback: exported resource syntax is too magical, hard to read
On 05/20/2011 01:24 PM, Randall Hansen wrote:
http://projects.puppetlabs.com/issues/7612
The exported resources syntax:
@@user { luke: ensure = present }
Is concise and powerful, but very difficult to read. We should
consider word-based syntax, e.g.:
export @user { luke: ensure = present }
And taking into account #7605, perhaps:
export virtual user { luke: ensure = present }
Yes on both counts. My coworkers have often commented on the cryptic
nature of this construct, and googling for 'puppet @@' doesn't return
anything immediately useful. Googling for 'puppet virtual export', on
the other hand, does. In fact, the first hit is the documentation on
Exporting and Collecting Resources.
--
Russell A Jackson r...@csub.edu
Network Analyst
California State University, Bakersfield
--
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.
Re: [Puppet Users] Puppet Dashboard on Freebsd 8.2
On 05/12/2011 07:37 PM, Panaman wrote: Is anyone running the puppet dashboard on freebsd 8.2 I am kinda a newb to freebsd but managed to get puppet installed with apache and mysql. But I haven't actually figured out how to get the dashboard to install. I have it running on FreeBSD 8.x. Hint: don't use ports to install ruby dependencies for anything having to do with rails. Use gem to install all of them. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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.
Re: [Puppet Users] Git Workflow
On 05/03/2011 09:16 AM, Stefan Schulte wrote: Hi, I would like to know how your workflow looks like when you're writing manifests. Currently we have the following construct: * 1 git repository with all modules * 3 git branches: dev, staging, prod * 3 puppet environments: dev, staging, prod The modulepath of each environment is a checkout of the corresponding branch. Writing/Editing manifests only happens in dev. If you're done you commit your work to a central repo. If dev is somewhat stable it is merged into staging (fast-forward-merge) etc. This comes with a few problems: * If all your systems are running prod and you change something big (e.g. new filesystem layout) you only have too options: Change all your machines to follow the new standard or take the machines you cannot change out of puppet control. * There are changes I make in dev that I want to take immediate effect. Example: Deploy the SSH-Key of a new employee to all machines. I can add the key in dev and then cherry-pick the commit in the other branches but I'm not yet sure if that is really a good idea. So how do you use environments and branches? One Repository for each module or one repository for all modules? Do you use git tag to tag certain revisions? Do you run your servers agains different releases of your manifests or do you just have one prod environment? I'd recommend one repository per module. I don't use tags at all. Changes are introduced into the development branch and get merged into the production branch. Differences between servers are typically handled within the module classes (i.e. subclass/conditionals/selectors) rather than having them run against different versions of the module. I can't see how you could keep a sane environment otherwise. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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.
Re: [Puppet Users] Installing port on FreeBSD
On 04/20/2011 02:45 PM, Nigel Kersten wrote:
On Fri, Apr 15, 2011 at 3:26 PM, fafaforza fafafo...@gmail.com wrote:
New user trying to get a port to compile: I tried searching but all I
get are links to the FreeBSD port of puppet. Easier to find a needle
in a haystack.
A class has:
exec { port-sudo:
cwd = /usr/ports/security/sudo,
environment = BATCH=yes,
command = '/bin/sh -c /usr/bin/make install',
path= [/bin/, /usr/bin/, /usr/local/bin/, /sbin/, /
usr/sbin/, /usr/local/sbin/],
returns = 1,
}
Shouldn't you be using the ports package provider instead?
package { sudo:
provider = ports,
ensure = installed,
}
I haven't touched Puppet on FreeBSD personally, it may auto-detect the
provider automatically for you correctly.
The ports provider doesn't work due to bugs in portupgrade when run
without a controlling tty. I opened a problem report about this sometime
ago and recommended removing the provider entirely.
The port (sysutils/puppet) already patches the providers to demote the
ports provider in favor of the package provider. There's also an
optional (but enabled by default) patch to use an alternate package
provider that uses the port origin as the package name as well as
utilizing the INDEX for name resolution.
http://github.com/xraj/puppet/commits/freebsd%2Fpackage
--
Russell A Jackson r...@csub.edu
Network Analyst
California State University, Bakersfield
--
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.
Re: [Puppet Users] Installing port on FreeBSD
On 04/21/2011 11:05 AM, Nigel Kersten wrote: On Thu, Apr 21, 2011 at 11:03 AM, Russell Jackson r...@csub.edu wrote: The ports provider doesn't work due to bugs in portupgrade when run without a controlling tty. I opened a problem report about this sometime ago and recommended removing the provider entirely. I'll chase this up now Russell. The port (sysutils/puppet) already patches the providers to demote the ports provider in favor of the package provider. There's also an optional (but enabled by default) patch to use an alternate package provider that uses the port origin as the package name as well as utilizing the INDEX for name resolution. http://github.com/xraj/puppet/commits/freebsd%2Fpackage Which package provider is preferred over the ports provider Russell? package/freebsd.rb Have those patches been sent to the dev-list for merging into upstream ? An older incarnation was, but died and never went anywhere. On the other hand, I haven't been very good about pushing for it either. There are also a few competing provider rewrites. I thought I'd let the community decide which one was best, but that doesn't appear to be happening either. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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.
Re: [Puppet Users] provisioning bare metal (best practices)
On 02/22/2011 10:14 AM, James A. Peltier wrote: - Original Message - | I thought about DHCP for static addresses. I'd need the MAC for each | machine snip This is not necessarily true. If you configure the client to send a requested hostname it will not require you to register the MAC address, although, as per the usual this is a security risk since anyone on the network could pose as a machine if they knew that was the setup. ;) Only if you have a flat network. A host can't get an address for a subnet they're not in. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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.
Re: [Puppet Users] Puppet on a purely push basis no possible?
On 02/18/2011 11:32 AM, Daniel Pittman wrote: On Thu, Feb 17, 2011 at 12:16, Russell Jackson r...@csub.edu wrote: On 02/15/2011 05:37 PM, James Louis wrote: in spite of this not actually being a push mechanism if it walks like a duck. it would be nice if the documentation and previous discussions on this were more clear or even better if it's not a push then the it should be redefined within puppet world. IMHO Actually, almost anything that is referred to as push is usually implemented as some sort of pull trigged via a notification mechanism. That seems an odd claim in general, but whatever. In the specific case of puppet we have a prototype for a static compiler that we are working on internally. The goal is to allow a set of files, catalog included, to be pushed out from the central server to the client, with no loss of fidelity or control. So, we are sympathetic to the requirement for a genuine push solution (which is actually push), and are working on solutions to the problem. They don't even have a roadmap date yet, though, I fear. :) Well, let look at push email in IMAP for example. The client connects to the server and issues the IDLE command and waits for the server to send a notification via an EXISTS response that a mailbox has new mail. The client then pulls the email from the server the usual way. The server doesn't ever actually push email to the client, but it's still referred to as push email. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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.
Re: [Puppet Users] Puppet on a purely push basis no possible?
On 02/15/2011 05:37 PM, James Louis wrote: in spite of this not actually being a push mechanism if it walks like a duck. it would be nice if the documentation and previous discussions on this were more clear or even better if it's not a push then the it should be redefined within puppet world. IMHO Actually, almost anything that is referred to as push is usually implemented as some sort of pull trigged via a notification mechanism. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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.
Re: [Puppet Users] freebsd rc.conf type - looking for beta testers
On 02/07/2011 09:30 AM, Ross W wrote:
While working on a bunch of freebsd servers, one feature that I found
lacking was the ability to nicely modify rc.conf variables (eg:
item_flags=--something) for installed ports/applications and have a
service do dependency checking so it restarts if it changes.
You can already use augeas to do this.
augeas { item_flags:
context = /files/etc/rc.conf,
changes = set item_flags '--something'
}
The textproc/augeas port has lens for both /etc/rc.conf and
/boot/loader.conf
--
Russell A Jackson r...@csub.edu
Network Analyst
California State University, Bakersfield
--
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.
Re: [Puppet Users] Can one definition require another definition?
On 11/16/2010 11:21 AM, Yushu Yao wrote: Hi Experts, *The question is: Won't it help if Puppet support require=Definition[inst_a] directly?* Or am I missing some important issues? Defines are macros. The macro itself doesn't exist in the catalog; only the generated resources do. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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] Can one definition require another definition?
On 11/16/2010 11:33 AM, Nan Liu wrote:
On Tue, Nov 16, 2010 at 11:21 AM, Yushu Yaoy...@lbl.gov wrote:
Hi Experts,
I am in a situation that need one definition to require another (to enforce
execution order). E.g.
define a(x,y,z) {
do task 1
}
define b(u,v,w) {
so task 2
}
To use them:
Below won't make sure task 1 is executed before task 2 (or does it?):
The question is:
Won't it help if Puppet support require=Definition[inst_a] directly?
Yes it supports it.
a { inst_a:
x=x, ...
}
b { inst_b:
u=u, ...
require=A[inst_a],
}
Just capitalize the first letter:
define foo:bar ...
require = Foo:Bar[..]
I stand corrected. It does work.
I've always thought of defines as macros, but apparently they are
objects themselves. I'm still confused why they don't appear in my
catalogs. Would nesting them inside of classes have anything to do with
that?
--
Russell A Jackson r...@csub.edu
Network Analyst
California State University, Bakersfield
--
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] FreeBSD puppetd CSRs being ignored by puppetmaster
On 10/21/2010 03:01 AM, sasepp wrote: Hi, I'm trying to deploy puppetd 0.25.4 (from ports) on two servers running FreeBSD 8.0-RELEASE and 8.1-RELEASE. Are you sure you installed this from ports? Ports currently has version 2.6.2. -- Russell A. Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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] Disabling Puppet
On 10/21/2010 02:56 PM, Douglas Garstang wrote: On Thu, Oct 21, 2010 at 2:48 PM, Patrickkc7...@gmail.com wrote: On Oct 21, 2010, at 2:30 PM, Douglas Garstang wrote: Having some issues disabling puppet. I want to use scripts to update RPM's, and obviously you need to quiesce puppet first. The pid file directory is empty: [pax] app01 ~:# ls -l /var/run/puppet/ total 0 Puppet is stopped: [pax] app01 ~:# service puppet status puppetd is stopped Really really stopped: [pax] app01 ~:# ps -ef | grep puppet root 13079 7958 0 21:27 pts/000:00:00 grep puppet So, I start puppet: [pax] app01 ~:# service puppet start Starting puppet: [ OK ] The pid file exists, and it's pid matches the running puppet: [pax] app01 ~:# cat /var/run/puppet/agent.pid 13612 [pax] app01 ~:# ps -ef | grep puppet root 13612 1 22 21:28 ?00:00:08 /usr/bin/ruby /usr/sbin/puppetd root 13978 7958 0 21:28 pts/000:00:00 grep puppet And, then I try and disable puppet: [pax] app01 ~:# puppetd disable Could not prepare for execution: Could not create PID file: /var/run/puppet/agent.pid What's up with that? This is puppet 2.6.1. If you are going this far, why not use service puppet stop? That sounds safer to me. Because puppet might be in the middle of a run when you stop it, and does anyone know what the worse case scenario is there? I believe puppet finishes the current catalog run when it receives a SIGTERM. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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] First boot with Puppet
On 10/14/2010 03:49 PM, Michal Ludvig wrote:
On 10/15/2010 08:36 AM, Arnau Bria wrote:
On Thu, 14 Oct 2010 23:47:16 +1300
Michal Ludvig wrote
1) kickstart installs the system, including puppet from our local repo
2) after reboot I have to login and set the hostname and IP
kickstart is able to configure your network / hostname. Why don't you
use that feature?
Because we've got a common kickstart for all installs, not a per-host
kickstart. It only installs the very core system and the rest is brought
in and configured by puppet.
We're moving to cobbler,
Looks like cobbler is the prefered method here. I'll give it a try.
You can pass in arguments to the kernel via the bootloader which the
kickstart pre-script then read in.
Example.
while read key value; do
eval karg_${key}='${value:-1}'
done - EOF
$( /proc/cmdline sed 's/ /\n/g' | sed 's/=/\t/1')
EOF
Which are then used later in the script to set kickstart parameters or
wherever needed.
Then at the syslinux boot prompt, I do:
install-centos-5 ip=10.0.0.1/24 hostname=host.domain foo
which will install variables like so:
karg_ip=10.0.0.0/24
karg_hostname=host.domain
karg_foo=1
--
Russell A Jackson r...@csub.edu
Network Analyst
California State University, Bakersfield
--
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] Installing MySQL on FreeBSD
On 10/07/2010 10:43 AM, Ross W wrote:
Sorry to get this way late, but I've got a solution for you if you haven't
found it already. So I'm putting this into the archives.
On Sun, Sep 12, 2010 at 10:32 AM, FreddieBfreddie.bra...@gmail.com wrote:
Hi everyone,
I have an interesting problem I think.
I'm trying to install MySQL on FreeBSD. This is what I have in my
init.pp of the module:
start --
package { 'MySQL-server' :
name = $operatingsystem ? {
freebsd = 'mysql51-server',
debian = 'mysql-server-5.0',
default = 'mysql51-server',
},
ensure = installed,
}
- end
When I run puppet this works fine, MySQL gets installed.
But, when I run it a second time I get an error:
I rewrote the freebsd package/port provider a while ago and it's in the tree
- if you can handle having the portupgrade system installed, it should fix
your problem. Also ensure = latest works.
Use the portupgrade provider, and specify the package name as the _full
origin_ database/mysql51-server.
I'd note that portupgrade is buggy when run non-interactively. You may
have problems with puppet hanging and have script instances spinning
on the CPU at 100%. YMMV.
If you've got custom compile options, then you can just make a dependency to
/var/db/ports/name/options so they get compiled correctly as well.
The format of the files and layout of /var/db/ports is considered
private. Only the ports framework should mess with it. If you're going
to set compile options by hand, they belong in /etc/make.conf.
--
Russell A Jackson r...@csub.edu
Network Analyst
California State University, Bakersfield
--
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: FreeBSD Puppet 2.6.1 odd core-dump
On 09/21/2010 12:47 PM, FreddieB wrote: Splendid! The time was off by months. Apparently FreeBSD's ntpd doesn't handle this to well (it just quits) so an initial ntpdate -b got it back on track, and after that both nptd and puppet works fine. I've always set my machines to boot with ntpdate_enable=YES. -- Russell A. Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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: Installing MySQL on FreeBSD
On 09/12/2010 02:51 PM, FreddieB wrote:
Problem just keep hitting me...
Can anyone see why this simple script fails:
--- start
class mysql-server {
Package['mysql-server'] - Service['mysql']
package { mysql-server :
name = mysql-server,
ensure = installed,
}
service { mysql :
name= 'mysql-server',
require = Package['mysql-server'],
ensure = running,
enable = true,
}
--- end
Removing the name parameter from the service definition lets it work. I
understand why you set name, and it seems like you should be able to.
This seems like a bug. Setting name on the service shouldn't cause the
resource title to not work.
--
Russell A Jackson r...@csub.edu
Network Analyst
California State University, Bakersfield
--
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] Installing MySQL on FreeBSD
On 09/12/2010 07:32 AM, FreddieB wrote: I looks like Puppet is not able to figure out that MySQL 5.1 is already installed. If I list the packages installed (with pkg_info) I find MySQL there but it's not called mysql51-server but mysql- server-5.1.48. If I go back to my init.pp and change the name from mysql51-server to just mysql-server, it works again (i.e. it will not try to install the package again). It is not possible to start with just mysql-server, because there is no package called just mysql-server. My conclusion is that FreeBSD's inconsistent way of naming the packages fools Puppet to think it's not installed. I've never written a line of ruby-code so I could use some help here. Can anyone think of a good workaround? BTW - my current, and not so pretty workaround is to link mysql- server.tbz to mysql51-server.tbz on my local FreeBSD-mirror-site. Yes. The package system has turned out to be a royal PITA for puppet. I don't have any good work-a-rounds at the moment. I think we might be able to do something by specifying the package name as the port origin (pkg_info -o) and looking up the right package out of ports/INDEX. There's been some discussion on the freebsd-ports list about improving the pkg_* tools and ports in general. I'm tempted to just say use APT and call it good. There's zero chance of that happening due to licensing. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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] Installing MySQL on FreeBSD
On 09/13/2010 09:59 AM, Russell Jackson wrote:
On 09/12/2010 07:32 AM, FreddieB wrote:
I looks like Puppet is not able to figure out that MySQL 5.1 is
already installed. If I list the packages installed (with pkg_info) I
find MySQL there but it's not called mysql51-server but mysql-
server-5.1.48. If I go back to my init.pp and change the name from
mysql51-server to just mysql-server, it works again (i.e. it will
not try to install the package again). It is not possible to start
with just mysql-server, because there is no package called just
mysql-server.
My conclusion is that FreeBSD's inconsistent way of naming the
packages fools Puppet to think it's not installed. I've never written
a line of ruby-code so I could use some help here. Can anyone think of
a good workaround?
BTW - my current, and not so pretty workaround is to link mysql-
server.tbz to mysql51-server.tbz on my local FreeBSD-mirror-site.
Yes. The package system has turned out to be a royal PITA for puppet. I
don't have any good work-a-rounds at the moment. I think we might be
able to do something by specifying the package name as the port origin
(pkg_info -o) and looking up the right package out of ports/INDEX.
I imagine it could work something like this:
# Download the ports index
mkdir /tmp/ports-index
cd /tmp/ports-index
fetch
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.1-release/INDEX.bz2
bunzip2 INDEX
# Lookup package name from origin path
pkgname=$(awk -F\| '{ if ($2 == /usr/ports/databases/mysql51-server)
print $1 }' INDEX)
pkg_add -r
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.1-release/All/${pkgname}.tbz
Checking if the package was installed could be done with pkg_info -O:
pkg_info -O databases/mysql51-server | tail -n+2 | grep -qc '$'
echo 'installed' || echo 'not installed'
Then the resource definition would look like this:
package { mysql-server:
name = $operatingsystem ? {
FreeBSD = databases/mysql51-server,
default = mysql-server,
},
ensure = installed,
}
--
Russell A Jackson r...@csub.edu
Network Analyst
California State University, Bakersfield
--
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] Installing MySQL on FreeBSD
On 09/13/2010 11:26 AM, Russell Jackson wrote:
On 09/13/2010 09:59 AM, Russell Jackson wrote:
On 09/12/2010 07:32 AM, FreddieB wrote:
I looks like Puppet is not able to figure out that MySQL 5.1 is
already installed. If I list the packages installed (with pkg_info) I
find MySQL there but it's not called mysql51-server but mysql-
server-5.1.48. If I go back to my init.pp and change the name from
mysql51-server to just mysql-server, it works again (i.e. it will
not try to install the package again). It is not possible to start
with just mysql-server, because there is no package called just
mysql-server.
My conclusion is that FreeBSD's inconsistent way of naming the
packages fools Puppet to think it's not installed. I've never written
a line of ruby-code so I could use some help here. Can anyone think of
a good workaround?
BTW - my current, and not so pretty workaround is to link mysql-
server.tbz to mysql51-server.tbz on my local FreeBSD-mirror-site.
Yes. The package system has turned out to be a royal PITA for puppet. I
don't have any good work-a-rounds at the moment. I think we might be
able to do something by specifying the package name as the port origin
(pkg_info -o) and looking up the right package out of ports/INDEX.
I imagine it could work something like this:
# Download the ports index
mkdir /tmp/ports-index
cd /tmp/ports-index
fetch
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.1-release/INDEX.bz2
bunzip2 INDEX
# Lookup package name from origin path
pkgname=$(awk -F\| '{ if ($2 == /usr/ports/databases/mysql51-server)
print $1 }' INDEX)
pkg_add -r
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.1-release/All/${pkgname}.tbz
Checking if the package was installed could be done with pkg_info -O:
pkg_info -O databases/mysql51-server | tail -n+2 | grep -qc '$'
echo 'installed' || echo 'not installed'
Hum... I'm just realizing that the Latest tree on the ftp mirror sort of
already is a mapping from the origin (without the category) to the
package name. So the install method can stay the same and just modify
the pkg_info lookup to use pkg_info -O '*/package_name'
--
Russell A Jackson r...@csub.edu
Network Analyst
California State University, Bakersfield
--
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] puppet 2.6.0 vs apache/mod_passenger
I'm having a hell of a time with mod_passenger. Where would I even begin to investigate where this exception is coming from? My configuration works fine with the 2.6.0 webrick server. [Thu Jul 29 18:03:00 2010] [error] [client 136.168.1.4] Premature end of script headers: preamble [ pid=28460 file=ext/apache2/Hooks.cpp:735 time=2010-07-29 18:03:00.77 ]: The backend application (process 30417) didn't send a valid HTTP response. It might have crashed during the middle of sending an HTTP response, so please check whether there are crashing problems in your application. This is the data that it sent: [Content-Type] *** Exception NoMethodError in PhusionPassenger::Rack::ApplicationSpawner (undefined method `each' for 3238:Fixnum) (process 30417): from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:100:in `process_request' from /usr/local/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/utils.rb:278:in `each' from /usr/local/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/utils.rb:277:in `each' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:96:in `process_request' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:120:in `run' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:65:in `spawn_application' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/utils.rb:252:in `safe_fork' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:58:in `spawn_application' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:41:in `spawn_application' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:150:in `spawn_application' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:278:in `handle_spawn_application' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in `__send__' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in `main_loop' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously' from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/bin/passenger-spawn-server:61 -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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] puppet 2.6.0 vs apache/mod_passenger
On 08/02/2010 10:26 AM, Christopher Johnston wrote: Can you paste gem list? # gem list *** LOCAL GEMS *** actionmailer (2.3.8) actionpack (2.3.8) activerecord (2.3.8) activeresource (2.3.8) activesupport (2.3.8) fastthread (1.0.7) passenger (2.2.15) rack (1.1.0) rails (2.3.8) rake (0.8.7) ruby-augeas (0.3.0) sources (0.0.2) On Mon, Aug 2, 2010 at 1:17 PM, Russell Jackson r...@csub.edu wrote: I'm having a hell of a time with mod_passenger. Where would I even begin to investigate where this exception is coming from? My configuration works fine with the 2.6.0 webrick server. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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] puppet 2.6.0 vs apache/mod_passenger
On 08/02/2010 10:35 AM, Christopher Johnston wrote: Looks good from what I can tell, did you setup the config.ru? Yep. Got the modified one for the puppetmaster - server class rename. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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] puppet 2.6.0 vs apache/mod_passenger
On 08/02/2010 10:35 AM, Christopher Johnston wrote: Looks good from what I can tell, did you setup the config.ru? Can I take this to mean that you have a working passenger installation of 2.6.0? Knowing that it can work would at least narrow it down to a local installation issue rather than a bug in puppet. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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] puppet 2.6.0 vs apache/mod_passenger
On 08/02/2010 11:24 AM, Christopher Johnston wrote: I have not played with 2.6.0 yet, but I do have it working fine with .25 just fine. Same here. Worked in 0.25.5. Stopped working 2.6.0. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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] puppet 2.6.0 vs apache/mod_passenger
On 08/02/2010 11:46 AM, Thorsten Biel wrote: Hi, On Mon, Aug 2, 2010 at 7:38 PM, Russell Jackson r...@csub.edu wrote: On 08/02/2010 10:35 AM, Christopher Johnston wrote: Looks good from what I can tell, did you setup the config.ru? Can I take this to mean that you have a working passenger installation of 2.6.0? Knowing that it can work would at least narrow it down to a local installation issue rather than a bug in puppet. I have a working installation with 2.6.1 (actually, 2.6.0 and the RCs before that worked, too). This on Ubuntu 10.4 with mod_passenger 2.2.15 installed via gem. Also, I had to upgrade rack from 1.0.1 to 1.2.1, notably removing all traces of the old rack version. With rack 1.0.1 the master actually did work, but would crash with manifests using the file type with more than one source. Confirmed. It just happens that the node I was using to test against had a such a manifest. Tested against a node that didn't, and I didn't get the error. -- Russell A Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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] sysutils/puppet: disabling freebsd ports package provider
Is there any objection to the ports provider being disabled on FreeBSD systems since it mostly just causes puppet to hang anyway? I've had no luck in fixing it. The problem is that portupgrade and script don't interact well when running non-interactively. I've been running it this way in a local port, and I'm thinking of disabling it in the official port as well. I'd post a patch for upstream as well. If there are no objections, I'll submit a PR for the change by the end of the week. Thanks, -- Russell A. Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- 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: Have a good workaround for network service on Fedora?
Bryan Kearney wrote:
Has anyone solved status checking for the network service on fedora?
Since it always returns success, using 'hastatus = true' does not work.
We have some recipes that always cause the network service to restart
even when it does not need to.
Override 'pattern'. The daemon's name often doesn't match the service name, and
the
default pattern sometimes also matches more than it should out of the process
list (e.g.
the service name is a substring of another process' name).
For example, the autofs service:
service { autofs:
ensure= stopped,
enable= false,
hasstatus = false,
pattern = \bautomount\b,
}
The '\b' matches word boundaries which forces it to match the entire word
rather than any
substring. While not strictly necessary in this example, I included it for
completeness.
--
Russell A. Jackson [EMAIL PROTECTED]
Network Analyst
California State University, Bakersfield
He that would govern others, first should be the master of himself.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
