Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA backup fails and generates errors

NTA backup fails and generates errors

Updated November 21, 2017

Overview

When a Solarwinds NetFlow Traffic Analyzer (NTA) backup fails, the following error displays in the Orion Web Console:

Backup failed
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://<FSDB_Server>:17777/orion/nta/FlowStorageService. The connection attempt lasted for a time span of 00:00:21.0290696. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <FSDB_Server_IP>:17777.

The backup failure also generates errors in the Orion server and NTA Flow storage database server log files, as listed below.

Orion server error

The following error displays in the Fastbit_Backup_Restore_BusinessLayer.log file:

2017-11-14 10:59:05,873 [53] ERROR Backup_Restore - PerformBackup() - Backup failed
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://<FSDB_Server>:17777/orion/nta/FlowStorageService. The connection attempt lasted for a time span of 00:00:21.0290696. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <FSDB_Server_IP>:17777.  ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <FSDB_Server_IP>:17777

NTA Flow storage database server error

The following error displays in the FastBit_Backup_Restore.log file. Each Backup Ended at the same partition (TN#2017-11-06@14_0 in this instance)

2017-11-14 09:07:52,261 [38] DEBUG Backup_Restore - Backing up table Flows, 11/06/2017 00:00:00 - 11/07/2017 00:00:00
2017-11-14 09:07:52,277 [38] DEBUG Backup_Restore - Backing up partition _metadata
2017-11-14 09:07:52,355 [38] DEBUG Backup_Restore - Backing up partition TN#2017-11-06@0_0
2017-11-14 09:07:53,793 [38] DEBUG Backup_Restore - Backing up partition TN#2017-11-06@10_0
2017-11-14 09:08:09,262 [38] DEBUG Backup_Restore - Backing up partition TN#2017-11-06@11_0
2017-11-14 09:08:09,621 [38] DEBUG Backup_Restore - Backing up partition TN#2017-11-06@12_0
2017-11-14 09:08:26,200 [38] DEBUG Backup_Restore - Backing up partition TN#2017-11-06@13_0
2017-11-14 09:08:26,653 [38] DEBUG Backup_Restore - Backing up partition TN#2017-11-06@14_0

 

Additionally, the following error displays in the FastBitServerService.log file:

2017-11-14 09:24:00,182 [82] ERROR FastbitCLR.FastbitIndex - appendInternal: Failed to index new data. Partition: TN#2017-11-06@14_0, column: DestinationAS
2017-11-14 09:24:00,182 [299] ERROR FastbitCLR.FastbitIndex - appendInternal: Failed to index new data. Partition: TN#2017-11-06@14_0, column: DestinationIP
2017-11-14 09:24:00,182 [82] ERROR FastbitCLR.Indexer - IndexerAppend std::exception: Failed to index new data.
2017-11-14 09:24:00,182 [299] ERROR FastbitCLR.Indexer - IndexerAppend std::exception: Failed to index new data.
2017-11-14 09:24:00,182 [164] ERROR FastbitCLR.FastbitIndex - appendInternal: Failed to index new data. Partition: TN#2017-11-06@14_0, column: ApplicationID
2017-11-14 09:24:00,182 [164] ERROR FastbitCLR.Indexer - IndexerAppend std::exception: Failed to index new data.
2017-11-14 09:24:00,182 [25] ERROR FastbitCLR.FastbitIndex - appendInternal: Failed to index new data. Partition: TN#2017-11-06@14_0, column: DestinationIPGroupSegmentID
2017-11-14 09:24:00,182 [25] ERROR FastbitCLR.Indexer - IndexerAppend std::exception: Failed to index new data.
2017-11-14 09:24:00,182 [22] ERROR FastbitCLR.FastbitIndex - appendInternal: Failed to index new data. Partition: TN#2017-11-06@14_0, column: InterfaceIDRx
2017-11-14 09:24:00,182 [22] ERROR FastbitCLR.Indexer - IndexerAppend std::exception: Failed to index new data.
2017-11-14 09:24:00,182 [83] ERROR FastbitCLR.FastbitIndex - appendInternal: Failed to index new data. Partition: TN#2017-11-06@14_0, column: InterfaceIDTx
2017-11-14 09:24:00,182 [83] ERROR FastbitCLR.Indexer - IndexerAppend std::exception: Failed to index new data.
2017-11-14 09:24:00,182 [24] ERROR FastbitCLR.FastbitIndex - appendInternal: Failed to index new data. Partition: TN#2017-11-06@14_0, column: SourceAS
2017-11-14 09:24:00,182 [24] ERROR FastbitCLR.Indexer - IndexerAppend std::exception: Failed to index new data.
2017-11-14 09:24:00,182 [93] ERROR FastbitCLR.FastbitIndex - appendInternal: Failed to index new data. Partition: TN#2017-11-06@14_0, column: SourceIP
2017-11-14 09:24:00,182 [93] ERROR FastbitCLR.Indexer - IndexerAppend std::exception: Failed to index new data.
2017-11-14 09:24:00,198 [82] ERROR FastbitCLR.FastbitIndex - appendInternal: Failed to index new data. Partition: TN#2017-11-06@14_0, column: SourceIPGroupSegmentID
2017-11-14 09:24:00,198 [82] ERROR FastbitCLR.Indexer - IndexerAppend std::exception: Failed to index new data.
2017-11-14 09:24:00,385 [232] ERROR SolarWinds.Netflow.FastBit.Server.Service.Program - NetFlowService will be abnormally terminated - UnhandledException was caught : System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at std.basic_ostream<char,std::char_trait

Environment

  • All NTA versions using a Fastbit Flow Storage Database

Cause 

Corrupt database partition. 

Resolution

Delete the corrupt partition (for example, TN#2017-11-06@14_0). When completed, the NTA backups will complete as expected. 

 

Last modified

Tags

Classifications

Public