Comment 2 for bug 1989168

Thanks for the hints. rsyslog is installed and running:

user@s4:~$ sudo apt list rsyslog -a
Listing... Done
rsyslog/focal-updates,focal-security,now 8.2001.0-1ubuntu1.3 amd64 [installed,automatic]
rsyslog/focal 8.2001.0-1ubuntu1 amd64

user@s4:~$ sudo systemctl status rsyslog
● rsyslog.service - System Logging Service
     Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2023-05-21 10:49:01 UTC; 26min ago
TriggeredBy: ● syslog.socket
       Docs: man:rsyslogd(8)
             https://www.rsyslog.com/doc/
   Main PID: 130916 (rsyslogd)
      Tasks: 4 (limit: 9406)
     Memory: 1.6M
     CGroup: /system.slice/rsyslog.service
             └─130916 /usr/sbin/rsyslogd -n -iNONE

May 21 10:49:01 s4 systemd[1]: Starting System Logging Service...
May 21 10:49:01 s4 rsyslogd[130916]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2001.0]
May 21 10:49:01 s4 rsyslogd[130916]: rsyslogd's groupid changed to 110
May 21 10:49:01 s4 systemd[1]: Started System Logging Service.
May 21 10:49:01 s4 rsyslogd[130916]: rsyslogd's userid changed to 104
May 21 10:49:01 s4 rsyslogd[130916]: [origin software="rsyslogd" swVersion="8.2001.0" x-pid="130916" x-info="https://www.rsyslog.com"] start
user@s4:~$

And after adding the user, as in the initial bug report:

user@s4 ~$ id syslog
uid=104(syslog) gid=110(syslog) groups=110(syslog),4(adm),5(tty)