CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

Teradata Database on VMWare
Enthusiast

CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

Trying to start from scratch again with a brand new OVA.

 

But tdvm-init still failed to start PDE with the above error.

 

 

Tags (4)

Accepted Solutions
Teradata Employee

Re: CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

So the screen shot you attached shows that you have 29 VMs running on this host. The way you can tell if you are over provisioned is look at each of those 29 VMs and add up  all of the CPUs you see from all 29 images. It shows you have 64 cores, so if you see more than 64 CPUs (adding up the CPUs for each of the 29 images running on this system)  then you are over provisioned. Can you or your admin add up all of the CPUs the 29 images are using?

The picture in the top right corner of your screen shot where it says:

CPU                                   Free 42.65 GHZ
------------------------------------

|XXXXXXXX                      |

------------------------------------

Used: 29.79 GHZ              Capacity 73.44 GHZ

 

This does not tell us how many CPUs are configured and how many are reserved. This just shows us the total CPU  GHZ capacity but not how many are reserved CPUs and how many are available CPUs.

1 ACCEPTED SOLUTION
9 REPLIES 9
Teradata Employee

Re: CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

Hi,

 

You should have a valid license for the deployment, else you will see this error.

Please let know the version of the scripts and ova used for deployment.

 

 

Thanks

Srikanth

Enthusiast

Re: CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

Do I need to reach out to Teradata support to obtain my license? And where do I deploy the license file?

Teradata_Database_DT_16.20.07.01_SLES11_SP3_on_VMware_20180511145757.ova is the OVA

 

How do I find out the version of the scripts?
 

tdc-rebuild is 64949 bytes (Apr 2 12:50) version = 1.5.4
tdvm-init is 97 bytes (Apr 5 12:50)

Tags (1)
Teradata Employee

Re: CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

Hello Eric,

 

I believe you are using developer tier version of TDVM. It doesn't require any license file.

How are you deploying the OVA file? Have you deployed TDVM image using tdc.deploy.exe from VMware vSphere PowerCLI shell?

 

Please share the deployment logs and the property files.

Highlighted
Teradata Employee

Re: CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

In addition to the OVA file itself there is a set of deployment scripts that come in a zip file. The name of that file shows you the version of TDVM you are deploying. For example the name would look something like this: Teradata_Deployer_ET_03.03.00.05.zip

The ET is Enterprise Tier and the version is 03.03.00.05. Other acronyms you might see are DT (Developer Tier), AT (Advanced Tier), BT (Base Tier). If you did not pay then you are probably running the Developer Tier which does not require a license.

 

One common mistake I see is that people try to deploy these systems without reading the "Teradata on VMWare Getting Started Guide" and they simply start the image from VMWare . If you do that then there is a 100% chance the image will not work properly. There is a tdcdeploy.exe script that needs to be run from a Windows PC installed with PowerCLI and the approprite version of Powershell. You must deploy the image to a VCenter 5.5 or higher version (deployment will fail if you do not deploy from the Windows PC directly to a VCenter uisng the tdcdeploy.exe scripts).

 

You can find the manuals at:

https://www.info.teradata.com/doclist.cfm?txtTitle=VMWare&txtProdID=&selDocType=101&selLanguage=109

Then select the manual for the version you are running.

Enthusiast

Re: CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

I will ask the vCenter guy to run tdcdeploy.exe agin.

 

Thanks

Enthusiast

Re: CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

the VM admin ran into weird error during td.deploy.exe

Error: Failed to pre-validate vCPU number, desired vCPU number (2) exceeds the maximum available vCPU number (-27)  on host (dc-a1-esx03.company.biz).

http://knowledge.teradata.com/KCS/id/KCS008223 states:

  • Cause
    This is resource issue on the VMware hardware (the ESXi host) . TDVM has an algorithm that dynamically calculates the number of recommended vCPUs on a given host depending on the resources available. This prevents over-committing of
    virtual resources. (CPU, Memory, Disk..). TDVM requires reserved CPU and memory in order to deploy and run properly. In this case the customer was trying to deploy 6 CPUs, but the ESXi host they were deploying to was already overprovisioned.
  • Solution
    Find another EXSi host to deploy Teradata on or shutdown enough other systems on the ESXi host so that Teradata can reserve the desired number of systems on deployment.

But the host has a lot of CPU available. Even though we downsize the "PhysicalCoresPerTPA" in common.IT.properties.json: from 2 to 1

 

Script Version: 03.02.00.01
Enumerate current working directory!
Please choose a commonITproperties property file:
01) C:\Teradata_Deployer301\Properties\common.IT.properties.json
02) C:\Teradata_Deployer301\Properties\node.IT.properties.json
Read in the commonITproperties file
Enumerate current working directory!
Please choose a nodeITproperties property file:
01) C:\Teradata_Deployer301\Properties\common.IT.properties.json
02) C:\Teradata_Deployer301\Properties\node.IT.properties.json
Read in the nodeITproperties file
commonITproperties file is: C:\Teradata_Deployer301\Properties\common.IT.properties.json
  nodeITproperties file is: C:\Teradata_Deployer301\Properties\node.IT.properties.json

***********************************************************************************************
*
*   9/26/2018 12:49:44 PM   - Pre-validate the properties files
*
***********************************************************************************************
Warning: A Single TPA Node Deployment detected. Bynet Switches are redundant for this deployment and will be ignored.

All TPA ESXi hosts have the following CPU and Memory resources:
CPU Model ( Intel(R) Xeon(R) CPU E5-2698 v3 @ 2.30GHz ) and MemoryMB ( 393039 )
EsxiCPUtotal( 64) EsxiCPUreserved% (0.02) EsxiMemTotal (373949) EsxiMemReserved (19090)

VirtualCores memoryMBPerTPA numpdisks pdiskSize subpools/node amps/subpool pdisks/subpool
2            20480          2         500       2             2            1


Chosen step ( deploy ) requires a password
Please choose the root password you would like to use for your system. If the password has ALREADY BEEN CHANGED in a previous deployment this will be the password that is used. Enter blank twice to skip this and use the default password.

WARNING: Using default credentials is NOT RECOMMENDED. It is advised that they should be changed after deployment.

Please choose the Teradata DBC password you would like to use for your system. Enter blank to skip this step or use the default value

***********************************************************************************************
*
*   9/26/2018 12:50:18 PM   - Confirmation...
*
***********************************************************************************************

The following Virtual Machines will be deployed:
VM         ESXi Host                      vCPU Memory pdiskSize VM Type Template
td-vm01    dc-a1-esx03.company.biz        2    20480  500       tpa     C:\Teradata_Deployer301\Teradata_Database_DT_16.20.07.01_SLES11_SP3_on_VMware_20180511145757.ova
Continuing at user's request!

***********************************************************************************************
*
*   9/26/2018 12:50:30 PM  Pre-validate if VM's can be cloned
*
***********************************************************************************************
9/26/2018 12:50:30 PM Verify that the Virtual Machines can be created:

Confirm the ESXi hosts are available for deployment.

( td-vm01 ) can be deployed

Fetching available Hosts. Checking if VM's requested Hosts are available


Checking if the VM's requested OS Datastore is available

Found datastore checking available space
The ( ltx1-pure01-t1-gen-03 ) has enough space to clone a VM
All of the requested hosts are suitable for VM deployment

***********************************************************************************************
*
*   9/26/2018 12:50:31 PM   - Pre-validate CPU and Memory
*
***********************************************************************************************
Failed to pre-validate vCPU number, desired vCPU number ( 2 ) exceeds the maximum available vCPU number ( -27) on host (dc-a1-esx03.company.biz).

***********************************************************************************************
*
*   9/26/2018 12:50:35 PM   - Pre-Validate virtual switch public
*
***********************************************************************************************
Find the ( public) network ( VM Network ) in the ESXi host ( dc-a1-esx03.company.biz )

All hosts requested are available for ( public) network attachment.

***********************************************************************************************
*
*   9/26/2018 12:50:36 PM   - Pre-Validate virtual switch bynet
*
***********************************************************************************************

bynet network label(s) not given in common properties file, skip to next step.

***********************************************************************************************
*
*   9/26/2018 12:50:36 PM   - Pre-Validate virtual switch cmic
*
***********************************************************************************************

cmic network is not required to be attached in this deployment, skip to next step.

***********************************************************************************************
*
*   9/26/2018 12:50:36 PM   - Pre-Validate virtual switch dsu
*
***********************************************************************************************

dsu network is not required to be attached in this deployment, skip to next step.

***********************************************************************************************
*
*   9/26/2018 12:50:36 PM   - Pre-Validate ESXi Storage
*
***********************************************************************************************
9/26/2018 12:50:37 PM  - Check if there are enough data stores to attach to the VMs...

VM ( td-vm01 ) can have Data-stores successfully attached to it 2 dataStores can be attached.

***********************************************************************************************
*
*   9/26/2018 12:50:37 PM  Initial Pre-Validation Summary
*
***********************************************************************************************

9/26/2018 12:50:37 PM Status of step:
Run: Deployment Script can be run

9/26/2018 12:50:37 PM Status of step:
Error: Failed to pre-validate vCPU number, desired vCPU number (2) exceeds the maximum available vCPU number (-27)  on host (dc-a1-esx03.company.biz).

9/26/2018 12:50:37 PM Status of step:
Run: (public) network attachment Script can be run

9/26/2018 12:50:37 PM Status of step:
Skip: bynet network label(s) not given in common properties file, skip to next step.

9/26/2018 12:50:37 PM Status of step:
Skip: cmic network is not required to be attached in this deployment, skip to next step.

9/26/2018 12:50:37 PM Status of step:
Skip: dsu network is not required to be attached in this deployment, skip to next step.

9/26/2018 12:50:37 PM Status of step:
Run: All VMs can have Data-stores successfully attached to it.

Deployment started  - 9/26/2018 12:49:34 PM
Deployment finished - 9/26/2018 12:50:37 PM

 Can we ignore the vCPU pre-validation error?

Teradata Employee

Re: CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

Based on the error message you posted:

 

Error: Failed to pre-validate vCPU number, desired vCPU number (2) exceeds the maximum available vCPU number (-27)  on host (dc-a1-esx03.company.biz).

 

It appears that you ESXi host is already over provisioned on CPU by 27 CPU's. Teradata requires dedicated CPUs and cannot run on a system where the CPU's are over provisioned. The best option option would be to deploy to a system that is not over provisioned. One other posibilility which is not very pratical would be to stop enough of the current instances so that you have at least 2 available cpus that Teradata can reserve exclusively. Then launch Teradata. Once Teradata is up and unning, then you could start up the other images which would share the remaining CPUs.

Enthusiast

Re: CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

vCenter 2018-09-26.png

The Admin said that we still have plenty of CPU available on this host...

Teradata Employee

Re: CRITICAL: TdatTools: 29003 #startpde(): can't find pdemain

So the screen shot you attached shows that you have 29 VMs running on this host. The way you can tell if you are over provisioned is look at each of those 29 VMs and add up  all of the CPUs you see from all 29 images. It shows you have 64 cores, so if you see more than 64 CPUs (adding up the CPUs for each of the 29 images running on this system)  then you are over provisioned. Can you or your admin add up all of the CPUs the 29 images are using?

The picture in the top right corner of your screen shot where it says:

CPU                                   Free 42.65 GHZ
------------------------------------

|XXXXXXXX                      |

------------------------------------

Used: 29.79 GHZ              Capacity 73.44 GHZ

 

This does not tell us how many CPUs are configured and how many are reserved. This just shows us the total CPU  GHZ capacity but not how many are reserved CPUs and how many are available CPUs.