Reset Search
 

 
Article

KB40805 - Command to "start services" fails with error "Name could not be resolved"

Printable View
« Go Back

Information

 
Last Modified Date7/2/2018 6:06 PM
Synopsis
This article describes an issue with Pulse One on-premise appliance that occurs during initial configuration where the command to "start services" fails with the error "Name could not be resolved".
Problem or Goal

Using the Pulse One Getting Started Guide 2.0 1649 to perform the initial configuration steps, the command to "start services" results in the following error: 
  
Name could not be resolved

And although the command line output indicates that services have been started, when running the command to check the status of the services, the proxy service is not running.  

This issue applies to Pulse One 2.0 1637.  

 
Cause
If the certificate chain being used to validate the host name of the Pulse One Appliance cannot be verified, this will cause the proxy service to not start.
If the proxy service is not running then the name resolution error will occur.  
Solution

During initial setup it is recommended to upgrade to Pulse One 2.0 1649 (or later) prior to performing the initial configuration step that  involves running the "start services" command.

The procedure to upgrade to Pulse One 2.0 1649 is documented in the Pulse One Appliance 2.0 1637 Getting Started Guide with a link to KB43622 - Pulse One (PSA7000) Setup Guide where the details to upgrade during initial configuration are documented.

To resolve this issue:

  • Verify that the private key for the device certificate is not password-protected when it is imported.  If the private key for the certificate is password-protected the password can be removed with the following command:  (Enter the password when prompted then the password will be removed.)
openssl rsa -in privateKey.pem -out newPrivateKey.pem
  • Make sure the entire certificate chain is found in the ca-bundle--even when using a self-signed certificate.
  • After removing the password for the private key, and/or including any missing certificates in the chain, reimport the ca-bundle using the command 
https ca-bundle
Related Links
Attachment 1 
Created ByNick Christen

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255