NSX-V 6.4.11 Controller syslog service fails to start
search cancel

NSX-V 6.4.11 Controller syslog service fails to start

book

Article ID: 307343

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Syslog messages are not exported from the Controller to the configured syslog server
     
  • Controllers running NSX-V 6.4.11


Environment

VMware NSX Data Center for vSphere 6.4.x

Cause

The syslog user is missing from within the system causing the rsyslog daemon failure to initialize.

# systemctl status rsyslog
 rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2021-10-06 08:33:45 UTC; 11h ago
     Docs: man:rsyslogd(8)
           https://www.rsyslog.com/doc/
  Process: 4533 ExecStart=/usr/sbin/rsyslogd -n $RSYSLOGD_PARAMS (code=exited, status=1/FAILURE)
 Main PID: 4533 (code=exited, status=1/FAILURE)

Resolution

This issue is resolved in VMware NSX 6.4.13.

Workaround:
While logged into the Controller as root user run the following:
'useradd syslog; systemctl restart rsyslog'

Additional Information

Impact/Risks:
Syslog messages will not be exported to external configured syslog receivers