Mohit Chawla

  • Email:
  • Registered on: 06/29/2010
  • Last connection: 09/13/2011

Activity

Reported issues: 4

09/13/2011

08:49 am MCollective Feature #9456 (Closed): keep track of message counts that exceeded TTLs in the global stats and r...
With direct addressing and using queues, messages can be replayed on nodes. Although this is logged at the nodes, it ...

04/16/2011

11:10 am Puppet Bug #6718: runit service provider fails when trying to install a new service
Similar to #4480 ?

03/08/2011

05:42 am Puppet Bug #4480: Runit service provider behavior
I do not have to manually invoke runsv, that is done by runsvdir ( http://smarden.org/runit/runsvdir.8.html ) . What ...

02/01/2011

01:46 pm Puppet Bug #4480: Runit service provider behavior
Sorry for the delay. Hopefully this will be useful. The run script was placed under/etc/sv/test manually.
The man...

01/24/2011

07:18 pm Puppet Bug #4480: Runit service provider behavior
I think Brice was the maintainer/author for these providers - daemontools and runit. He told that in earlier Puppet v...
06:01 am Puppet Bug #4480: Runit service provider behavior
runsvdir monitors the services directory ( /etc/service ) for new services. http://smarden.org/runit/runsvdir.8.html ...

09/09/2010

04:38 am Puppet Feature #864: Enhance puppetrun to pass through --no-noop functionality
This could be really useful. :)

09/08/2010

05:39 am Puppet Bug #4629: puppet run Error 403 on SERVER: Forbidden request
Hi,
1) With just the namespaceauth.conf present with the following block:
[puppetrunner]
allow foo.serv...

09/07/2010

09:47 am Puppet Bug #4629: puppet run Error 403 on SERVER: Forbidden request
For the time being I have just added the following in auth.conf (and created an empty namespaceauth.conf otherwise pu...
09:30 am Puppet Bug #4629: puppet run Error 403 on SERVER: Forbidden request
I am experiencing the same problem on 2.6.0-2 master as well as 2.6.0-2 client. Even with allow * under the puppetrun...

Also available in: Atom