Opennms remains with open connections after starting to minitor with WMI.

Hi All,

On one of the Windows2000/NT server machines we have, Opennms starts opening ports without closing them, every 5 minutes one. See the enclosed graph with the open TCP connection for the Opennms server. Note that the drops to 30-40 are after restarting opennms.

Up until now the ports used have been: 1980, 1974 and 4095 that are not even in the capsd-configuration.xml nor the poller-configuration.xml

This happens on Opennms 1.7.2 on an intel machine with Solaris10 x86  06/06 and after we implemented monitoring with WMI for Windows.

Any clues?

Output from:

# netstat -an | grep ESTABLISHED :

10.228.130.119.55382 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.55539 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.56102 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.56224 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.56560 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.56893 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.56913 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.57423 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.57619 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.57950 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.58330 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.58352 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.58988 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.59166 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.59665 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
10.228.130.119.59851 10.228.128.91.1980   17520      0 49640      0 ESTABLISHED
.... etc
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

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

[David Hustace]

Some javascript/style in this post has been disabled (why?)

On Nov 6, 2009, at 3:28 AM, [hidden email] wrote:

This happens on Opennms 1.7.2 on an intel machine with Solaris10 x86  06/06 and after we implemented monitoring with WMI for Windows.

If you are running 1.7 code, I would be inclined to upgrade to 1.7.7...

Does the problem go away if you disable the WMI monitoring?

David Hustace

The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

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