跳转到主内容

SnapCenter 作业无法触发,长时间运行的作业已终止

Views:
21
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx<a>SnapCenter 服务器</a>
Last Updated:

适用场景

SnapCenter Server 4.1.x 及更高版本

问题描述

  • 计划的默认作业或备份作业在20分钟内无法触发、并且正在运行的作业可能会过早终止、似乎仍在运行。
  • 作业启动器在启动作业时,也会使用 SMCore 服务通过 SnapCenter Web 应用程序启动它,这样就无法在两个 IIS 事件之间启动备份(此时 IIS 将不再处理传入请求)。
  • SMcore 错误消息:
    DEBUG SMCore_28089 PID=[7152] TID=[49] RemoteUrl: https://<SNAPCENTER_SERVER>:8146/JobStatusService.svc/UpdateJobStatus
    ERROR SMCore_28089 PID=[7152] TID=[49] WebException in method: Invoke.
       System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
  • 系统事件日志将显示 ID 为 5186 的信息性 IIS 事件:
    "A worker process with process id of '<PID>' serving application pool 'SnapCenter' has requested
     a recycle because the worker process reached its allowed processing time limit."
  • 默认情况下,在 30 分钟后,系统事件日志将显示 ID 为 5013 的警告事件:
    "A process serving application pool 'SnapCenter' exceeded time limits during shut down. The process id was '<PID>'."
  • 尽管SMCore已完成操作(备份、克隆等)、但SnapCenter 也可能会出现以下作业错误:

    We noticed an IIS application pool recycle event when this job was in progress. The final state of this job is unkown.
    Consider restarting the job if required.

     

     

 

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.