Java Agent Installation: Default Linux Install

System Requirements

The following packages must be installed on the server you are installing the agent on:

  • 32-bit glibc (‘yum install glibc.i686’ or ‘apt-get install libc6-i386’, etc.)
  • Curl or wget

One Step Installation Script

Here is a script you can copy into your terminal that will download, un-tar, and install the agent all in one step:

wget https://s1.stackify.com/Account/AgentDownload/Linux --output-document=stackify.tar.gz && tar -zxvf stackify.tar.gz stackify-agent-install-32bit && cd stackify-agent-install-32bit && sudo ./agent-install.sh --devicealias [aliasname]

Note: –devicealias parameter is optional and [aliasname] should be replaced with the desired name for your device.

When prompted, enter your Activation Key from the Settings -> Account page as shown above

Enter your Environment Name when prompted. Your Environment will group your servers and Apps, so be sure to specify something meaningful. For example, if the server you’re installing the monitoring agent on is in your west coast data center, and it’s a production environment, you would use something like “West Coast Production”.

 

Updating an Existing Installation

If you already have an agent installed and need to manually update it (for instance, an automated update failed for some reason), use the following steps:

Stop existing service if running (‘sudo service stackify-agent stop’, ‘sudo /etc/init.d/stackify-agent stop’, etc.)

sudo service stackify-agent stop

Run the original installation script with “–update” following the end of the script:

wget https://s1.stackify.com/Account/AgentDownload/Linux --output-document=stackify.tar.gz && tar -zxvf stackify.tar.gz stackify-agent-install-32bit && cd stackify-agent-install-32bit && sudo ./agent-install.sh --update

Start the service (‘sudo service stackify-agent start’, ‘sudo /etc/init.d/stackify-agent start’, etc.)

sudo service stackify-agent start

Removing an Existing Installation

To remove the Stackify agent from you device, use the following command:

Stop existing service if running (‘sudo service stackify-agent stop’, ‘sudo /etc/init.d/stackify-agent stop’, etc.)

sudo service stackify-agent stop

Remove the existing service:

sudo ./agent-install.sh --remove

Performing a “Silent” (Unattended or Automated) Install

If you have an automation tool that enables scripted environment configuration, you can ensure that Stackify is installed by default on every server by having the tool perform a silent install, or unattended install, by providing command line arguments. You can also do this at the command line when installing manually, simply to streamline the process a bit. To do so, simply add the following arguments on the install command:

wget https://s1.stackify.com/Account/AgentDownload/Linux --output-document=stackify.tar.gz && tar -zxvf stackify.tar.gz stackify-agent-install-32bit && cd stackify-agent-install-32bit && sudo ./agent-install.sh --key <em>your_activation_key</em> --environment <em>your_environment_name</em>

By adding these parameters, the installer will use the key and environment provided on the command line and won’t prompt for any additional information during installation.

Troubleshooting Installation

If your install is held up by glibc.i686 install, try running: ‘yum install glibc.i686

You may see this output:

No package glibc.i686 available.

Error: Nothing to do

Check the yum.conf file, for an exclusion explicitly set for “.i686” files. This command is attempting to install ‘glibc.i686’ which would be excluded by this. Ex:

exclude=*.i386 *.i586 *.i686 nginx* php* mysql*