Active IQ Unified Manager Discussions

Lost connection to OUM for capacity metrics

lornedornak
3,132 Views

We've been collecting capacity metrics in harvest by connecting to OUM.  This has been working flawlessly for months.  Now, I'm not able to collect metrics.  I'm not aware of any changes that would impact this issue.  I've also rebooted the OUM server with no success.  Here's the log entries:

 

[2016-07-19 04:18:01] [NORMAL ] WORKER STARTED [Version: 1.2.2] [Conf: netapp-harvest.conf] [Poller: oum1]
[2016-07-19 04:18:01] [NORMAL ] [main] Poller will monitor a [OCUM] at [oum1.company.com:443]
[2016-07-19 04:18:01] [NORMAL ] [main] Poller will use [password] authentication with username [netapp-harvest] and password [**********]
[2016-07-19 04:18:01] [WARNING] [sysinfo] system-about API failed with reason: Server returned HTTP Error:
[2016-07-19 04:18:01] [WARNING] [main] system-info update failed; will try again in 10 seconds.
[2016-07-19 04:18:11] [WARNING] [sysinfo] system-about API failed with reason: Server returned HTTP Error:
[2016-07-19 04:18:11] [WARNING] [main] system-info update failed; will try again in 10 seconds.
[2016-07-19 04:18:21] [WARNING] [sysinfo] system-about API failed with reason: Server returned HTTP Error:

 

Does anyone know what would cause the "HTTP error"?

 

I also have a poller in another site.  I configured OUM on that poller and get the same results.

1 ACCEPTED SOLUTION

madden
3,095 Views

Hi @lornedornak

 

I would check if SSL can be connected from the poller host with:

poller-host# curl -k -v https://ocum/

 

If it gives some SSL related error then maybe try regenerating SSL certificate on the node that doesn't work?

 

I also recall a problem caused by a software update on the poller host from another user here, so maybe check that post too.

 

 

Cheers,
Chris Madden

Storage Architect, NetApp EMEA (and author of Harvest)

Blog: It all begins with data

 

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both!

View solution in original post

2 REPLIES 2

madden
3,096 Views

Hi @lornedornak

 

I would check if SSL can be connected from the poller host with:

poller-host# curl -k -v https://ocum/

 

If it gives some SSL related error then maybe try regenerating SSL certificate on the node that doesn't work?

 

I also recall a problem caused by a software update on the poller host from another user here, so maybe check that post too.

 

 

Cheers,
Chris Madden

Storage Architect, NetApp EMEA (and author of Harvest)

Blog: It all begins with data

 

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both!

lornedornak
3,068 Views

@madden

 

Thank You very much.  I received the same curl output as seen in your referenced link.

 

root@harvest:/opt/netapp-harvest# curl -k -v https://oum1

* Rebuilt URL to: https://oum1

* Hostname was NOT found in DNS cache

*   Trying 10.0.0.81...

* Connected to oum1 (10.0.0.81) port 443 (#0)

* successfully set certificate verify locations:

*   CAfile: none

  CApath: /etc/ssl/certs

* SSLv3, TLS handshake, Client hello (1):

* SSLv3, TLS handshake, Server hello (2):

* SSLv3, TLS handshake, CERT (11):

* SSLv3, TLS handshake, Server key exchange (12):

* SSLv3, TLS alert, Server hello (2):

* error:14082174:SSL routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small

* Closing connection 0

curl: (35) error:14082174:SSL routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small

 

Apparently ubuntu was configured to automically update and received the patch to close the SSL security hole, which broke my harvest connection to OCUM.  Upgrading OCUM from 6.3RC1 to 6.4p1 fixed the issue.  I'm now collecting capacity metrics again!

Public