NetXMS Support Forum

Server version 5.2.3

We made some routing changes on our network and now the "route from" option no longer works. The routing table for our mikrotik routers no longer loads, just a time out error.

I just need some assistance on how to troubleshoot this. I am able to see the arp cache and all the interfaces, and there are no SNMP errors.

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.)

My goal is to have three alarms when a node goes down. One alarm after being down for 2 min, another alarm after being down 5 minutes, and a third alarm once the node has been down for 20 minutes. 

Once the node comes back on line then we get a node Up alert.

With my current setup this is all working with one snag. If a node goes down for less than 2 minutes and then comes back up I get a node up alert. Since the node was down for less than 2 minutes I never get the node down alert. 

Very similar to the issue in this post from 2012, but when I try to add the first script Netxms tells me its deprecated. 
https://www.netxms.org/forum/general-support/event-based-on-resolving-an-alarm-timeout/

I'm not familiar with scripting at all so I was hoping I could get this accomplished using some combo of event processing policies. Any help would be appreciated.

Is there a way to use threshold to alert when a value changes? The goal is to monitor access point frequency and alert if it changes. The problem I have is each AP has a different frequency and I don't want to create a threshold for each individual AP. I just want the template DCI to monitor whatever value is there and alert if it changes.

We have a bunch of towers with a Mikrotik router, a switch, and a bunch of Ubiquiti AP's. What is the best way to set up dependencies? For example, Tower 14 router locks up and I don't want to get alerts for all 5 UBNT AP's and the switch that is plugged into the Tower 14 router. I just want to see an alert for the router that is down. I haven't been able to find anything like this in my searching. 

I am attempting to have netxms generate a slack message for when nodes go down and come up. 

I have created a slack alert notification channel that works when hitting the "send notification" button.
I have created a slack alert action.
I have enabled the slack alert server action in the event processing policy for "show alarm when node is down" and "terminate node down alarms when node is up."

From my understanding this should generate a slack message when a node goes down, and generate a second slack message when a node comes up. 

Currently I get no slack alerts when a node goes down or comes up again. What am I missing?

Thanks

Management client 5.0.6
Windows 10

The client opens up but when I click on a node it hangs and has to be force closed. Any ideas? 

The client that lives on the server seems to be fine, but the client on my desktop has developed this issue. I reinstalled the client and that fixed it for a few days, but now the problem is back.