简介
本文档说明通过邮件发送安全管理设备(SMA)上的计划报告时可能发生故障的原因。
通过邮件发送定期报告时出现故障的警报的原因是什么?
警报从SMA发送
The Critical message is:
A failure occurred while emailing periodic report 'Executive Summary'.
This subscription has been removed from the scheduler.
凌晨2:00整的GUI日志文件
gui.current:Mon Oct 3 02:00:03 2016 Critical: A failure occurred while emailing periodic report 'Executive Summary'.
gui.current:Mon Oct 3 02:00:03 2016 Critical: PERIODIC REPORTS: Could not e-mail report. Subscription settings: {'report_title': 'Executive Summary', 'recipients': ['user@example.com'], 'schedule': {'hour': [2], 'month': [], 'callback': <bound method System.execute_subscription_by_id of <reporting.periodic_reports.system.System instance at 0x94038680>>, 'second': [0], 'arguments': ('20160120095635_Executive Summary_calendar_day',), 'year': [], 'wday': [], 'day': [], 'minute': [0]}, 'user_name': 'user', 'options': {'lang': 'en-us', 'scheduled': 1, 'format': 'pdf', 'days_include': 'calendar_day', 'host_name': None, 'host_id': '0'}, 'report_type': 'phoebe', 'report_def_id': 'mga_overview_scheduled', 'creation_timestamp': 1453301795L, 'archive': 1} Traceback: ('egg/command_client.py send_message|558', "<class 'Commandment.DaemonUnresponsiveError'>", 'dc-ironmgt-001.cvent.net: The daemon is not responding.', '[periodic_reports/report_task.py run|188] [periodic_reports/report_task.py _send_message|612] [periodic_reports/report_task.py _send_SMTP|592] [egg/command_client.py call|237] [egg/command_client.py send_message|558]')
解决方案
计划报告在凌晨2:00之前几乎每天都会失败,原因是在每日备份期间运行的进程发生冲突,在本例中配置为凌晨1:30。在此备份过程中,某些进程将停止并重新启动,以便将数据推送到远程SMA。如果SMA在备份过程中生成报告或跟踪数据,则可能导致在凌晨2点生成报告(如本示例所示)有时无法按预期工作。根据SMA必须传输的数据量,备份可能需要更多或更少时间。如果备份在凌晨2点之前完成,则计划报告生成工作正常。如果SMA仍然忙于备份,并在生成报告时重新启动该过程,则可能导致故障。解决方案是在运行每日备份之前配置计划报告。