New install of TDV v8.0 on linux will encounter a "Fatal failure during server startup"
book
Article ID: KB0079943
calendar_today
Updated On:
Products
Versions
TIBCO Data Virtualization
v8.0
Description
Scenario:
A new install of TDV v8.0 on linux fails to boot up. Looking at the cs_server.log, you see these lines in the boot routine: (your actual file path will vary from this example shown)
ERROR [main] 2018-11-22 14:33:30.543 +0000 ClusterModule - [./drillbit.sh, start, -Djavax.net.ssl.keyStore=/opt/TIBCO/TDV_Server_8.0/conf/server/security/cis_server_keystore.jks -Djavax.net.ssl.trustStore=/opt/TIBCO/TDV_Server_8.0/conf/server/security/cis_server_truststore.jks -Djavax.net.ssl.keyStoreAlias=cis_server -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStorePassword=changeit ]: /opt/TIBCO/TDV_Server_8.0/apps/drill/bin/drill-config.sh: line 315: lsb_release: command not found
Followed by:
---------------------- SUMMARY -------------------- An internal error has occurred. Cause: [./drillbit.sh, start, -Djavax.net.ssl.keyStore=/opt/TIBCO/TDV_Server_8.0/conf/server/security/cis_server_keystore.jks -Djavax.net.ssl.trustStore=/opt/TIBCO/TDV_Server_8.0/conf/server/security/cis_server_truststore.jks -Djavax.net.ssl.keyStoreAlias=cis_server -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStorePassword=changeit ]: /opt/TIBCO/TDV_Server_8.0/apps/drill/bin/drill-config.sh: line 315: lsb_release: command not found ---------------------------------------------------
Followed by:
ERROR [main] 2018-11-22 14:33.546 +0000 CompositeServerModuleManager - Fatal failure during server startup. ERROR [main] 2018-11-22 14:33.546 +0000 CompositeServerModuleManager - Exiting.
Issue/Introduction
This concerns a new linux requirement for TDV v8.0.
Resolution
The new SQL Parallel Processing feature in TDV v8.0 employs the use of Drillbit. During a server boot, we will validate the linux release by calling the lsb_release command. If that tool has not been installed on your linux system, it will fail and halt our server boot.
You can manually verify your lsb_release status outside of TDV, on the linux command line by manually running this command to see if you get a response. lsb_release -a
An example of a successful response from a linux host:
[root@dv-vdi-x06080 logs]# lsb_release -a LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: CentOS Description: CentOS release 6.6 (Final) Release: 6.6 Codename: Final
If your response is something similar to a "command not found", you will need to install the lsb_release tool on linux before running TDV.
Consult your linux system administrator. Depending on your exact linux system, it may need a cmd such as one of these: "yum install redhat-lsb-core" "sudo yum install lsb_release"