Home Forums HDP on Linux – Installation hmc start fails

This topic contains 5 replies, has 2 voices, and was last updated by  Sasha J 2 years, 4 months ago.

  • Creator
    Topic
  • #6500

    I am following the instructions here:

    From a shell on the main installation host, enter:
    service hmc start
    2. Agree to the Oracle JDK license when asked. You must accept this license to be able to download the necessary JDK from Oracle. The JDK is installed during the deploy phase.
    NOTE: If you already have a local copy of the Oracle JDK v 1.6 update 31 32 and 64-bit bina­ries accessible from the install host, you can skip this and the next step. Use the Miscella­neous section on the Customize Settings in the deployment wizard to provide the path to your binaries.
    3. Agree to let the installer download the JDK binaries.

    I did let the JDK binaries download.

    Then I see:

    Starting HMC Installer [ OK ]
    Starting httpd: Syntax error on line 18 of /etc/httpd/conf.d/puppetmaster.conf:
    SSLCertificateFile: file ‘/var/lib/puppet/ssl/certs/jjscentos64.pem’ does not exist or is empty
    [FAILED]
    Failed to start HMC

    What do I do to correct this error?

    Jim

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

  • Author
    Replies
  • #6505

    Sasha J
    Moderator

    James,
    first, FQDN is a mandatory for Hadoop functionality.
    If you are unable to setup real DNS, please use your /etc/hosts file(s).
    You should not have more than 1 127.0.0.1 lines in /etc/hosts.
    Give some “real” ip to your box and edit your /etc/hosts file to be something like:

    127.0.0.1 localhost.localdomain localhost
    10.10.10.10 jjscentos64

    put same name (jjscentos64) to /etc/sysconfig/network

    this way your FQDN will be jjscentos64 and this will work fine.

    As of pdsh update, why do you want to use it? Please do not update anything.
    Just ignore all updates and restart HMC after you make changes in /etc/hosts

    Collapse
    #6504

    Side note. I have centos updates turned on and I am told that there is an update to pdsh. I did not have pdsh installed initially so I added a reference to the Atomic repo and installed pdsh from there. Now the attempt to update pdsh fails with the message:

    file /usr/lib64/pdsh/sshcmd.so from install of pdsh-2.27-1.el5.rf.x86_64 conflicts with file from package pdsh-rcmd-ssh-2.17-1.el5.art.x86_64

    The latter package is apparently the one currently installed from Atomic.

    So do I need to remove the old pdsh and get the right one? Which repo should I use for pdsh?

    Like I said in another thread, my CentOS skills are rusty.

    Collapse
    #6503

    OK, I fixed the error by adjusting the hosts file to look like this at the beginning:

    127.0.0.1 localhost.localdomain localhost
    127.0.0.1 jjscentos64.localdomain jjscentos64

    Now I do not get the FQDN warning any more.

    Is this the preferred way to correct the issue? What name should I use in hostdetail.txt for this host?

    Collapse
    #6502

    I did some searching and found a thread in another forum. The certificates where created with the name jjscentos64.localdomain and the puppetmaster.conf file had the host names without .localdomain.

    So I edited the puppetmaster conf file to use this suffix for both entries. The start command now works but I see this message:

    service hmc start
    Starting HMC Installer
    Starting httpd: httpd: Could not reliably determine the server’s fully qualified domain name, using 127.0.0.1 for ServerName
    [ OK ]
    Starting HMC

    Can I ignore the warning about FQDN?

    Collapse
    #6501

    Sasha J
    Moderator

    Looks like your SSL certificate was not created correctly on the HMC host…
    Is this the only host you try to setup?
    Please, do the following:
    yum erase hmc
    yum erase puppet

    reboot node, then :
    you install hmc
    this should also install puppet as a prerequisite and SSL certificate will be created when puppet installed.

    Then

    service hmc start

    you should accept license again and then HMC should work.

    Please, try and get back to us.

    Collapse
Viewing 5 replies - 1 through 5 (of 5 total)