Hi all,
I have similar problem. When I start puppet interactive console and run
'puppet agent -t' it complete successfully. But when I start puppet service
under same (or any other use) it fail with powershell crash
*Fault bucket , type 0*
*Event Name: PowerShell*
*Response: Not available*
*Cab
uppet use environment.bat) or install puppet updates/patches. I
couldn't do any test now, because problem was fixed after restart. But if
it happen again I may replay and I hope provide more information.
**
*Best Regards,*
*Pavel Drobushevich*
*mailto:* p.drobushev...@gmail.com*
**skype*: pave
ay stopped.
Thanks, Pavel
On Wednesday, September 26, 2012 12:55:29 AM UTC+3, Josh Cooper wrote:
>
> Hi Pavel,
>
> On Tue, Sep 25, 2012 at 2:28 PM, Pavel Drobushevich
> > wrote:
> > Hi all,
> >
> > We use puppet on many windows machines (Windows Server2008R2 x64)
Hi all,
We use puppet on many windows machines (Windows Server2008R2 x64). It works
fine, but on one of them it was fail down and couldn't start work again. I
try to reinstall, but it didn't help. May be you have any idea. Thanks in
advance.
*Error message from puppet*
C:/puppet/puppet/lib/pup
e?
>
> -Jeff
>
> On Friday, June 8, 2012, Pavel Drobushevich wrote:
>
>> Hi all,
>>
>> I've installed Puppet Enterprise 2.5 on Ubuntu 10.04.4 ("minimal" version
>> on our new hosting provider, previous on amazon ec2 all works fine). So
>&
Hi all,
I've installed Puppet Enterprise 2.5 on Ubuntu 10.04.4 ("minimal" version
on our new hosting provider, previous on amazon ec2 all works fine). So
couldn't login to puppet dashboard - internal server error. I found problem
in rubycas-server. It fails when try to hash password:
(/opt/pupp
Hi John,
Thank you for your response. We use very short interval, so I think first
scenario is applicable for us. We will try to reduce execution time.
Pavel
On Tuesday, June 5, 2012 4:51:06 PM UTC+3, jcbollinger wrote:
>
>
>
> On Jun 5, 2:13 am, Pavel Drobushevich
> wro
Hi all,
Sometimes one of agent prints message "Skipping run of Puppet configuration
client; administratively disabled; use 'puppet Puppet configuration client
--enable' to re-enable." and stops working. No one disables it. Any reason
why it happens?
Thanks in advance.
--
You received this m
