BrowserBot Installation Fails on Red Hat or CentOS in Amazon EC2
PreviousAgent Unable to Trace Path to Destination?NextWhat to Do If te-agent Stops Running Due to a VACUUM Error
Last updated
Last updated
Due to recent platform-wide naming, navigation, and URL changes in the product, you may notice some discrepancies between the product and the screenshots displayed in our technical documentation. The instructions and actual pages in the product are still valid and haven’t changed. Please bear with us as we update our screenshots to better match the in-product experience. See the full scope of changes on .
The BrowserBot component of an Enterprise Agent performs Page Load and Transaction tests. For customers of Amazon Web Service's Elastic Computing 2 platform, installing a Linux Package-based Enterprise Agent with the BrowserBot component in an AWS Red Hat or CentOS virtual machine may fail due to a missing package on which the te-browserbot package depends. Most commonly, this is due to a disabled repository that contains the dependency package. To install the BrowserBot component, the repository must first be enabled.
Installation of BrowserBot with a Linux Package-based Enterprise Agent is normally done via the install_thousandeyes.sh script with the -b flag:
The most common way to detect failure to install BrowserBot is during the execution of the install script in a terminal window. A typical installation failure for BrowserBot would appear similar to the following (emphasis added):
In the above example, BrowserBot (package name "te-browserbot") depends on the xorg-x11-server-Xvfb package, which was neither present on the system nor could the package be retrieved from a package repository.
Alternatively, you can find a similar error in the installation log file. The install_thousandeyes.sh script logs to the /tmp directory in a file "install_thousandeyes_<random characters>.log". The corresponding error in the install log appears as:
After running the installation script, your new Enterprise Agent will contact the ThousandEyes collector to register itself. Agent information is displayed on the Network & App Synthetics > Agent Settings page, on the Enterprise Agents tab. The General Info section will display the installation status of BrowserBot:
If logs indicate that a package dependency failed to install, list the system's configured package repositories and their status (enabled or disabled) using the yum repolist all command:
Per the 'status' column (user the horizontal scroll bar below the output to scroll right), many of the repositories have a status of "disabled". If most repositories are disabled, it is likely that the dependency package exists in one of the disabled repositories. Copy this output or make note of which repositories are enabled and which are disabled, as you may wish to use this information later in this procedure.
If you know which repository contains the dependency package, enable it using the yum-config-manager command. For example, the xorg-x11-server-Xvfb package is contained in the rhui-REGION-rhel-server-optional repository, so you can enable the repository with the following:
If the repository is not known, the simplest way solution is first to enable all of your repositories with the yum-config-manager command (but first make note of those repositories that are enabled):
You can verify the the repository or repositories are enabled by repeating the yum repolist all . Or just try to reinstall BrowserBot using the install_thousandeyes.sh script. The script's output should indicate successful installation of BrowserBot, or you can check the install log.
Once you've completed the BrowserBot installation, if you enabled all your repositories but wish to have enabled only the repository which provided the dependency package and not any of the others you enabled, you can then determine which repository provided the package using the yum list <packagename> command:
The above output shows that the xorg-x11-server-Xvfb package is available in the"rhui-REGION-rhel-server-optional repository.
Next, disable all packages with the following yum-config-manager command:
Then, using the information you saved from the first yum repolist all command, enable the repositories which should be enabled:
Then verify the repository statuses are correct by repeating the yum repolist all command.
If enabling all system repositories does not resolve the dependency problem, contact Amazon Web Services technical support to determine what repositories are needed and how to add and/or enable the needed repositories in your /etc/yum.repos.d directory.
