Are we missing the top of that stack trace Kim? FYI If you use Ctrl-A
+ [ you can scrollback in screen.
ken.
On Apr 23, 8:54 am, Kim Gert Nielsen wrote:
> On Apr 21, 2010, at 2:51 PM, Ken wrote:
>
> > More data is needed I think.
>
> > Can you run puppetd --no-daemonize --debug in 'screen' or by
On Apr 21, 2010, at 2:51 PM, Ken wrote:
> More data is needed I think.
>
> Can you run puppetd --no-daemonize --debug in 'screen' or by piping
> the output somewhere? It may give you a better clue.
>
All I get is this:
/usr/lib/ruby/1.8/net/protocol.rb:135:in `sysread'
/usr/lib/ruby/1.8/net/pr
puppet will re-parse its config file if it is changing, so usually no need
to restart the daemon.
saying that, imho, its much better to run puppet via a cron.
Ohad
On Thu, Apr 22, 2010 at 3:48 AM, Patrick wrote:
>
> On Apr 21, 2010, at 12:01 PM, Kim Gert Nielsen wrote:
>
> >
> > On Apr 21, 2010
On Apr 21, 2010, at 12:01 PM, Kim Gert Nielsen wrote:
>
> On Apr 21, 2010, at 8:50 PM, Patrick wrote:
>
>>
>> Is restarting puppet using itself supported? I had always assumed it wasn't.
>>
>
> I got the example long time ago from example42 and they just added a service
> for it. It has wo
On Apr 21, 2010, at 5:51 AM, Ken wrote:
> More data is needed I think.
>
> Can you run puppetd --no-daemonize --debug in 'screen' or by piping
> the output somewhere? It may give you a better clue.
First, it think your saying that the client is crashing or hanging.
My advice would be to do th
On Apr 21, 2010, at 8:50 PM, Patrick wrote:
>
> Is restarting puppet using itself supported? I had always assumed it wasn't.
>
I got the example long time ago from example42 and they just added a service
for it. It has worked before but if its unsupported then it might be the
problem I have
On Apr 21, 2010, at 11:43 AM, Kim Gert Nielsen wrote:
>
> On Apr 21, 2010, at 2:51 PM, Ken wrote:
>
>> More data is needed I think.
>>
>> Can you run puppetd --no-daemonize --debug in 'screen' or by piping
>> the output somewhere? It may give you a better clue.
>>
>
> debug: Service[puppet](
nevermind .. someone actually made a change so it restartet just as it should
leavning my screen killed
/Kim
On Apr 21, 2010, at 8:43 PM, Kim Gert Nielsen wrote:
>
> info: Filebucket[/var/lib/puppet/clientbucket]: Adding
> /etc/puppet/puppet.conf(f855be601e533a86b2c86a1e48e40281)
> info: //pu
On Apr 21, 2010, at 2:51 PM, Ken wrote:
> More data is needed I think.
>
> Can you run puppetd --no-daemonize --debug in 'screen' or by piping
> the output somewhere? It may give you a better clue.
>
Well I partly got something
info: Filebucket[/var/lib/puppet/clientbucket]: Adding
/etc/pupp
More data is needed I think.
Can you run puppetd --no-daemonize --debug in 'screen' or by piping
the output somewhere? It may give you a better clue.
On Apr 21, 12:39 pm, Kim Gert Nielsen wrote:
> Hi all,
>
> The last 2 weeks we have been having problems with puppetd just randomly
> stopping. T
Peter Meier wrote :
> > Is this a known problem with 0.25 clients? Has anyone seem these
> > problems too?
>
> There have been some fixes for it in 0.25.1 [1] but I'm still
> encountering such issues as well. Especially as I'm connecting some
> clients over the internet, so I might encounter
Hi
> Is this a known problem with 0.25 clients? Has anyone seem these
> problems too?
There have been some fixes for it in 0.25.1 [1] but I'm still
encountering such issues as well. Especially as I'm connecting some
clients over the internet, so I might encounter high latency.
I'm in discus
12 matches
Mail list logo
