跳转到主内容

StorageGRID 节点无法将日志转发到外部系统日志服务器

Views:
12
Visibility:
Public
Votes:
0
Category:
storagegrid
Specialty:
sgrid
Last Updated:

适用场景

  • NetApp StorageGRID 11.6,11.7
  • 外部系统日志服务器
  • 故障转移系统日志服务器

问题描述

  • StorageGRID网格管理器报告以下警报:
    • 名称: External syslog server forwarding error 
    • 说明:Node cannot forward logs to the external syslog server
    • 检查 /var/local/log/miscd.log
    • [2022-03-22T09:25:25.092] syslMon - INFO -- Updating connection state for remoteSyslogServerA [2022-03-22T09:25:25.092] syslMon - INFO -- Checking 'omfwd: remote server at sysmlog.net:60119 seems to have closed connection. This often happens when the remote peer (or an interim system like a load balancer or firewall) shuts down or aborts a connection. Rsyslog will re-open the connection if configured to do so (we saw a generic IO Error, which usually goes along with that behaviour). [v8.2108.0 try https://www.rsyslog.com/e/2027 ]' for errors [2022-03-22T09:25:25.092] syslMon - INFO -- Detected 'p_connection_closed_by_partner' [2022-03-22T09:25:25.092] syslMon - INFO -- Setting forwarding error for remoteSyslogServerA [2022-03-22T09:25:25.111] syslMon - INFO -- Updating connection state for remoteSyslogServerA 
  • 自动故障转移到配置的第二个外部系统日志服务器
  • 切换到故障转移系统日志服务器所需时间超过15分钟、因此触发了警报

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.