Good day
Is it possible to get a proper Linux Installation file (deb or rpm) for Linux installations, instead of the .jar file? I did not see this as part of the Downloads sessions. This will make automated installations in large environments easier.
Thanks
Anton
Answer by Manish G. ·
Hi Guenter,
We are trying to install the Dynatrace Host Agents on the Linux servers. We have installed the Host Agent on the Database Server, started the dthostagent service, made updates in the .ini file after creating the Tier in the System Profile. Still it is not getting detected in the Dynatrace client. Very Frustrating, as we have restarted the services multiple time and no response. Do you have any link which could help or a generalized installation document, that you would mind sharing. I will appreciate any help provided.
Thanks
Manish
What does the agent.log of the hostagent say? Usually this has enough information if it can connect to the dynatrace collector/server or if the mapping worked.
Reinhard
Answer by Anton G. ·
Great, thanks for the feedback!
The install seem to work fine with the automatic installation tool as described by Guenter.
Our model at the moment is that even if a Java/Webserver agent is installed, we install a Host Agent pointing to a different dynaTrace Server/Collector anyway. If the Java app crashes, we still have visibility of the machine/OS. This seem to work well.
Thanks again.
Anton
Answer by Guenter H. ·
Hi again,
hope this already works for you?
#extract dthostagent and libdtagentcore.so from agent/lib64/ in the jar #extract init.d/dynaTraceHostagent from the jar #mimic Agent directory structure on the host mkdir dynatrace-agent-5.6.0 mkdir dynatrace-agent-5.6.0/agent mkdir dynatrace-agent-5.6.0/agent/lib64 mkdir dynatrace-agent-5.6.0/agent/conf #copy dthostagent and libdtagentcore.so to agent/lib64/ #write a basic dthostagent.ini (see below) to agent/conf #copy dynaTraceHostagent shell script to /etc/init.d #be sure the Name specified in dthostagent.ini is mapped in some tier #try the Agent before you add it to boot #/etc/init.d/dynaTraceHostagent start chkconfig add dynaTraceHostagent
dthostagent.ini
Name host Server CollectorToConnectTo
Hopefully the hosts have some talking Name so you can distinguish them by the Agent name.
Did you make sure that the Host Agent has permissions to write to its own directory – so that the bootstrapper can download new versions from the Collector?
One other important thing / quote from the documentation:
Only use the Host Agent to monitor a machine where no other Agent runs, because if there is any other Agent running it can / will take over the Host Agent role.
I think I will add this bulk installation thing to the regular documentation as I heard of several customers with this and larger sizes.
Thanks for asking! Have fun!
G.
Answer by Anton G. ·
Cool. I'll try it.
Hi Anton,
In general most of our customers wrap the installation into a customer script anyways. You can just tar/gzip the folder on one machine and make that the first step of your script.
After all the installation alone is not enough to roll out an agent - you will still need to modify the dtwsagent.ini or dthostagent.in files with the right collector for that machine.
Best, Roman
Answer by Guenter H. ·
Hi Anton,
I can´t verify this now as I´m on the commute, but to try a solution NOW:
I think you can easily roll your own by extracting the Host Agent from the jar and run a shell script to deploy it to the hosts and chkconfig add
the daemon to boot.
Sounds reasonable?
G.
Answer by Anton G. ·
Hi Guenter
I understand the complications you are describing. Mostly it is only for Agents. The Server and Collectors we do manually. We are rolling the Host Agent out to about 1000 Linux servers, so a Package will make automatic roll-out of any of the agents easier.
Thanks
Anton
Answer by Guenter H. ·
Hi Anton,
there are tar
ed shell scripts for Apache and PHP Agents (see e.g. Apache Web Server Agent Configuration#AgentInjectionCopy/PasteExamplesLinux/UNIX), because there might be no Java on the machine where these items are installed.
For all Agent jar installers an ancient Java 1.4 is sufficient. This should be available?!
For the one or two dynaTrace Servers Java 1.6 should hopefully not be a problem?!
How about the Collectors? Are the boxes without Java 1.6 or later? Is that the problem?
You could extract the private Java 1.7 form the dynaTrace installer jar and use this for installation!
Please mind that we already got a considerable number of installers (we tried to be thoughtful!) for different OSes and bitnesses, full and / or Server-, Collector- and Client-only, half a dozen Agents or so, ADKs,... Adding variants complicates documentation and might confuse people more than it helps.
What component do you have specifically in mind?
Thanks
G.
JANUARY 15, 3:00 PM GMT / 10:00 AM ET