Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Bookmark
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
I've installed and configured Grafana, Graphite, and NetApp Harvest based on the Installation and Admin Guide 1.2. When importing dashboard from NetApp Harvest to Grafana server (which is on a different VM), I get:
[root@svl-nahvst netapp-harvest]# pwd
/opt/netapp-harvest
[root@svl-nahvst netapp-harvest]# /opt/netapp-harvest/netapp-manager -import
[OK ] Will import dashboards to https://svl-nagraph.siliconimage.com
[ERROR ] Failed to import dashboard [db_netapp-detail-graphite-server.json] due to error: 501 Protocol scheme 'https' is not supported (IO::Socket::SSL not installed)
[ERROR ] -Response was :LWP will support https URLs if either IO::Socket::SSL or Crypt::SSLeay
is installed. More information at
<http://search.cpan.org/dist/libwww-perl/README.SSL>.
So I installed
[root@svl-nahvst netapp-harvest]# yum install perl-Crypt-SSLeay
Now I get a different error:
[root@svl-nahvst netapp-harvest]# /opt/netapp-harvest/netapp-manager -import
[OK ] Will import dashboards to https://svl-nagraph.siliconimage.com
[ERROR ] Failed to import dashboard [db_netapp-detail-graphite-server.json] due to error: 500 SSL negotiation failed:
[ERROR ] -Response was :500 SSL negotiation failed:
I can't figure out what this means. Is it because protocol version mismatch?
The Graphite server is using self signe certificate.
my netapp-harvest.conf has:
grafana_api_key = eyJrIjoiZUk3M1Zyam8zbnJqRHRXUUk0OGxvM2c2TEJIeEFDNGwiLCJuIjoibmV0YXBwLWhhcnZlc3QiLCJpZCI6MX0=
grafana_url = https://172.25.3.239
and I can reach https://172.25.3.239 via a browser and wget on the NetApp Harvest host (even though wget complains about self signed certificate).
Thanks,
1 REPLY 1
- Bookmark
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi @ACHOU_SIMG
Sorry to hear you have issues. First thing I'd try is to update to Harvest v1.3 which was released last week Friday. I'm not sure if it will help your issue, but worth a try.
My experience is that these kinds of vague errors are usually due to SSL negociation failures. Sometimes newer SSL client libraries disable ciphers or negociation methods that were supported in older releases. So you could make sure your system is patched (SSL libraries specifically) to the latest levels on both the Harvest and Grafana server.
If your issue still isn't solved can you respond with:
o) OS flavor and version running on Grafana server
o) OS flavor and version running on Harvest poller host
o) Grafana version
Cheers,
Chris Madden
Solution Architect - 3rd Platform - Systems Engineering 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!