I think this bug should be followed up with a change to retain=3 on
Ubuntu servers.
** Changed in: snapd (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948995
** Summary changed:
- Bcache bypasse writeback on caching device with fragmentation
+ Bcache bypass writeback on caching device with fragmentation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirm I got it working at first boot on azure with
systemd-245.4-4ubuntu3.4
```
ubuntu@machine-3:~$ sudo networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 etherroutableconfigured
2 links listed.
ubuntu@machine-3:~$ sudo apt update
Sadly, the journalctl logs don't go back that far now.
It failed on a baremetal server, not a cloud.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904549
Title:
MTU is not set on vlan interface
Ack !
I'll check with Launchpad team then, I think they would probably prefer
to wait for the -updates indeed.
Thanks again for your work dans Dan's.
Cheers,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Matthew, sorry for the lack of response.
I'll check with Launchpad people if we can justify a reboot of the
server soon and will keep you posted !
Regards,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
I don't need it on bond-manlan for sure (MTU 1500 on this one and its VLANs),
but I read in several place that setting MTU on the bond would also set it on
interface members.
And that indeed worked correctly.
As I said, I think the issue is definitely more in the udevd/networkd
part
Thanks for the explanation.
I confirm that the workaround using "sytemctl restart systemd-udev-
trigger && systemctl restart systemd-networkd" does the trick.
@Dan Watkins : did you do some specific thing to reproduce the issue on
your local VM ? It would be interesting to see the whole logs
Here is a pastebin of the situation and how I tried to resolve this :
https://pastebin.ubuntu.com/p/c6cfKqvBmN/
Unfortunately, the interface stays "unmanaged".
When I check the netplan source
(https://github.com/CanonicalLtd/netplan/blob/master/netplan/cli/commands/apply.py#L128),
it just stops
I tried to run the apport-collect on one of the server we can see the
issue on :
Waiting to hear from Launchpad about your decision...
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
Public bug reported:
Hello,
An upstream bug has been opened on the matter for quite some time now [0].
I can reproduce easily on our production compute node instance, which are
trusty host with xenial hwe kernels (4.15.0-101-generic).
However due to heavy backport and such, doing real tracing
** Description changed:
Hello,
Let's first list my configuration items:
* apache2 2.4.29-1ubuntu4.14
* release: Ubuntu 18.04.5 LTS
Upon reboot, the following message is seen in apache2.service logs:
-- Unit apache2.service has begun starting up.
Oct 14 12:18:32 SERVER
Public bug reported:
Hello,
Let's first list my configuration items:
* apache2 2.4.29-1ubuntu4.14
* release: Ubuntu 18.04.5 LTS
Upon reboot, the following message is seen in apache2.service logs:
-- Unit apache2.service has begun starting up.
Oct 14 12:18:32 SERVER apachectl[3833]: (99)Cannot
The testing of the new kernel looks very promising. We don't observe any
of the latency/IOwait we had before even with the btree_shrinker
enabled.
We'll give it a week probably, but having a backport of those patches
would be fantastic for sure.
--
You received this bug notification because you
Thanks Matthew, we'll try this kernel tomorrow.
I tested it on an openstack instance, the only downside is that it
uninstalls the official 4.15.0-118-generic one.
Regards,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Mauricio,
The tests in [5][6] and [7] have been done with a 44GB memory VM.
This VM usually has 64GB of allocated memory.
The goal was to verify that the load of the whole btree in RAM was not
prevented (like in mca-reap -> down_write_trylock).
All this kernel stuff is rather new to me, so I
** Description changed:
Hello,
In short, we faced an issue with a huge IO wait on a bionic Ubuntu
4.15.0-118.119-generic kernel.
This is the full list of process and the kernel function they were stuck in
[0].
The main issue can probably be summarized by this perf reports
*
** Description changed:
Hello,
In short, we faced an issue with a huge IO wait on a bionic Ubuntu
4.15.0-118.119-generic kernel.
This is the full list of process and the kernel function they were stuck in
[0].
The main issue can probably be summarized by this perf reports
*
Hello Mauricio,
That was also one of the conclusion we reached yesterday.
I followed a wrong lead yesterday, after getting another more detailed
output with klockstat.
I'll update the description of the bug at the end, adding the bits I
found.
The system is not really having memory pressure
** Description changed:
Hello,
In short, we faced an issue with a huge IO wait on a bionic Ubuntu
4.15.0-118.119-generic kernel.
This is the full list of process and the kernel function they were stuck in
[0].
The main issue can probably be summarized by this perf reports
*
Here is a trace of the bcache event related lock in the kernel obtained
with some bpfcc-tools.
klockstat-bpfcc -c bch_ -i 5 -s 3
The trace has been run in parallel with the following command line
echo "Shrinker disabled: $(date)"; sleep 60; echo "Enabling shrinker:
$(date)"; echo 0 | sudo tee
Actually we cannot be sure no. The server didn't have any metrics prior
to few days ago and the issue was already there.
It's worth nothing that few servers have this bcache configuration,
because the cache mode is configured as writethrough and the load is
pretty significant.
So no last "good"
Public bug reported:
Hello,
In short, we faced an issue with a huge IO wait on a bionic Ubuntu
4.15.0-118.119-generic kernel.
This is the full list of process and the kernel function they were stuck in [2].
The main issue can probably be summarized by this perf reports
* first identify that
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355748/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873352
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355742/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873352
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355745/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355749/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873352
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355747/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873352
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355743/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355746/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873352
apport information
** Attachment added: "NonfreeKernelModules.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355741/+files/NonfreeKernelModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355738/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355744/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873352
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355740/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873352
Title:
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355736/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873352
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355737/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873352
Title:
Public bug reported:
Hello,
We recently encountered an issue when trying to stop nova instances.
| Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice:
waiting for tape3e33cb9-d6 to become free. Usage count = 2
When I try to stop manually the qemu process, it errors
"""
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1873352/+attachment/5355739/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873352
Title:
38 matches
Mail list logo
