------- Comment From [email protected] 2020-09-22 12:42 EDT------- (In reply to comment #12) > Well, some more information is needed before one can start to look at this > more deeply: > - What is the Ubuntu release where this happened? NAME="Ubuntu" VERSION="20.04.1 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.1 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal
> - Was the system up-to-date? yes it is/was at the version provided before > - Which syslog was used? Could you provide instructions to get that info? > - What is the version of the syslog package? (apt-cache policy <package>) Could you provide instructions to get that info? > - When did the last log rotation happened and did it worked? Looks like it happen in September 17th root@ilzlnx4:~# ls -ltr /var/log/syslo* -rw-r----- 1 syslog adm 23708 Aug 21 17:16 /var/log/syslog.7.gz -rw-r----- 1 syslog adm 829189 Aug 24 00:00 /var/log/syslog.6.gz -rw-r----- 1 syslog adm 223641 Aug 25 00:00 /var/log/syslog.5.gz -rw-r----- 1 syslog adm 211875 Aug 25 22:30 /var/log/syslog.4.gz -rw-r----- 1 syslog adm 32440 Aug 28 04:49 /var/log/syslog.3.gz -rw-r----- 1 syslog adm 16991 Sep 15 12:37 /var/log/syslog.2.gz -rw-r----- 1 syslog adm 391793 Sep 17 09:55 /var/log/syslog.1 -rw-r----- 1 syslog adm 0 Sep 18 00:00 /var/log/syslog > - Is there any indication in the logs that the service got stopped (by human > interaction or by tools/application) or crashed? No > - Are there entries in /var/crash? No > - Any indication for problems with systemd? Could you provide instructions to get that info? > - Was this identified more than once (on this or other systems)? Yes, I restarted the syslog service couple of days before and it stop working again ------- Comment From [email protected] 2020-09-22 12:48 EDT------- (In reply to comment #14) > This would usually be handled and written by rsyslog, what is this reporting: > $ systemctl status syslog root@ilzlnx4:~# systemctl status syslog ?? rsyslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-09-15 10:48:09 MST; 6 days ago TriggeredBy: ?? syslog.socket Docs: man:rsyslogd(8) https://www.rsyslog.com/doc/ Main PID: 3344005 (rsyslogd) Tasks: 5 (limit: 38379) Memory: 73.1M CGroup: /system.slice/rsyslog.service ????3344005 /usr/sbin/rsyslogd -n -iNONE Sep 15 10:48:09 ilzlnx4 systemd[1]: Starting System Logging Service... Sep 15 10:48:09 ilzlnx4 rsyslogd[3344005]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2001.0] Sep 15 10:48:09 ilzlnx4 rsyslogd[3344005]: rsyslogd's groupid changed to 110 Sep 15 10:48:09 ilzlnx4 rsyslogd[3344005]: rsyslogd's userid changed to 104 Sep 15 10:48:09 ilzlnx4 rsyslogd[3344005]: [origin software="rsyslogd" swVersion="8.2001.0" x-pid="3344005" x-info="https://www.rsyslog.com";] start Sep 15 10:48:09 ilzlnx4 systemd[1]: Started System Logging Service. Sep 16 00:00:28 ilzlnx4 rsyslogd[3344005]: [origin software="rsyslogd" swVersion="8.2001.0" x-pid="3344005" x-info="https://www.rsyslog.com";] rsyslogd was HUPed Sep 17 09:55:03 ilzlnx4 rsyslogd[3344005]: [origin software="rsyslogd" swVersion="8.2001.0" x-pid="3344005" x-info="https://www.rsyslog.com";] rsyslogd was HUPed Sep 17 09:55:03 ilzlnx4 rsyslogd[3344005]: main Q:Reg: high activity - starting 1 additional worker thread(s), currently 1 active worker threads. [v8.2001.0 try https:> Sep 18 00:00:31 ilzlnx4 rsyslogd[3344005]: [origin software="rsyslogd" swVersion="8.2001.0" x-pid="3344005" x-info="https://www.rsyslog.com";] rsyslogd was HUPed > Also was /etc/rsyslog* modified in any way (please attach the config files) root@ilzlnx4:~# cat /etc/rsyslog.conf # /etc/rsyslog.conf configuration file for rsyslog # # For more information install rsyslog-doc and see # /usr/share/doc/rsyslog-doc/html/configuration/index.html # # Default logging rules can be found in /etc/rsyslog.d/50-default.conf ################# #### MODULES #### ################# module(load="imuxsock") # provides support for local system logging #module(load="immark") # provides --MARK-- message capability # provides UDP syslog reception #module(load="imudp") #input(type="imudp" port="514") # provides TCP syslog reception #module(load="imtcp") #input(type="imtcp" port="514") # provides kernel logging support and enable non-kernel klog messages module(load="imklog" permitnonkernelfacility="on") ########################### #### GLOBAL DIRECTIVES #### ########################### # # Use traditional timestamp format. # To enable high precision timestamps, comment out the following line. # $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat # Filter duplicated messages $RepeatedMsgReduction on # # Set the default permissions for all log files. # $FileOwner syslog $FileGroup adm $FileCreateMode 0640 $DirCreateMode 0755 $Umask 0022 $PrivDropToUser syslog $PrivDropToGroup syslog # # Where to place spool and state files # $WorkDirectory /var/spool/rsyslog # # Include all config files in /etc/rsyslog.d/ # $IncludeConfig /etc/rsyslog.d/*.conf > You showed this case with a tail -f, any chance that it rotated away and > there are new entries in a new /var/log/syslog file? Yes it rotated and the previous one stop logging in Sep 15 root@ilzlnx4:~# ls -ltr /var/log/syslo* -rw-r----- 1 syslog adm 23708 Aug 21 17:16 /var/log/syslog.7.gz -rw-r----- 1 syslog adm 829189 Aug 24 00:00 /var/log/syslog.6.gz -rw-r----- 1 syslog adm 223641 Aug 25 00:00 /var/log/syslog.5.gz -rw-r----- 1 syslog adm 211875 Aug 25 22:30 /var/log/syslog.4.gz -rw-r----- 1 syslog adm 32440 Aug 28 04:49 /var/log/syslog.3.gz -rw-r----- 1 syslog adm 16991 Sep 15 12:37 /var/log/syslog.2.gz -rw-r----- 1 syslog adm 391793 Sep 17 09:55 /var/log/syslog.1 -rw-r----- 1 syslog adm 0 Sep 18 00:00 /var/log/syslog root@ilzlnx4:~# tail /var/log/syslog.1 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664541] sd 3:0:0:2: [sdt] tag#81 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664542] sd 3:0:0:2: [sdt] tag#81 Sense Key : Illegal Request [current] Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664543] sd 3:0:0:2: [sdt] tag#81 Add. Sense: Invalid field in cdb Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664656] sd 4:0:0:2: [sdq] tag#32 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 Sense Key : Illegal Request [current] Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664658] sd 4:0:0:2: [sdq] tag#32 Add. Sense: Invalid field in cdb Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664773] sd 5:0:0:2: [sdaa] tag#48 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664774] sd 5:0:0:2: [sdaa] tag#48 CDB: Inquiry 12 01 c9 00 fe 00 Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664775] sd 5:0:0:2: [sdaa] tag#48 Sense Key : Illegal Request [current] root@ilzlnx4:~# tail /var/log/syslog root@ilzlnx4:~# ------- Comment From [email protected] 2020-09-23 12:27 EDT------- Rebooted the system to get the latest kernel patch in place and the syslog gets restarted working for a moment and then stops again Latest versions in the system: root@ilzlnx4:~# uname -a Linux ilzlnx4 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux root@ilzlnx4:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04.1 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.1 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Latest syslog messages: root@ilzlnx4:~# tail /var/log/syslog root@ilzlnx4:~# root@ilzlnx4:~# tail /var/log/syslog.1 Sep 22 10:27:40 ilzlnx4 slim[1630]: Please consult the The X.Org Foundation support Sep 22 10:27:40 ilzlnx4 slim[1630]: #011 at http://wiki.x.org Sep 22 10:27:40 ilzlnx4 slim[1630]: for help. Sep 22 10:27:40 ilzlnx4 slim[1630]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. Sep 22 10:27:40 ilzlnx4 slim[1630]: (EE) Sep 22 10:27:40 ilzlnx4 slim[1630]: (EE) Server terminated with error (1). Closing log file. Sep 22 10:27:40 ilzlnx4 systemd-udevd[486]: target7:0:0: Process '/bin/sh -c 'echo 20 > /sys/class/scsi_disk/target7:0:0/max_medium_access_timeouts'' failed with exit code 2. Sep 22 10:27:40 ilzlnx4 systemd-udevd[492]: target6:0:0: Process '/bin/sh -c 'echo 20 > /sys/class/scsi_disk/target6:0:0/max_medium_access_timeouts'' failed with exit code 2. Sep 22 10:27:40 ilzlnx4 systemd-udevd[484]: target9:0:0: Process '/bin/sh -c 'echo 20 > /sys/class/scsi_disk/target9:0:0/max_medium_access_timeouts'' failed with exit code 2. Sep 22 10:27:41 ilzlnx4 systemd-udevd[488]: target8:0:0: Process '/bin/sh -c 'echo 20 > /sys/class/scsi_disk/target8:0:0/max_medium_access_timeouts'' failed with exit code 2. Actual date: root@ilzlnx4:~# date Wed 23 Sep 2020 09:19:54 AM MST -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896575 Title: [UBUNTU 20.04] syslog daemon stop running unexpectedly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896575/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
