The monitor section is filling up with these critical errors. Can anyone shed some light on what this means? I have plenty of hard drive space.
Standard windows install using built in database.
15.10.2024 15:12:01 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2162 (item_id,idata_timestamp,idata_value,raw_value) VALUES (9031,1729023120,'-74','-74'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2162'.'idx_idata_2162_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)
15.10.2024 15:11:59 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2162 (item_id,idata_timestamp,idata_value,raw_value) VALUES (9029,1729023119,'-43','-43'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2162'.'idx_idata_2162_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)
15.10.2024 15:11:53 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2162 (item_id,idata_timestamp,idata_value,raw_value) VALUES (9023,1729023113,'-60','-60'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2162'.'idx_idata_2162_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)
15.10.2024 15:11:51 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2813 (item_id,idata_timestamp,idata_value,raw_value) VALUES (12294,1729023111,'333','333'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2813'.'idx_idata_2813_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)
15.10.2024 15:11:50 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2162 (item_id,idata_timestamp,idata_value,raw_value) VALUES (8218,1729023109,'4144','19176478311'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2162'.'idx_idata_2162_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)
15.10.2024 15:11:48 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2751 (item_id,idata_timestamp,idata_value,raw_value) VALUES (9200,1729023108,'5072','15860024'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2751'.'idx_idata_2751_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)
Hi!
Looks like your database runs out of space and is not configured for automatic growth. You have to manually add new data file or enable automatic growth.
Best regards,
Victor
I figured out how to do that. Thank you! I also learned that SQL Server Express that comes with Netxms has a 10GB database size limit. Looks like we need to upgrade to Standard to get around that.