Configuring syslog in VAMI gives error : "Error in method invocation failure() missing 1 required positional argument 'err'"

Products

• VMware vCenter Server

Issue/Introduction

• Configuring syslog in VAMI gives error : "Error in method invocation failure() missing 1 required positional argument 'err'"
• Check for below error in applmgmt.log:
   

2020-05-28T16:53:45.306 [26119]ERROR:vmware.vapi.provider.local:Error in invoking com.vmware.appliance.logging.forwarding in set - _failure() missing 1 required positional argument: 'err'
Traceback (most recent call last):
TypeError: _failure() missing 1 required positional argument: 'err'

 

Environment

VMware vCenter Server Appliance 6.7.x

Cause

 rsyslog.service not having an updated version of the service in VMware vCenter Server Appliance 6.7 U3. 

Resolution

1. Check the syslog service status and see the active state.
   
   systemctl status syslog
   
   ● rsyslog.service - System Logging Service
   Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Thu 2020-05-28 17:06:44 UTC; 4min 28s ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
  Process: 16821 ExecStart=/usr/sbin/rsyslogd -n $RSYSLOGD_PARAMS (code=exited, status=1/FAILURE)
 Main PID: 16821 (code=exited, status=1/FAILURE)
May 28 17:06:44 ustxhouvcsa.hcch.com systemd[1]: rsyslog.service: Failed with result 'exit-code'.
May 28 17:06:44 ustxhouvcsa.hcch.com systemd[1]: rsyslog.service: Service hold-off time over, scheduling restart.
May 28 17:06:44 ustxhouvcsa.hcch.com systemd[1]: Stopped System Logging Service.
May 28 17:06:44 ustxhouvcsa.hcch.com systemd[1]: rsyslog.service: Start request repeated too quickly.
May 28 17:06:44 ustxhouvcsa.hcch.com systemd[1]: Failed to start System Logging Service.
May 28 17:06:44 ustxhouvcsa.hcch.com systemd[1]: rsyslog.service: Unit entered failed state.
May 28 17:06:44 ustxhouvcsa.hcch.com systemd[1]: rsyslog.service: Failed with result 'start-limit'.
   
   
2.  If the active state is failed check for a stale pid for rsyslog.
   
   
   1. Check for pid file
      
      ls -l /var/run/

-rw-r--r-- 1 root       root         0 Mar  9 16:19 rsyslogd.pid
      
      
   2.  Move the stale rsyslogd.pid to /tmp
      
       mv rsyslogd.pid /tmp/ryslogd.pid
      
      
3.  Start the syslog service again
   
   systemctl start syslog
   
   
   
4. Check the status again and validate the active status.
   
   systemctl status syslog

● rsyslog.service - System Logging Service
   Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-05-28 17:15:39 UTC; 20s ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
 Main PID: 30269 (rsyslogd)
    Tasks: 12
   Memory: 6.5M
      CPU: 47ms
   CGroup: /system.slice/rsyslog.service
           └─30269 /usr/sbin/rsyslogd -n
   
   
   
5.  Retry to configure syslog in VAMI.