Re: [Nagios-users] About new release for Nagios

2011-10-17 Thread Michael Friedrich
Yu Watanabe wrote:
 Thank you for the reply.

 I see.

 Then I will think of using v 3.3.1.

wait for 3.4.x
 Which one is better to  use? The Latest snapshot or
 the Latest stable release? It would be a great help if you 
 could give us your opinion.

3.2.3 is considered stable, 3.3.x is a developer release tree and
contains various things to be fixed or already fixed in svn. still,
empty perfdata is not re-enabled and breaks various graphing addons.
anyhow, that's up the nagios core devs to decide what to fix and when to
release.

the developer guidelines on wiki.nagios.org are lost, but iirc it's
mentioned over there which versions indicate which release tree.


 Thanks,
 Yu Watanabe

 Andreas Ericsson さんは書きました:
 On 10/14/2011 02:01 AM, Yu Watanabe wrote:
 Hello Andreas.

 Thank you for the reply.

 I understood the situation. So, is v3.2.3 more stable version
 for now?

 No. 3.2.3 has the same leaks but more other bugs. I'm still not entirely
 convinced that one of the reported leaks is actually a leak though as I
 can't see it in valgrind myself. The other leaks are primarily onetimers,
 and the downtime and comment removal patches only matter if you're using
 the new custom commands from altinity (or is it opsera?) that delete
 downtime and comments on remote hosts when using nsca as a distribution
 mechanism, and noone in their right mind should be doing that nowadays
 anyway.

 -- 
 Andreas Ericsson   andreas.erics...@op5.se
 OP5 AB www.op5.se
 Tel: +46 8-230225  Fax: +46 8-230231

 Considering the successes of the wars on alcohol, poverty, drugs and
 terror, I think we should give some serious thought to declaring war
 on peace.


 --
 All the data continuously generated in your IT infrastructure contains a
 definitive record of customers, application performance, security
 threats, fraudulent activity and more. Splunk takes this data and makes
 sense of it. Business sense. IT sense. Common sense.
 http://p.sf.net/sfu/splunk-d2d-oct
 ___
 Nagios-users mailing list
 Nagios-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nagios-users
 ::: Please include Nagios version, plugin version (-v) and OS when reporting 
 any issue. 
 ::: Messages without supporting info will risk being sent to /dev/null


-- 
DI (FH) Michael Friedrich

Vienna University Computer Center
Universitaetsstrasse 7 A-1010 Vienna, Austria

email:  michael.friedr...@univie.ac.at
phone:  +43 1 4277 14359 
mobile: +43 664 60277 14359 
fax:+43 1 4277 14338
web:http://www.univie.ac.at/zid
http://www.aco.net

Icinga Core  IDOUtils Developer
http://www.icinga.org


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] About new release for Nagios

2011-10-17 Thread Yu Watanabe
Michael,

Thank you for the reply. Your information would be very useful.

Thanks,
Yu

Michael Friedrich さんは書きました:
Yu Watanabe wrote:
 Thank you for the reply.

 I see.

 Then I will think of using v 3.3.1.

wait for 3.4.x
 Which one is better to  use? The Latest snapshot or
 the Latest stable release? It would be a great help if you 
 could give us your opinion.

3.2.3 is considered stable, 3.3.x is a developer release tree and
contains various things to be fixed or already fixed in svn. still,
empty perfdata is not re-enabled and breaks various graphing addons.
anyhow, that's up the nagios core devs to decide what to fix and when to
release.

the developer guidelines on wiki.nagios.org are lost, but iirc it's
mentioned over there which versions indicate which release tree.


 Thanks,
 Yu Watanabe

 Andreas Ericsson さんは書きました:
 On 10/14/2011 02:01 AM, Yu Watanabe wrote:
 Hello Andreas.

 Thank you for the reply.

 I understood the situation. So, is v3.2.3 more stable version
 for now?

 No. 3.2.3 has the same leaks but more other bugs. I'm still not entirely
 convinced that one of the reported leaks is actually a leak though as I
 can't see it in valgrind myself. The other leaks are primarily onetimers,
 and the downtime and comment removal patches only matter if you're using
 the new custom commands from altinity (or is it opsera?) that delete
 downtime and comments on remote hosts when using nsca as a distribution
 mechanism, and noone in their right mind should be doing that nowadays
 anyway.

 -- 
 Andreas Ericsson   andreas.erics...@op5.se
 OP5 AB www.op5.se
 Tel: +46 8-230225  Fax: +46 8-230231

 Considering the successes of the wars on alcohol, poverty, drugs and
 terror, I think we should give some serious thought to declaring war
 on peace.


 --
 All the data continuously generated in your IT infrastructure contains a
 definitive record of customers, application performance, security
 threats, fraudulent activity and more. Splunk takes this data and makes
 sense of it. Business sense. IT sense. Common sense.
 http://p.sf.net/sfu/splunk-d2d-oct
 ___
 Nagios-users mailing list
 Nagios-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nagios-users
 ::: Please include Nagios version, plugin version (-v) and OS when reporting 
 any issue. 
 ::: Messages without supporting info will risk being sent to /dev/null


-- 
DI (FH) Michael Friedrich

Vienna University Computer Center
Universitaetsstrasse 7 A-1010 Vienna, Austria

email: michael.friedr...@univie.ac.at
phone: +43 1 4277 14359 
mobile: +43 664 60277 14359 
fax:   +43 1 4277 14338
web:   http://www.univie.ac.at/zid
   http://www.aco.net

Icinga Core  IDOUtils Developer
http://www.icinga.org


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] About new release for Nagios

2011-10-17 Thread Fournier, Wim
On 10/17/11 9:31 AM, Michael Friedrich michael.friedr...@univie.ac.at
wrote:


3.2.3 is considered stable, 3.3.x is a developer release tree and
Are you sure? 3.3.1 is marked as the latest stable on
http://nagios.org/download/core/thanks/?registered=1 and 3.2.3 as the
previous stable.

-- Wim Fournier


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] About new release for Nagios

2011-10-17 Thread Michael Friedrich
Fournier, Wim wrote:
 On 10/17/11 9:31 AM, Michael Friedrichmichael.friedr...@univie.ac.at
 wrote:


 3.2.3 is considered stable, 3.3.x is a developer release tree and
 Are you sure? 3.3.1 is marked as the latest stable on
 http://nagios.org/download/core/thanks/?registered=1 and 3.2.3 as the
 previous stable.

oh. i wasn't aware of that change, thanks for the pointer. well if they 
say so. i've encountered and fixed various bugs on my 3.3.1 github tree, 
so i don't consider it stable as it should be.
anyhow, as stated before, that's nagios devs' decision not mine ;-)


 -- Wim Fournier


 --
 All the data continuously generated in your IT infrastructure contains a
 definitive record of customers, application performance, security
 threats, fraudulent activity and more. Splunk takes this data and makes
 sense of it. Business sense. IT sense. Common sense.
 http://p.sf.net/sfu/splunk-d2d-oct
 ___
 Nagios-users mailing list
 Nagios-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nagios-users
 ::: Please include Nagios version, plugin version (-v) and OS when reporting 
 any issue.
 ::: Messages without supporting info will risk being sent to /dev/null


-- 
DI (FH) Michael Friedrich

Vienna University Computer Center
Universitaetsstrasse 7 A-1010 Vienna, Austria

email:  michael.friedr...@univie.ac.at
phone:  +43 1 4277 14359
mobile: +43 664 60277 14359
fax:+43 1 4277 14338
web:http://www.univie.ac.at/zid
http://www.aco.net

Icinga Core  IDOUtils Developer
http://www.icinga.org


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] About new release for Nagios

2011-10-17 Thread Andreas Ericsson
On 10/17/2011 11:10 AM, Michael Friedrich wrote:
 Fournier, Wim wrote:
 On 10/17/11 9:31 AM, Michael Friedrichmichael.friedr...@univie.ac.at
 wrote:


 3.2.3 is considered stable, 3.3.x is a developer release tree and
 Are you sure? 3.3.1 is marked as the latest stable on
 http://nagios.org/download/core/thanks/?registered=1 and 3.2.3 as the
 previous stable.
 
 oh. i wasn't aware of that change, thanks for the pointer. well if they
 say so. i've encountered and fixed various bugs on my 3.3.1 github tree,
 so i don't consider it stable as it should be.
 anyhow, as stated before, that's nagios devs' decision not mine ;-)
 

All non-trivial programs have bugs. How many have you fixed in Icinga
that were shipped in stable releases? The ones reported for Nagios have
all been fairly safe in that they're small or one-time leaks, exist in
code not normally exercised (recently added features without ui support),
changes in behaviour that might as well have been misdocumented in the
first place or only triggered by certain combinations of eventbroker
modules.

And yes, 3.3.1 is the latest stable. I'm not aware of any bugs in it,
apart from the potential one that Dorian sent me a patch for a few weeks
ago that I still haven't had time to review and test properly, so it's a
bug in potentia, but not actually verified.

-- 
Andreas Ericsson   andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] About new release for Nagios

2011-10-17 Thread Michael Friedrich
Andreas Ericsson wrote:
 On 10/17/2011 11:10 AM, Michael Friedrich wrote:
 Fournier, Wim wrote:
 On 10/17/11 9:31 AM, Michael Friedrichmichael.friedr...@univie.ac.at
 wrote:


 3.2.3 is considered stable, 3.3.x is a developer release tree and
 Are you sure? 3.3.1 is marked as the latest stable on
 http://nagios.org/download/core/thanks/?registered=1 and 3.2.3 as the
 previous stable.
 oh. i wasn't aware of that change, thanks for the pointer. well if they
 say so. i've encountered and fixed various bugs on my 3.3.1 github tree,
 so i don't consider it stable as it should be.
 anyhow, as stated before, that's nagios devs' decision not mine ;-)

 All non-trivial programs have bugs. How many have you fixed in Icinga
 that were shipped in stable releases? The ones reported for Nagios have
 all been fairly safe in that they're small or one-time leaks, exist in
 code not normally exercised (recently added features without ui support),
 changes in behaviour that might as well have been misdocumented in the
 first place or only triggered by certain combinations of eventbroker
 modules.

i've added my input on the empty perfdata behaviorial change on the 
nagios-devel lists and i do think that this is a bug because it actually 
breaks compatibility. even if not intended, if the behaviour stayed thre 
for a long time, i don't see the reason to fix that this way. but 
solely, that's just my opinion even if i break the abi myself from time 
to time. just a hint to reduce support questions.


 And yes, 3.3.1 is the latest stable. I'm not aware of any bugs in it,
 apart from the potential one that Dorian sent me a patch for a few weeks
 ago that I still haven't had time to review and test properly, so it's a
 bug in potentia, but not actually verified.

i've looked over them and i am still waiting for further input on what 
exactly leaks. i'm with you, free'ing the macros themselves rather than 
cleaning up the whole mess.


-- 
DI (FH) Michael Friedrich

Vienna University Computer Center
Universitaetsstrasse 7 A-1010 Vienna, Austria

email:  michael.friedr...@univie.ac.at
phone:  +43 1 4277 14359
mobile: +43 664 60277 14359
fax:+43 1 4277 14338
web:http://www.univie.ac.at/zid
http://www.aco.net

Icinga Core  IDOUtils Developer
http://www.icinga.org


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] About new release for Nagios

2011-10-16 Thread Yu Watanabe
Thank you for the reply.

I see.

Then I will think of using v 3.3.1.

Which one is better to  use? The Latest snapshot or
the Latest stable release? It would be a great help if you 
could give us your opinion.

Thanks,
Yu Watanabe

Andreas Ericsson さんは書きました:
On 10/14/2011 02:01 AM, Yu Watanabe wrote:
 Hello Andreas.
 
 Thank you for the reply.
 
 I understood the situation. So, is v3.2.3 more stable version
 for now?
 

No. 3.2.3 has the same leaks but more other bugs. I'm still not entirely
convinced that one of the reported leaks is actually a leak though as I
can't see it in valgrind myself. The other leaks are primarily onetimers,
and the downtime and comment removal patches only matter if you're using
the new custom commands from altinity (or is it opsera?) that delete
downtime and comments on remote hosts when using nsca as a distribution
mechanism, and noone in their right mind should be doing that nowadays
anyway.

-- 
Andreas Ericsson   andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] About new release for Nagios

2011-10-14 Thread Andreas Ericsson
On 10/14/2011 02:01 AM, Yu Watanabe wrote:
 Hello Andreas.
 
 Thank you for the reply.
 
 I understood the situation. So, is v3.2.3 more stable version
 for now?
 

No. 3.2.3 has the same leaks but more other bugs. I'm still not entirely
convinced that one of the reported leaks is actually a leak though as I
can't see it in valgrind myself. The other leaks are primarily onetimers,
and the downtime and comment removal patches only matter if you're using
the new custom commands from altinity (or is it opsera?) that delete
downtime and comments on remote hosts when using nsca as a distribution
mechanism, and noone in their right mind should be doing that nowadays
anyway.

-- 
Andreas Ericsson   andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] About new release for Nagios

2011-10-13 Thread Andreas Ericsson
On 10/13/2011 07:09 AM, Yu Watanabe wrote:
 Hello all.
 
 I was curious there will be any new releases coming out in Nagios.
 I remember there was memory leak in 3.3.1.
 
 Are there any plans for any new releases?
 

No, there will never be a new release of Nagios ever again. We've all
decided to take up knitting and unicorn-breeding instead.

On a more serious note; Ofcourse there will be a new release of Nagios.
The memory leaks are not very serious and have not yet been merged to
the Nagios core, so making a new release right now would be stupid. I
still need more time to fully investigate the pros and cons of the patch
sent in to handle the memory leak in the notification, for instance. I
believe the proposed fix either doesn't fix the leak completely or fixes
it in a bad way that would cause other problems, so I need to run it
through valgrind a couple of times to first of all see the leak for
myself and secondly make sure nothing bad happens when the patch is
applied and there are multiple notifications going out, of which some
are sent to escalated contacts.

In the meantime, you can restart your Nagios daemon once a year to avoid
any realworld problems from any potential leaks (although running latest
svn trunk would fix most of them too, so you could probably get away with
restarting only ever leapyear or something).

-- 
Andreas Ericsson   andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] About new release for Nagios

2011-10-13 Thread Yu Watanabe
Hello Andreas.

Thank you for the reply.

I understood the situation. So, is v 3.2.3 more stable version 
for now?

Thanks,
Yu

Andreas Ericsson さんは書きました:
On 10/13/2011 07:09 AM, Yu Watanabe wrote:
 Hello all.
 
 I was curious there will be any new releases coming out in Nagios.
 I remember there was memory leak in 3.3.1.
 
 Are there any plans for any new releases?
 

No, there will never be a new release of Nagios ever again. We've all
decided to take up knitting and unicorn-breeding instead.

On a more serious note; Ofcourse there will be a new release of Nagios.
The memory leaks are not very serious and have not yet been merged to
the Nagios core, so making a new release right now would be stupid. I
still need more time to fully investigate the pros and cons of the patch
sent in to handle the memory leak in the notification, for instance. I
believe the proposed fix either doesn't fix the leak completely or fixes
it in a bad way that would cause other problems, so I need to run it
through valgrind a couple of times to first of all see the leak for
myself and secondly make sure nothing bad happens when the patch is
applied and there are multiple notifications going out, of which some
are sent to escalated contacts.

In the meantime, you can restart your Nagios daemon once a year to avoid
any realworld problems from any potential leaks (although running latest
svn trunk would fix most of them too, so you could probably get away with
restarting only ever leapyear or something).

-- 
Andreas Ericsson   andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


[Nagios-users] About new release for Nagios

2011-10-12 Thread Yu Watanabe
Hello all.

I was curious there will be any new releases coming out in Nagios.
I remember there was memory leak in 3.3.1.

Are there any plans for any new releases?

Thanks,
Yu


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null