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

Network Inventory taking too long?

I wanted to know if anyone else is expericing this issue. I have a nightly job starting at 11PM to run a full network inventory. As of 9AM it's still running and only about 15 devices have "finished".

I'll open a case with support but was wondering if anyone else is having this issue.

Thanks.

BB

Find more posts tagged with

cirrus

Accepted answers

All comments

BryanBecker

Bump.

I know people have to be using the inventory piece.

Any luck with this?

BB

jonchill

BB, I've run the inventory during the day without any problems, we are currently managing 126 devices. I've set an inventory in the schedule to run at 11pm every night, I'll let you know what happens tomorrow.

Jon

jonchill

I've checked this morning and the job tells me it's still running but when I run the report to see when the last inventory update happened no devices updated last night but the job is still running.

Jon

BryanBecker

I rebuilt our server and its running fine now. The only difference was I added the route table add-on with the last install. I haven't added that just yet.

BB

Grabowski

I also had the problem with jobs being stuck in the "running" state. The cure was to have an account that had local administrator privileges run the job.

Lars Grabowski
Global Infrastructure
Chr. Hansen A/S

Currently using:
Cirrus Version 2.1 DL-500 Feb. 2006 (8.1.42)
Orion Application Monitor 7.8.94
Orion Web Engine Version 7.8.133
Orion NPM SLX 7.8.5 March 2006
Alert Manager 8.1.15

BryanBecker

quote:Originally posted by Grabowski

I also had the problem with jobs being stuck in the "running" state. The cure was to have an account that had local administrator privileges run the job.

My nightly inventory was fine until last night. I enbale the route table and cidr route table as part of the inventory and not its hung again in the running state. We have about 600 devices and its only gone thru about 50 of them since 11PM last night.

Doesn't make sense.

jonchill

Bryan, I've got an outstanding call with support they have told me

Thank you for the update. The Development team is reviewing this information, and is currently working on a resolution. I will keep you posted when an update is available to address this issue.

This was on the 17th March. So I assume they are still working on it.

Jon

IT Infrastructure Manager
Pilgrim Hospital
UK

BryanBecker

Thanks....I have a call into them as well.

BB

BryanBecker

quote:Originally posted by BryanBecker

Thanks....I have a call into them as well.

BB

Update for u all. We narrowed it done to when Cirrus is pulling the route and cidr route tables out of our ISP routers which have the full Internet tables in them. Cirrus is just crashing. If we remove those devices from inventory it works fine. They are taking that to the developers to see if anything can be done.

BB

FormerMember

Has there been any updated information on the inventory issue that you guys are experiencing? I currently have 300 nodes that need to be inventoried but Cirrus only make it to about 10 nodes then locks up. Any advice on this would be appreciated

Thanks!

Victor

chris.lapoint

Has everyone experiencing these issues submitted a case with support (either online or by phone)? I want to make we're tracking this inventory issue properly. If you have, can you please post your case # so I can see where we are on this issue.

BryanBecker

Wow....I didn't realize I opened this in 2006...yikes. I'm not sure what my case was. We have 2 Cirrus servers....one has about 600 devices the other has about 200. The 600 server inventories everything in about 3 1/2 hours.

BB

onEOFsix

Yes, I'm having the same problem

ElisabethZakes

In the case cited above, the solution was to manually update the credentials in the database.