Troubleshooting "vmsyslog logger lost #### log messages" on ESXi hosts
search cancel

Troubleshooting "vmsyslog logger lost #### log messages" on ESXi hosts

book

Article ID: 433493

calendar_today

Updated On:

Products

VMware vSphere ESX 8.x

Issue/Introduction

This article categorizes the various reasons an ESXi host might report dropped syslog messages.

Dropped syslog messages are not "lost" but are unable to be sent to a syslog aggregator or other destination due to various causes.

Environment

VMware ESXi 8.x

Cause

There are a variety of causes for syslog to drop message sends on ESX.  See the Resolution section for specific articles relevant to your symptoms.

Resolution

  • Network Connectivity:
    • If nc -zv fails to the syslog server from the ESX host, see [406249].
  • Aria Operations / Load Balancer Integration:
    • If logs are being sent to an external VIP and the "Auto-Config" task is enabled, see article [429023].
  • NSX Exporter / Resource Contention:
    • If the environment uses NSX and vmsyslogd-dropped.log shows high volume, see [415811].
  • vSAN Specific Logging:
    • If the environment is vSAN and cmmdsTimeMachineDump is seen in drops, see [374707].

Additional Information

ESXi ホストにおける "vmsyslog logger lost #### log messages" のトラブルシューティング