Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

NetFlowServices

Scorpio

NetFlowServices stopped suddenly due to System.OutofMemory Exception.

Window Event Viewer:

Exception: Error occurred during packet processing. Exception of type "System.OutOfMemory.Exception" was thrown.

Critical error in NetFlow Listener: Exception of type "System.OutOfMemory.Exception" was thrown.

Exception: Error occurred during packet processing. Exception of type "System.OutOfMemory.Exception" was thrown.

Unhanded Exception: Exception of type "System.OutOfMemory.Exception" was thrown.

Exception: Error occurred during packet processing. Exception of type "System.OutOfMemory.Exception" was thrown.

NetFlow Receiver Service [Servername] Stopped

Service Stopped successfully.

>Net Runtime 2.0 Error
EventType clr20r3, P1 netflowservice.exe

Find more posts tagged with

Accepted answers

All comments

CoreyMac

So what are you looking for?

mcbridea

Hi Scorpio,

This is a known issue which we are addressing as top priority. For now, you can manually restart the service. We have a fix in testing.

Andy

CoreyMac

Scorpio,

If it is a reason for the crash you are seeking then it is most likely due to a problem in NetFlow v3. You can look around in the various forum messages and find two things. NetFlow v3 works for some, but not others (no idea of the ratio) due to what appears to be a problem with the way that data in managed to/from the SQL Server by the NetFlow Service. Also, calling Solarwinds support could be the best thing as there are no real solutions for NetFlow v3 here yet, if you are experiencing what the rest of us see with regards to running out of memory, slow performance, excessive SQL Server loads, etc...The expectation is that the next Service Pack (SP2) will help. SP1 did not really help this but did allow limits to be set that would prevent the machine from running out of memory, but the NetFlow Service still can run out and cease to operate. SP1 also fixed some other issues.My other suggestions/observations are two-fold... First, if you are running out of memory with that process quickly, you might consider just shutting down the NetFlow service for now because you are getting little data and what you get is not very reliable. You will get some data to be sure, but only an unpredictable subset and that may or may not suffice for you. Also, if you are having the problem described here it is likely destroying the overall performance of Orion on that same SQL Server. Restarting the NetFlow service every so often will drop the unprocessed data and start things fresh losing the 200-600MB of flow data packets that is was holding when it went down. However Orion will still suffer from the same performance problems anytime it is running and receiving flows...It appears from what I have seen in my environment that basically the NetFlow service is tying up the system with some huge number of overlapping locks and hanging up the various calls with locks that are averaging >10 seconds (in recent testing again some lasted >90 seconds under a *very* light load). It seems that some critical SQL objects are hanging up and that just clogs up the works. (This Orion server before the NetFlow service was started, averaged waits around ~0 seconds for all locks.)This same SQL server was running about 8,000 lock requests per second before, but once the NetFlow service started with a small amount of traffic flows, the lock rate climbs to more than 40-70,000 lock requests per second. I am no SQL expert though by any means so take these numbers with that knowledge. The ones with trouble are the ones looking for help I would guess.You can always go back to the previous version as that seems comparatively stable.