Error Message in data_engine log - de: WARNING: more than 301 seconds since last QoS message; the data_engine will restart

book

Article ID: 35418

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

 

Issue: 

The data_engine probe's log reports the following error message:

de: WARNING: more than 301 seconds since last QoS message; the data_engine will restart

Environment:  

If not available within the data_engine configuration, the idle_timeout key can be added via Raw Configure.  This makes it applicable to nearly any data_engine version.

Cause: 

If the data_engine didn't get response from SQL Server to its last bulk inserts, it will timeout and restart itself. There are various reasons this can happen, including:

  1. The data_engine maintenance job's deletion part, which starts at 12:40 AM by default, is locking tables and causing inserts to fail.
  2. The data_engine maintenance job's re-indexing part (if enabled) is locking indexes and blocking access for longer duration of time. Only SQL Server Enterprise Edition supports “online” indexing, which does not lock indexes.
  3. Any database maintenance activity such as backups, re-indexing, VMWare snapshot operations (if the database is on a Virtual Machine).
  4. Any network level configuration changes can also block communication path between the Unified Infrastructure Management (UIM) server and database server.

Resolution/Workaround:

1.  Increase idle_timeout to a value higher than seen in data_engine.log.

<Please see attached file for image>

User-added image

2.  Set the Maintenance schedule to a time when there is no other server/database level maintenance jobs are running.

<Please see attached file for image>

User-added image

3. Check the SQL Server logs for any errors related to the UIM database.
4. Check for any connectivity problems between the UIM primary hub and the SQL Server. You will see the following errors in the data_engine.log if there is a real connectivity issue or SQL Server is too busy to respond:

Jul 31 01:10:26:584 [0212] de: (1) ExecuteNoRecords [Microsoft OLE DB Provider for SQL Server] [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
Jul 31 01:10:26:584 [0212] de: COM Error [0x80004005] Unspecified error - [Microsoft OLE DB Provider for SQL Server] [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.

5. Check the 'autogrowth' option of the UIM database and make sure that it is set in size of MBs instead of 'percent'.

Environment

Release: CNMSPP99000-7.6-Unified Infrastructure Mgmt-Server Pack-- On Prem
Component:

Attachments

1558722342062000035418_sktwi1f5rjvs16wej.jpeg get_app
1558722340090000035418_sktwi1f5rjvs16wei.jpeg get_app