Hmmm. Not sure but here's what I would do..
I would ensure all rpm packages and any gems relating to puppet and facter are
uninstalled, then install again from whatever package manager you prefer.
It feels like an unclean gem/rpm issue.
Den
> On 9 Nov 2014, at 7:51, Schofield wrote:
>
> Afte
On 10/27/2014 11:59 PM, Paul Krizak wrote:
> Has anybody else experienced this? It's behaving as if the purge
> isn't even active. But I've verified that my inifile module is up to
> date and does indeed support purging. I've also verified that the
> splunkforwarder_output and splunkforwarder_in
Thanks for the feedback.
If I could avoid it, I would.
I have worked at this job for 3-1/2 years and the Linux admin team I am part of
is still trying to get rid of several instances of RHEL 3 and RHEL 4 in
operational use.
On Nov 8, 2014, at 3:12 PM, Felix Frank wrote:
> Hi,
>
> for what i
On 10/21/2014 09:17 PM, sych wrote:
> Hello!
>
> I want to parallel deploy apps on the same node from the puppet. How
> to do it?
>
> Thanks in advance,
> Gena
Can you elaborate on the specific problem that you need to solve?
--
You received this message because you are subscribed to the Google
Hi,
I have some trouble with file or directory containing French accent. How could
I managed file or directory with accent?
I tried using 8.3 file name format without success.
Someone had this kind of problem?
Regards,
Dominique Arpin
Mise en garde concernant la confidentialité : Le présent
Hi,
try with these steps:
1. Choose a name for your master, such as master.mysite.org
2. Configure it in the master's puppet.conf
[main]
certname=master.mysite.org
3. Restart puppet master - it will generate its certificate
4. Configure the agent to use this master, in its puppet.conf.
[main]
ser
Hi,
this is a misunderstanding. What you implemented is a native custom
fact. You cannot deploy it along with your external facts.
Instead of putting is in some_module/facts.d/, move it to
some_module/lib/facter/ instead. It will be synced as a custom fact and
should then work.
With external fac
After upgrading a puppet agent from v3.0.1 to v3.7.1 on a CentOS 6.5
server I get the following error during a puppet agent run.
[junk-01: SU: lib/facter 455] puppet agent -t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
*/usr/lib/ruby/site_ruby/1.8/rubygems/custom_r
Hi,
I never fiddled with MCO or ActiveMQ, but here are some general thoughts:
- Does /usr/share/activemq/activemq-data/localhost/ exist?
- Does the KahaDB subdir already exist?
- What are the permission on the directories and which user is running
ActiveMQ?
- What kind of filesystem stores the di
Hi,
for what it's worth - it rather sounds like something I would actively
try and avoid, even if you add good module support for it.
Would it not be cleaner to use Docker or a similar solution to isolate
your Apache instances?
Cheers,
Felix
On 11/06/2014 03:12 PM, Dan White wrote:
> My workpla
OK, thank so much for your response
Il giorno giovedì 30 ottobre 2014 14:43:48 UTC+1, jcbollinger ha scritto:
>
>
>
> On Wednesday, October 29, 2014 9:50:30 AM UTC-5, Diego Lagos wrote:
>>
>> Hello everyone,
>>
>> I ask you a hand to better understand if puppet is the right tool to use
>> in my
11 matches
Mail list logo
