> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/software-releases-and-backups/toolpack-install-validation-for-centos-5.md). # Toolpack Install Validation for CentOS 5 **Applies to version(s) v2.5 to v2.9** \*WARNING\*: The system must have gone through the \[CentOS 5 Prerequisites Guides]\(../operations/toolpack-prerequisites-for-centos-5.md). If the system followed the CentOS Prerequisites Guides 2-5 Manual page, please follow the \[Validation for the Manual Procedure]\(../../tmedia/installation/README.md) instead. \*WARNING\*: This procedure requires internet access If any of those steps fails, refer to the [CentOS 5 Prerequisites Guides](/tmedia-documentation/other-pages/operations/toolpack-prerequisites-for-centos-5.md) ### Yum Packages * Validation of the following package on the system using yum: yum list installed mysql-devel zlib-devel rubygems ruby-devel libxml2-devel lighttpd lighttpd-fastcgi fcgi mysql-server mysql-connector-odbc ruby unixODBC-devel rubygem-fcgi Output (Depending of the architecture, it is possible that only 1 package version is installed): \[root\@srv-test-install-centos54-x64-1 tblab]# yum list installed mysql-devel zlib-devel rubygems ruby-devel libxml2-devel lighttpd lighttpd-fastcgi fcgi mysql-server mysql-connector-odbc ruby unixODBC-devel rubygem-fcgi Installed Packages fcgi.i386 2.4.0-12.el5 installed fcgi.x86\_64 2.4.0-12.el5 installed libxml2-devel.i386 2.6.26-2.1.2.8.el5\_5.1 installed libxml2-devel.x86\_64 2.6.26-2.1.2.8.el5\_5.1 installed lighttpd.i386 1.4.18-1.rf installed lighttpd.x86\_64 1.4.18-1.rf installed lighttpd-fastcgi.i386 1.4.18-1.rf installed lighttpd-fastcgi.x86\_64 1.4.18-1.rf installed mysql-connector-odbc.i386 5.1.5r1144-8.el5 installed mysql-connector-odbc.x86\_64 5.1.5r1144-8.el5 installed mysql-devel.i386 5.1.47-5.el5 installed mysql-devel.x86\_64 5.1.47-5.el5 installed mysql-server.x86\_64 5.1.47-5.el5 installed ruby.i386 1.8.7.299-4.el5 installed ruby.x86\_64 1.8.7.299-4.el5 installed ruby-devel.i386 1.8.7.299-4.el5 installed ruby-devel.x86\_64 1.8.7.299-4.el5 installed rubygem-fcgi.x86\_64 0.8.7-1.el5 installed rubygems.noarch 1.3.7-1.el5 installed unixODBC-devel.i386 2.2.11-7.1 installed unixODBC-devel.x86\_64 2.2.11-7.1 installed zlib-devel.i386 1.2.3-4 installed zlib-devel.x86\_64 1.2.3-4 installed \[root\@srv-test-install-centos54-x64-1 tblab]# **NOTE**: If the version of 1 or more packages doesn't match, please update your system using the command: ``` yum clean metadata yum update ``` #### lighttpd * lighttpd version should be 1.4.18 or higher \[root\@srv-test-install-centos54-x64-1 tblab]# lighttpd -v lighttpd-1.4.18 (ssl) - a light and fast webserver Build-Date: Nov 29 2010 18:05:08 \[root\@srv-test-install-centos54-x64-1 tblab]# #### ruby * ruby version should be 1.8.7 or higher Example: \[root\@srv-test-install-centos4-x64-1 pkg]# ruby --version ruby 1.8.7 (2010-06-23 patchlevel 299) \[x86\_64-linux] \[root\@srv-test-install-centos4-x64-1 pkg]# #### rubygems * rubygems version should be 1.3.7 or higher Example: \[root\@srv-test-install-centos4-x64-1 pkg]# gem --version 1.3.7 \[root\@srv-test-install-centos4-x64-1 pkg]# #### gem Installation * execute the following command: gem list --local > Result should contain: - LOCAL GEMS \*\*\* ``` bundler (1.2.3) fcgi (0.8.7) json (1.7.7) ``` ### ODBC Configuration * Verify that the following file exists: ls -al /usr/lib64/libmyodbc5.so * Verify odbc config file: cat /etc/odbcinst.ini > For 32 bits systems, result should contain: 1. Driver from the MyODBC package 2. Setup from the unixODBC package \[MySQL] <----- This line must NOT start with a '#' Description = ODBC for MySQL Driver = /usr/lib/libmyodbc5.so Setup = /usr/lib/libodbcmyS.so FileUsage = 1 > For 64 bits systems, result should contain: 1. Driver from the MyODBC package 2. Setup from the unixODBC package \[MySQL] <----- This line must NOT start with a '#' Description = ODBC for MySQL Driver = /usr/lib64/libmyodbc5.so Setup = /usr/lib/libodbcmyS.so FileUsage = 1 ### MySQL Configuration * Verify MySQL config file: cat /etc/my.cnf > Result should contain under \[mysqld]: log-bin server-id=''\[UniqueId]'' **Note**: server-id value may vary, but server-id needs to be a non-zero value and unique when using more than one host. * Verify if the server is running service mysqld status > Result: mysqld (pid 5101) is running... #### SELinux Check SELinux status ``` sestatus ``` It should be disabled or in 'permissive' mode. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/software-releases-and-backups/toolpack-install-validation-for-centos-5.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.