Skip to main content
NetApp Knowledge Base

ONTAPI access via https may fail with EOF (end-of-file) on Trident

Views:
1,007
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • Data ONTAP 8.3
  • ONTAP 9.x
  • API
  • Trident

Issue

Errors depend on the tool in question, for example:

  • Trident: 

level=error msg="API invocation failed. Post https://<IP>t/servlets/netapp.servlets.admin.XMLrequest_filer: EOF"
level=error msg="Could not initialize storage driver." error="error initializing ontap-nas driver: could not create Data ONTAP API client: error reading SVM details: Post https://<IP>/servlets/netapp.servlets.admin.XMLrequest_filer: EOF"

 

  • Test from Linux with curl:  

curl -k -u vsadmin -X POST -d @request.xml https://<SVM_IP>/servlets/netapp.servlets.admin.XMLrequest_filer Enter host password for user 'vsadmin':
curl: (35) Ecountered end of file

  • Seen in the Apache error logs from ONTAP:

[ssl:warn] [pid <PID#>:tid <TID#>] [client <IP_ADDR>:<PORT>] [vserver <VSERVER_Id-Unsigned#>] SSL is not configured for this vserver


Note: In this case the effect does not change if the password is correct or not, otherwise a failure is a 401 response, and success returns XML with ONTAP Release.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device