メインコンテンツまでスキップ

「SID Lookup Failed」イベントが報告される

Views:
12
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core<a>2009813500</a>
Last Updated:

環境

ONTAP 9

問題

  • クォータユーザ 「ADMIN\GD-Admin」 が削除され、同じ名前のクォータユーザグループ「 ADMIN\GD-Admin」が作成されました。
  • SID検索に失敗した エラーがイベントログに報告されたことを投稿します。

Wed Jan 03 00:39:21 +0100 [Cluster: secd: secd.unexpectedFailure:error]: Unexpected SecD failure in Vserver "svm1". Details: Error: Lookup of CIFS account SID procedure failed   [ 0 ms] Using cached S-1-5-21-1586194396-3347935261-3522003902-4376 to 'Admin\GD-Admin' mapping   [2] Successfully connected to ip 172.XX.XXX.XX, port 88 using TCP   [2077] TCP connection to ip 172.XX.XXX.XX, port 88 failed: Operation timed out.   [2088] Successfully connected to ip 172.XX.XXX.XX, port 88 using TCP   [2098] Could not get credentials via S4U2Self based on full Windows user name 'GD-Admin@XXXX.YY'. Continuing to LDAP.   [2098] Using a cached connection to Cluster.XXXXX.YYY **[2099] FAILURE: Cannot get credentials for SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'. No associated primary group.   [2099] Could not get credentials via LDAP for Windows user 'GD-Admin' based on SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'   [2099] Could not get credentials for Windows user 'GD-Admin' or SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'   [2099] SID lookup failed 

Wed Jan 03 00:40:35 +0100 [Cluster: secd: secd.unexpectedFailure:error]: Unexpected SecD failure in Vserver "svm1". Details: Error: Lookup of CIFS account SID procedure failed   [0 ms] Using cached S-1-5-21-1586194396-3347935261-3522003902-4376 to 'Admin\GD-Admin' mapping   [2] Successfully connected to ip 172.24.XXX.XX, port 88 using TCP   [2052] TCP connection to ip 172.26.XXX.XX, port 88 failed: Operation timed out.   [4057] TCP connection to ip 172.26.XX.XXX, port 88 failed: Operation timed out.   [6060] TCP connection to ip 172.26.XXX.XXX, port 88 failed: Operation timed out.   [8062] TCP connection to ip 172.24.XXX.XXX, port 88 failed: Operation timed out.   [10064] TCP connection to ip 172.27.XXX.XXX, port 88 failed: Operation timed out.   [12068] TCP connection to ip 172.26.XXX.XXX, port 88 failed: Operation timed out.   [14070] TCP connection to ip 172.25.XX.XXX, port 88 failed: Operation timed out.   [ 14082] Successfully connected to ip 172.26.XX.XXX, port 88 using TCP   [14092] Could not get credentials via S4U2Self based on full Windows user name 'GD-Admin@XXXX.YY'. Continuing to LDAP.   [14092] Using a cached connection to Cluster.XXXX.YYY **[14093] FAILURE: Cannot get credentials for SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'. No associated primary group.   [14093] Could not get credentials via LDAP for Windows user 'GD-Admin' based on SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'   [14094] Could not get credentials for Windows user 'GD-Admin' or SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'   [14094] SID lookup failed   [14094] Retry requested, but the retry window (7000 ms) has expired; giving up. 

Wed Jan 03 00:49:38 +0100 [Cluster: quota_map_proc: wafl.quota.user.map.retry:debug]: User identifier (UID) to Windows Security Identifier (SID) mapping or vice versa failed for certain user quota records on volume GlobalData@vserver:0d1e78c2-c702-11ed-8015-d039eaa26884. The quota user mapping for these records will be retried after the initial attempt in 1 minute intervals.

 

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.