Excessive number loglines of payload-type data in nsx-syslog.log file in NSX 4.x and ESXi 8.0
search cancel

Excessive number loglines of payload-type data in nsx-syslog.log file in NSX 4.x and ESXi 8.0

book

Article ID: 376709

calendar_today

Updated On:

Products

VMware NSX VMware vSphere ESXi 8.0

Issue/Introduction

  • Excessive amount of logging data in the nsx-syslog log file on ESXi Hosts with NSX versions 4.x and ESXi versions 8.0 resulting in very frequent log rotation.
  • Above logging data is identifiable by the [+] sign in the log lines

Examples:

2024-07-30T17:12:43.981Z In(182) cfgAgent[2788014]: NSX 2788014 - [nsx@6876 comp="nsx-controller" subcomp="cfgAgent" tid="C0FC9C80" level="info"] Decoder: Received LOG_SWITCH_FIB VTEP old msg ########-####-####-####-############: vtep {
2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: vtep_ip {
2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: ipv4: ##.###.###.##
2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: }
2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: vtep_label {
2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: label: 88065
2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: }
2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: segment_id {
2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: ipv4: ##.###.###.##

2024-07-30T17:12:44.399Z In(182) nestdb-server[2788056]: NSX 2788056 - [nsx@6876 comp="nsx-esx" subcomp="nsx-nestdb" tid="2788056" level="INFO"] ExtractRepeatedDelta (Patch Op): vtep {
2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: self {
2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: op: APPEND
2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: }
2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: }
2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: mac {
2024-07-30T17:12:44.399Z In(182) nestdb-server[2788056]: NSX 2788056 - [nsx@6876 comp="nsx-esx" subcomp="nsx-nestdb" tid="2788056" level="INFO"] ExtractRepeatedDelta (Patch): id {
2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: left: ################
2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: right: #####################
2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: }
2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: vtep {
2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: vtep_ip {

Environment

vSphere ESXi 8.0
NSX 4.x

Cause

Syslog service, vmsyslogd, will break messages into separate lines when it encounters embedded newlines in the log message. This is standard and uniform for all log messages, as embedded newlines are inferred as the need for parts to be printed in separate lines.

This was introduced for vmsyslogd using std::endl in ESXi 8.0 versions - Hence std::endl is translated to "" on ESXi host 7.0 but on ESXi host 8.0 it is changed to a newline resulting in a single log message being broken down into multiple log lines.

Resolution

Issue will be fixed in NSX 4.2.1

There is no workaround for prior NSX versions

Additional Information