This is a quick and dirty one… after upgrading my homelab vCenter to 6.7 I noticed that vCenter stopped sending logs to vRLI… When I logged into the VAMI and headed over to syslog section the error below was occurring when I tried to modify / test the syslog settings…
Error in method invocation _failure() missing 1 required positional argument: 'err'
After sshing into the vCenter…
Rrunning systemctl status rsyslog.service reported the status below…
May 02 12:48:37 vcsa.vMan.ch systemd[1]: rsyslog.service: Unit entered failed state. May 02 12:48:37 vcsa.vMan.ch systemd[1]: rsyslog.service: Failed with result 'start-limit'. May 02 12:48:37 vcsa.vMan.ch systemd[1]: rsyslog.service: Start request repeated too quickly. May 02 12:48:37 vcsa.vMan.ch systemd[1]: Failed to start System Logging Service. -- Subject: Unit rsyslog.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Unit rsyslog.service has failed. -- The result is failed. May 02 12:48:37 vcsa.vMan.ch systemd[1]: syslog.socket: Unit entered failed state. May 02 12:48:37 vcsa.vMan.ch systemd[1]: rsyslog.service: Failed with result 'start-limit'.
After trying to manually restart the rsyslog service, reboot the vCenter etc… it just wouldn’t start…
I manually deleted rsyslog.pid from /var/run with rm -f /var/run/rsyslogd.pid and then systemctl start rsyslog.service to start it back up followed by systemctl status rsyslog.service -l to check the status….
rsyslog.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-05-02 13:24:44 UTC; 1h 15min ago Docs: man:rsyslogd(8) Main PID: 21937 (rsyslogd) Tasks: 12 Memory: 1.5M CPU: 1.127s CGroup: /system.slice/rsyslog.service └─21937 /usr/sbin/rsyslogd -n May 02 13:24:43 vcsa.vMan.ch systemd[1]: Stopped System Logging Service. May 02 13:24:43 vcsa.vMan.ch systemd[1]: Starting System Logging Service… May 02 13:24:44 vcsa.vMan.ch systemd[1]: Started System Logging Service. May 02 13:24:44 vcsa.vMan.ch rsyslogd[21937]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1910.0] May 02 13:24:44 vcsa.vMan.ch rsyslogd[21937]: [origin software="rsyslogd" swVersion="8.1910.0" x-pid="21937" x-info="https://www.rsyslog.com"] start
and woooohooo… bobs your uncle it’s working again!
Hope you found this helpful.
vMan
Today, vMAN, you are a ‘bacon saver’.!!
Had this issue today after upgrading to 6.7 U3.
Thanks for posting.
Pin
Glad it was helpful!
Dude, saved the day ❤
Thanks, glad it was helpful.
sure did help – thanks!