VMware Cloud Community
camel114222
Contributor
Contributor

i installed log insight but when i Start New Deployment, have some error:Error starting new deployment: java.net.SocketException: Invalid argument or cannot assign requested address

What's problem ?

pastedImage_0.png

0 Kudos
11 Replies
camel114222
Contributor
Contributor

VMware ESXi, 6.7.0, 10764712

VMware vCenter Server Appliance 6.7.0.21000,11726888

0 Kudos
camel114222
Contributor
Contributor

Does anybody have this problem?

0 Kudos
daphnissov
Immortal
Immortal

How did you deploy the appliance? Delete and redeploy it and show your steps.

0 Kudos
GayathriS
Expert
Expert

What version of Log insight you are using ?

Have you used the IP and FQDN provided to this LI server previously to any other machine  or any previous LI deployment ?

As daphnissov​ said remove this completely and start new deployment and check that helps.

regards

Gayathri

0 Kudos
camel114222
Contributor
Contributor

VMware-vRealize-Log-Insight-4.7.1-10752772_OVF10

Through OVF deployment, after importing ovf,

the display will appear as shown in https.

Redeployed several times, still the same error message

0 Kudos
camel114222
Contributor
Contributor

Enter the console, is there a debug or log to help with troubleshooting?

0 Kudos
sk84
Expert
Expert

As mentioned before, please show us a screenshot of your OVA deployment settings so we can see how you configured the appliance. Otherwise we will hardly be able to help you.

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.
0 Kudos
GayathriS
Expert
Expert

Did you resolve this ?

regards

Gayathri

0 Kudos
camel114222
Contributor
Contributor

BaiduShurufa_2019-2-13_10-34-39 - 1.pngBaiduShurufa_2019-2-13_10-36-18 - 2.pngBaiduShurufa_2019-2-13_10-36-45 - 3.pngBaiduShurufa_2019-2-13_10-40-27 - 4.pngBaiduShurufa_2019-2-13_10-42-40 - 5.pngBaiduShurufa_2019-2-13_10-44-32 - 7.png

0 Kudos
camel114222
Contributor
Contributor

In the latest configuration, I did not fill in the hostname and it succeeded.

Thank you for your help!

The reason for this problem is still not clear, if anyone knows, you can tell everyone.

0 Kudos
daphnissov
Immortal
Immortal

The hostname is the FQDN and not short name.

0 Kudos