Introduction
本文描述原因为什么故障能发生,当给关于安全管理工具时(SMA)的定期报告发电子邮件。
什么是戒备的原因故障发生了,当给安排报表发电子邮件时?
戒备从SMA被发送
The Critical message is:
A failure occurred while emailing periodic report 'Executive Summary'.
This subscription has been removed from the scheduler.
GUI在正确地上午2:00的日志文件
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是繁忙的与备份并且重新启动进程报告当时被生成,则能导致故障。解决方案将配置定期报告,在每日备份运行前。