Help:Installing Log Insight in Nested vSphere 5.5 (ESXi 5.5) environment

[RMHiran]

Hello,

I have installed vRealize Log Insight 2.5 ova on a nested ESXi 5.5 host. When the VM was deployed, the IP address on login page on the console was https:///.

To resolve this, I logged in the console and was able to set the root password. Then, I statically assigned IP address in /etc/sysconfig/network/ifcfg-eth0. The output is as shown below -

cat /etc/sysconfig/network/ifcfg-eth0

DEVICE=eth0

BOOTPROTO='static'

STARTMODE='auto'

ONBOOT=yes

TYPE=Ethernet

USERCONTROL='no'

GATEWAY=192.168.19.1

NAMESERVER=8.8.8.8

IPADDR='192.168.19.225'

NETMASK='255.255.255.0'

BROADCAST='192.168.19.255'

Even set dns also

cat /etc/resolv.conf

nameserver 4.2.2.2

nameserver 8.8.8.8

Issue:

I am unable to access web interface of the appliance to configure. How do I resolve this? Are there any logs to check from the console?

I have restarted the VM couple of times. I checked netstat -tulpn and didn't see port 80 or 8080 open. Is there any configuration that I am missing?  I have attached the pictures of the console and web interface error I am getting.

I would really appreciate any kind of help to resolve this.

Thanks,

Radhika

[sflanders]

Network configuration can only be set, and is only supported if set, through OVF properties. When you deploy the VM through the vSphere client, you have the option to specify networking information. If you do not see this option then that means you are deploying straight to ESXi instead of through vCenter Server, which is also not supported.

If the above is not possible, then you can try to set manually through the CLI (like you did) and then run ifconfig to confirm the IP is properly set (if not you need to restart networking) then run "service loginsight restart". Note that on restart of the VM, network setting will likely be lost. I hope this helps!

[RMHiran]

Hi,

I ran 'service loginsight restart' and this is the output I got -

Log Insight did not shutdown cleanly. Cleaning up.

Starting Log Insight...

Error message unavailable.

StartupException(description:com.vmware.loginsight.daemon.LogInsightDaemon$StartupFailedException: Daemon startup failed: Failed to start Logging Server: java.net.SocketException: Invalid argument or cannot assign requested address.)

        at com.vmware.loginsight.daemon.protocol.commands.DaemonCommands$waitUntilStarted_result.read(DaemonCommands.java:5818)

        at com.vmware.loginsight.daemon.protocol.commands.DaemonCommands$Client.recv_waitUntilStarted(DaemonCommands.java:1832)

        at com.vmware.loginsight.daemon.protocol.commands.DaemonCommands$Client.waitUntilStarted(DaemonCommands.java:1808)

        at com.vmware.loginsight.daemon.protocol.commands.DaemonCommands$PooledClient.waitUntilStarted(DaemonCommands.java:1476)

        at com.vmware.loginsight.daemon.protocol.commands.DaemonCommands$ClientStub.waitUntilStarted(DaemonCommands.java:375)

        at com.vmware.loginsight.daemon.protocol.commands.DaemonCommands$ClientStub.waitUntilStarted(DaemonCommands.java:389)

        at com.vmware.loginsight.daemon.DaemonClient.waitUntilStarted(DaemonClient.java:56)

        at com.vmware.loginsight.admintool.LICommandlineAdminTool.startDaemon(LICommandlineAdminTool.java:1287)

        at com.vmware.loginsight.admintool.LICommandlineAdminTool.access$300(LICommandlineAdminTool.java:85)

        at com.vmware.loginsight.admintool.LICommandlineAdminTool$StartTask.process(LICommandlineAdminTool.java:562)

        at com.vmware.loginsight.admintool.LICommandlineAdminTool$StartTask.process(LICommandlineAdminTool.java:539)

        at com.vmware.loginsight.commons.actions.commandline.AbstractCommandLineAction.handleOwnArgs(AbstractCommandLineAction.java:149)

/etc/init.d/loginsight status

daemonNotRunning

Runtime log

/storage/core/loginsight/var/runtime.log

[2015-04-24 18:07:55.623+0000] [main/127.0.0.1 FATAL] [com.vmware.loginsight.daemon.LogInsightDaemon] [Error starting services]

com.vmware.loginsight.daemon.LogInsightDaemon$StartupFailedException: Daemon startup failed: Failed to start Logging Server: java.net.SocketException: Invalid argument or cannot assign requested address.

        at com.vmware.loginsight.daemon.LogInsightDaemon.startService(LogInsightDaemon.java:693)

        at com.vmware.loginsight.daemon.LogInsightDaemon.startAllServices(LogInsightDaemon.java:543)

        at com.vmware.loginsight.daemon.LogInsightDaemon.run(LogInsightDaemon.java:387)

        at com.vmware.loginsight.daemon.LogInsightDaemon.main(LogInsightDaemon.java:834)

[2015-04-24 18:07:55.641+0000] [ActiveMQ ShutdownHook/127.0.0.1 INFO] [org.apache.activemq.broker.BrokerService] [Apache ActiveMQ 5.9.0 (notifications, ID:2-56186-1429898854983-1:1) is shutting down]

[2015-04-24 18:07:55.646+0000] [Thread-11/127.0.0.1 INFO] [com.vmware.loginsight.daemon.notifications.PersistentNotificationQueue] [Notification queue stopped]

[2015-04-24 18:07:55.657+0000] [main/127.0.0.1 INFO] [com.vmware.loginsight.daemon.LogInsightDaemon] [Stopping Tomcat]

[2015-04-24 18:07:55.661+0000] [main/127.0.0.1 INFO] [com.vmware.loginsight.daemon.LogInsightDaemon] [Stopped Tomcat]

[2015-04-24 18:07:55.665+0000] [ActiveMQ ShutdownHook/127.0.0.1 INFO] [org.apache.activemq.broker.TransportConnector] [Connector vm://notifications stopped]

[2015-04-24 18:07:55.694+0000] [ActiveMQ ShutdownHook/127.0.0.1 INFO] [org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl] [JobSchedulerStore:/storage/core/loginsight/cidata/notifications/data/notifications/scheduler stopped]

[2015-04-24 18:07:55.697+0000] [ActiveMQ ShutdownHook/127.0.0.1 INFO] [org.apache.activemq.store.kahadb.plist.PListStoreImpl] [PListStore:[/storage/core/loginsight/cidata/notifications/data/notifications/tmp_storage] stopped]

[2015-04-24 18:07:55.697+0000] [ActiveMQ ShutdownHook/127.0.0.1 INFO] [org.apache.activemq.store.kahadb.KahaDBStore] [Stopping async queue tasks]

[2015-04-24 18:07:55.697+0000] [ActiveMQ ShutdownHook/127.0.0.1 INFO] [org.apache.activemq.store.kahadb.KahaDBStore] [Stopping async topic tasks]

[2015-04-24 18:07:55.697+0000] [ActiveMQ ShutdownHook/127.0.0.1 INFO] [org.apache.activemq.store.kahadb.KahaDBStore] [Stopped KahaDB]

[2015-04-24 18:07:55.945+0000] [ActiveMQ ShutdownHook/127.0.0.1 INFO] [org.apache.activemq.broker.BrokerService] [Apache ActiveMQ 5.9.0 (notifications, ID:2-56186-1429898854983-1:1) uptime 26.172 seconds]

[2015-04-24 18:07:55.945+0000] [ActiveMQ ShutdownHook/127.0.0.1 INFO] [org.apache.activemq.broker.BrokerService] [Apache ActiveMQ 5.9.0 (notifications, ID:2-56186-1429898854983-1:1) is shutdown]

How I fix this? Thanks for your help.

[sflanders]

I have not seen the exception before. I would guess it is a network configuration issue. Perhaps restart the VM?

[RMHiran]

I have restarted the VM couple of times and it hasn't helped. I have other appliances like Palo Alto Networks firewall VM and other instances running perfectly fine.

[sflanders]

We run LI internally nested without issue so I would guess it is something environmental. I would suggest you opening a support case with VMware and upload a support bundle as it should have details of the issue.