About the author

Related Articles

14 Comments

  1. 1

    manish

    Can I use the powercli script to update the article 2003127 for the syslog service function?

    Reply
  2. 2

    viktorious

    Of course, no problem! Any reference would be appreciated (if possible) 🙂

    Reply
  3. 3

    Peter

    I’ve just changed to using UDP hoping that will fix the problem. By default it is TCP.

    Reply
  4. 4

    viktorious

    Interesting thought, what are your results Peter?

    Reply
    1. 4.1

      Peter

      I unfortunately found out the same day that it still stops. This is the only syslog client I know of that acts like this. Most just ship out the logs and if the server is down they are lost. I think VMware needs to fix this.

      Reply
  5. 5

    Smock

    I’ve hit this problem too. I’m setting it set up so I ship logs to a CentOS box, but every time I reconfigure the rsyslog config and restart the rsyslog service or reboot the log server, the connection is lost, and I have to reload the syslog config on the vm hosts. This script will save quite a bit of time, but ideally the vm host should poll the syslog server every X seconds or minutes (could be a custom setting in the Syslog.global section). Once setup it should be less of a problem, but it’s a major annoyance at the moment!

    Reply
    1. 5.1

      viktorious

      Hi, also check this post on this subject:
      http://www.viktorious.nl/2012/07/30/esxi-syslogger-problem-with-interrupted-syslog-service-partially-solved/
      This issue is solved for syslog based on UDP.

      Important: You have to explicitly patch you ESXi servers with path ESXi 201207401!

      Reply
    2. 5.2

      Ed

      ESXi 5.0 wants to use tcp for syslog. When you kill and restart your rsyslog service, that connection is lost. Try ‘service rsyslog reload’ instead.

      Reply
      1. 5.2.1

        viktorious

        You can also use UDP for syslog. On top of this VMware solved this issue for UDP, see this article:
        http://www.viktorious.nl/2012/07/30/esxi-syslogger-problem-with-interrupted-syslog-service-partially-solved/

        I have successfully configured ESXi 5.0 syslog with UDP several times and it works like charm.

        Reply
  6. 6

    JustDave

    I am new to scripting, but I am familiar with PowerCLI/vMA. How do I create/run the script you listed above? thanks!

    Reply
    1. 6.1

      viktorious

      You just run the script from your favourite scripting editor!

      Reply
  7. Pingback: Detecting ESXi Remote Syslog Connection Error Using a vCenter Alarm | virtuallyGhetto

  8. 7

    jawed

    is this really working for you guys? I can’t see how it works for you and not for me.
    here is what i am getting this error which I understand is happening because we are not even storing the variable in $cluster and it becomes a null string.

    PowerCLI C:\> foreach ($esxhost in (Get-Cluster -Name $cluster | Get-VMHost )){Write-Host “ESX: $esxhost”$esxcli = Get-EsxCli -VMhost $esxhost $esxcli.system.syslog.reload()}
    Get-Cluster : Cannot validate argument on parameter ‘Name’. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
    At line:1 char:41
    + foreach ($esxhost in (Get-Cluster -Name $cluster | Get-VMHost )){Write-Host “ESX …
    + ~~~~~~~~
    + CategoryInfo : InvalidData: (:) [Get-Cluster], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetCluster

    Reply
    1. 7.1

      viktorious

      Hi, did you put the clustername in $cluster variable?

      Reply

Leave a Reply