This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Discovery and Inventory tasks never stop running...

bbrehart over 10 years ago

I've finally configured my credential ring correctly so that my Discovery and Inventory tasks don't fail immediately, but now I have the opposite problem: the tasks never seem to stop running, and never show any progress. My initial network discovery kicked off on Friday, but it's still in a running state on Monday. The same for my scheduled inventory tasks - they kicked off over the weekend and are still running. Has anyone seen this behavior before?

0 LGarvin over 10 years ago

My initial network discovery kicked off on Friday, but it's still in a running state on Monday

What is the target of the discovery task? What does the Active Tasks node show as far as the state of the task?

The same for my scheduled inventory tasks

What is the target of the inventory task? How many objects are in that target? What does the Active Tasks node show as far as the state of the task?
Cancel
Vote Up 0 Vote Down

Cancel
0 bbrehart over 10 years ago in reply to LGarvin

The target is a 500-node Domain and the state of the task is Running
Cancel
Vote Up 0 Vote Down

Cancel
0 bbrehart over 10 years ago in reply to LGarvin

What's very strange is that most of these processes are ones that had been completed previously.
Cancel
Vote Up 0 Vote Down

Cancel
0 LGarvin over 10 years ago in reply to bbrehart

the state of the task is Running

Does the task details tab show actual activity. Is the process moving from one computer to another.
Cancel
Vote Up 0 Vote Down

Cancel
0 LGarvin over 10 years ago in reply to bbrehart

What's very strange is that most of these processes are ones that had been completed previously.

I'm not understanding what significance this has.
Cancel
Vote Up 0 Vote Down

Cancel
0 bbrehart over 10 years ago in reply to LGarvin

No, no progress at all. And the reason I mentioned that the processes had completed previously is that they were working at one time. I attempted to stop the tasks this morning and there was no change.
Cancel
Vote Up 0 Vote Down

Cancel
0 LGarvin over 10 years ago in reply to bbrehart

I attempted to stop the tasks this morning and there was no change.

I would suggest opening a support ticket via the CustomerPortal on this. Something is (not) happening that's causing unexpected behaviors in your environment.
Cancel
Vote Up 0 Vote Down

Cancel
0 bbrehart over 10 years ago

So I figured it out - the main issue was that I needed to not only set the preferred DC, but also make sure the local firewall allowed the traffic out and set the HOSTS file to point to the DC in the domain that didn't contain the Orion server.
Cancel
Vote Up 0 Vote Down

Cancel
0 LGarvin over 10 years ago in reply to bbrehart

A properly configured firewall is very important. Glad you found that. :-)
(Although the task should have timed out in the event of non-connectivity.)
If you need to add entries to the HOSTS file to locate a Domain Controller in a trusted domain/forest, that would suggest that inter-domain DNS has not been properly configured. Domain Controllers should always be locatable via DNS -- this is a core requirement of using Active Directory.
Cancel
Vote Up 0 Vote Down

Cancel
0 bbrehart over 10 years ago in reply to LGarvin

We're using a one-way trust between the domains and the DNS in the domain where the Orion server is located isn't configured with a FLZ for the other domain. The HOSTS file (in this case) was the only way to go.
Thanks for all your help.
Cancel
Vote Up 0 Vote Down

Cancel