Foglight - Not Starting

All,

I just installed Foglight on CentOS 5.5 x64, 3gigs, i5, plenty of disk space. I took the typical install for the fms_silent.install except I changed that path to /opt.

Fired it up without error and tracing the Management server log it just sits here -

2013-04-23 14:25:27.046 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using HA Pooled Invoker port: 4446

2013-04-23 14:25:27.046 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using HA JNDI UDP Auto Discovery port: 1102

Selinux is off so is the firewall. Any idea why it won't start?

  • I re-ran the installer with the -i console flag and no problems.

    Once again, not starting and sitting at

    2013-04-23 14:59:03.114 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using HA JNDI UDP Auto Discovery port: 1102

  • First of all I believe you need to create a Support case for issues like this so that we have the analysis within our support organization.

    But for this particula one it would also be helpful if you could try to get an fms thread-dump using the fms -t commandline switch.

    This should be possible even during startup and would tell us more about where it stucks.

    Also it would be helpful to start the fms with support enabled and save the output

    fms -D quest.debug=1

    Stefan

  • Hey guys,

    I didn't open a support case since this was a lab/demo machine I was setting up. I did figure it out though, turns out I had a typo in my hosts file. (again, lab envionment, no dns server).

    Thanks for everyone who chimed in.

  • Hi Guys,

    I have the same problem.... What is the solution ???? I'm using a red hat 6.0 without firewall....

    Tks a lot,

    Best Regards,

  • Can you plese post the server log file, we need more details

    Golan

  • Hi Golan, tks for your quick reply...

    Follow the .log

    [root@foglight logs]# tail ManagementServer_2013-11-07_183933_001.log

    2013-11-07 18:39:33.858 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using JNDI RMI port: 1098

    2013-11-07 18:39:33.858 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using JNDI JNP port: 1099

    2013-11-07 18:39:33.858 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using JRMP Invoker port: 4444

    2013-11-07 18:39:33.858 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using Pooled Invoker port: 4445

    2013-11-07 18:39:33.858 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using Unified Invoker port: 4448

    2013-11-07 18:39:33.858 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using HA JNDI RMI port: 1101

    2013-11-07 18:39:33.858 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using HA JNDI JNP port: 1100

    2013-11-07 18:39:33.858 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using HA JRMP Invoker port: 4447

    2013-11-07 18:39:33.859 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using HA Pooled Invoker port: 4446

    2013-11-07 18:39:33.859 INFO    [main] com.quest.nitro.startup.StartupConfigLoader - Forge Server starting up using HA JNDI UDP Auto Discovery port: 1102

    Regards,

  • The lines posted do not give us enough information (they actually look fine).

    Under the Foglight server installation directory (typically /Quest_Software/Foglight/logs ) there are log files, can you please upload the recent log from that directory?

    Thanks

         Golan

  • You are getting this error

    2013-11-07 19:02:32.047 ERROR   [main] com.quest.common.util.HostUtils - Could not determine a valid host name for this machine, using "localhost". It is possible that the host name for this machine has been set to something that is not resolvable via DNS or the local hosts file. Some functionality may be affected.

    java.net.UnknownHostException: foglight: foglight

    Try following the KB article but also make sure you don't just have a typo in the hosts file like dpw had

    https://support.quest.com/SolutionDetail.aspx?id=SOL77544&pr=Foglight

    Knowledge Article 77544

     

    • Title

      FMS will not startup giving a "java.net.UnknownHostException" error

    • Description

      FMS will not start up. The following error appears in the FMS log:

      "ERROR [main] com.quest.common.util.HostUtils - Could not determine a valid host name for this machine, using localhost. Some functionality may be affected.

      java.net.UnknownHostException: XXXXX: XXXXX"

      where XXXX is the hostname of the FMS host.

    • Resolution

      Add an entry for the hostname in the hosts file on the FMS host

    Golan