Skip to main content
NetApp Knowledge Base

Newly created ONTAP S3 server doesn't have s3 service listened on the configured port due to "cifs.replay.failure" EMS event

  1. Last updated
  2. Save as PDF
Views:
209
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9 versions earlier than 9.11.1
  • Object Store Server (ONTAP S3 server)

Issue

  • It is not recommended to add the "root" user to any ONTAP S3 group. 
  • If the "root" user is added without regenerating keys in advance, the "cifs.replay.failure" event will be continuously logged, as shown below:

::> event log show -message-name cifs.replay.failure

Time                Node             Severity      Event
------------------- ---------------- ------------- ---------------------------
X/XX/XXXX XX:XX:XX  XXXXXXXXXXX      ALERT         cifs.replay.failure: Failed to replay configuration for object-server module.

  • When the above EMS event occurs, the s3 service will not listen on the configured port for the newly created ONTAP S3 server. 
  • You can verify this by checking the output of the following command: 

"network connections listening show -service s3 -vserver <vserver which hosts the newly created ONTAP S3 server>"
(the output is empty).

 

 

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

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.