URL Response Probe Fails To Start On Linux Robot
Article ID: 36893
Updated On:
Products
Issue/Introduction
Issue:
URL Response Probe Fails To Start On Linux Robot and produces "max restarts" error in controller log. (Example: "Controller: Max. restarts reached for probe 'url_response' (command = url_response)"). The probe may even turn green in Infrastructure Manager, but not get a port or pid.
Cause:
Determined there was a missing shared library rpm package (such as: compat-libstdc++) (Note - Some recent Linux distributions come with newer versions of the C++ libraries and some probes depend on older libraries.)
Resolution:
Do the following to determine if this is the issue and see what package it is looking for:
1. De-activate url_response probe.
2. From Linux machine, go to the \url_response\ folder on the system and provide the output of the following command (run the url_response binary):
> ldd url_response
3. Review the output for a missing library. Example output:
linux-vdso.so.1 => (0x00007fff87980000)
libdl.so.2 => /lib64/libdl.so.2 (0x00000037cb800000)
libz.so.1 => /usr/lib64/libz.so.1 (0x00000037cc800000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00000037cc000000)
libstdc++.so.5 => not found
libm.so.6 => /lib64/libm.so.6 (0x00000037cbc00000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00000037ce800000)
libc.so.6 => /lib64/libc.so.6 (0x00000037cb400000)
/lib64/ld-linux-x86-64.so.2 (0x00000037cb000000)
In this instance, this is the missing library:
libstdc++.so.5 => not found
4. Research the particular version for your particular Linux version to find a correct install command (Google is effective here). Example:
yum install compat-libstdc++-[particular version... such as 33.x86_64]
5. Run the command and install the package.
With package successfully installed, url_response probe will successfully start.
Additional Information:
Parent case information that may be helpful. Recap:
- ahead of webex customer had set log level to 5 and increased log size for the controller, ensured url_response probe was activated, and restarted controller
- we ssh'd into the server and reviewing the controller.log found this error:
Controller: Process stopped (probe=url_response, pid=10570) RET = 127
- error led us to a case showing this issue and we followed the steps that resolved that case, as follows...
Did the following to check for a missing rpm package, and if missing, determine what package is that it is looking for (expecting compat-libstdc++):
- De-activate url_response probe
- From Linux machine, run the url_response binary i-e
# ./url_response
Researched particular version for particular Linux version and ran this install command:
yum install compat-libstdc++-[particular version... such as 33.x86_64]
With the package installed, the url_response probe successfully started.
Environment
Component:
Feedback
