Smarts NCM: Vcmaster unable to start services; Services not starting; Error: SSLCertificateFile: file '/opt/smarts-ncm/conf/server.crt' does not exist or is empty
search cancel

Smarts NCM: Vcmaster unable to start services; Services not starting; Error: SSLCertificateFile: file '/opt/smarts-ncm/conf/server.crt' does not exist or is empty

book

Article ID: 331060

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:


Smarts NCM services fail to start, therefore application is not usable.
 

vcmaster command fails to start services.

Following error is seen when command is executed.


[root@ncmserver bin]# service vcmaster start
Starting vcmaster services
Starting httpd: Syntax error on line 114 of /opt/smarts-ncm/conf/httpd.conf:
SSLCertificateFile: file '/opt/smarts-ncm/conf/server.crt' does not exist or is empty
                                                           [FAILED]
[root@ncmserver bin]#     






Environment

VMware Smart Assurance - NCM

Cause

The post upgrade procedure is not executed successfully.


Resolution

Please execute the below steps ( available in the installation guide > post upgrade procedure ) :

Please follow the below steps to resolve this issue :

1. Use the prereq-check.pl script to confirm if the prerequisites are met by the server.
Script is located in the ISO file, at Utils/prereq-check.zip

Add distributed system hosts to the lockbox for remote servers

Use the following steps to add distributed system hosts to the lockbox:

1. On the Application server, go to [Product directory]/bin directory.

2. Source the voyence.conf file

3. Add distributed system hosts to the lockbox using the cstdriver utility:
./cstdriver -lockbox [Product directory]/data/lockb.clb
-passphrase <passphrase> -addHost <FQDN of Database server>

./cstdriver -lockbox [Product directory]/data/lockb.clb
-passphrase <passphrase> -addHost <FQDN of Report advisor Server>

./cstdriver -lockbox [Product directory]/data/lockb.clb
-passphrase <passphrase> -addHost <FQDN of Device server>

4. Go to [Product directory]/data directory.

5. Copy the lockbox file to any directory on each of the distributed system hosts.
For example:

scp lockb.clb Host2_DB_Server:/root/
scp lockb.clb Host3_RA_Server:/root/
scp lockb.clb Host4_Device_Server:/root/ 

Follow these steps to get the certificates from Application server:

1. On a Linux server, run the command
# source /etc/voyence.conf

2. Go to [Product directory]/conf directory.

3. Copy the bundle.p12 certificate file to remote Report server and remote Device server.

For example:
scp bundle.p12 Host3_RA_Server:/root/
scp bundle.p12 Host4_Device_Server:/root/

Moving the files from the correct location from AS to the correct location in the DS will resolve the issue.