VMware Cloud Community
Ales
Contributor
Contributor
Jump to solution

Configuring Log Insight 3.3.2

I deploy Log Insight of OVF template and after start VM. In console VM I see the below

I can't connect this URL - WEB server in not started.

Why the Log Insight appliance reports as VMware vCenter Server Appliance?

pastedImage_2.png

Thank

Ales

Labels (1)
Reply
0 Kudos
1 Solution

Accepted Solutions
mjunek
Contributor
Contributor
Jump to solution

Right, so I think I figured it out.

On first boot, it configures LogInsight, and brings you to the login screen. If you Alt-F2 to the holding screen, it shows VCSA.

If you do ANYTHING at this point, it appears processes stop, and the installation seems to be stuffed.

What needs to happen is just let it sit there at the login screen for some time, after which it then brings up the Log Insight holding screen.

It's still doing some configuration in the background, until it reaches this point.

So hopefully this helps someone in the future who runs into this issue Smiley Happy

M.

View solution in original post

Reply
0 Kudos
6 Replies
sflanders
Commander
Commander
Jump to solution

If you SSH to it what does the login banner say? What size VM did you deploy this as? Can you go to edit settings and post a screenshot? Any chance you downloaded VC on accident?

Hope this helps! === If you find this information useful, please award points for "correct" or "helpful". ===
Reply
0 Kudos
Ales
Contributor
Contributor
Jump to solution

Console  VM - alt F1

pastedImage_0.png

SSH - Network error: Connection refused

ping is function

Deployment is Extra small - vSphere Client - Provisioned Storage 149.92 GB

Ales

Reply
0 Kudos
sflanders
Commander
Commander
Jump to solution

What does "rpm -qa | grep loginsight" return? Does loginsight-support exist? If so can you generate a support bundle and open a support case? If it does not can you still open a support case and upload the contents of /var/log?

Hope this helps! === If you find this information useful, please award points for "correct" or "helpful". ===
Reply
0 Kudos
sflanders
Commander
Commander
Jump to solution

I cannot repro this -- if you deploy the VM again does the same thing happen?

Hope this helps! === If you find this information useful, please award points for "correct" or "helpful". ===
Reply
0 Kudos
mjunek
Contributor
Contributor
Jump to solution

All,

I've just reproduce this in my environment. Deployed 3 new 3.6 VMs, and they have all come to the VCSA start screen. No ports are listening other than RPC (111) and SMTP (localhost only).

I'll try re-deploying one and see what happens.

My other DC has 3.0 VM's upgraded to 3.3 then 3.6, so I didnt see this issue there.

M.

pastedImage_0.png

pastedImage_0.png

Reply
0 Kudos
mjunek
Contributor
Contributor
Jump to solution

Right, so I think I figured it out.

On first boot, it configures LogInsight, and brings you to the login screen. If you Alt-F2 to the holding screen, it shows VCSA.

If you do ANYTHING at this point, it appears processes stop, and the installation seems to be stuffed.

What needs to happen is just let it sit there at the login screen for some time, after which it then brings up the Log Insight holding screen.

It's still doing some configuration in the background, until it reaches this point.

So hopefully this helps someone in the future who runs into this issue Smiley Happy

M.

Reply
0 Kudos