戻る
-
タイトル
"Too many events in Scheduler task queue" -
説明
ChangeAuditor is not getting any new events.
Coordinator log shows: "Too many events in Scheduler task queue: 1003 (maximum: 1000), cannot accept more."
Agent log shows: "Coordinator FQDN (GUID) ...busy, suspending event forwarding for 60 seconds..."
-
原因
Bulk insertion of events are exceeding the default SQL timeout of 30 seconds causing the Coordinator to back up and inform the Agents that the Coordinator is too busy to accept more events. -
対策
The ideal solution would be to install additional Coordinators to balance the load but if that is not possible then one or more of the following may help:
- Create 2 registry keys as mentioned below to increase the default timeout value from 30:
SQL Command Timeout
Location: Registry
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Quest\ChangeAuditor
Value Name: SQLTimeout
Value Type: DWORD
Value: Default 30 seconds (decimal)
Value: Maximum time in seconds for SQL command to execute. Impacts most client and Coordinator queries.
Note: Start with 600 seconds (decimal) and increase to 1200 if the warnings continue after increasing to 600 and waiting about a day
Bulk SQL Command Timeout
Location: Registry
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Quest\ChangeAuditor
Value Name: BulkSQLTimeout
Value Type: DWORD
Value: Default = 30 seconds (decimal)
Value: Maximum time in seconds for bulk SQL command to execute. This includes bulk insertion of SQL events from agents.
Note: Start with 600 seconds (decimal) and increase to 1200 if the warnings continue after increasing to 600 and waiting about a day
Restart the Coordinator service either from the Coordinator Systray icon or from the Service.msc applet to make the new reg key effective - Check to ensure there is sufficient free space for the CA database. If needed, consider increasing the size of the volume where the database is stored
- Go to Client - Overview and go to bottom left, click on Funnel beside Print icon and filter Events by Event count. You will see events by its count number. Create Event specific Purge job for all those events having more count or if you do not need them, disable those searches.
- If there is still an issue, consider installing a second Coordinator
If the issue persists, please monitor the SQL server as a possible bottleneck.
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support (http://support.microsoft.com/default.aspx?kbid=256986) - Create 2 registry keys as mentioned below to increase the default timeout value from 30: