Attaching 20 seconds of strace output for my case.
This actually lead me to look at /var/log/unattended-
upgrades/unattended-upgrades-shutdown.log and I Noticed the following:
2024-01-18 15:01:16,996 WARNING - SIGTERM or SIGHUP received, stopping
unattended-upgrades only if it is running
2024-01
** Tags removed: rls-nn-incoming rls-oo-incoming
** Tags added: foundations-bugs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063094
Title:
unattended-upgrades is running forever
To manage notifi
Also, note that out of my three stuck processes, it seems got unstuck.
Can't tell why however.
I also talked about running out of space but I don't think that was the
issue: it was the reason I looked at the machine but it wasn't related
to unattended-upgrades.
--
You received this bug notificat
I have 10 backtraces with python3-dbg installed and therefore more
complete backtraces (but I wouldn't call them very readable). I'm going
to attach them here (.tar.xz archive which extracts in the current
directory).
** Attachment added: "unattended-upgrades-bt.tar.xz"
https://bugs.launchpad.
I'm seeing very different traces. Sorry. :)
I have processes which appear stuck and which have been using more than
11 weeks of CPU time over the past 132 days. No idea if it was in only
one run (I think I looked at CPU time less than 132 days ago, and even
less than 11 weeks ago, so it probably h
Calling "strace" and "perf record" against the process would also help
debugging it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063094
Title:
unattended-upgrades is running forever
To manage no
We're still going to need a couple more snapshots of backtraces - it's
important to check if we ever return from pkgDepCache::MarkInstall()
because I do not see an infinite loop in unattended-upgrades
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I'm seeing that bug as well on a Noble system, the log shows that it
installed an openjdk updates some hours ago, no activity since but it's
burning CPU
trying to attach gdb to the process
0x77fdc49445f1 in ?? () from target:/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
(gdb) bt
#0 0x77fdc4944
** Tags added: rls-oo-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063094
Title:
unattended-upgrades is running forever
To manage notifications about this bug go to:
https://bugs.launchp
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063094
Title:
unattended-upgrades is running forever
To manage notificati
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063094
It also seemed rather unkillable.
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063094
Title:
unattended-upgrades is running forever
To manage notifications about t
12 matches
Mail list logo
