I have some belief that I've successfully assembled the various bits for
'puppet-runtime' (v6.4). Now Im trying to build the puppet-agent (also
v6.4).
At the end of the runtime build I have these 4 files:
-rw-r--r-- 1 pocl root 514 Aug 11 12:53
agent-runtime-6.4.x-201906190.debian-9-arm-b
I'm wondering if puppet could be used to collect `sar` style data. Does
such a module exist? Is this outside the intended use of facter?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails fr
On Friday, January 23, 2015 at 5:04:54 AM UTC-8, Nick Howes wrote:
>
> On Tuesday, 20 January 2015 20:00:14 UTC, JonY wrote:
>
> I'm hoping to use this library (or something similar) to request a single
>> fact from all nodes. The equiv curl request would be 'curl -X
y service that I
monitor with puppet.
On Tuesday, January 20, 2015 at 12:19:12 PM UTC-8, JonY wrote:
>
> Debian 6 machine running 3.7.1. Attempts to run 'puppet agent --test' give
> a stream of errors like this:
>
> invoke-rc.d: WARNING: 'invoke-rc.d dnsmasq start&#x
Debian 6 machine running 3.7.1. Attempts to run 'puppet agent --test' give
a stream of errors like this:
invoke-rc.d: WARNING: 'invoke-rc.d dnsmasq start' called
invoke-rc.d: during shutdown sequence.
invoke-rc.d: enabling safe mode: initscript policy layer disabled.
If I do a 'service dnsmasq
I'm hoping to use this library (or something similar) to request a single
fact from all nodes. The equiv curl request would be 'curl -X GET
http://host:8080/v3/facts --data-urlencode 'query=["=","name","fs_space"]'.
I've been looking at the docs on
'https://github.com/puppetlabs/puppetdb-ruby'
e
problem - if wvdial isn't running then the puppet agent will fail so the
exec script won't get run.
Is there a way around this? Or do i need to use a cron to fix this?
On Tuesday, December 9, 2014 6:12:35 AM UTC-8, jcbollinger wrote:
>
>
>
> On Monday, December 8, 2
Anything? Some cached set?
--
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
> Its not for lack of packages...rather how they get installed that's the
> issue. The AMI is installing ruby 1.8 AND 2.0 when 'yum install
> puppet-server' runs. PS can't find its packages when it tries to run.
In any event I'll try a diff package and see if I get any further.
--
You received t
AME="cpe:/o:amazon:linux:2014.09:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/";
In any event - you were right about it being a duplicate of an existing
bug.
On Friday, November 14, 2014 9:18:53 AM UTC-8, Kylo Ginsberg wrote:
>
> On Fri, Nov 14, 2014 at 6:03 AM, Ky
Since p-server 3.7 doesn't appear to work on the AWS linux AMI how about
creating an AMI that does work?
--
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-
AMI? I'm new to this world.
On Thursday, November 13, 2014 2:42:31 PM UTC-8, Felix.Frank wrote:
>
> On 11/13/2014 08:00 PM, JonY wrote:
> > Installed latest from puppetlabs repro on an EC2 instance.
>
> ...running...which platform?
>
--
You received this message bec
y from this system
and when I reinstall 'puppet-server' it brings down both ruby 1.8 and 2.0.
The 'command_line.rb' file is put in 1.8 but the interpreter runs with 2.0.
On Thursday, November 13, 2014 11:00:01 AM UTC-8, JonY wrote:
>
> Installed latest from puppetlabs rep
Installed latest from puppetlabs repro on an EC2 instance.
Started working through steps
from https://docs.puppetlabs.com/guides/install_puppet/post_install.html
# puppet master --verbose --no-daemonize
/usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:55:in
`require': cannot
I put together a module and some files to control cassandra. When I change
one of the dependent files in my module the cassandra service is stopped
but not restarted.
The service uses a std start/stop/status file and 'status' sets the
appropriate exit code:
[root@cass1 security]# service cass
On Tuesday, November 11, 2014 11:12:37 PM UTC-8, Felix.Frank wrote:
>
> On 11/01/2014 01:46 PM, JonY wrote:
> > 2. Maintain two (nearly identical - but not quite) file trees. It's
> > all in git so maybe this isn't so bad. Looks messy though. Means
> > ha
Situation: systems come from imaging with /var/tree full of (a hierarchy
of) stuff that needs to be removed and replaced. I have a 'file/force =>
true/recurse => true' resource setup to accomplish this.. short and to the
point...works great..replaces the folder hierarchy with a new one.
Along
on when Puppet calls it. If you fail to generate *any* log
> output, this likely means that Ruby won't even start interpreting your
> code.
>
> HTH,
> Felix
>
> On 10/31/2014 02:20 AM, JonY wrote:
> > Im recoding an ENC in ruby (from Perl). The new version gives
Im recoding an ENC in ruby (from Perl). The new version gives me the error:
Oct 30 18:03:25 serv puppet-master[29051]: Failed when searching for node
nodexx: Failed to find nodexx via exec: Execution of ' nodexx'
returned 1:
What I've checked:
- both can be run under the 'puppet' account ("sud
Would like to upgrade Ruby to the latest. To make everything on my puppet
server happy I need to remove the Ruby 1.8.7 that YUM installed.
When I run 'yum erase ruby' it looks like it will also remove puppet,
puppetdb, and so on. If I follow through with this:
- will a reinstall of puppet and
Is it (reasonably) feasible to add new resource types? I don't want to
disassemble the whole code base but if there is a known path to this I'd
like to read about it.
Some thoughts:It strikes me that there are at a few situations that I run
into with this SW that would make for decent addition
gt; > To: "puppet-users" >
> > Sent: Wednesday, October 29, 2014 1:09:04 PM
> > Subject: [Puppet Users] Re: ENC vs manifest - cage match
>
> > On Wednesday, October 29, 2014 5:44:41 AM UTC-5, JonY wrote:
> >>
> >> If we throw these two into the oc
If we throw these two into the octagon.. who wins? If one says "add it" and
the other says "remove it".. what do I end up with?
--
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, s
Situation: folder tree that gets installed via 'file' resource. In some
circumstances I want to add files/ folders to this tree.
Given that the tree is 100% puppet controlled if I add the extra files they
will get booted out.. right?
Is there some way to tell puppet to accept the extra bits (
on.exec("dpkg -l | grep apache2 | grep -v
>>>> apache2-utils | grep ^ii")
>>>
>>> "true"
>>>
>>> end
>>>
>>> end
>>>
>>> end
>>>
>>>
>> ... and then, in a manifest, refer
I get the rationale of an 'immutable system' but I don't have the privilege
of replacing these. They are field-deployed in sensitive locations.
On Sunday, October 26, 2014 6:11:56 PM UTC-7, Garrett Honeycutt wrote:
>
> On 10/26/14 5:18 AM, JonY wrote:
> > Let
Let's say that I'm deploying a steady stream of identical hosts. Each has
some piece of SW on it that's managed by Puppet. I continue to (regularly)
add to and maintain this group over time.
Day comes when this SW is no longer required.
So I remove the module from Puppet to prevent it being i
I recently changed over to a postgres back end. Now puppetdb.log seems to
be awash in these errors.
I'm pretty sure everything is up to date:
# rpm -qa | grep puppet
puppetlabs-release-6-11.noarch
puppet-server-3.7.2-1.el6.noarch
puppetdb-2.2.2-1.el6.noarch
puppet-3.7.2-1.el6.noarch
puppetdb-te
be
> performant on hsql, and at current pace it will still be done in seven
> hours or so.
>
> To the extent that you're still having trouble a stack dump may be
> helpful in diagnosing the issue.
>
> Thanks,
> Wyatt
>
>
> On Thu Oct 9 03:50:13 2014,
Update: 45 hours - ~75% complete
On Tuesday, October 7, 2014 1:32:02 PM UTC-7, JonY wrote:
>
> Running for 7 hours now. Has exported ~15-20% of the data.
>
> I'm intrigued to see what I end up with.
>
>
> On Tuesday, October 7, 2014 1:19:04 PM UTC-7, Wyatt Alt wrote:
>
Running for 7 hours now. Has exported ~15-20% of the data.
I'm intrigued to see what I end up with.
On Tuesday, October 7, 2014 1:19:04 PM UTC-7, Wyatt Alt wrote:
>
> Thanks Jony.
>
> I've loaded up an embedded database to comparable capacity and while
> export isn&#x
- it's a fair bit more then the default.
On Tuesday, October 7, 2014 9:00:17 AM UTC-7, Wyatt Alt wrote:
>
> Hey JonY,
>
> Sounds interesting. What version of PuppetDB are you using? Do you have
> reports, facts, and catalogs, or only some of those? Can you paste your
&g
(ok - terrribly unprofessional title.. I get it).
I'm trying to 'do the right thing' and move from the embedded DB to
Postgres. Following the instructions I figured I would dump out the
contents of the embedded DB and import this into Postgres.
So I start 'puppetdb export --outfile '.
Pour so
I've been having problems (documented here) with upgrading my clients from
p-ver 3.5.1 and facter 1.7.5 to 3.7 and 2.2 respectively. (TL;DR - the
client gives a facter error with every run and is essentially wedged).
I filed a bug but was told "restarting the puppet service will clear up
this e
My instructions for setting up the repo and such for Dell OpenManage start
with this command "wget -q -O -
http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash". It turns
out the .cgi file has some cumbersome logic in it to determine OS and so
forth - more so than I want to implement
Just wondering. I was messing about with some queries this morning.
Asking for '/v3/reports --data-urlencode
'query=["=","certname","client_name"]' only returned about 2 weeks worth of
reports. This system has been up and running for 6-8 months.
--
You received this message because you are s
Use an ENC: https://docs.puppetlabs.com/guides/external_nodes.html
On Wednesday, September 24, 2014 10:13:00 AM UTC-7, Tom Tucker wrote:
>
>
> I would like to use a profile that would be applied against all Linux
> based systems to ensure they have an appropriate /etc/ntp.conf based on
> their d
day, September 24, 2014 6:34:13 AM UTC-7, jcbollinger wrote:
>
>
>
> On Tuesday, September 23, 2014 7:30:40 AM UTC-5, JonY wrote:
>>
>> I'm attempting to make the jump to directory-based environments and am
>> curious about what to do with custom facts.
>>
>
I'm seeing this error appear on a client machine (/var/log/syslog):
puppet-agent[17158]: Failed to apply catalog: Could not retrieve local
facts: Invalid facter option(s) type
If I run 'puppet agent --test' it runs fine.
If I run 'puppet agent --test --debug' there is no mention of this error
ase/lib/facter/puppet_info.rb
>
> As you can see i'm very much learning as I go as well.
>
> On Wednesday, 24 September 2014 17:58:08 UTC+9:30, David LeVene wrote:
>>
>> Hey JonY,
>>
>> Firstly, i'm not an expert but hopefully this assist you
>>
>
I'm attempting to make the jump to directory-based environments and am
curious about what to do with custom facts.
In my current config I've tried putting custom facts into a separate module
as /etc/puppet/modules/facts/{manifest,lib} and
/etc/puppet/modules/facts/lib/facter/. I haven't had any
FWIW: I repackaged facter 1.7.5 as a "_all" and it installs on my ARM
systems. I can upgrade to puppet/common 3.5.1 now.
On Monday, April 28, 2014 3:39:21 PM UTC-7, JonY wrote:
>
> In the past I've worked around this by creating a stub version of
> dmidecode. facter
hat facter is not an all arch package. It depends on dmidecode,
> which is not available for all architectures. Because of this, facter
> is an arch dependent package and there is no all package for it. There
> is more detail in the linked ticket.
>
> HTH
>
> On Mon, Ap
To the build-czars at puppet labs: could you please include a "*_all.deb"
version of facter in your build cycle? It doesn't appear to have been
created since v 1.6.18.
My clients are almost exclusively ARM based and can't upgrade without this
being available.
Humbly yours, me.
--
You receiv
On Saturday, April 26, 2014 11:05:50 AM UTC-7, JonY wrote:
>
> I think I'm past that version already:
>
> # rpm -qa | grep puppet
> puppetdb-1.6.3-1.el6.noarch
> puppet-3.5.1-1.el6.noarch
> puppet-server-3.5.1-1.el6.noarch
> vim-puppet-2.7.20-1.el6.rf.noarch
>
owse/PDB-349
> >
> > You can usually solve this by upgrading to Puppet 3.4.3.
> >
> > ken.
> >
> > On Sat, Apr 26, 2014 at 3:39 PM, JonY >
> wrote:
> >> FWIW: I tried to remove all the db files and restart in hopes of
> removing
> &
FWIW: I tried to remove all the db files and restart in hopes of removing
the constraint issue. It immediately came back so I'm assuming that this is
a bug in the version of puppetdb I have installed (1.6.3.1)
On Saturday, April 26, 2014 6:03:22 AM UTC-7, JonY wrote:
>
> It seems th
It seems that puppetdb has run itself into a corner. It starts (albeit
briefly) and then stops soon afterwards with this error:
2014-04-25 20:38:30,242 ERROR [command-proc-65] [puppetdb.command]
[6c141db1-eeac-4c3f-be08-d03e5f445a19] [store report] Retrying after
attempt 13, due to: java.sql.SQ
Ah nice! I did the same on the dream plug. It's the same chip.
On Tuesday, April 8, 2014 5:07:52 AM UTC-7, Dirk Heinrichs wrote:
>
> Am 08.04.2014 12:29, schrieb JonY:
>
> Not sure. The devices are fanless PCs called 'dream plugs'. How would I
> determine
orm you made it working ?
>
> Thanks,
> Ashutosh
>
>
> On Saturday, December 14, 2013 12:45:26 AM UTC+5:30, JonY wrote:
>>
>> Answer here:
>> http://stackoverflow.com/questions/14607385/puppet-does-not-start-a-service-varnish-when-puppet-apply-is-run
>>
>&g
On Monday, March 17, 2014 8:43:54 AM UTC-7, JonY wrote:
>
> Over the weekend there were some intermittent outages at our data center.
> The puppet server would let clients connect but they would eventually time
> out.
>
> Unf this timeout wasn't handled gracefully and the cl
Over the weekend there were some intermittent outages at our data center.
The puppet server would let clients connect but they would eventually time
out.
Unf this timeout wasn't handled gracefully and the clients would hang.
Doing a 'ps -ax | grep puppet' would show the service and the 'puppet
I'm trying to setup a nagios server via puppet to monitor the other servers
in the group. I can get the various stored info from puppet db but when the
*.cfg files are created in the nagios folder they are all root:root 0600.
IE nagios can't read them.
I can work around this but I'm wondering
On Monday, February 24, 2014 7:17:28 AM UTC-8, jcbollinger wrote:
>
>
>
> On Friday, February 21, 2014 10:50:20 AM UTC-6, JonY wrote:
>>
>> I have 36 (seemingly) identical machines deployed from a single manifest.
>>
>
>
> Puppet does not do deployment,
On Monday, February 24, 2014 7:21:28 AM UTC-8, jcbollinger wrote:
>
>
>
> On Friday, February 21, 2014 10:19:10 AM UTC-6, JonY wrote:
>>
>>
>> On Friday, February 21, 2014 8:10:23 AM UTC-8, jcbollinger wrote:
>>>
>>>
>>>
>&g
I have 36 (seemingly) identical machines deployed from a single manifest.
For some reason I'm getting this error in my logs for a subset of them.
/etc/hosts:
127.0.0.1 hostname hostname.fqdn localhost
Where else should I look?
--
You received this message because you are subscribed to the G
On Friday, February 21, 2014 8:10:23 AM UTC-8, jcbollinger wrote:
>
>
>
> On Thursday, February 20, 2014 4:41:33 PM UTC-6, JonY wrote:
>>
>> Looks like my server updated to 3.4.2. Since then I've started seeing
>> these occasional messages like:
>>
>
Looks like my server updated to 3.4.2. Since then I've started seeing
these occasional messages like:
Feb 20 14:19:05 puppet-master[5626]: YAML in network requests is deprecated
and will be removed in a future version. See
http://links.puppetlabs.com/deprecate_yaml_on_network
Feb 20 14:19:05 p
I set up a simple ENC this morning that just logs every agent request to a
file. What I've noticed is that every agent is logging two requests per
run. Each request is about ~10 seconds apart.
Is this normal? Are my agents not setup correctly?
--
You received this message because you are subsc
>> Have you tried setting hasstatus => true in the service definition?
>>
>> Could you provide a puppet agent -t --debug from the node?
>>
>> Regards,
>> El 04/02/2014 20:55, "JonY" > escribió:
>>
>>> I have an issue where puppet
y.
>
> Regards,
> El 04/02/2014 21:09, "José Luis Ledesma" >
> escribió:
>
>> Have you tried setting hasstatus => true in the service definition?
>>
>> Could you provide a puppet agent -t --debug from the node?
>>
>> Regards,
>>
I have an issue where puppet keeps starting additional instances of a
process even though it's already running. The 'control script' in question
does have a 'status' command but I'm thinking that I'm not properly telling
puppet that the process is ok.
>From the site:
The init script’s status co
11:16:41 AM UTC-8, Jose Luis Ledesma wrote:
>
> Have you looked syslog and apache logs?
>
> BTW /tmp should be 1777, but this shouldn't be the problem.
>
> Regards,
> El 04/02/2014 20:07, "JonY" > escribió:
>
>> I'm stumped then.
>>
>>
I'm stumped then.
Folder is 0777. Files are 0777.
I'm running the p-master using Passenger in apache2 which runs as the
'puppet' account. I used this account to run the app in question without
any problem. 'su - puppet -c "/tmp/test0.pl"'.
SELinux is in 'permissive' mode.
What else should I
64 matches
Mail list logo
