baber
Expert
Expert

Syslog configuration failed during configure log insight

Jump to solution

Dear all

Hi

after deploy log insight i inser vcenter login info but now get this error

Syslog configuration failed. See http://kb.vmware.com/kb/2003322 for manual configuration. (Details: Client received SOAP Fault from server: A general system error occurred: Internal error

Please see the server log to find more detail regarding exact cause of the failure.)

what is my problem ??????

BR

Please mark helpful or correct if my answer resolved your issue.
1 Solution

Accepted Solutions
baber
Expert
Expert

so thanks the problem has been solved

fill this field : syslog.global.loghost with tcp://hostname:514

hostname means log insight

BR

Please mark helpful or correct if my answer resolved your issue.

View solution in original post

9 Replies
RajeevVCP4
Expert
Expert

It is because of DNS issue you should provide correct FQDN

This blog can help you

ESXi syslog - A general system error occurred: Internal error - SFlanders.net

Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
0 Kudos
baber
Expert
Expert

thanks

but please the link that it say :  http://kb.vmware.com/kb/2003322

in this link nothing say about dns just say have to set syslog

and i have attached pic from syslog option in advance page is that correct ?

Please mark helpful or correct if my answer resolved your issue.
0 Kudos
baber
Expert
Expert

i have attached 2 pic one of them show error that appear and second of that is syslog config (i have create a folder in datastore with name log and change scratchConfig to /vmfs/volumes/58f4f158-840e70d2-14a0-a0d3c1f1f824/logs

now what is problem ?

BR

Please mark helpful or correct if my answer resolved your issue.
0 Kudos
baber
Expert
Expert

please see attach file after login to log insight and click on view details for connect to host chk syslog attached error appear now what do i have to do ?

BR

Babak

Please mark helpful or correct if my answer resolved your issue.
0 Kudos
baber
Expert
Expert

so thanks the problem has been solved

fill this field : syslog.global.loghost with tcp://hostname:514

hostname means log insight

BR

Please mark helpful or correct if my answer resolved your issue.
jkghfjkasdhfjka
VMware Employee
VMware Employee

You might also find that if you already had an ESXi host configured with Log Insight and are redeploying you could run into this issue as well. Simply edit the host configuration for this entry: syslog.global.loghost with tcp://hostname:514 and delete the value and save as blank. Go back into Log Insight and reconfigure the host, success.

NetArcher
VMware Employee
VMware Employee

Experiencing this problem with following environment

vRealize Log Insight Manager : 4.7.1

vCenter : 6.7

vSphere : 6.5

In this case host doesn't accept the change in value of  "Syslog.global.logHost"  , has anybody else seen this issue.

0 Kudos
BrianBurdorf
Contributor
Contributor

I was having same issue, i stood up a new log insight server and was not able to set new or delete old, until i reset logDir to defaults.

0 Kudos
virtume
VMware Employee
VMware Employee

Try configuring Syslog in the ESXi host manually. Run the following commands

esxcli system syslog config set --loghost='tcp://172.20.xxx.xxx:514'
esxcli system syslog reload
nc -z 172.20.xxx.xxx 514

0 Kudos