BrowserBot Installation Fails on Red Hat or CentOS in Amazon EC2

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.
Identifying the Problem
Installation of BrowserBot with a Linux Package-based Enterprise Agent is normally done via the install_thousandeyes.sh script with the -b flag:
1
sudo ./install_thousandeyes.sh -b <account group installation token>
Copied!
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):
1
[[email protected] ~]$ sudo ./install_thousandeyes.sh -b 12345abcde67890fghij12345klmno12
2
​
3
========================== Welcome to ThousandEyes ============================
4
[ OK ] checking installation privileges
5
[ OK ] checking architecture (x86_64)
6
[ OK ] checking operating system (RedHat/CentOS)
7
[ OK ] checking ThousandEyes (RedHat) installation tools
8
[ OK ] detecting RedHat flavor (CentOS/6)
9
[ OK ] checking repository
10
[ OK ] loading the ThousandEyes public key
11
[ OK ] installing the ThousandEyes agent
12
Configuring ThousandEyes
13
[ OK ] detecting IP address (209.197.221.99)
14
Selecting log path: The default log path is /var/log. Do you want to change it [y/N]? N
15
[ OK ] editing configuration file
16
Installing Add-ons (RedHat)
17
[ WARNING ] ThousandEyes' BrowserBot (Package required for Page Load and Transaction tests)
18
(Failed installing ThousandEyes' BrowserBot)
19
Starting ThousandEyes
20
[ WARNING ]ThousandEyes' BrowserBot
21
(Failed starting ThousandEyes' BrowserBot)
22
Error: Package: te-browserbot-1.10-1.x86_64 (thousandeyes)
23
Requires: xorg-x11-server-Xvfb
24
You could try using --skip-broken to work around the problem
25
You could try running: rpm -Va --nofiles --nodigest
Copied!
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:
1
yum -y -q install te-browserbot
2
Error: Package: te-browserbot-1.10-1.x86_64 (thousandeyes)
3
Requires: xorg-x11-server-Xvfb
Copied!
After running the installation script, your new Enterprise Agent will contact the ThousandEyes collector to register itself. Agent information is displayed on the Cloud & Enterprise Agents > Agent Settings, 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:
1
[[email protected] ~]$ sudo yum repolist all
2
​
3
Loaded plugins: amazon-id, rhui-lb, search-disabled-repos
4
repo id                                                                          repo name                                                                                status
5
rhui-REGION-client-config-server-7/x86_64                                        Red Hat Update Infrastructure 2.0 Client Configuration Server 7                          enabled:      6
6
rhui-REGION-rhel-server-debug-extras/7Server/x86_64                              Red Hat Enterprise Linux Server 7 Extra Debug (Debug RPMs)                               disabled
7
rhui-REGION-rhel-server-debug-optional/7Server/x86_64                            Red Hat Enterprise Linux Server 7 Optional Debug (Debug RPMs)                            disabled
8
rhui-REGION-rhel-server-debug-rh-common/7Server/x86_64                           Red Hat Enterprise Linux Server 7 RH Common Debug (Debug RPMs)                           disabled
9
rhui-REGION-rhel-server-debug-rhscl/7Server/x86_64                               Red Hat Enterprise Linux Server 7 RHSCL Debug (Debug RPMs)                               disabled
10
rhui-REGION-rhel-server-debug-supplementary/7Server/x86_64                       Red Hat Enterprise Linux Server 7 Supplementary Debug (Debug RPMs)                       disabled
11
rhui-REGION-rhel-server-extras/7Server/x86_64                                    Red Hat Enterprise Linux Server 7 Extra(RPMs)                                            disabled
12
rhui-REGION-rhel-server-optional/7Server/x86_64                                  Red Hat Enterprise Linux Server 7 Optional (RPMs)                                        disabled
13
rhui-REGION-rhel-server-releases/7Server/x86_64                                  Red Hat Enterprise Linux Server 7 (RPMs)                                                 enabled: 11,067
14
rhui-REGION-rhel-server-releases-debug/7Server/x86_64                            Red Hat Enterprise Linux Server 7 Debug (Debug RPMs)                                     disabled
15
rhui-REGION-rhel-server-releases-source/7Server/x86_64                           Red Hat Enterprise Linux Server 7 (SRPMs)                                                disabled
16
rhui-REGION-rhel-server-rh-common/7Server/x86_64                                 Red Hat Enterprise Linux Server 7 RH Common (RPMs)                                       enabled:    196
17
rhui-REGION-rhel-server-rhscl/7Server/x86_64                                     Red Hat Enterprise Linux Server 7 RHSCL (RPMs)                                           disabled
18
rhui-REGION-rhel-server-source-extras/7Server/x86_64                             Red Hat Enterprise Linux Server 7 Extra (SRPMs)                                          disabled
19
rhui-REGION-rhel-server-source-optional/7Server/x86_64                           Red Hat Enterprise Linux Server 7 Optional (SRPMs)                                       disabled
20
rhui-REGION-rhel-server-source-rh-common/7Server/x86_64                          Red Hat Enterprise Linux Server 7 RH Common (SRPMs)                                      disabled
21
rhui-REGION-rhel-server-source-rhscl/7Server/x86_64                              Red Hat Enterprise Linux Server 7 RHSCL (SRPMs)                                          disabled
22
rhui-REGION-rhel-server-source-supplementary/7Server/x86_64                      Red Hat Enterprise Linux Server 7 Supplementary (SRPMs)                                  disabled
23
rhui-REGION-rhel-server-supplementary/7Server/x86_64                             Red Hat Enterprise Linux Server 7 Supplementary (RPMs)                                   disabled
24
thousandeyes                                                                     ThousandEyes                                                                             enabled:    114
25
repolist: 11,383
Copied!
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.
Solution
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:
1
[[email protected] ~]$ sudo yum-config-manager --enable rhui-REGION-rhel-server-optional
Copied!
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):
1
[[email protected] ~]$ sudo yum-config-manager --enable \*
Copied!
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.
Cleanup
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:
1
[[email protected] ~]$ sudo yum list xorg-x11-server-Xvfb
2
Loaded plugins: amazon-id, rhui-lb, search-disabled-repos
3
Available Packages
4
xorg-x11-server-Xvfb.x86_64        1.17.2-10.el7                    rhui-REGION-rhel-server-optional
Copied!
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:
1
sudo yum-config-manager --disable \*
Copied!
Then, using the information you saved from the first yum repolist all command, enable the repositories which should be enabled:
1
sudo yum-config-manager --enable rhui-REGION-client-config-server-7 --enable rhui-REGION-rhel-server-releases --enable rhui-REGION-rhel-server-rh-common --enable thousandeyes --enable rhui-REGION-rhel-server-optional
Copied!
Then verify the repository statuses are correct by repeating the yum repolist all command.
Further Troubleshooting
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.
Agent Unable to Trace Path to Destination?
What to Do If te-agent Stops Running Due to a VACUUM Error
Last modified 16d ago
Copy link
Contents
Identifying the Problem
Solution
Cleanup
Further Troubleshooting