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/189657
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 lis
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.
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
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
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 unrelat
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
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 becau
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
** 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
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 tha
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?
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 i
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
** 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
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/sy
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
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:
18 matches
Mail list logo
