Home Forums HDP on Linux – Installation Get a blank page for hmc console

This topic contains 14 replies, has 2 voices, and was last updated by  Sasha J 2 years, 1 month ago.

  • Creator
    Topic
  • #6515

    I seem to have hmc installed. I started the service. httpd is reported as running. I stopped iptables.

    But when I enter the url:

    http://localhost.localdomain/hmc/html/index.php

    I get a blank page. Not an error, just an empty page.

    The url http://localhost.localdomain gives me the Apache landing page.

    I believe in the recent Hortonworks webinar, the demo giver was using this quasi FQDN successfully.

    Stuck for now.

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

You must be logged in to reply to this topic.

  • Author
    Replies
  • #6571

    Sasha J
    Moderator

    OK, let us do it again.
    First of all, in your case hostname does not really matter, but as you can imagine, local domain is just something not real. Your choice, use it or not… I usually don’t.
    so, let us say we have hostname as jjscentos64 and the same name returned by both “hostname” and “hostname -f” commands.
    So, our /etc/hosts files contains the following line:
    10.41.5.53 jjscentos64

    Now, do the following (in order):

    service hmc stop
    yum erase hmc puppet (puppet needs to be removed in order to get fresh certificate on the place, referring to the correct node name)
    yum install hmc (this will also install puppet as a dependency and create all needed certificates)
    service hmc start

    When it started, (it will show “Could not reliably determine the server’s fully qualified domain name, using 10.41.5.53 for ServerName”, just ignore this) point your browser to http://10.41.5.53/hmc/html

    If you use “remote” browser and have set hosts file on windows to resolve node name (10.41.5.53 jjscentos64), you can also use http://jjscentos64/hmc/html.

    Please, try and let me know of results.

    Thank you!
    Sasha

    Collapse
    #6570

    I am investigating still. I reverted my hosts file and everything to jjscentos64.localdomain. The hostname command reports jjscentos64.localdomain.

    I then tried to run puppet from the command line and get this:

    puppet kick jjscentos64.localdomain
    Triggering jjscentos64.localdomain
    Host jjscentos64.localdomain failed: hostname not match with the server certificate
    jjscentos64.localdomain finished with exit code 2
    Failed: jjscentos64.localdomain

    So what is the trick to get the right hostname in the certificate?

    How/Can I start over here to try and straighten this out? I can’t believe this is as hard as it is with a 1.0 release!!

    Collapse
    #6569

    And now I am stuck with a “Cluster uninstallation failed” message with no guidance as to how to proceed!

    Now What!!

    Collapse
    #6568

    I did what you suggest and now I see this when I start hmc:

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

    Something is still basically not right!!

    Collapse
    #6567

    OK, I will try that.

    I tried to go ahead and do an install and I get the infamous puppet kick errors.

    Looking at the hmc.log file, the first error I see is:

    [2012:06:29 20:26:16][ERROR][sequentialScriptExecutor][sequentialScriptRunner.php:261][]: Got error while getting hostInfo for jjscentos64.localdomain :Could not find host in DB

    What does this error mean? What DB is meant here?

    If I make the host name changes you recommend, will I be more likely to succeed?

    How can I restart the installation. I tried to “uninstall” and that fails too with puppet kick errors.

    Jim

    Collapse
    #6553

    Sasha J
    Moderator

    Yes.
    It is better to get all the packages from the same repository, otherwise it could be inconsistent.
    Looks like there was a problem with php itself.
    IN any case, good to know you are up and running now.
    By the way, to simplify your own live, you can remove .localdoman from the host name.
    In case you use local (through /etc/hosts) names resolution, you can put

    10.41.5.53 jjscentos64

    to /etc/hosts,

    jjscentos64

    to /etc/sysconfig/network,
    and run “hostname jjscentos64″
    This way you will have FQDN as “jjscentos64″

    Hope this helps.

    Sasha

    Collapse
    #6552

    Page no longer blank!

    Turns out the Atomic repo I had used to get pdsh was screwing me up in odd ways.

    I did this:

    rpm -e atomic-release-1.0-14.el5.art

    to get rid of it after first yum erase-ing hmc and php-common and then after the repository reference was gone, I did the sequence:

    yum install php-pecl-json
    yum install hmc

    successfully which installed some other php bits and then after starting hmc, I get an actual page!

    There should be some warnings in the docs about php sensitivities!!

    Collapse
    #6551

    One more thing.

    Prior to the yum install for hmc, you are supposed to install php-pecl-json.

    Yum tells me this when I try to install it:

    yum install php-pecl-json
    Loaded plugins: fastestmirror
    Loading mirror speeds from cached hostfile
    * atomic: www2.atomicorp.com
    * base: centos.mirror.lstn.net
    * epel: fedora-epel.fastsoft.net
    * extras: mirror.trouble-free.net
    * updates: mirror.san.fastserv.com
    Setting up Install Process
    Package php-pecl-json is obsoleted by php-common, trying to install php-common-5.3.14-6.el5.art.x86_64 instead
    Package php-common-5.3.14-6.el5.art.x86_64 already installed and latest version
    Nothing to do

    I thought this was a benign event when it first occurred, but now I am not so sure. Should I remove the php-common version I have and then install the pecl-json one?

    Jim

    Collapse
    #6549

    OK here you go:
    /etc/hosts from CentOS
    # Do not remove the following line, or various programs
    # that require network functionality will fail.
    # 127.0.0.1 jjscentos64.localdomain jjscentos64
    127.0.0.1 localhost.localdomain localhost
    10.41.5.53 jjscentos64.localdomain jjscentos64
    ::1 localhost6.localdomain6 localhost6

    Hosts file from Windows:

    # localhost name resolution is handled within DNS itself.
    # 127.0.0.1 localhost
    # ::1 localhost
    10.41.5.53 jjscentos64.localdomain jjscentos64

    ifconfig:
    [root@jjscentos64 ~]# ifconfig
    eth0 Link encap:Ethernet HWaddr 00:0C:29:04:25:DA
    inet addr:10.41.5.53 Bcast:10.41.5.255 Mask:255.255.254.0
    inet6 addr: fe80::20c:29ff:fe04:25da/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:3595 errors:0 dropped:0 overruns:0 frame:0
    TX packets:727 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:502382 (490.6 KiB) TX bytes:88398 (86.3 KiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:1676 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1676 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2537527 (2.4 MiB) TX bytes:2537527 (2.4 MiB)

    hmc restart
    service hmc restart
    Shutting down HMC
    Stopping httpd: [ OK ]
    Stopped HMC
    Starting HMC Installer
    Starting httpd: [ OK ]
    Starting HMC

    netstat:

    netstat -a | grep LISTEN
    tcp 0 0 jjscentos64.localdomai:2208 *:* LISTEN
    tcp 0 0 *:sunrpc *:* LISTEN
    tcp 0 0 *:ssh *:* LISTEN
    tcp 0 0 jjscentos64.localdomain:ipp *:* LISTEN
    tcp 0 0 *:952 *:* LISTEN
    tcp 0 0 jjscentos64.localdomai:smtp *:* LISTEN
    tcp 0 0 jjscentos64.localdomai:2207 *:* LISTEN
    tcp 0 0 *:8140 *:* LISTEN
    tcp 0 0 *:http *:* LISTEN
    tcp 0 0 *:ssh *:* LISTEN
    tcp 0 0 *:https *:* LISTEN
    unix 2 [ ACC ] STREAM LISTENING 10458 @/var/run/hald/dbus-P0qGmc6KBt
    unix 2 [ ACC ] STREAM LISTENING 8956 @ISCSIADM_ABSTRACT_NAMESPACE
    unix 2 [ ACC ] STREAM LISTENING 13102 @/tmp/fam-root-
    unix 2 [ ACC ] STREAM LISTENING 14430 /tmp/mapping-jjs
    unix 2 [ ACC ] STREAM LISTENING 9350 /var/run/audispd_events
    unix 2 [ ACC ] STREAM LISTENING 10324 /var/run/sdp
    unix 2 [ ACC ] STREAM LISTENING 8938 @ISCSID_UIP_ABSTRACT_NAMESPACE
    unix 2 [ ACC ] STREAM LISTENING 8370 /var/run/cups/cups.sock
    unix 2 [ ACC ] STREAM LISTENING 10412 /var/run/pcscd.comm
    unix 2 [ ACC ] STREAM LISTENING 10432 /var/run/acpid.socket
    unix 2 [ ACC ] STREAM LISTENING 10457 @/var/run/hald/dbus-zKr27l1kmF
    unix 2 [ ACC ] STREAM LISTENING 16003 /var/run/rubygem-passenger/passenger.1.0.4890/generation-0/socket
    unix 2 [ ACC ] STREAM LISTENING 16007 /var/run/rubygem-passenger/passenger.1.0.4890/generation-0/spawn-server/socket.4895.509554784
    unix 2 [ ACC ] STREAM LISTENING 16024 /var/run/rubygem-passenger/passenger.1.0.4890/generation-0/logging.socket
    unix 2 [ ACC ] STREAM LISTENING 12469 /tmp/.font-unix/fs7100
    unix 2 [ ACC ] STREAM LISTENING 10205 /var/run/dbus/system_bus_socket
    unix 2 [ ACC ] STREAM LISTENING 12923 /tmp/.X11-unix/X0
    unix 2 [ ACC ] STREAM LISTENING 13457 /tmp/ssh-npaQDU4333/agent.4333
    unix 2 [ ACC ] STREAM LISTENING 13524 /tmp/orbit-jjs/linc-1135-0-3f3a07d36a471
    unix 2 [ ACC ] STREAM LISTENING 13533 /tmp/orbit-jjs/linc-10ed-0-237b57c874e5d
    unix 2 [ ACC ] STREAM LISTENING 13733 /tmp/.ICE-unix/4333
    unix 2 [ ACC ] STREAM LISTENING 13742 /tmp/keyring-QK8Qgz/socket
    unix 2 [ ACC ] STREAM LISTENING 13761 /tmp/orbit-jjs/linc-113a-0-18ce8c071bc11
    unix 2 [ ACC ] STREAM LISTENING 13830 /tmp/orbit-jjs/linc-114e-0-308e8988f2445
    unix 2 [ ACC ] STREAM LISTENING 13874 /tmp/orbit-jjs/linc-1152-0-4afc897013508
    unix 2 [ ACC ] STREAM LISTENING 13895 /tmp/orbit-jjs/linc-1154-0-4afc897015b31
    unix 2 [ ACC ] STREAM LISTENING 13926 /tmp/orbit-jjs/linc-115b-0-7a5e073c1a4d5
    unix 2 [ ACC ] STREAM LISTENING 13934 /tmp/orbit-jjs/linc-1156-0-4afc89701ac2d
    unix 2 [ ACC ] STREAM LISTENING 14186 /tmp/orbit-jjs/linc-1181-0-7382c9a04ea90
    unix 2 [ ACC ] STREAM LISTENING 14231 /tmp/orbit-jjs/linc-1166-0-4afc897080339
    unix 2 [ ACC ] STREAM LISTENING 14242 /tmp/orbit-jjs/linc-115d-0-4afc897082b6f
    unix 2 [ ACC ] STREAM LISTENING 14273 /tmp/orbit-jjs/linc-1158-0-6f9bb9c53c80c
    unix 2 [ ACC ] STREAM LISTENING 14319 /tmp/orbit-jjs/linc-118f-0-45136ce8bc6a8
    unix 2 [ ACC ] STREAM LISTENING 14352 /tmp/orbit-jjs/linc-11a7-0-6f1e6639cfee7
    unix 2 [ ACC ] STREAM LISTENING 14385 /tmp/orbit-jjs/linc-11a9-0-6f1e66269e1
    unix 2 [ ACC ] STREAM LISTENING 14411 /tmp/orbit-jjs/linc-1191-0-71af2a4813205
    unix 2 [ ACC ] STREAM LISTENING 12415 /dev/gpmctl
    unix 2 [ ACC ] STREAM LISTENING 14852 /tmp/orbit-jjs/linc-1201-0-32258a57e8696
    unix 2 [ ACC ] STREAM LISTENING 14874 /tmp/orbit-jjs/linc-1203-0-32258a57ecba3
    unix 2 [ ACC ] STREAM LISTENING 14890 /tmp/orbit-jjs/linc-1205-0-32258a57f1ec0
    unix 2 [ ACC ] STREAM LISTENING 14997 /tmp/orbit-jjs/linc-1215-0-23d564beab00f
    unix 2 [ ACC ] STREAM LISTENING 15063 /tmp/orbit-jjs/linc-1233-0-6312a716c4de5
    unix 2 [ ACC ] STREAM LISTENING 16177 /tmp/orbit-jjs/linc-1354-0-51be316af1ca6
    unix 2 [ ACC ] STREAM LISTENING 14440 @/tmp/fam-jjs-
    unix 2 [ ACC ] STREAM LISTENING 12659 /var/run/avahi-daemon/socket
    unix 2 [ ACC ] STREAM LISTENING 13503 @/tmp/dbus-bPuHkw4gND
    unix 2 [ ACC ] STREAM LISTENING 12893 /tmp/.gdm_socket

    That’s what I get

    Collapse
    #6548

    Sasha J
    Moderator

    could you show me your /etc/hosts file from CentOS and hosts file from windows?
    also, please run ifconfig on CentOS and show output.
    Also, please show me output from “service hmc restart” and “netstat -a | grep LISTEN”

    Thank you!
    Sasha

    Collapse
    #6547

    I am running the VM with VMware player on Windows 7 Enterprise 64 bit. At first I was using NAT networking but this did not allow my attempts to connect to the web server running in the VM to succeed.

    So I shut down the VM, changed to bridged networking, and restarted. At least now I can connect to the CentOS Apache server. I can get to the Apache landing page, but using the IP address of the CentOS machine, I can’t get to the hmc server.

    So I figured I was back in FQDN hell and I tried to define an entry in my Windows Hosts file for a name for this machine. But my browser is forced to use a Proxy by corporate policy and so address assignments are ignored from the Hosts file.

    And I don’t see how to add exceptions to the proxy either.

    So still stuck.

    Collapse
    #6546

    Sasha J
    Moderator

    Did you try to access it from remote machine?

    Sasha

    Collapse
    #6545

    On the CentOS 5.8 box I only have Firefox 13 — this is a local install in my home directory. The built-in firefox is 10 something. But local install is overriding access to this.

    Which browser do you suggest?

    Collapse
    #6531

    Sasha J
    Moderator

    Hi James,

    Are you able to try a different browser?

    Sasha

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