login about faq

We have a few server that, for reasons beyond my control, had Tectia software installed directly rather than pushed via the management server. They have the management agent, so the management server knows they exist...but it's all it knows: it doesn't report on any installed software or configurations. Which of course means I can't upgrade or deploy any updated configurations!

The documentation seems to imply that the agent process is responsible for determining what software is installed and reporting that to the management server...but it doesn't seem to be doing that. Is there some trick to force it to do so?

Most of the servers are running agent version 6.1.0.401, but a few are running a 6.2.2.28. The behavior appears to be identical. Also, it doesn't seem to matter whether the host is running Linux or Windows. The management server itself is 6.2.2.28.

asked Apr 04 '12 at 17:20

Kevin%20Vail's gravatar image

Kevin Vail
56161721


Hi Kevin,

In this instance I would generate a new icb.dat and deploy it to the effected machines. Then restart the management agent process on the effected machines. This should allow the agent to refresh and populate the information required.

It would be interesting to know what information the management server sees - does it just report back the hostname / IP of the machines?

Thanks, James

link

answered Apr 11 '12 at 14:24

jamesw's gravatar image

jamesw ♦♦
468815

It reports everything (processor type, operating system, etc.) except the installed software. And we're installing everything in the default locations.

I will try setting a new ICB, but it seems to me that I've tried it before and it hasn't worked.

(Apr 11 '12 at 18:06) Kevin Vail Kevin%20Vail's gravatar image

I tried the new ICB/restart agent, and the manager still doesn't know about installed software and configuration.

(Apr 12 '12 at 16:31) Kevin Vail Kevin%20Vail's gravatar image

OK, I have searched the Tectia Management Server document, starting from the Management Agent Configuration, and discovered that the binary polling is controlled by the agent-secsh.dat file...which does not exist on the systems that aren't reporting this information, but does on the ones that are. Makes sense as the ones that aren't never had a managment agent configuration pushed to them.

I added this file to one of the Linux servers that has the problem, and restarted the management agent...so far it hasn't reported the software information yet, but the polling period has not expired.

(Apr 19 '12 at 17:38) Kevin Vail Kevin%20Vail's gravatar image

This problem disappeared when we updated the management agent to 6.3.x.

(Dec 15 '14 at 16:31) Kevin Vail Kevin%20Vail's gravatar image
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×15
×10
×3

Asked: Apr 04 '12 at 17:20

Seen: 3,794 times

Last updated: Dec 15 '14 at 16:31

All user contributed content licensed under the cc-by-sa license.
Powered by OSQA.