[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Setting the project entry to Invalid, too. (Can be later re-opened if needed.) ** Changed in: ubuntu-z-systems Status: Incomplete => Invalid -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Due to the current state these won't auto-expire. I agree with the discussion so far, and after half a year without further insights or new ways to attack this I'd even say we close this and if there is anything new that might help it can be re-opened. But until then it will be off the recheck lists. @Frank, I'm closing the Ubuntu task, could you talk to IBM if they agree and close the project task then? ** Changed in: ubuntu Status: Incomplete => Invalid -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
I think we can also set the Ubuntu task to Incomplete for the moment. ** Changed in: ubuntu Status: New => Incomplete -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Waiting for IBM on a decision to create an upstream bug. Hence setting to Incomplete for now (like discussed per chat with IBM). ** Changed in: ubuntu-z-systems Status: Triaged => Incomplete -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Hi! Well, based on what we could see from the logs and the tries and output we asked for, we think that we can't do so much more w/o touching the system. Hence we're asking if it's possible to recreate the situation on a system that allows remote access, so that we can have a direct look at it. Do you think that's possible ? That would have the following two goals: 1. allows to exclude errors/problems based on the current hw setup and env. (especially in case the system with remote access runs in a different env.) 2. it obviously allows a direct debugging by us -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Thanks for all the attachments. This is Rafael from the Ubuntu Server team. I have gone through all the logs and I could find the I/O errors related to disk full (/var/log/syslog cannot be write) but that was a long time ago and I'm assuming this is not the case here. There are 2 (possible unrelated) issues I could see: 1) lots of CDB inquiry SCSI errors: sd 2:0:0:4: [sdj] tag#76 CDB: Inquiry 12 01 c9 00 fe 00 sd 2:0:0:4: [sdj] tag#76 Sense Key : Illegal Request [current] sd 2:0:0:4: [sdj] tag#76 Add. Sense: Invalid field in cdb sd 2:0:0:5: [sdl] tag#65 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK sd 2:0:0:5: [sdl] tag#65 CDB: Inquiry 12 01 c9 00 fe 00 sd 2:0:0:5: [sdl] tag#65 Sense Key : Illegal Request [current] sd 2:0:0:5: [sdl] tag#65 Add. Sense: Invalid field in cdb sd 3:0:0:1: [sdr] tag#108 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK sd 3:0:0:1: [sdr] tag#108 CDB: Inquiry 12 01 c9 00 fe 00 sd 3:0:0:1: [sdr] tag#108 Sense Key : Illegal Request [current] sd 3:0:0:1: [sdr] tag#108 Add. Sense: Invalid field in cdb sd 3:0:0:2: [sdt] tag#96 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK sd 3:0:0:2: [sdt] tag#96 CDB: Inquiry 12 01 c9 00 fe 00 sd 3:0:0:2: [sdt] tag#96 Sense Key : Illegal Request [current] sd 3:0:0:2: [sdt] tag#96 Add. Sense: Invalid field in cdb sd 3:0:0:3: [sdu] tag#103 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK sd 3:0:0:3: [sdu] tag#103 CDB: Inquiry 12 01 c9 00 fe 00 likely because storage server is not accepting those inquiries on non existent LUNs (were they removed from the system ? The storage server admin can tell you why your INQ CDB was denied.. but, since this is an INQ command AND there are no further I/O errors, I think it is safe to consider this as non-fatal and unrelated to this bug as well. 2) I have tried to reproduce the issue locally but was not able to. I'm sorry for the back and forth, if we could reproduce it here it would way faster. With that said, it is unclear to me if have you tried editing "/usr/lib/rsyslog/rsyslog-rotate" and changing: systemctl kill -s HUP rsyslog.service for systemctl restart rsyslog.service to see if this mitigates the issue ? That will help isolate the problem and allow us to know if the problem is related to the HUP signal handling feature in rsyslog (which is responsible for cleaning up opened file descriptors and might be causing this in some situation). By always restarting the service we will do a full initialization of descriptors and could be a good indicator if that is the problem. That is the suggestion right now because from all the log files, the only messages coming out of rsyslog were related to the HUP signal handler. This may also be a "hotfix" if it works, because there are some fixes in between the rsyslog you're using and the latest, one of them being: commit 723f6fdfa Author: John Brooks Date: Wed Jul 3 15:10:30 2019 rsyslogd: Fix race between signals and main loop timeout The main loop sleeps in a select() call for a long interval in order to periodically run housekeeping tasks. The main loop is also responsible for responding to flags set by signal handlers, so this sleeping should be interrupted by signals so that it can check those flags. However, a signal could be delivered between when the flags are checked and when select() is called. In which case the main loop will block for the full interval (currently 10 minutes) before handling the signal. If this occurs, it could take up to 10 minutes for rsyslogd to terminate after a SIGTERM or respond to SIGHUP. Fix this by blocking signals before checking the flags and using pselect() to unblock the signals while waiting. This is recommended by the select(2) manual page to avoid this very issue. Signed-off-by: John Brooks among others. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Hi Mario, would you also be so kind to provide us with a "sos report" and the "dbginfo.sh" output? This should help to shed some more light into this ... -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Hi Mario, would you also be so kind to provide us with a "sos report" and the "dbginfo.sh" output? This should help to shed some more light into this ... And please from one of the iSCSI systems as well as from that 'normal' (zFCP and/or DASD) system. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
So you said that the problem with rsyslogd is not only on two of your iSCSI system, but you had it also on a 'normal' system (with either 'local' DASD and/or zFCP storage), right? I think there is definitely an issue with the (i)SCSI env. due to the several errors in the logs. But if it's on non-iSCSI too, this might not be the root cause for the rsyslogd issue though. I asked server team to look at this too ... -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
** Changed in: ubuntu Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Server Team (canonical-server) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu Status: Incomplete => Triaged ** Changed in: ubuntu Status: Triaged => New ** Changed in: ubuntu-z-systems Status: Incomplete => Triaged -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
The SCSI devices in the logs made me think that this is an environment
with standard zFCP storage - iSCSI is of course d different thing.
Sharing /etc/fstab and some more details about the disk and filesystem layout
could be helpful.
I assume that the second system has a similar configuration than the first one
(again iSCSI)?
I saw that lszdev shows several DASDs - is /var/log is placed on a local
(DASD) disk or on an iSCSI volume?
If the disk/fs for rsyslogd is on iSCSI (especially on sdq or sdaa in
your example) I think this problem is likely a follow-on problem of the
disk issues that are reported:
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]
The sense codes 3 4 and 5 of the driver byte point to:
3 MEDIUM ERROR
4 HARDWARE ERROR
5 ILLEGAL REQUEST
(https://www.t10.org/lists/2sensekey.htm)
Such errors occur in your initial log (bug description) as well as in the
attached rsyslog.debug output.
If you have system with local storage only (e.g. DASD only) I would
assume that you will not face such rsyslogd issues. Can you please try
or check on an existing non-iSCSI system, too?
And btw. did you ran 'multipath -ll' (and maybe 'lvs') when the problem
happened and rsyslogd stopped? Were any failures ('Failed Path' or
'device-mapper: multipath: Failing path') reported?
I at least saw some access timeouts in the logs.
(Just as a side note: this problem is reported on 'Launchpad', the bug
and issue tracking system of Canonical/Ubuntu. In case the problems
occurs on a production system, it's recommended to open a salesforce
case based on an UA account. That would provide dedicated severity
levels and response times.)
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
I just recognized something in your log in comment #10 which concerns me a bit. You seem to have a massive amount of multipath paths in your system - represented (as usual) as scsi disk devices - I can see a sdz and even sdax. Is this real and correct or is it due to a shaky SCSI/zFCP environment? Please can you verify that the output of: lszdev zfcp lszdev zfcp --online sudo multipath -ll really fits exactly to your physical zFCP/SCSI setup of your environment? (and share the output) A shaky disk environment with temporarily unavailable devices or changing or unstable paths 'could' be a reason for rsyslog no longer being able to write to the underlying device. An btw. I also came across this: https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg83837.html We may should consider to ask Steffen Maier to have a look at your (zFCP) environment. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Thanks Mario! I'm cutting this down a bit for readability ... > root@ilzlnx4:~# sudo logrotate --force --verbose /etc/logrotate.conf > ... > rotating pattern: /var/log/syslog > considering log /var/log/syslog > log does not need rotating (log is empty) This seems to happen at a time the process is already broken and the logging dead. Any chance to catch the logrotate that switches it from working to failing if that shows anything different? > ... > root@ilzlnx4:~# logger -e "Test Error" > ... > root@ilzlnx4:~# tail /var/log/syslog > ... > Note that after the journal command also the syslog file was check and it > still empty Yeah that really means it is active but not taking up messages it should take :-/ > - Enable the syslog debugger with the env variables and restarted the service > ... > After reboot and activate the syslog debug mode, the syslog crashed again. > > root@ilzlnx4:~# tail /var/log/syslog > root@ilzlnx4:~# logger "Test Error" > root@ilzlnx4:~# tail /var/log/syslog > > Attaching the debug log file generated: rsyslog.debug The file did not get mirrored/attached in case that was a mail attachment. Could someone get that attached to the bug on launchpad? Also since this again was called a "crash" (I doubt since in the logs before it seemed the PID stayed the same, but if there is a chance) is there a crash file in /var/crash for it? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Ok, but some more thoughts: - Regarding: apt-cache policy rsyslog; rsyslogd -version make sure you're on '8.2001.0-1ubuntu1.1' package level (and not on 8.2001.0-1ubuntu1) $ apt-cache policy rsyslog | grep Installed Installed: 8.2001.0-1ubuntu1.1 (from the logs I can only see 'v8.2001.0' which is reported in both cases - I believe) - with that also make sure the latest logrotate package is installed: $ apt-cache policy logrotate | grep Installed Installed: 3.14.0-4ubuntu3 - Just to double check: did you ran 'systemctl status syslog' at a point where the syslog was no longer working? if not please provide the output of this in case syslog stopped working - Were user, group and/or other permissions changed, check/compare: $ ls -ld /var/log/ drwxrwxr-x 11 root syslog 4096 Sep 22 16:27 /var/log/ $ ls -la /var/log/syslog -rw-r- 1 syslog adm 5598 Sep 29 07:05 /var/log/syslog - Was the rsyslog configuration changed? according to your previousmsg the config looks like the (unchanged) default config (anyway, a quick rsyslog config validation can be done with: rsyslogd -N1) - Do you have selinux installed and enabled ? (/usr/sbin/sestatus) - Did the time (or TZ) of the system changed in anyway? "rsyslog no longer stops receiving messages after system time change" https://bugzilla.redhat.com/show_bug.cgi?id=1088021 - Is someone/something sending signals to rsyslog (in addition to logrotate)? I see msgs like "rsyslogd was HUPed" -- it could just be caused by a normal logrotate, but if not: according to the rsyslogd mane page: "HUPThis lets rsyslogd perform close all open files." - Could you run the following sequence: - systemctl status syslog.service - sudo logrotate --force --verbose /etc/logrotate.conf - logger -e "Test Error" - journalctl --no-pager | grep "Test" Sep 29 06:38:40 s1lp15 ubuntu[206083]: Test Error - systemctl status syslog.service - Potential systemd problems could be found with: grep -i systemd /var/log/syslog - I guess you already checked for syslog unit issues in the journal: journalctl -u syslog.service - If all this will not provide more indications about what might have happened, I guess rsyslog in debug mode could be a next step (https://www.rsyslog.com/doc/v8-stable/troubleshooting/debug.html) ** Bug watch added: Red Hat Bugzilla #1088021 https://bugzilla.redhat.com/show_bug.cgi?id=1088021 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin20041 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
This would usually be handled and written by rsyslog, what is this reporting: $ systemctl status syslog Also was /etc/rsyslog* modified in any way (please attach the config files) 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? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
Well, some more information is needed before one can start to look at this more deeply: - What is the Ubuntu release where this happened? - Was the system up-to-date? - Which syslog was used? - What is the version of the syslog package? (apt-cache policy ) - When did the last log rotation happened and did it worked? - Is there any indication in the logs that the service got stopped (by human interaction or by tools/application) or crashed? - Are there entries in /var/crash? - Any indication for problems with systemd? - Was this identified more than once (on this or other systems)? ** Package changed: linux (Ubuntu) => ubuntu ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu Status: New => Incomplete ** Changed in: ubuntu-z-systems Status: New => Incomplete -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
A quick scan of the Launchpad bugs didn't brought up any bug that are similar to this - not for focal, nor for any other Ubuntu release. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
