On Fri, May 13, 2011 at 4:47 PM, Venelin Petkov wrote:
> Hi,
>
> I tested your suggestion and the validation passed successfuly,
> only that the bug was in shinken/objects/item.py ;)
>
> Venelin
>
Hi,
Gregory patched it in t a refactory pass of this function :)
Thanks again for the bug report
Hi,
I tested your suggestion and the validation passed successfuly,
only that the bug was in shinken/objects/item.py ;)
Venelin
On Tue, May 10, 2011 at 1:10 PM, nap wrote:
>
>
> On Mon, May 9, 2011 at 3:49 PM, Venelin Petkov
> wrote:
>>
>> Regarding the problem with 0.6: The problem oc
On Mon, May 9, 2011 at 3:49 PM, Venelin Petkov wrote:
> Regarding the problem with 0.6: The problem occurs at the
> verification stage (Tested with -v ), so it is a parsing bug. I
> checked again the last part of shinken-specific, the notification
> section was all commented out. Just to be sure
Regarding the problem with 0.6: The problem occurs at the
verification stage (Tested with -v ), so it is a parsing bug. I
checked again the last part of shinken-specific, the notification
section was all commented out. Just to be sure I removed it (including
the 'x' in 24x7), but I still get the
Hi Jean,
Both the poller and the arbiter installation used 0.5.6, therefore
it is certainly not a version mismatch.
On Mon, May 9, 2011 at 1:45 PM, nap wrote:
>
>
> On Mon, May 9, 2011 at 11:44 AM, Venelin Petkov
> wrote:
>>
>> Hi Jean,
>
> Hi,
>
>>
>> We recently upgraded our main Shinken s
On Mon, May 9, 2011 at 11:44 AM, Venelin Petkov <
venelin.pet...@iwr.uni-heidelberg.de> wrote:
> Hi Jean,
>
Hi,
>
> We recently upgraded our main Shinken setupt to 0.5.6, including a
> distributed poller. Today I noticed that the arbiter has crashed:
>
Was your distributed poller updated too? I
