OpenNMS 1.3.8 Released with Windows Support

Gang:

It is with great pleasure that I get to announce that we have  
released OpenNMS 1.3.8 - the next development release on our way to  
the 1.8 stable release. This is the fifth release of OpenNMS this year.

The new packages are on Sourceforge:

http://sourceforge.net/project/showfiles.php? 
group_id=4141&package_id=4151&release_id=552521

We also have a Yum repository for RPM-based distros:

http://www.opennms.org/index.php/Installation:Yum

and an APT repository for Debian-based distros:

http://www.opennms.org/index.php/Installation:Debian

And, for the first time, OpenNMS is available on Windows:

http://www.opennms.org/index.php/Installation:Windows

We have tested it on XP and 2000, but it should also work on Vista.

Outside of Windows support, this is mainly a bug fix release. We have  
a number of small features that have been added to the application.

Certain lists in the WebUI can be exported as RSS feeds:

http://www.opennms.org/index.php/RSS_Feeds

Also, we have changed the way a number of monitors act concerning  
timeouts.

Currently, when OpenNMS makes an attempt to reach a service, if there  
is no reply within the timeout the attempted is retried a number of  
times and then the service is marked down. For example, if the SMTP  
monitor is set up to wait 3 seconds for a timeout, and with 2  
retries, a polling cycle can take up to 9 seconds before the service  
is considered unavailable.

However, if instead of no response OpenNMS receives a "no route to  
host" or "connection refused" exception, the retries occur  
immediately and thus the service can be marked down on the order of  
milliseconds.

While the service is definitely not available during that time and  
should be marked down, on certain networks there may be a greater  
tolerance for very short outages versus extra outages/notifications.  
To this end the option "strict-timeout" was added to most monitors.  
This will cause the monitor to wait for the timeout period even if a  
connection refused message is received. Thus the network and/or  
service will have a few more seconds to recover before being marked  
down.

An example:

<service name="SMTP" interval="300000" user-defined="false" status="on">
         <parameter key="retry" value="1"/>
         <parameter key="timeout" value="3000"/>
         <parameter key="strict-timeout" value="true"/>
         <parameter key="port" value="25"/>
         <parameter key="rrd-repository" value="/opt/opennms/share/ 
rrd/response"/>
         <parameter key="rrd-base-name" value="smtp"/>
         <parameter key="ds-name" value="smtp"/>
</service>

As usual, the full release notes are here:

http://www.opennms.org/documentation/ReleaseNotesUnStable.html

We hope you find this new release useful. Remember our Wishlist:

http://www.opennms.org/index.php/WishList

and the Amazing Wall of Cards:

http://www.opennms.org/index.php/WallOfCards

-T

_______________________________________________________________________
Tarus Balog, OpenNMS Maintainer             Main:   +1 919 533 0160
The OpenNMS Group, Inc.                     Fax:    +1 503 961 7746
Skype: tarusb                               Direct: +1 919 647 4749
Email: [email protected]                    URL: http://www.opennms.org
PGP Key Fingerprint: 8945 8521 9771 FEC9 5481  512B FECA 11D2 FD82 B45C



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/wiki/index.php?page=MailingListFaq

opennms-announce mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-announce