nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Orion V8 stops monitoring

FormerMember

Hello,

I just installed Orion V8, but have had nothing but problems with it. It seems to stop working every two to three hours, and is essentially useless as a performance monitoring tool. I am sure that this is not the case fro the entire product, as they would not be able to sell it if it didn't work.

So, I am curious if anyone else has had this problem, and if there was anything specific you did to correct it.

I have it installed on a Windows 2003 server using the SQL Express database on the same server. Both the monitoring and the web page stop working at about the same time. I have nothing else installed on this server.

Any thoughts?

Thanks

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

How many nodes/interfaces/volumes etc are you monitoring? What kind of hardware are you running on? (Specs) Is there anything else running on the box other then Orion and SQL?

FormerMember

Hello,

It is currently set up for 500 interfaces, most of which (about 98%) are switch interfaces. There is nothing else running on the server. The server itself seems to be performing very well, just the application locks up. I am planning on moving this to a newer server when the new hardware gets here.

Thank you

aLTeReGo

Do you show anything in your windows event viewer? What is your Disk I/O look like? What is the raid level and drive spec? (ATA/SCSI/SATA/SCA)

jtimes

Have you checked the servers event viewer for application, Security, SolarWinds.net, or system events? Virus scann apps possibly crashing the services? Or the ever so popular .NET Runtime Optimization Service v2.0.50727_X86 fully installed (with the dotnetfx.exe applied?)

John J. Times

FormerMember

Yes, I have checked the event viewer, it's loaded with all kinds of errors. There are so many, I am not sure where to begin. I was just wondering if anyone else has had this problem, I can troubleshoot my specific problem if not, but if there is a known bug, there may also be a fix.

quote:Originally posted by aLTeReGo

Do you show anything in your windows event viewer? What is your Disk I/O look like? What is the raid level and drive spec? (ATA/SCSI/SATA/SCA)

aLTeReGo

If you can it would probably be a good idea to reinstall on another server, or rebuild the one you have with a clean install of Windows Server 2003 with all the appropriate windows updates. You will need to make sure that you have .NET 2.0 installed for Orion to work properly.

There are no known bugs that could explain the problems that you are experiencing. As always make sure you're on the latest build (8.02).

If you do manage to solve your problem post back here and let us know what you did to resolve it. It may help someone else in the future.

FormerMember

OK, I am now installing all the latest service packs, and if necessary, I will format and rebuild the server. I can always back up the database, so that won't be too bad to rebuild. If I figure out what it is, I will post it.

I think something didn't go right with the install, though it worked flawlessly for two days, until I installed the Netflow pieces. Something seems to have gone wrong after that.

Thanks

quote:Originally posted by aLTeReGo

If you can it would probably be a good idea to reinstall on another server, or rebuild the one you have with a clean install of Windows Server 2003 with all the appropriate windows updates. You will need to make sure that you have .NET 2.0 installed for Orion to work properly.

There are no known bugs that could explain the problems that you are experiencing. As always make sure you're on the latest build (8.02).

If you do manage to solve your problem post back here and let us know what you did to resolve it. It may help someone else in the future.

aLTeReGo

Yikes! You never mentioned running NetFlow Analyzer. Did you check the size of your database? SQL Express is limited to 4GB. Once you hit that limit the database no longer accepts writes and lots of really strange things start happening to Orion. This is also true if you run out of disk space, but I don't think this is the case here.

I know there is no technical reason why you can't run NetFlow Analyzer with SQL Express but I wouldn't recommend it (ever). I've yet to see anyones NetFlow NOT consume more then 4GB of database space. Especially with all the indexing going on in the current build. Also NetFlow Analyzer is extremely I/O intensive on the SQL database. In it's current state it is highly recommended that run your SQL server on dedicated hardware. You will also need very fast drives preferably in a RAID 10 configuration. SAS drives are highly recommended.

FormerMember

Ok, perhaps I need to look at that. I was not aware of that problem. Right now, I am only accepting Netflow for one interface, but I hadn't considered that possible problem.

I did deinstall Netflow thinking it may help, but it has not.

quote:Originally posted by aLTeReGo

Yikes! You never mentioned running NetFlow Analyzer. Did you check the size of your database? SQL Express is limited to 4GB. Once you hit that limit the database no longer accepts writes and lots of really strange things start happening to Orion. This is also true if you run out of disk space, but I don't think this is the case here.

I know there is no technical reason why you can't run NetFlow Analyzer with SQL Express but I wouldn't recommend it (ever). I've yet to see anyones NetFlow NOT consume more then 4GB of database space. Especially with all the indexing going on in the current build. Also NetFlow Analyzer is extremely I/O intensive on the SQL database. In it's current state it is highly recommended that run your SQL server on dedicated hardware. You will also need very fast drives preferably in a RAID 10 configuration. SAS drives are highly recommended.

aLTeReGo

FYI: Uninstalling NFA does not clear the data in the database. If your database is full you'll need to truncate the NetFlow tables to clear the data.

From Mark Wiggans:
Go to the database manager, right click on the Flowstats table, select query table, select refresh. From there change the radial dial from Read-only to Read/Write and type "truncate table flowstats". This command will delete - yes permanently delete - the data in that table. The other tables to truncate are:

FlowAnalysis

FlowCorrelation

Remember that this will delete all your historical data. The database will shrink when database maintenance runs the next morning. You can also run the maintenance utility immediately if you want to clean up the db immediately.

FormerMember

OK, The first problem appears to be resolved, but another problem cropped up in the process. I can no longer open Orion Systme Manger, Orion NFM or the configuration wizard. I was thinking that perhaps if I ran through the configuration wizzard one more time, it would help with the netflow and System manager opening, but since I can't open that either, I can't really do anything. The good news is that it seems to be collecting the data again, and you can view the data that has been collected via the web site. Unfortunately, I can't do any systems administration anymore.

Does this sound familiar to anyone?

FormerMember

I did a fresh install of everything (SolarWinds wise), and it seems to all be working again. We will see if monitoring fails.

Thanks for your help and suggestions. If this works, the resolution appears to be a combination of Windows 2003 SP2 and reinstalling Solarwinds. Hopefully it will run until I get the actual server it is supposed to be installed on.

quote:Originally posted by mpdurkin

OK, The first problem appears to be resolved, but another problem cropped up in the process. I can no longer open Orion Systme Manger, Orion NFM or the configuration wizard. I was thinking that perhaps if I ran through the configuration wizzard one more time, it would help with the netflow and System manager opening, but since I can't open that either, I can't really do anything. The good news is that it seems to be collecting the data again, and you can view the data that has been collected via the web site. Unfortunately, I can't do any systems administration anymore.

Does this sound familiar to anyone?